Motion sensor hsm100 fail to initialise

Information on sensors etc is not included in the multi-channel command class - it’s included elsewhere in subsequent requests, so I would doubt that this is the problem.

I can only apologise for not getting this resolved. However, I’ve also put quite a lot of time into trying to help where I can, and it is very difficult to try and debug a device I don’t have remotely.

If there are a lot of people who have this, I could look to buy one to get it working - but until now it’s only one or two people and it’s hard for me to justify spending money on a device I won’t use myself with so few people seemingly having this device (I already have a lot of devices I’ve purchased to help others).

From my point of view there is no need to apologize ever … your 99.9 % success in making the zwave binding work is far more than enough :grinning:

2 Likes

@chris, I feel exactly like shiui. You don’t need to apologise. Actually, the opposite. The reason I’m sticking with this issue is that I see responsiveness and solutions in so many other threads that encourage me to keep digging. (I understand the difficulty of not having the device, and understanding my questions since I may be mixing terms being an Openhab / zwave noob)

What would help me are directions in response to my questions that will send me digging more until I find a solution :slight_smile:
Can you look at the xml file here and tell me:

  • is it expected to have all 9 command classes appear identicaly for each of the endpoints? (I mentioned the details in this post)
  • is it expected not to have Temperature, and Luminance entries? (compared to this reference from another user)
    I want to make sure that node XML file is correct before investigating beyond initialisation
    Thanks again.

Hi Chris

I’m a relative new comer to this thread and wanted to echo the other comments that there is no need to apologise as it looks like you’ve put a significant amount of resource in (I know I wouldn’t be a popular person at home if I worked on an open source project while on holiday as you did :slight_smile:

The HSM100 I’ve got is pretty old. I acquired them a number of years ago so they probably aren’t even available now.

I’d be happy to mail you one of mine if that helps (preference is to get it back if possible :-), as they aren’t doing anything given the issues I currently have with homassistant and openhab?

Regards

I never got my HSM100 (Express Control EZMotion 3in1) to work with OH either. But it may be a unrelated issue, it was so long time ago since I gave up, that I don’t remember anymore… :slight_smile:

I decided to give it a go by pressing the button on the side for a NIF, I get;

17:45:12.769 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 53: Application update request. Node information received.
17:45:12.770 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Node is ALIVE. Init stage is PING.
17:45:12.770 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveNodeStatusEvent
17:45:12.770 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node Status event during initialisation - Node is ALIVE
17:45:12.770 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - PING: queue length(0), free to send(true)
17:45:12.770 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: loop - PING try 1: stageAdvanced(false)
17:45:12.770 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: PING - send NoOperation
17:45:12.770 [DEBUG] [ndclass.ZWaveNoOperationCommandClass] - NODE 53: Creating new message for command No Operation
17:45:12.770 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - queued packet. Queue length is 1
17:45:12.770 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
17:45:12.770 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
17:45:12.770 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 53: Node Status event - Node is ALIVE
17:45:12.770 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 08 00 13 35 01 00 25 87 72 
17:45:12.770 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Creating new instance of command class MULTI_INSTANCE
17:45:12.770 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 53: Sending REQUEST Message = 01 08 00 13 35 01 00 25 87 72 
17:45:12.771 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Command class MULTI_INSTANCE, endpoint null created
17:45:12.771 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 53: Application update is adding command class MULTI_INSTANCE.
17:45:12.771 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Adding command class MULTI_INSTANCE to the list of supported command classes.
17:45:12.771 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Creating new instance of command class CONFIGURATION
17:45:12.771 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Command class CONFIGURATION, endpoint null created
17:45:12.771 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 53: Application update is adding command class CONFIGURATION.
17:45:12.771 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Adding command class CONFIGURATION to the list of supported command classes.
17:45:12.771 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Creating new instance of command class WAKE_UP
17:45:12.771 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Command class WAKE_UP, endpoint null created
17:45:12.772 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 53: Application update is adding command class WAKE_UP.
17:45:12.772 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Adding command class WAKE_UP to the list of supported command classes.
17:45:12.772 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Creating new instance of command class ASSOCIATION
17:45:12.772 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Command class ASSOCIATION, endpoint null created
17:45:12.772 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 53: Application update is adding command class ASSOCIATION.
17:45:12.772 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Adding command class ASSOCIATION to the list of supported command classes.
17:45:12.772 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Creating new instance of command class BATTERY
17:45:12.772 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Command class BATTERY, endpoint null created
17:45:12.772 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 53: Application update is adding command class BATTERY.
17:45:12.772 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Adding command class BATTERY to the list of supported command classes.
17:45:12.772 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Creating new instance of command class MANUFACTURER_SPECIFIC
17:45:12.772 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Command class MANUFACTURER_SPECIFIC, endpoint null created
17:45:12.772 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 53: Application update is adding command class MANUFACTURER_SPECIFIC.
17:45:12.772 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Adding command class MANUFACTURER_SPECIFIC to the list of supported command classes.
17:45:12.772 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Creating new instance of command class NODE_NAMING
17:45:12.772 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Command class NODE_NAMING, endpoint null created
17:45:12.772 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 53: Application update is adding command class NODE_NAMING.
17:45:12.772 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Adding command class NODE_NAMING to the list of supported command classes.
17:45:12.772 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Creating new instance of command class VERSION
17:45:12.772 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Command class VERSION, endpoint null created
17:45:12.772 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 53: Application update is adding command class VERSION.
17:45:12.772 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 53: Adding command class VERSION to the list of supported command classes.
17:45:12.773 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 53: Is awake with 0 messages in the wake-up queue.
17:45:12.773 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
17:45:12.773 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Wakeup during initialisation.
17:45:12.773 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - PING: queue length(1), free to send(false)
17:45:12.773 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - queued packet. Queue length is 1
17:45:12.773 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
17:45:12.773 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=38, callback=134, payload=26 07 60 0D 01 01 25 01 FF 
17:45:12.773 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 35 0E 04 21 01 60 31 70 84 85 80 72 77 86 EF 20 
17:45:12.773 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationUpdate, callback id=134, expected=SendData, cancelled=false      MISMATCH
17:45:13.773 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 53: No more messages, go back to sleep
17:45:13.773 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 53: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION

Then I get a notification about a new thing, which I add. But it does not arrive into the ‘thing list’ under configuration.
I push the nif button again, and get;

18:21:14.989 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 53: Application update request. Node information received.
18:21:14.989 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 53: Is awake with 2 messages in the wake-up queue.
18:21:14.989 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
18:21:14.989 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Wakeup during initialisation.
18:21:14.989 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - PING: queue length(1), free to send(false)
18:21:14.989 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - queued packet. Queue length is 1
18:21:14.989 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
18:21:14.989 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
18:21:14.989 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
18:21:14.989 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 08 00 13 35 01 00 25 ED 18 
18:21:14.989 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=20, callback=235, payload=14 02 26 02 
18:21:14.989 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 53: Sending REQUEST Message = 01 08 00 13 35 01 00 25 ED 18 
18:21:14.989 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 35 0E 04 21 01 60 31 70 84 85 80 72 77 86 EF 20 
18:21:14.990 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationUpdate, callback id=235, expected=ApplicationCommandHandler, cancelled=false      MISMATCH
18:21:14.996 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
18:21:14.997 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
18:21:14.997 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
18:21:14.997 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
18:21:14.997 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
18:21:14.997 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 53: Sent Data successfully placed on stack.
18:21:15.013 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 ED 00 00 02 04 
18:21:15.013 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
18:21:15.013 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 ED 00 00 02 00 00 0A 
18:21:15.013 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 ED 00 00 02 00 00 0A 
18:21:15.013 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=ED 00 00 02 
18:21:15.013 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 53: SendData Request. CallBack ID = 237, Status = Transmission complete and ACK received(0)
18:21:15.014 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Poll, dest=53, callback=237, payload=35 01 00 
18:21:15.014 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=ED 00 00 02 
18:21:15.014 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=237, expected=SendData, cancelled=false        transaction complete!
18:21:15.014 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
18:21:15.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - PING: Transaction complete (SendData:Request) success(true)
18:21:15.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - checking initialisation queue. Queue size 1.
18:21:15.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - message removed from queue. Queue size 0.
18:21:15.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - PING: queue length(0), free to send(true)
18:21:15.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: loop - PING try 2: stageAdvanced(false)
18:21:15.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - advancing to DETAILS
18:21:15.014 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInitializationStateEvent
18:21:15.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: loop - DETAILS try 0: stageAdvanced(true)
18:21:15.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: received RequestNodeInfo
18:21:15.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - advancing to INCLUSION_START
18:21:15.014 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInitializationStateEvent
18:21:15.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: loop - INCLUSION_START try 0: stageAdvanced(true)
18:21:15.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: Unknown node state INCLUSION_START encountered.
18:21:15.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - advancing to IDENTIFY_NODE
18:21:15.014 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInitializationStateEvent
18:21:15.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: loop - IDENTIFY_NODE try 0: stageAdvanced(true)
18:21:15.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: PROTOINFO - send IdentifyNode
18:21:15.014 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - queued packet. Queue length is 1
18:21:15.015 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 2. Queue={}
18:21:15.015 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 3. Queue={}
18:21:15.015 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 53: Response processed after 25ms/4984ms.
18:21:15.015 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 2
18:21:15.015 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 08 00 13 35 01 00 25 EF 1A 
18:21:15.015 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 53: Sending REQUEST Message = 01 08 00 13 35 01 00 25 EF 1A 
18:21:15.022 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
18:21:15.022 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
18:21:15.022 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
18:21:15.022 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
18:21:15.022 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
18:21:15.022 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 53: Sent Data successfully placed on stack.
18:21:15.038 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 EF 00 00 02 06 
18:21:15.038 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
18:21:15.039 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 EF 00 00 02 00 00 08 
18:21:15.039 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 EF 00 00 02 00 00 08 
18:21:15.039 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=EF 00 00 02 
18:21:15.039 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 53: SendData Request. CallBack ID = 239, Status = Transmission complete and ACK received(0)
18:21:15.039 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=53, callback=239, payload=35 01 00 
18:21:15.039 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=EF 00 00 02 
18:21:15.039 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=239, expected=SendData, cancelled=false        transaction complete!
18:21:15.039 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
18:21:15.039 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - IDENTIFY_NODE: Transaction complete (SendData:Request) success(true)
18:21:15.039 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - checking initialisation queue. Queue size 1.
18:21:15.039 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 53: Response processed after 24ms/4984ms.
18:21:15.039 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 1
18:21:15.039 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 35 02 84 08 25 EE 95 
18:21:15.039 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 53: Sending REQUEST Message = 01 09 00 13 35 02 84 08 25 EE 95 
18:21:15.046 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
18:21:15.046 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
18:21:15.046 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
18:21:15.046 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
18:21:15.046 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
18:21:15.047 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 53: Sent Data successfully placed on stack.
18:21:15.063 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 EE 00 00 02 07 
18:21:15.063 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
18:21:15.064 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 EE 00 00 02 00 00 09 
18:21:15.064 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 EE 00 00 02 00 00 09 
18:21:15.064 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=EE 00 00 02 
18:21:15.064 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 53: SendData Request. CallBack ID = 238, Status = Transmission complete and ACK received(0)
18:21:15.064 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=53, callback=238, payload=35 02 84 08 
18:21:15.064 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=EE 00 00 02 
18:21:15.064 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=238, expected=SendData, cancelled=false        transaction complete!
18:21:15.064 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
18:21:15.064 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - IDENTIFY_NODE: Transaction complete (SendData:Request) success(true)
18:21:15.064 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - checking initialisation queue. Queue size 1.
18:21:15.064 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 53: Went to sleep
18:21:15.064 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 53: Is sleeping
18:21:15.064 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 53: Response processed after 25ms/4984ms.
18:21:15.064 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
18:21:15.065 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 00 41 35 8F 
18:21:15.065 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 04 00 41 35 8F 
18:21:15.066 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 01 41 51 8C 00 04 21 01 4F 
18:21:15.067 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
18:21:15.067 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 01 41 51 8C 00 04 21 01 4F 
18:21:15.067 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 01 41 51 8C 00 04 21 01 4F 
18:21:15.067 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=IdentifyNode[0x41], type=Response[0x01], priority=High, dest=255, callback=0, payload=51 8C 00 04 21 01 
18:21:15.067 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 53: ProtocolInfo
18:21:15.067 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 53: Listening = false
18:21:15.067 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 53: Routing = true
18:21:15.067 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 53: Beaming = false
18:21:15.067 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 53: Version = 2
18:21:15.067 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 53: FLIRS = false
18:21:15.068 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 53: Security = false
18:21:15.068 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 53: Max Baud = 40000
18:21:15.068 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 53: Basic = Routing Slave
18:21:15.068 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 53: Generic = Multi-Level Sensor
18:21:15.068 [DEBUG] [rialmessage.IdentifyNodeMessageClass] - NODE 53: Specific = Routing Multilevel Sensor
18:21:15.068 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Creating new instance of command class NO_OPERATION
18:21:15.068 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Command class NO_OPERATION, endpoint null created
18:21:15.068 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Version = 1, version set. Enabling extra functionality.
18:21:15.068 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Creating new instance of command class BASIC
18:21:15.068 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Command class BASIC, endpoint null created
18:21:15.068 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Creating new instance of command class SENSOR_MULTILEVEL
18:21:15.068 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 53: Command class SENSOR_MULTILEVEL, endpoint null created
18:21:15.068 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=IdentifyNode[0x41], type=Request[0x00], priority=High, dest=255, callback=0, payload=35 
18:21:15.068 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=IdentifyNode[0x41], type=Response[0x01], priority=High, dest=255, callback=0, payload=51 8C 00 04 21 01 
18:21:15.068 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=IdentifyNode, callback id=0, expected=IdentifyNode, cancelled=false        transaction complete!
18:21:15.068 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
18:21:15.068 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - IDENTIFY_NODE: Transaction complete (IdentifyNode:Request) success(true)
18:21:15.068 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - checking initialisation queue. Queue size 1.
18:21:15.069 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - message removed from queue. Queue size 0.
18:21:15.069 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - IDENTIFY_NODE: queue length(0), free to send(true)
18:21:15.069 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: loop - IDENTIFY_NODE try 1: stageAdvanced(false)
18:21:15.069 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - advancing to MANUFACTURER
18:21:15.069 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInitializationStateEvent
18:21:15.069 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: loop - MANUFACTURER try 0: stageAdvanced(true)
18:21:15.069 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer: MANUFACTURER - send ManufacturerSpecific
18:21:15.069 [DEBUG] [WaveManufacturerSpecificCommandClass] - NODE 53: Creating new message for command MANUFACTURER_SPECIFIC_GET
18:21:15.069 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 53: Node advancer - queued packet. Queue length is 1
18:21:15.069 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 53: Putting message SendData in wakeup queue.
18:21:15.069 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 53: Putting message SendData in wakeup queue.

Does this look like the same issue?
I haven’t done any reset or removal of the device, it has been located by the stick since before summer, when I gave up on it.

More observations…
I initialised the device in several attempts, and got different results depending on the timing on which I pressed the button to wake up the device.
At one attempt I got no sensors created, at a second I got 1 sensor created and 2 not created, and at a third attempt I got all 3 created with UNKNOWN.
I think that the initialisation is progressing beyond the ENDPOINTS stage, without waiting to the received response for each of the endpoints.
(I think that this is done in ZWaveMultiInstanceCommandClass.java in handleMultiChannelCapabilityReportResponse)

Please provide some logs showing what’s happening. It’s probably not impossible for this to happen, but the OH2 binding tries pretty hard to get the information it needs but it will also timeout after a while if it doesn’t get the responses.

Note that “sensors” are not created during the ENDPOINTS stage - this is done during the STATIC stage.

Thanks for clarifying where sensors are reated.
The log files for

  • case 1 (1 sensor created and 2 not created) is here
  • case 2 (no sensors created) is here

Just an update that the readings in Home Assistant do change, but very slightly and the temperature value seems inaccurate (I’m getting 27 Celsius at home, while it is more like 21), so I’m still hoping that this can be resolved within openhab.

Looking through the logs it’s not immediately clear why there’s a difference - the ENDPOINTs part looks the same and the STATIC_VALUES also looks similar (both very limited). With retries, wakeups, duplicate messages etc, it’s difficult to do a simple comparison.

If I can find a supplier in the EU for this device I will try and buy one to get this resolved - it will save me a lot of my time, along with everyone elses. I will take a look over the next few days to see if I can find one and try and get this resolved.

Okay thanks.

Reading other users feedback some have said they think they are gettting higher readings when they have them hardwired rather than battery operated, or they are a little close to the wall and picking up some kind of reflection.

I’ve upgraded homeassistant as I see there were a few zwave mods/bugs squashed and will see how that goes.

I’ve also been using the openzwave web gui that comes with homeassistant (manual start up). it shows a wealth of info. Clearly shows that my battery appliances are being polled so will see how they pan out.

Also might be of interest is that there is a TempAdj parameter within openzwave that presumably allows you to enter in some kind of offset for corrections on a per appliance basis.

According to the developer of the device the EZMotion was EOL in 2014 and they have not been manufactured since 2012, so I’m don’t know how easy it will be to buy one.
@Hamish kindly suggested to send one of his devices (in this post) (I can’t send mine since i only have one device and I’m constantly poking at it. Hopefully this will help to find a solution to this problem.

Thanks,
Avner

According to the developer of the device the EZMotion was EOL in 2014 and they have not been manufactured since 2012, so I’m don’t know how easy it will be to buy one.
@Hamish kindly suggested to send one of his devices in this post. Hopefully this will help to find a solution to this problem.

Thanks,
Avner

I must say, that does lower my drive to spend so much time trying to solve the problem on such an old device ;).

Hmmm - I missed this. Is it an EU version? If so, that might be a useful way forward. I certainly won’t have any time for the next few weeks as I need to update the security work, and also finalise some stuff on the ZigBee binding, but if I can get hold of one it’s might not be too much work to resolve (he says hopefully!).

Hi Chris

Yes it is an EU one (but not being run in the EU :slight_smile:

I could however just make my RPI3 box available to you to SSH into and play with it as you wish. It isn’t a production system so worst case I could place it outside the DMZ zone and you could log in (it would be sitting behind a 200/20 link so should be plenty responsive). My rationale is I’ve had 3 parcels go missing with the post in the last week so don’t have a lot of confidence with them at the moment, and this might be quicker/easier all round?

Yes you are right, the values do update, but they appear to do so fairly slowly as if using some moving average which limits the usability.

Hi guys,

I have recently began using OpenHAB2 and must say that i am very impressed with it so far.
Before, i used a home automation platform thats used the Open Zwave Library for their Zwave implementation.
The HSM100 sensor works great with the Open Zwave Library.
Maybe by looking at the differences between the two solutions, brings the answer, just a suggestion, trying to help.
I have 3 of those sensors, 2 in active use, 1 battery powered, 1 mains powered. I can help test.

br,
Raymond

From my zwave debug log;
This is my battery operated HSM100 sensor:

14:11:52.502 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Application Command Request (ALIVE:DONE)
14:11:52.502 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Starting initialisation from DONE
14:11:52.503 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1441602 already registered
14:11:52.504 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Incoming command class WAKE_UP
14:11:52.504 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 18: Received Wake Up Request
14:11:52.505 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 18: Received WAKE_UP_NOTIFICATION
14:11:52.505 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 18: Is awake with 3 messages in the wake-up queue.
14:11:52.506 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
14:11:52.506 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got an event from Z-Wave network: ZWaveWakeUpEvent
14:11:52.509 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
14:11:52.509 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
14:11:52.509 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Transaction not completed: node address inconsistent.  lastSent=13, incoming=255
14:11:52.511 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0D 00 13 12 06 60 0D 01 01 80 02 25 C3 FC 
14:11:52.513 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 18: Sending REQUEST Message = 01 0D 00 13 12 06 60 0D 01 01 80 02 25 C3 FC 
14:11:52.928 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
14:11:52.932 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
14:11:52.937 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
14:11:52.942 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
14:11:52.946 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
14:11:52.949 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 18: Sent Data successfully placed on stack.
14:11:53.098 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 05 00 13 C3 00 2A 
14:11:53.100 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
14:11:53.101 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 13 C3 00 00 00 28 
14:11:53.102 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 13 C3 00 00 00 28 
14:11:53.104 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=C3 00 
14:11:53.105 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 18: SendData Request. CallBack ID = 195, Status = Transmission complete and ACK received(0)
14:11:53.106 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Starting initialisation from DONE
14:11:53.107 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1441602 already registered
14:11:53.108 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=18, callback=195, payload=12 06 60 0D 01 01 80 02 
14:11:53.110 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=C3 00 
14:11:53.111 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=195, expected=ApplicationCommandHandler, cancelled=false      MISMATCH
14:11:57.518 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 18: Too many retries. Discarding message: Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=18, callback=195, payload=12 06 60 0D 01 01 80 02 

and some other, hopefully useful info from that log:

5:39:01.868 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Polling...
15:39:01.873 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Polling zwave:device:364dcb3b:node18:sensor_binary
15:39:01.877 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Polling zwave:device:364dcb3b:node18:sensor_temperature
15:39:01.879 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 18: Generating poll message for SENSOR_MULTILEVEL, endpoint 0
15:39:01.880 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 18: Creating new message for command SENSOR_MULTI_LEVEL_GET
15:39:01.882 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Polling zwave:device:364dcb3b:node18:sensor_luminance
15:39:01.884 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 18: Generating poll message for SENSOR_MULTILEVEL, endpoint 0
15:39:01.887 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 18: Creating new message for command SENSOR_MULTI_LEVEL_GET
15:39:01.889 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Polling zwave:device:364dcb3b:node18:battery-level
15:39:01.890 [DEBUG] [rnal.converter.ZWaveBatteryConverter] - NODE 18: Generating poll message for BATTERY endpoint 0
15:39:01.891 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 18: Creating new message for application command BATTERY_GET
15:39:01.894 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 18: Putting message SendData in wakeup queue.
15:39:01.897 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 18: Message already on the wake-up queue. Removing original.
15:39:01.898 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 18: Putting message SendData in wakeup queue.
15:39:01.900 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 18: Putting message SendData in wakeup queue.

Hope this helps to pin down the problem

br,
Raymond

1 Like

Unfortunately not. The first log only has a single request which looks fine -:
Uploading…

The next log doesn’t have any useful information.

I’m not really sure how I can progress with this. I can’t sit here an do a code review of OZW versus OH - that’s really not practical. The two implementations are very different and reviewing code like that is pretty error prone. Sorry.

I was able to include the HSM100 device with the via the Z-Way binding (I had to get a Z-Way library license and a UZB stick).
I successfully triggered an update to get new readings from the device. I opened/closed the light and triggered an update via the Z-Way server (left image in the Light Off snapshot) and the results are reasonable (Lux changes from 96% to 0%, and the temperature updates are in the expected ballpark)

I have some questions regarding the Z-Way binding:

  • Do I need to run the z-way-server? (in my testing I have it running while openhab2 is running)
  • How can I initiate an update request from PaperUI? (similar to Zwave Expert UI -> Control -> Update All - in the left image in the Light Off snapshot)
  • I cannot find the device configuration parameters (e.g. motion sensitivity) in PaperUI (see left image in the LightOn snapshot)
    @pathec or anyone else, I am hoping you can help me with the Z-Way questions above.

Light On snapshot


Light Off snapshot