I just made the change to Hubitat from Smartthings. Over all things are going well … learning a lot about Hubitat, but it has only been 6 hours starting the change over and have a lot more to go. Changing devices are time consuming.
One big issue I have run into is my door/window sensors (Aeon ZW120) inclusion as Generic … they do not function correctly. I had a Smartthings version and that worked fine.
I found very little with regards to ZW120. I found one article and it was talking about using a z-wave stick. A little over my head … didn’t give enough info to walk through process.
I hate to replace all my ZW120s.
Does anybody have experience getting them to work?
You have just a single z-wave device? Also, it is much easier to post this as screenshots, rather than take a photograph of your screen using a camera.
While still trying to get it to work I found something that is interesting.
After clicking on "configure" under Commands. It will give you one function on the contact and then it stays at that.
Sensor and Magnet are in a closed position - You click configure and pull them apart then it will report open. It will stay open no matter how many times you put the two parts together. Then you click configure again and put them together and will now report closed and will stay saying closed until configure is pushed again.
There doesn't appear to be a specific driver for this device, (hence the generic driver that was picked) but I wonder what would happen if you tried one of the Aeon specific ones?
This appears to be an issue from people who tried to pair these sensors, from what I saw in a couple older threads.
@jtp10181 you are more well versed in Z-wave than I am. Could you tell by in-clusters or other information why these sensors might not report states? Any other data that might help to track down what is going on? Would your generic Z-wave scanner driver help here?
The motion would report inactive and active when the sensor and the magnet would come together and pulled away. It was constantly working … never missed a beat.
Sorry for the phone screenshots. Was no longer by a computer and wanted to give you what you asked for. Only gave you a couple shots from the log. Need more let me know. Nothing is reported after the one contact it appears to me.
Please make sure you hub is updated, should be 2.4.2.160 platform. You can check in Settings > Hub Details.
Stick to that Generic Contact Sensor driver, the issue is not with the driver, I can see the messages in the debugging but the platform is not parsing them correctly.
Once you are updated, if still not working the next thing I would try is check the Zwave Gateway. On the Z-wave details page in one of your images above it is showing a button "Switch to Zwave JS". If that is still there, DO NOT press it. If you have already switched to Zwave JS then switch back to legacy with the button.
I would like to see a bigger view of the logs from a PC screenshot please.
Also according to your device info you have a DSB29 AEON Labs / Door/Window Sensor Gen2 Z-Wave JS Config DB Browser
I would be curious to see what that parameter 121 is set to. if you want to get more adventurous you could install this custom driver: Super basic Z-Wave parameter tool
Switch over to that, and be ready on the command page. Wake up the device (according to the manual you just press the z-wave button to wake it). Then within ~10s you should run the Get Parameter Report command with value of 121 in the input box. The device should respond back and it will show up in the logs.
You could try and open/close on this driver as well, the state wont work but it will log stuff to debug. Might give me a better ides of what the device is doing. The logs from the generic driver are sort of confusing and since I cannot see the driver source code its hard to determine what it is doing.
