[SOLVED] Z-Wave HomeSeer HS-FL100+ motion notification not changing switch state

I have two HS-FL100+ z-wave floodlight sensor/switch units and am having some trouble getting motion to change the state of an item in OpenHab (version 2.4.0). I have items linked to both the sensor_binary and the alarm_burglar channels and don’t see updates when I trigger motion, but I do see a notification in the z-wave log from the motion sensor.

The item configuration is:

Switch SideYard_EntryFloodMotion {channel="zwave:device:67e70bb9:node64:alarm_burglar"}
Switch SideYard_EntryFloodMotion2 {channel="zwave:device:67e70bb9:node64:sensor_binary"}

Here is what I’m seeing in the z-wave log:

2019-01-19 20:40:25.510 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-01-19 20:40:25.510 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-01-19 20:40:27.286 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 40 09 71 05 00 00 00 FF 07 08 00 39 
2019-01-19 20:40:27.287 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=64, callback=0, payload=00 40 09 71 05 00 00 00 FF 07 08 00 
2019-01-19 20:40:27.288 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=64, callback=0, payload=00 40 09 71 05 00 00 00 FF 07 08 00 
2019-01-19 20:40:27.288 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-01-19 20:40:27.288 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 64: Application Command Request (ALIVE:DONE)
2019-01-19 20:40:27.288 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 64: resetResendCount initComplete=true isDead=false
2019-01-19 20:40:27.288 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 64: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2019-01-19 20:40:27.289 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 64: SECURITY not supported
2019-01-19 20:40:27.289 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 64: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2019-01-19 20:40:27.289 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 64: NOTIFICATION report - 0 = 0, event=8, status=255, plen=0
2019-01-19 20:40:27.289 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 64: Alarm Type = BURGLAR (0)
2019-01-19 20:40:27.290 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 64: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2019-01-19 20:40:27.290 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 64: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255
2019-01-19 20:40:27.290 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 64: Alarm converter processing NOTIFICATION
2019-01-19 20:40:27.291 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 64: Alarm converter NOTIFICATION event is 8, type OnOffType
2019-01-19 20:40:27.291 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 64: Alarm converter processing NOTIFICATION
2019-01-19 20:40:27.291 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 64: Alarm converter NOTIFICATION event is 8, type OnOffType
2019-01-19 20:40:27.291 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 64: Commands processed 1.
2019-01-19 20:40:27.292 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 64: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@47b32592.
2019-01-19 20:40:27.292 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-01-19 20:40:27.292 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-01-19 20:40:27.292 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-01-19 20:40:27.293 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-01-19 20:40:35.898 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 64: Command received zwave:device:67e70bb9:node64:switch_binary --> OFF [OnOffType]
2019-01-19 20:40:35.898 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 64: Creating new message for application command SWITCH_BINARY_SET
2019-01-19 20:40:35.899 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 64: SECURITY not supported
2019-01-19 20:40:35.899 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 64: Command Class COMMAND_CLASS_SWITCH_BINARY is NOT required to be secured
2019-01-19 20:40:35.899 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 64: Adding to device queue
2019-01-19 20:40:35.900 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 64: Added 41878 to queue - size 4

Any ideas why the items in OpenHAB aren’t updating when this z-wave event happens?

Let me know if more information is needed… first time digging through the z-wave debug logs.

Thanks!

It looks like upgrading to the latest 2.5 z-wave snapshot fixed this

1 Like

Sorry to resurrect this, but I am having issues with this myself in openhab 2.5 and doing it here seemed better than starting a new topic. I have items defined for all of the channels and am able to switch the light on/off, but I do not see the ‘alarm_burglar’ channel ever switching to ON when motion occurs. It does maybe seem to update it to OFF when motion ceases though. See the Zwave logging for relevant node when motion occurs here (basically same as above):

2020-01-30 08:55:50.836 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 16: Application Command Request (ALIVE:DONE)

2020-01-30 08:55:50.840 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 16: resetResendCount initComplete=true isDead=false

2020-01-30 08:55:50.848 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 16: Incoming command class COMMAND_CLASS_ALARM, endpoint 0

2020-01-30 08:55:50.852 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 16: SECURITY not supported

2020-01-30 08:55:50.856 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 16: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT

2020-01-30 08:55:50.860 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 16: NOTIFICATION report - 0 = 0, event=0, status=255, plen=1

2020-01-30 08:55:50.864 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 16: Alarm Type = BURGLAR (0)

2020-01-30 08:55:50.870 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 16: Got an event from Z-Wave network: ZWaveAlarmValueEvent

2020-01-30 08:55:50.876 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 16: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255

2020-01-30 08:55:50.881 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 16: Alarm converter processing NOTIFICATION

2020-01-30 08:55:50.889 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 16: Alarm converter NOTIFICATION event is 0, type OnOffType

2020-01-30 08:55:50.897 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 16: Alarm converter processing NOTIFICATION

2020-01-30 08:55:50.901 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 16: Alarm converter NOTIFICATION event is 0, type OnOffType

2020-01-30 08:55:50.905 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 16: Updating channel state zwave:device:512:node16:alarm_burglar to OFF [OnOffType]

2020-01-30 08:55:50.916 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 16: Commands processed 1.

2020-01-30 08:55:50.924 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 16: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@558647.

2020-01-30 08:55:50.930 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 16: Command NOT verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@558647.

Any ideas? Did you maybe do something else aside from changing the Zwave binding? I need to send this device back if it is a hardware issue and not something to do with the device’s DB entry.

Have you tried binding the switch item for the motion detection to alarm_motion instead of alarm_burglar? I just looked at my item file and that’s what I’m using and it seems to work.

1 Like

Huh I don’t have that channel listed in the thing description. I tried to set it to an item to no avail. Maybe the snapshot you have didn’t make it to the stable release? Are you using stable 2.5 release with built in zwave binding?

Strange. I recently upgraded to 2.5 stable and it still works. PaperUI doesn’t show alarm_burglar for me anymore (it did before the 2.4 snapshot update that was my previous solution. I only see alarm_motion. Have you tried deleting the thing and re-adding or unpairing/repairing the device? I think I had to do something like that after the 2.4 snapshot upgrade

1 Like

I bet that’s it. Let me try. Thanks for the responsiveness and help!
EDIT: Yes that did it! Thanks! As an aside have you been happy with the performance of this sensor?

Great! glad that did it!

So far, no complaints. I’m using it just for triggering lighting, not security so I don’t really care too much about false activations (although I can’t say I’ve noticed any). I haven’t had it miss me walking around though, and it seems to pick me up at a pretty good distance.

1 Like