Couldn’t find any real info ‘googling’ and don’t fully understand the Zwave specs…
Does anyone know or can look at the ‘Zwave alliance’ docs and know whether ring alarm individual components work with Zwave natively.
I’m looking to use the alarm keypad only with my aeotec stick within openhab. Ring (Amazon) obviously keep as much to their chest as possible. I can’t see any mention of scenes (ie button presses) or lifelines in the docs, but all the components are Zwave certified. Not too bothered if it’s not in cd Jackson database (should be able to do this myself with a little reading) but don’t want to waste my time if it’s not going to work in the first instance.
I am personally not aware of anyone using Ring devices with OH. In trying to verify they are Z-Wave certified I found this possibly useful link.
Both the current database website and the old one are both down currently. If the devices use command classes not in the binding then development would be needed.
We would need somebody to purchase a device and then create the database entry for it.
So this device is not listed in your database at present and ive no idea whether ill be able to get it to work, looking for your help whether i’m wasting my time or not.
Its meant to be used with the Ring alarm system but is Z-Wave.
I’ve opened this device and tried to do a secure inclusion from the binding, this is what i get:
If its a case of adding it to your database then ill progress with it.
020-12-12 15:19:26.503 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:controller:node22' to inbox.
==> /QPKGs/OpenHab/userdata/logs/events.log <==
2020-12-12 15:19:26.503 [home.event.InboxAddedEvent] - Discovery Result with UID 'zwave:device:controller:node22' has been added.
2020-12-12 15:19:40.937 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zwave:device:controller:node22' has been removed.
2020-12-12 15:19:40.942 [hingStatusInfoChangedEvent] - 'zwave:device:controller:node22' changed from UNINITIALIZED to INITIALIZING
2020-12-12 15:19:40.948 [hingStatusInfoChangedEvent] - 'zwave:device:controller:node22' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2020-12-12 15:19:40.951 [hingStatusInfoChangedEvent] - 'zwave:device:controller:node22' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2020-12-12 15:19:40.951 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:controller:node22' has been updated.
2020-12-12 15:19:40.954 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:controller:node22' has been updated.
2020-12-12 15:19:42.228 [hingStatusInfoChangedEvent] - 'zwave:device:controller:node22' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
==> /QPKGs/OpenHab/userdata/logs/openhab.log <==
2020-12-12 15:19:53.005 [INFO ] [alization.ZWaveNodeInitStageAdvancer] - NODE 22: SECURITY_INC State=FAILED, Reason=GET_SCHEME
==> /QPKGs/OpenHab/userdata/logs/events.log <==
2020-12-12 15:20:09.210 [hingStatusInfoChangedEvent] - 'zwave:device:controller:node22' changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE
==> /QPKGs/OpenHab/userdata/logs/openhab.log <==
2020-12-12 15:20:32.232 [hingStatusInfoChangedEvent] - 'zwave:device:controller:node22' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
==> /QPKGs/OpenHab/userdata/logs/openhab.log <==
Did you follow my advice and request access to the database or do you wish somebody else to try?
If you want somebody else to try we need a copy of the xml file from the zwave directory under userdata. That contains information directly from the device.
If it doesn’t create an xml file it is not fully discovered by the binding. The information in the xml file is used as a basis for the database. It contains information the device is required to provide according to the standard.
yeah just see that have added a ticket.
So once the device is in the database…
its available for all versions of the binding?
I cannot update to 3 (wouldnt want to at present anyway) as im running on a qnap nas and the latest version available for it is 2.5.10.