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
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.
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
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
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?
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
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
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
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
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.
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
joe.ak2@gmail.com
posted this
07 December 2012
You're the man Ryan! The sensors work awesome now!
Ryan-Scott
posted this
07 December 2012
Any luck with your sensors in this new version?
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.
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.
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
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!
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
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
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
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},
