Zwave node stuck on STATIC_VALUES

Add-ons Bindings
1

Dear @chris,

I have a small problem with my latest Aeon Labs Dimmer 6. It keep saying “Node initialising: STATIC_VALUES”.

I have tried restarting with the dimmer next to my controller, exlude and include again. Making sure we use the insecure inclusion. This node supports both.

But sending commands and configuration parameters work. Altough the attributes are also not correct, I guess due to the problem above?

Routing, beaming and such should be supported. Also accoring to your database.
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/275

Is there something I can check?

Many thanks!

2

The flags being incorrect is strange since this is provided by the controller right at the beginning of the initialisation.

Can you provide a debug log of the initialisation so I can see what is happening. Also please ensure that you are using an up to date binding first.

Cheers
Chris

3

Chris,

I added a zwave debug log.
https://drive.google.com/open?id=0B28Wqil4MUVybk1xYzJ0cERmbTg
I guess the important data is:

2016-09-04 10:05:43.639 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 13: Timeout while sending message. Requeueing - 1 attempts left!
2016-09-04 10:05:43.639 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 13: Got an error while sending data. Resending message.
2016-09-04 10:05:43.639 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 39. Queue={}
2016-09-04 10:05:43.639 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 38
2016-09-04 10:05:43.639 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0D 00 13 0D 06 60 0D 01 01 33 01 25 56 C6 
2016-09-04 10:05:43.639 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 13: Sending REQUEST Message = 01 0D 00 13 0D 06 60 0D 01 01 33 01 25 56 C6 
2016-09-04 10:05:43.650 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
2016-09-04 10:05:43.652 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-09-04 10:05:43.652 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
2016-09-04 10:05:43.652 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
2016-09-04 10:05:43.652 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
2016-09-04 10:05:43.653 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 13: Sent Data successfully placed on stack.
2016-09-04 10:05:43.778 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 56 00 00 0E B3 
2016-09-04 10:05:43.780 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-09-04 10:05:43.780 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 56 00 00 0E 00 00 BD 
2016-09-04 10:05:43.780 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 56 00 00 0E 00 00 BD 
2016-09-04 10:05:43.780 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=56 00 00 0E 
2016-09-04 10:05:43.780 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 13: SendData Request. CallBack ID = 86, Status = Transmission complete and ACK received(0)
2016-09-04 10:05:43.780 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=13, callback=86, payload=0D 06 60 0D 01 01 33 01 
2016-09-04 10:05:43.781 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=56 00 00 0E 
2016-09-04 10:05:43.781 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=86, expected=ApplicationCommandHandler, cancelled=false      MISMATCH

It seems something goes wrong there. Let me know if you need anything else.
Binding is max 1 week old. Same as the Openhab exec. (Online snapshot distro)

Thanks!!!

4

Thnaks. I’ll need to look at this more, but from a quick look the flags should be correct (the values in the log are correct - so not sure why it’s wrong in HABmin!).

It’s not responding to the COLOR on endpoint 1 - I’ll need to look at this in more detail though over the next day or so.

5

Super,

Like I said, It is working normally, only showing strange values, so No pressure.

Strange that it queries a color value? It is a regular dimmer :slight_smile:

6

I thought the same! However, it allows you to set the colour of the LED around the plug. The binding is asking for colour number 1, but the device doesn’t support this colour so that’s probably why it’s not working. I need to have a read through the new ZWave docs to see if there’s something I’ve missed with the implementation.

Do you mind raising an issue for this - just so I don’t loose sight of it ;).

Thanks
Chris

7

On further investigation, the problem is likely caused by endpoint 1 not supporting the color class, but for some reason the binding requests it. It doesn’t look like the device is reporting color in this endpoint so there’s something wrong in the multi_instance class.

Please attach the log to the issue when you create it and link back to this conversation. I’ll try and take a look over the coming week or so.

8

Chris,

Will do this later today, many thanks!