Ryan,
Any chance you've got a version of the software where the Schlage sensors work AND the Schlage lock works. Been without my lock for a while now and I'd like to get it reintegrated into my setup.
Thanks
How to get door sensors to work?
- 58 Views
- Last Post 05 December 2013
joe.ak2@gmail.com
posted this
02 December 2012
rscott
posted this
02 December 2012
Have you already associated your USB stick with each sensor?
1. Click sensor
2. Wake it up, then quickly click Associations
3. Find USB stick, wake sensor up, check mark USB stick
4. Hit OK
joe.ak2@gmail.com
posted this
02 December 2012
Ryan,
Tried this earlier too (http://www.incontrolzwave.com/page/Device-Associations.aspx), but the USB controller (Z Stick 2) isn't showing in my device list.... It's also not listed in Hidden Devices either. Occasionally I'll open InControl HA and the USB controller with be there, but soon after it'll disappear. Seems to happen when I reboot.
One note, the sensors seems to be only sporadically sending updates, took like 30 minutes to get the last update.
Joe
joe.ak2@gmail.com
posted this
02 December 2012
Just rebooted and the USB controller still isn't listed. Any ideas for making it show up in the device list?
One more note, after rebooting, when I open up the Properties for my sensor it now says Extended properties are not available for this device.
On a second note, I'd like to move my z stick to another computer that would make it much easier to troubleshoot. Is there something I can do to move the configuration from my current incontrol computer to my laptop?
Thanks
joe.ak2@gmail.com
posted this
02 December 2012
Ok, moved to a different computer and have the usb controller showing. When I associations, I put check boxes in both usb and sensor and close window. Then go back into Associations, no change, no association shows.
Joe
joe.ak2@gmail.com
posted this
03 December 2012
Ryan,
Still no luck with the association. I've tried it everyway I can think of and I can't get any associations to work. I woke up both the sensor and controller and clicked the associations button, put a checkbox in the controller on the sensor, then closed the window (there is no OK button that I'm not seeing, right?) and the same thing for the controller (vice versa). WHen I reopen the associations windows, there checkbox is gone...
Any help?
Thanks
Ryan-Scott
posted this
04 December 2012
Oops... I wrongly assumed that the forum would send me an email when someone replied. Sorry!
It sounds like your USB stick may be showing up consistently now? If not... sometimes a USB stick can be wrongly detected as a DimmerSwitch. If your USB stick is the master controller, look for a device with an id of 1 (by clicking each device and looking at the number at the bottom of the info window). If you find a device, you can rename it to Controller and set it's type to controller.
As far as associations... all I can think of is that the sensor is still sleeping. There are two points where you need to wake it up; one is right when you first click "Associations" and the second time is just before you click the checkbox. If you woke it both times, I have a special tool we can install to try and send the commands manually. Send me a PM for more info.
Ryan
joe.ak2@gmail.com
posted this
04 December 2012
Ryan,
Yes the USB controller shows up consistently now. Had to reinstall on another computer. Once setup, I will try your trick to get it to show up on my home server.
As for the associations, seems that no matter what I do, I can't get the checkbox to stay checked. Here is exactly, what I'm doing:
1. Double click on Sensor A (my name assigned to sensor)
2. Double Click on Controller
3. single click on Sensor A
4. single click on Associations
5. Put a checkbox in Controller
6. Close window
7. Click Associations again and the controller is not checked.
I did notice that "Queued commands" seems to show 0 if I leave it alone for a while, then I'll try to do the above and it will have another number in it. Right now it's 2. At some point this will go back down to 0.
I will send you a PM, as I'd like to get the special tool so I can get these working.
Thanks
Ryan-Scott
posted this
04 December 2012
If the queued command is going up then it's not able to communicate with the sensor. Are you able to get it to wake up before you go into associations and just before you click the checkbox?
joe.ak2@gmail.com
posted this
04 December 2012
Ok, I'm one step closer. By opening up the sensor, I apparently woke it up properly (rather than how I was doing it before) and I see that a the controller checkbox is checked when I click associations on Sensor A now. Should "Sensor A" be checked when I highlight controller and click Associations (it is not and I can't get it to stay checked when closing window)?
Do you have a writeup or a guide on how to associate the sensor with an event?
Joe
Ryan-Scott
posted this
05 December 2012
You only need a one-way association. You are basically telling the sensor who it needs to send reports to. It's normal that you can't get the checkmark to stay when doing it the other way around.
What type of event are you trying to do with your sensor? There are a number of videos on my YouTube page that might be helpful.
joe.ak2@gmail.com
posted this
05 December 2012
Found your youtube videos. Created a scene to turn off front lights, then created a rule that associated the sensor with the scene and would be activated when "Any level change" was true. No love. I can manually activate the scene just fine, but the sensor doesn't activate it. If I try to use On to Off or vice versa, the log shows:
12/4/2012 6:10:03 PM Unrecognized value " entered for Off to On. Expected a value of 'true' or 'false'
12/4/2012 6:06:03 PM Unrecognized value " entered for Off to On. Expected a value of 'true' or 'false'
But no error for any level change. So it looks like it's getting sensor readings (of some sort, don't know what it's reading), but doesn't activate the scene properly.
Ryan-Scott
posted this
05 December 2012
Found your youtube videos. Created a scene to turn off front lights, then created a rule that associated the sensor with the scene and would be activated when "Any level change" was true. No love. I can manually activate the scene just fine, but the sensor doesn't activate it. If I try to use On to Off or vice versa, the log shows:
12/4/2012 6:10:03 PM Unrecognized value " entered for Off to On. Expected a value of 'true' or 'false'
12/4/2012 6:06:03 PM Unrecognized value " entered for Off to On. Expected a value of 'true' or 'false'
But no error for any level change. So it looks like it's getting sensor readings (of some sort, don't know what it's reading), but doesn't activate the scene properly.
Can you put 'false' (without quotes) into the two boxes and tell me if it fixes it? Also, are you seeing the tripped box get changed properly when motion is detected for the sensor device?
joe.ak2@gmail.com
posted this
05 December 2012
This is a window/door sensor, not motion sensor. I bought them for my garage doors, but am testing them on a light switch before installing on the doors with LFM20 relays.
As for setting to false, no errors in the log now when changing state of sensor, but still no change in the lights scene either.
Ryan-Scott
posted this
05 December 2012
This is a window/door sensor, not motion sensor. I bought them for my garage doors, but am testing them on a light switch before installing on the doors with LFM20 relays.
As for setting to false, no errors in the log now when changing state of sensor, but still no change in the lights scene either.
Does the log ever say it was activated? Also, did you mention if the sensor is actively showing as "tripped" when you look at it in the console? Btw, I've got mine set to "BinarySensor."
joe.ak2@gmail.com
posted this
05 December 2012
It's funny that you mention that, no, there is no check in the checkbox in tripped/open when the sensor bar is detached. It is set to binarysensor currently.
The log never says activated.
Is there a log file I can send for troubleshooting purposes?
EDIT: Here is one of my sensors from the output listed at http://www.incontrolzwave.com/category/InControl-Tips.aspx
{"__type":"ZWaveHaDevice:#MLS.HA.DeviceController.Device.ZWave","as":true,"autoToggleOff":false,"autoToggleSeconds":0,"cs":true,"deviceId":"5d0b0026-9146-426b-aff8-941012a22a75","deviceName":"Sensor A","deviceType":6,"displayOrder":0,"et":null,"he":false,"il":false,"lastLevelUpdate":"/Date(1354582110189-0600)/","level":0,"levelPresets":[],"name":"Sensor A","newLevel":null,"newPowerState":null,"newPowerTimerSeconds":null,"nextEventPowerLevel":null,"nextEventPowerOn":null,"nextEventTime":null,"nodeId":11,"pd":false,"providerDeviceId":11,"roomId":null,"sr":[{"label":"%","name":"Battery","value":100}],"st":null,"visible":true},
Ryan-Scott
posted this
05 December 2012
It's funny that you mention that, no, there is no check in the checkbox in tripped/open when the sensor bar is detached. It is set to binarysensor currently.
The log never says activated.
Is there a log file I can send for troubleshooting purposes?
There's a logfile.txt found in your installation folder in your Program Files. Also, you can try to run from a console window to get more details. To do this, go offline, open up a CMD prompt in Administrator mode (right click, run as admin), cd\ to the install folder and then type in "mls.zwave.service.exe /console"
It'll dump quite a bit of output - but in there, you should see a line saying when the sensor reports a state change.
joe.ak2@gmail.com
posted this
05 December 2012
Ryan, I ran the console command and here is the output when I break the sensor bar:
Received update from node 12. Command: SENSORBINARYREPORT. (< sensor="" b="" with="" magnet="">
Received unprocessed command SENSORBINARYREPORT
Received update from node 11. Command: SENSORBINARYREPORT. (< sensor="" a="" with="" magnet="">
Received unprocessed command SENSORBINARYREPORT
Joe
Ryan-Scott
posted this
05 December 2012
Ryan, I ran the console command and here is the output when I break the sensor bar:
Received update from node 12. Command: SENSORBINARYREPORT. (< sensor="" b="" with="" magnet="">
Received unprocessed command SENSORBINARYREPORT
Received update from node 11. Command: SENSORBINARYREPORT. (< sensor="" a="" with="" magnet="">
Received unprocessed command SENSORBINARYREPORT
Joe
I don't recall... do you have a door lock? If you don't (or even if you do), try this version out and let me know if the console log changes: http://www.moonlitzwave.com/incontrolsetup2.115.exe and if the sensor starts to respond.
Just an FYI, the lock won't work in this version; I'm doing some tweaks to the lock code so it's currently broken.
Ryan
joe.ak2@gmail.com
posted this
05 December 2012
I do have a door lock, but am not really using it right now. Will try this out tomorrow and let you know.
Go get some sleep man, didn't mean to keep you working on this all evening!
joe.ak2@gmail.com
posted this
05 December 2012
Ok, just installed that version and here is the output I get on the console when testing sensor magnet:
Received update from node 11. Command: SENSORBINARYREPORT.
ParamDefinition.Name:SensorValue
Received update from node 12. Command: SENSORBINARYREPORT.
ParamDefinition.Name:SensorValue
They do not show as tripped in InControl though...
joe.ak2@gmail.com
posted this
05 December 2012
Something funky is going on.... something happened and they both "tripped/open" checked themselves. Then, the rule that I setup to email me (I removed the turning on of the light switch) sent me a bunch of emails (Sensor A (or) B is activated or turned on). So apparently something in the 2.115 release is definitely on the right track. Seems very close!
One thing of note, around the time they showed tripped/open... I opened up the sensor to pull the battery and the tamper light went off. Is there any chance that the tripped/open checkbox is for the tamper setting and not the sensor magnet? Could there be two types of messages from the sensor?
by the way, the tripped/open is still checked even though they both are closed and the magnets are attached.
Ryan-Scott
posted this
05 December 2012
Here's a version 2.116 with an additional tweak. Again, there is no lock support in this version.
Ryan-Scott
posted this
07 December 2012
Any luck with your sensors in this new version?
joe.ak2@gmail.com
posted this
07 December 2012
You're the man Ryan! The sensors work awesome now!
joe.ak2@gmail.com
posted this
19 December 2012
Ryan,
Any chance you've got a version of the software where the Schlage sensors work AND the Schlage lock works. Been without my lock for a while now and I'd like to get it reintegrated into my setup.
Thanks
Ryan-Scott
posted this
19 December 2012
Exit or relaunch your GUI and you should be prompted to download an update with both items in it. It'll be version 2.119.
Axial-User
posted this
24 December 2012
I am having similar issues with a Schlage door sensor. Mine shows up in Devices and properly indicates tripped/open when my door is open or closed, but if I leave my computer idle for more than a few minutes, ICHA no longer accepts the updates from the sensor.
If I click ICHA offline and then back online, the sensor reports are once again accurate, but only for events that happen within a brief time (~10 minutes) after the stop/start. Once again, an offline/online makes OCHA report an accurate state for the sensor.
I have not been able to make the Associations button become active no matter what I try, it always remains greyed out...
I am using 2.119.4732.24439 Standard Edition on Windows 7.
Thanks for any help you can offer.
Ryan-Scott
posted this
25 December 2012
You need to make sure you are running the beta z-wave controller. You can find it in the tools/options menu.
Let me know how it works once you are switched over to it.
Ryan
Axial-User
posted this
25 December 2012
Thanks Ryan...no love.
After selecting the beta controller option and doing an 'auto configure' I am now able to see the battery percentage of the sensor - so that's cool - but at this point when I trip the sensor open or closed, I can see the sensor flash it's LED but ICHA does not acknowledge the state change at all. I also deleted and re-associated the sensor, but the same behavior persisted. All of my other devices continue (simple non-dimming standardswitches) continue to function just fine.
FWIW - I still cannot select the associations button...
Thanks again - and Merry Christmas!
andy
joe.ak2@gmail.com
posted this
25 December 2012
Andy,
Did you open the sensor when trying to do the associations? Mine wouldn't associate unless I "woke" them up (by opening the sensor and making the LED up constant). Then select associate and check the usb controller. Then close the sensor and it should show tripped/open... Once that was done and I was using the new version that Ryan made, all worked great with all 6 of my Schlage sensors.
Also, mine are setup as binaryswitches....
Thanks
Ryan-Scott
posted this
25 December 2012
Thanks Ryan...no love.
After selecting the beta controller option and doing an 'auto configure' I am now able to see the battery percentage of the sensor - so that's cool - but at this point when I trip the sensor open or closed, I can see the sensor flash it's LED but ICHA does not acknowledge the state change at all. I also deleted and re-associated the sensor, but the same behavior persisted. All of my other devices continue (simple non-dimming standardswitches) continue to function just fine.
FWIW - I still cannot select the associations button...
Thanks again - and Merry Christmas!
andy
Andy,
Can you send me a screen shot showing me your InControl window with the disabled Associations button?
Also, can you verify that it shows the "Standard Edition" in the title bar of the window?
NickTT
posted this
04 December 2013
I am seeing the same issue with the Aeon Labs door sensor. I have them paired and associated and the light on the sensor triggers when open or closed. However, InControl never processes the status change. InControl will update if I tap the Security Tamper Switch though. That's seems the only way to get InControl to read the new status.
Ryan-Scott
posted this
05 December 2013
I am seeing the same issue with the Aeon Labs door sensor. I have them paired and associated and the light on the sensor triggers when open or closed. However, InControl never processes the status change. InControl will update if I tap the Security Tamper Switch though. That's seems the only way to get InControl to read the new status.
There's not much more you can do... making sure the USB stick is checked when you go to the "associations" button is the only key... other than running the "Beta Z-Wave Controller."
You could try to Auto-Configure it and see if that makes a difference. Does it work when you have it within a few inches of your USB stick?
NickTT
posted this
05 December 2013
I think I just had a bad sensor. I switched it out and now everything is working. However, to make sure it was working right off the bat I did the follow:
1) Delete the device from the controller (Even if it's new just to make sure)
2) Add the device to the controller
3) Once the device shows in InControl wake the device back up by tapping the "Tamper\Pair" button and then click Auto Configure in InControl.
After that the door switches worked right away.
