Dome Z-wave Motion Sensor + Aeotec Z-Stick (Gen5): Unknown Device?

I’m having issues getting the Dome Z-Wave Plus Motion Sensor (here’s its database listing) to be recognized as a known device by my Aeotec Z-Stick (Gen5) and OpenHAB.

It’s a battery-powered sensor, which I’ve read means I’ll have to wake it several times after inclusion for it to communicate information like Manufacturer ID, etc. After digging, I found out that you wake it by pressing and holding its inclusion button for about a half-second; its face lights up when you do this, which I assume means it’s awake (can’t find any info on how long it stays awake, though). I’m not totally clear on when this process should take place: during inclusion (the Z-Stick has to be removed from the USB port before inclusion, then a button is pressed, etc.), or during Thing discovery in OpenHAB, but I’ve tried both.

I’m honestly not sure where the trouble is. I noticed that my Z-Stick Thing is missing quite a bit of information. Could this be a problem?

The logs show binary events for the motion sensor whenever I wave my hand in front of it/remain still (255 for waving hand, 0 for being still), and I’m not sure what I should be looking for in the logs outside of the obvious, but here goes, from Thing discovery and then on a bit:


    2018-03-25 17:18:29.079 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Checking zwave:zipato_zp3102_00_000

    2018-03-25 17:18:29.081 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Checking zwave:aeon_dsa38_00_000

    2018-03-25 17:18:29.083 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Checking zwave:isurpass_smokedetector_00_000

    2018-03-25 17:18:29.085 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Checking zwave:rcs_tz45_00_000

    2018-03-25 17:18:29.087 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Checking zwave:innovus_smartpower_00_000

    2018-03-25 17:18:29.088 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Checking zwave:innovus_smartpower_00_000

    2018-03-25 17:18:29.091 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0

    2018-03-25 17:18:29.098 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:36f5232f:node5' to inbox.

    ==> /var/log/openhab2/events.log <==

    2018-03-25 17:18:29.099 [home.event.InboxAddedEvent] - Discovery Result with UID 'zwave:device:36f5232f:node5' has been added.

    ==> /var/log/openhab2/openhab.log <==

    2018-03-25 17:18:29.100 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller start inclusion - mode 2

    2018-03-25 17:18:29.101 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Setting controller into INCLUSION mode, highPower:true networkWide:true.

    2018-03-25 17:18:29.109 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}

    2018-03-25 17:18:29.109 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0

    2018-03-25 17:18:29.112 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A C1 01 70 

    2018-03-25 17:18:29.114 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A C1 01 70 

    2018-03-25 17:18:29.120 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A 01 01 00 00 B2 

    2018-03-25 17:18:29.123 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0

    2018-03-25 17:18:29.126 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 4A 01 01 00 00 B2 

    2018-03-25 17:18:29.129 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 4A 01 01 00 00 B2 

    2018-03-25 17:18:29.131 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 01 00 00 

    2018-03-25 17:18:29.134 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Add Node: Learn ready.

    2018-03-25 17:18:29.136 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInclusionEvent

    ==> /var/log/openhab2/events.log <==

    2018-03-25 17:18:29.140 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@184581

    ==> /var/log/openhab2/openhab.log <==

    2018-03-25 17:18:29.140 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=C1 01 

    2018-03-25 17:18:29.144 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 01 00 00 

    2018-03-25 17:18:29.146 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=AddNodeToNetwork, callback id=0, expected=AddNodeToNetwork, cancelled=false        transaction complete!

    2018-03-25 17:18:29.148 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent

    2018-03-25 17:18:29.151 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 35ms/140ms.

    ==> /var/log/openhab2/events.log <==

    2018-03-25 17:18:35.906 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zwave:device:36f5232f:node5' has been removed.

    ==> /var/log/openhab2/openhab.log <==

    2018-03-25 17:18:35.910 [DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=365, service.bundleid=234, service.scope=singleton} - org.openhab.binding.zwave

    2018-03-25 17:18:35.928 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler.

    ==> /var/log/openhab2/events.log <==

    2018-03-25 17:18:35.939 [hingStatusInfoChangedEvent] - 'zwave:device:36f5232f:node5' changed from UNINITIALIZED to INITIALIZING

    ==> /var/log/openhab2/openhab.log <==

    2018-03-25 17:18:35.943 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: MANUFACTURER not set

    2018-03-25 17:18:35.945 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Controller status changed to ONLINE.

    2018-03-25 17:18:35.946 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Controller is ONLINE. Starting device initialisation.

    ==> /var/log/openhab2/events.log <==

    2018-03-25 17:18:35.950 [hingStatusInfoChangedEvent] - 'zwave:device:36f5232f:node5' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline

    ==> /var/log/openhab2/openhab.log <==

    2018-03-25 17:18:35.957 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating node properties.

    2018-03-25 17:18:35.959 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Updating node properties. MAN=2147483647

    2018-03-25 17:18:35.960 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising Thing Node...

    2018-03-25 17:18:35.962 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Polling intialised at 1800 seconds - start in 1800000 milliseconds.

    ==> /var/log/openhab2/events.log <==

    2018-03-25 17:18:35.962 [hingStatusInfoChangedEvent] - 'zwave:device:36f5232f:node5' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE

    2018-03-25 17:18:35.969 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:36f5232f:node5' has been updated.

    ==> /var/log/openhab2/openhab.log <==

    2018-03-25 17:18:37.558 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 10 05 09 71 05 00 00 00 FF 07 08 00 6C 

    2018-03-25 17:18:37.563 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0

    2018-03-25 17:18:37.566 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0F 00 04 10 05 09 71 05 00 00 00 FF 07 08 00 6C 

    2018-03-25 17:18:37.571 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0F 00 04 10 05 09 71 05 00 00 00 FF 07 08 00 6C 

    2018-03-25 17:18:37.575 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=10 05 09 71 05 00 00 00 FF 07 08 00 

    2018-03-25 17:18:37.578 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 5: Application Command Request (ALIVE:DETAILS)

    2018-03-25 17:18:37.582 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 5: Incoming command class ALARM

    2018-03-25 17:18:37.585 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 5: Received ALARM command V0

    2018-03-25 17:18:37.588 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 5: Process NOTIFICATION_REPORT V0

    2018-03-25 17:18:37.591 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 5: NOTIFICATION report - 0 = 0, event=8, status=255

    2018-03-25 17:18:37.593 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 5: Alarm Type = BURGLAR (0)

    2018-03-25 17:18:37.596 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent

    2018-03-25 17:18:37.600 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveAlarmValueEvent

    2018-03-25 17:18:37.602 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255

    2018-03-25 17:18:37.606 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 255: Transaction not completed: node address inconsistent.  lastSent=255, incoming=255

…and I get that the device hasn’t been fully included, but after trying everything I’ve found online, no luck.

Has anyone had any success with this combination (Aeotec Z-Stick + Dome motion sensor)? Or could someone point me in the right direction? I feel like I’ve exhausted Google at this point.

Almost certainly the device needs to be woken up so that the binding can initialise it. Read the manual on how to wake the device up - it might take a couple of wakes to get it fully initialised. Once complete you should see a lot more information in the properties.

I’ve tried waking it up. There’s no information in the device manual on how to do this, but I found out something over at the SmartThings community. I’ve sat in front of the Z-Stick and repeated this literally 30 times to no avail–both during device inclusion and Thing discovery (in Habmin).

Also, a question: since the device’s XML is already in the database, is there a way for me to just copy this file and somehow attach it to the Thing? I’ve tried doing so by creating a file in /var/lib/openhab2/zwave and naming it node5.xml, but it’s not having any effect on my Thing.

No - you need to get it initialised or it won’t work properly. It’s not just about getting an XML (the XML in the database is not related to this at all).

Somehow you need to get the device initialised. If it’s not waking up, then try excluding it and re-including.

1 Like

Would you believe I just figured it out? The folks over at SmartThings were wrong about how to wake the device, and the included manual didn’t give any indication on how to do so. I pressed the button a few times in rapid succession out of frustration, then saw a million things spit out in the log, and now all my information is filled out.

Spent at least three hours on this. To any future readers, you wake the device the same way you include it: press the button three times in rapid succession. The manufacturer’s manual incorrectly states that it’s awakened by holding the button for two seconds. This can be done at any point after inclusion.

2 Likes

Not sure if you’re the person I’m supposed to flag this to, but my Dome sensor is still showing as unknown device, although all of its information except for the firmware matches what’s in the database. I’m not clear on whether or not ‘All’ firmware is a flag that would allow any firmware to match the device, or if something else is wrong.

Here’s my screen for this device from HABMin:

…and the relevant info from the db:

Manufacturer Elexa Consumer Products Inc.
Manufacturer ID 021F
Name DMMS1
Device Description Dome Z-Wave Plus Motion Detector with Light Sensor and Flexible Magnetic Mount (DMMS1)
Category Motion Detector
References (Type:Id) 0003:0083
Firmware Versions All

I’m still getting my feet wet with OpenHAB, but if I can help get this into the database, please let me know. The database guide says I’d need to have my access updated.

If the data is the same as in the database, then I would guess that you are probably using an older version of the binding that does not support this device. In this case, you should update to the latest snapshot version and it should solve the issue.

1 Like

Thanks a lot for your help, Chris. Updating to snapshot 2.3 did the trick. I’ve now got a fully functional motion sensor Thing and all its Channels.

1 Like