It’s strange that the xml file showed that this was set correctly, as at least in this log, there is no response from the device to the read requests - they are reported as sent, but not acked, and I don’t see any response to the request. You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
HABmin shows this yellow until the update request is responded to - in theory at that point the data should be confirmed as the same that is in the device. So, on a battery device, when you set the parameter, the binding queues the command, along with an update request - these go into the wakeup queue until the device wakes up. This indicates that the value is not confirmed by the device - you'll normally only see this with battery devices since a powered device will respond almost instantly. When you set a parameter, HABmin will show it with a yellow background. Do we have a chance to find out whether the sensor really accepts it? Maybe there is something going wrong between HABmin and the sensor. I also suspect that the problem lies with this parameter, but no matter what I set it nothing changes. Let me know if you have any hassles with the database files.
It’s something I’ve been meaning to look at but haven’t gotten around to, but it may be that the controller doesn’t support some classes that report this, or maybe the binding nulls it out for some reason… The Z-stick controller should be in the database, but it doesn’t show up properly in the device list since the binding doesn’t fill in all the information in the node class for the controller.
Regarding the other devices, if you have the OH source, then feel free to add the devices to the database and create a pull request. I know the Vesternet site has a zwave guide, but I’ve not read it - it might have this sort of thing (?). To know about associations though, there’s probably some better, user oriented documentation around. Type sds10242 into google and the top hit should be the device specification which may or may not help, but it’s the best I’ve found on the protocol (it may or may not help you though). The docs for zwave are limited since you’re meant to pay a huge amount of money to get the information, but there is some information around if you do a search. I’ve had zwave for over 3 years and I probably picked up things like this on a forum (previously I had the MCV Vera).
Hmm - how did I know about associations? Good question. String ZwaveNode06home_id "Home ID " (gZwaveNode06) items file, I don't know what I could be missing but it looks like to me that openHab just isn't picking up the signals unless you trip the D\W security button. When this is triggered, communication (OPEN\CLOSE event and the ALARM event) data is sent to the controller.ĥ.This is the only time that communication is sent to the controller!! However, this D\W sensor has a Security\Tamper button that can triggered. When triggering the sensor NO communication is sent to the controller ( Aeon Labs Z-Stick S2)Ĥ. openHab shows this device as a BINARY_SENSOR.ģ. D\W sensor is successfully connected to Z-Wave network.Ģ. Here is a quick rundown of what happens:ġ.
I am trying to figure out how to get this sensor, Aeon Labs Aeotec Z-Wave Door\Window sensor to work properly using openHab.