[SOLVED] Zooz ZSE18 Sensor Woes

Add-ons Bindings
,
42

After many times trying to wake it up and failing, I finally realized the proper procedure, well, works but not stated, is to press the button once, then when the light come on press 3 times fast, otherwise it seems to miss the triple press most of the time.

Ira

2 Likes
43

I had not noticed that. Perhaps you’re correct.

After the triple press, the led blinks. I usually triple press again to cancel that.

1 Like
44

For all those coming across this thread later on, I ran into the same problems in 2022 with a Zooz ZSE18 sensor, initially. It seems that the problem is that the device doesn’t really fully complete its association with the controller the first time around.
But, it’s not defective. For me, the device included properly the first time, and then failed to send anything to the controller when motion was detected or the alarm was triggered.

I was finally able to get it to work by doing the following:

  1. Removing it from OpenHAB, and then re-adding it (I did NOT exclude it and include it again).
  2. Initializing the wake-up by pressing the z-wave button once, followed by a triple-press (light will blink rapidly to confirm)
  3. Repeated this wakeup procedure three times over the course of ten minutes before it finally completed its association.

Suddenly, motion events started showing up in the log.
Here’s my (INFO-level) log during this phase:

2022-02-07 11:56:35.726 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:920e03265a:node30' to inbox.
==> /var/log/openhab/events.log <==
2022-02-07 11:56:35.727 [INFO ] [openhab.event.InboxAddedEvent       ] - Discovery Result with UID 'zwave:device:920e03265a:node30' has been added.
2022-02-07 11:56:49.319 [INFO ] [openhab.event.InboxRemovedEvent     ] - Discovery Result with UID 'zwave:device:920e03265a:node30' has been removed.
2022-02-07 11:56:49.344 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:920e03265a:node30' changed from UNINITIALIZED to INITIALIZING
2022-02-07 11:56:49.374 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:920e03265a:node30' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2022-02-07 11:56:49.387 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:920e03265a:node30' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2022-02-07 11:56:49.924 [INFO ] [openhab.event.ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
2022-02-07 11:57:53.230 [INFO ] [openhab.event.ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
2022-02-07 11:57:56.221 [INFO ] [openhab.event.ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
2022-02-07 11:57:56.977 [INFO ] [openhab.event.ConfigStatusInfoEvent ] - ConfigStatusInfo [configStatusMessages=[]]
2022-02-07 11:57:56.993 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'zwave:device:920e03265a:node30' changed from ONLINE to ONLINE: Node initialising: SET_ASSOCIATION
2022-02-07 12:04:29.154 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ZWaveNode030OfficeMotionSensorZooz_BinarySensor' changed from NULL to ON
2022-02-07 12:04:39.933 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ZWaveNode030OfficeMotionSensorZooz_BinarySensor' changed from ON to OFF