Hello, Sorry to post this here and I do not know how to update the online zwave database myself. There is updated documentation on zooz website for Zooz 4-in-one motion/temperature/humidity/luminance sensor (ZSE40)
Parameter 2 (currently not in orig documentation or in database):
Under the temperature section –
Use Parameter 1 (size 1 byte dec) to switch from Celsius
(value 0x00) to Fahrenheit (value 0x01) scale.
Use Parameter 2 (size 1 byte dec) to set temperature change
to be reported by the sensor. Values from 1 to 50, where
1 stands for 0.1 degree and 50 stands for 5 degrees. Default
set to 1 degree (value 10) – the sensor will report new temperature
value to the controller whenever temperature goes
1 degree up or down
There is a little confusion with this parameter as there are 3 manuals for the device, and two show this parameter, and one doesn’t (I believe in age, it’s the middle one that doesn’t). I’m not sure if that means one is just an ommission, or if there are multiple versions of the firmware.
I guess on average we can probably add this and see if it causes any issues. If it does, we’ll have to find a way to create multiple versions of the device.
I will try and take a look over the next few days - of course anyone with an account on the site can do this
Also is there way I can put this in my local installation to try out? Currently I can’t get the sensor to work. I get lots of errors. First thing first, if I could either test locally the changes or if the db could be updated. That be great…
I am looking at the zwave bindings example for openhab (first one) is how I saw the channel was missing and the alarm channel looks incorrect:
Thank you @chris! I think I figured it out… That area is fine, the basic one needed the channel added. Again sorry just figuring out how all this works. I submitted the changes and requested approval. Thanks again for your patience.
If you’ve compiled your own binding with the updated XML, then you will need to delete the thing, and add it back in. Don’t exclude the device from the network - just delete, click the discovery button again, and it should instantly be rediscovered. Add it back and you should be good to go.
If you’ve not compiled a binding, you’ll need to wait till I update the repo and grab the snapshot. I’ll try and do this before I go to bed so it should be compiled in a few hours time.
Hi Chris,
Its been a while I figure I would give openhab 2 zwave another try. When adding this same device I get that its unknown now.
The device is not in the database. If the device attributes show that this device has a valid manufacturer ID, device ID and type, then this is likely the case (eg. you see a label like “Z-Wave node 1 (0082:6015:020D::2.0)”). Even if the device appears to be in the database, some manufacturers use multiple sets of references for different regions or versions, and your device references may not be in the database. In either case, the database must be updated and you should raise an issue to get this addressed.
Hi Brian,
If this used to work (ie I mean it is recognised), then chances are that the device might need waking up so that it can be configured in OH2 since it is a battery device.
So I did the usually, click the zwave button on the device a bunch of times, made it flash and I watched the controller flash sending and receiving. I read in the manual it uses secure inclusion, so I switched the setting in paper ui on the controller for secure inclusion from entry devices to all. I still can’t get it to not be unknown. Is there some other trick to get it include?
Is there somewhere I can see other than this “0082:6015:020D::2.0” that was in the message? Is that the info it would use to look up in the database?
I’ve installed the Zwave binding via Paper UI and Aeon labs devices are working correctly. The Fibaro FGPB 101 is listed in the current database however it still shows up as unknown device when discovered. I read that it can use different type ID’s etc…
In a previous post you mentioned I should upgrade to the latest Zwave binding snapshot. Is there also the option of just upgrading the Zwave database by downloading the database tar file and extracting to the correct directory?
Hi guys, got a ZooZ ZSE30 water sensor. Pairing worked, but OH is not able to complete initialization. I tried wakeup more than 20 times, devices gets ONLINE, but initialization is not completed (even node xml is not created). I tried the latest SNAPSHOT of the zwave binding with same result.
Searching the internet I found the device xml:
but I’m note sure if the latest binding include that information. Chris’ Device Database has only an entry for the ZSE40, but not for the ZSE30.
@chris: Could you give an info if the zse30 is included in the latest binding?
This XML is not for OH. The database will create the XML for OH - you can’t just use XML files from other software.
Yes - it is.
Looking at the image you posted from HABmin, there is no manufacturer or type/id. This means that the binding has not been able to communicate with the device yet. Normally this is because the device has not been woken up within range of the controller, but if you have done this, then possibly the inclusion has not worked correctly.
I would try excluding the device and adding it back into the network. If that doesn’t work, then you should get a debug log so we can see what is happening.
I found the magic in another manual:
Troubleshooting Tips
If you are unable to include the Z-Wave Water Sensor to your controller, try one of the following:
Bring the sensor closer to your hub or use a hand-held secondary controller to perform inclusion - Once in inclusion mode, press and release the Z-Wave button quickly 6-7 TIMES to ensure the command has gone through
Put your controller in EXCLUSION mode. Press and release the Z-Wave button quickly 3 TIMES, and then try adding the sensor to your network again
You may need to change the device type manually if the sensor is not recognized correctly (email us for more info: ask@getzooz.com)
Pressing the button 7 times and several cycles brought me through the INITIALIZATION process completed. Now it’s up an running and alarms are reported correctly. @chris: thanks for you help