I have got 2 new devices Aeotec ZW120 Door/Window sensor. It is in the device list. But, both are still unkown. In HABmin they are listet without a manufacturer and type-id! I tried to exclude and include the device again. Nothing changed. The controller is also Aeotec.
What can i do know?
Initialise the device - it is currently not known by the binding.
You should wake it up so that it can be discovered.
thanks. Also a tried this several times. Last time i go with the device to the controller and pushed the action button on the device 3 three times. I know this procedure from other devices…
Have you checked to see what is happening from the logs? You’ve not really provided a lot of information, and in general if you are waking up the device, and it’s in range of the controller, then it should be discovered.
oh, sorry. I forgot this task:
2019-06-15 16:45:57.853 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2019-06-15 16:45:59.929 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! Manufacturer data not known.
2019-06-15 16:45:59.939 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:d968db36:node7' to inbox.
2019-06-15 16:45:59.967 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Device discovery could not resolve to a thingType! Manufacturer data not known.
2019-06-15 16:45:59.979 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:d968db36:node8' to inbox.
2019-06-15 16:45:59.944 [home.event.InboxAddedEvent] - Discovery Result with UID 'zwave:device:d968db36:node7' has been added.
2019-06-15 16:45:59.981 [home.event.InboxAddedEvent] - Discovery Result with UID 'zwave:device:d968db36:node8' has been added.
2019-06-15 16:46:23.799 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zwave:device:d968db36:node7' has been removed.
2019-06-15 16:46:23.858 [hingStatusInfoChangedEvent] - 'zwave:device:d968db36:node7' changed from UNINITIALIZED to INITIALIZING
2019-06-15 16:46:24.016 [hingStatusInfoChangedEvent] - 'zwave:device:d968db36:node7' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2019-06-15 16:46:24.041 [hingStatusInfoChangedEvent] - 'zwave:device:d968db36:node7' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2019-06-15 16:46:24.068 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:d968db36:node7' has been updated.
2019-06-15 16:46:24.105 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:d968db36:node7' has been updated.
2019-06-15 16:46:24.131 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:d968db36:node7' has been updated.
2019-06-15 16:46:24.158 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:d968db36:node7' has been updated.
2019-06-15 16:46:24.163 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
2019-06-15 16:46:27.842 [ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.
2019-06-15 16:47:15.606 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zwave:device:d968db36:node8' has been removed.
2019-06-15 16:47:15.694 [hingStatusInfoChangedEvent] - 'zwave:device:d968db36:node8' changed from UNINITIALIZED to INITIALIZING
2019-06-15 16:47:15.732 [hingStatusInfoChangedEvent] - 'zwave:device:d968db36:node8' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2019-06-15 16:47:15.746 [hingStatusInfoChangedEvent] - 'zwave:device:d968db36:node8' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2019-06-15 16:47:15.758 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:d968db36:node8' has been updated.
2019-06-15 16:47:15.763 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:d968db36:node8' has been updated.
2019-06-15 16:47:15.780 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:d968db36:node8' has been updated.
2019-06-15 16:47:46.493 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:d968db36:node8' has been updated.
2019-06-15 16:47:46.499 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
2019-06-15 16:47:46.607 [hingStatusInfoChangedEvent] - 'zwave:device:d968db36:node8' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2019-06-15 16:47:46.616 [hingStatusInfoChangedEvent] - 'zwave:device:d968db36:node8' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2019-06-15 16:47:46.640 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:d968db36:node8' has been updated.
2019-06-15 17:00:16.387 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:d968db36:node7' has been updated.This looks to be the event log, or maybe it’s the openhab log, but without debugging enabled? Either way, it doesn’t have any information on the zwave network that helps here - sorry.
Please take a look at the documentation if you’re unsure about enabling debug level logging.
Many thanks! Now one device is known. The problem with the reinclude was, when i plugged back the controller, it got a new tty-ID and the controller wasn’t really online. After a reboot of the system it is know and listet correctly. So i have to try the procedure with the second device…
thumbs up!!
Many times that puts the device in a mode to join a network. Many devices use a long push on the button to reset.
According to this page, you need to press the button for 20 seconds to reset.
It will require multiple tries at waking the device up. Put your controller in inclusion mode, push the device wake up button, wait a minute or two, repeat
check your device documentation to figure out how to wake the device, don’t reset it,wake it