Hi all,
i have a new fibaro dimmer2 (FGD212) that’s know by OH.
Some configurations cann set - some not:
Values 21 i can’t change from:
“0xFF value is sent, which will set associated devices to their last saved state!” to
“current Dimmer 2 state is sent, which will synchronize brightness level of associated devices (other dimmers for example)”
the value keepy yellow all the time.
Best reguards
Hubertus
chris
(Chris Jackson)
December 19, 2015, 4:21pm
2
Please provide a debug log that shows you attempting to set this.
Hallo Chris,
here it is:
17:24:57.957 [DEBUG] [.z.i.config.ZWaveConfiguration:1177 ] - Set parameter index '21' to '0'
17:24:57.959 [DEBUG] [ZWaveConfigurationCommandClass:188 ] - NODE 19: Creating new message for application command CONFIGURATIONCMD_SET
17:24:57.961 [DEBUG] [o.b.z.i.protocol.SerialMessage:109 ] - NODE 19: Creating empty message of class = SendData (0x13), type = Request (0x00)
17:24:57.963 [DEBUG] [b.z.i.protocol.ZWaveController:938 ] - Callback ID = 56
17:24:57.965 [DEBUG] [b.z.i.protocol.ZWaveController:620 ] - Enqueueing message. Queue length = 1
17:24:57.965 [DEBUG] [WaveController$ZWaveSendThread:1211 ] - Took message from queue for sending. Queue length = 0
17:24:57.966 [DEBUG] [ZWaveConfigurationCommandClass:160 ] - NODE 19: Creating new message for application command CONFIGURATIONCMD_GET
17:24:57.967 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ] - Assembled message buffer = 01 0C 00 13 13 05 70 04 15 01 00 25 38 8B
17:24:57.969 [DEBUG] [o.b.z.i.protocol.SerialMessage:109 ] - NODE 19: Creating empty message of class = SendData (0x13), type = Request (0x00)
17:24:57.969 [DEBUG] [WaveController$ZWaveSendThread:1268 ] - NODE 19: Sending REQUEST Message = 01 0C 00 13 13 05 70 04 15 01 00 25 38 8B
17:24:57.970 [DEBUG] [b.z.i.protocol.ZWaveController:938 ] - Callback ID = 57
17:24:57.973 [DEBUG] [b.z.i.protocol.ZWaveController:620 ] - Enqueueing message. Queue length = 1
17:24:57.978 [DEBUG] [eController$ZWaveReceiveThread:1481 ] - Receive Message = 01 04 01 13 01 E8
17:24:58.011 [DEBUG] [eController$ZWaveReceiveThread:1405 ] - Receive queue ADD: Length=1
17:24:58.011 [DEBUG] [b.z.i.protocol.ZWaveController:1163 ] - Receive queue TAKE: Length=0
17:24:58.012 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ] - Assembled message buffer = 01 04 01 13 01 E8
17:24:58.013 [DEBUG] [b.z.i.protocol.ZWaveController:1164 ] - Process Message = 01 04 01 13 01 E8
17:24:58.014 [DEBUG] [b.z.i.protocol.ZWaveController:192 ] - Message: class = SendData (0x13), type = Response (0x01), payload = 01
17:24:58.015 [DEBUG] [b.z.i.p.s.SendDataMessageClass:38 ] - NODE 19: Sent Data successfully placed on stack.
17:24:58.017 [DEBUG] [eController$ZWaveReceiveThread:1481 ] - Receive Message = 01 07 00 13 38 00 00 02 D1
17:24:58.031 [DEBUG] [eController$ZWaveReceiveThread:1405 ] - Receive queue ADD: Length=1
17:24:58.031 [DEBUG] [b.z.i.protocol.ZWaveController:1163 ] - Receive queue TAKE: Length=0
17:24:58.033 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ] - Assembled message buffer = 01 09 00 13 38 00 00 02 00 00 DF
17:24:58.034 [DEBUG] [b.z.i.protocol.ZWaveController:1164 ] - Process Message = 01 09 00 13 38 00 00 02 00 00 DF
17:24:58.035 [DEBUG] [b.z.i.protocol.ZWaveController:192 ] - Message: class = SendData (0x13), type = Request (0x00), payload = 38 00 00 02
17:24:58.036 [DEBUG] [b.z.i.p.s.SendDataMessageClass:74 ] - NODE 19: SendData Request. CallBack ID = 56, Status = Transmission complete and ACK received(0)
17:24:58.038 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:63 ] - Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 13 05 70 04 15 01 00
17:24:58.039 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:64 ] - Recv message Message: class = SendData (0x13), type = Request (0x00), payload = 38 00 00 02
17:24:58.040 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:65 ] - Checking transaction complete: class=SendData, expected=SendData, cancelled=false
17:24:58.041 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:68 ] - transaction complete!
17:24:58.042 [DEBUG] [b.z.i.protocol.ZWaveController:635 ] - Notifying event listeners: ZWaveTransactionCompletedEvent
17:24:58.042 [DEBUG] [.z.internal.ZWaveActiveBinding:433 ] - ZwaveIncomingEvent
17:24:58.043 [DEBUG] [WaveController$ZWaveSendThread:1327 ] - NODE 19: Response processed after 72ms/3706ms.
chris
(Chris Jackson)
December 19, 2015, 4:38pm
4
This looks ok - the request is sent correctly, and appears to be ack’ed by the device. However, is there another transaction immediately after this in the log as well?
yes:
17:24:58.044 [DEBUG] [WaveController$ZWaveSendThread:1211 ] - Took message from queue for sending. Queue length = 0
17:24:58.045 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ] - Assembled message buffer = 01 0A 00 13 13 03 70 05 15 25 39 8A
17:24:58.046 [DEBUG] [WaveController$ZWaveSendThread:1268 ] - NODE 19: Sending REQUEST Message = 01 0A 00 13 13 03 70 05 15 25 39 8A
17:24:58.053 [DEBUG] [eController$ZWaveReceiveThread:1481 ] - Receive Message = 01 04 01 13 01 E8
17:24:58.081 [DEBUG] [eController$ZWaveReceiveThread:1405 ] - Receive queue ADD: Length=1
17:24:58.082 [DEBUG] [b.z.i.protocol.ZWaveController:1163 ] - Receive queue TAKE: Length=0
17:24:58.083 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ] - Assembled message buffer = 01 04 01 13 01 E8
17:24:58.084 [DEBUG] [b.z.i.protocol.ZWaveController:1164 ] - Process Message = 01 04 01 13 01 E8
17:24:58.085 [DEBUG] [b.z.i.protocol.ZWaveController:192 ] - Message: class = SendData (0x13), type = Response (0x01), payload = 01
17:24:58.086 [DEBUG] [b.z.i.p.s.SendDataMessageClass:38 ] - NODE 19: Sent Data successfully placed on stack.
17:24:58.088 [DEBUG] [eController$ZWaveReceiveThread:1481 ] - Receive Message = 01 07 00 13 39 00 00 02 D0
17:24:58.101 [DEBUG] [eController$ZWaveReceiveThread:1405 ] - Receive queue ADD: Length=1
17:24:58.101 [DEBUG] [b.z.i.protocol.ZWaveController:1163 ] - Receive queue TAKE: Length=0
17:24:58.103 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ] - Assembled message buffer = 01 09 00 13 39 00 00 02 00 00 DE
17:24:58.105 [DEBUG] [b.z.i.protocol.ZWaveController:1164 ] - Process Message = 01 09 00 13 39 00 00 02 00 00 DE
17:24:58.106 [DEBUG] [b.z.i.protocol.ZWaveController:192 ] - Message: class = SendData (0x13), type = Request (0x00), payload = 39 00 00 02
17:24:58.106 [DEBUG] [b.z.i.p.s.SendDataMessageClass:74 ] - NODE 19: SendData Request. CallBack ID = 57, Status = Transmission complete and ACK received(0)
17:24:58.108 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:63 ] - Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 13 03 70 05 15
17:24:58.109 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:64 ] - Recv message Message: class = SendData (0x13), type = Request (0x00), payload = 39 00 00 02
17:24:58.109 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:65 ] - Checking transaction complete: class=SendData, expected=ApplicationCommandHandler, cancelled=false
17:24:58.111 [DEBUG] [eController$ZWaveReceiveThread:1481 ] - Receive Message = 01 0B 00 04 00 13 05 70 06 15 01 00 84
17:24:58.131 [DEBUG] [eController$ZWaveReceiveThread:1405 ] - Receive queue ADD: Length=1
17:24:58.131 [DEBUG] [b.z.i.protocol.ZWaveController:1163 ] - Receive queue TAKE: Length=0
17:24:58.132 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ] - Assembled message buffer = 01 0B 00 04 00 13 05 70 06 15 01 00 84
17:24:58.133 [DEBUG] [b.z.i.protocol.ZWaveController:1164 ] - Process Message = 01 0B 00 04 00 13 05 70 06 15 01 00 84
17:24:58.134 [DEBUG] [b.z.i.protocol.ZWaveController:192 ] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 13 05 70 06 15 01 00
17:24:58.135 [DEBUG] [ApplicationCommandMessageClass:38 ] - NODE 19: Application Command Request (ALIVE:DONE)
17:24:58.135 [DEBUG] [ApplicationCommandMessageClass:56 ] - NODE 19: Incoming command class CONFIGURATION
17:24:58.136 [DEBUG] [ZWaveConfigurationCommandClass:76 ] - NODE 19: Received Configuration Request
17:24:58.136 [DEBUG] [ZWaveConfigurationCommandClass:121 ] - NODE 19: Node configuration report, parameter = 21, value = 0
17:24:58.137 [DEBUG] [b.z.i.protocol.ZWaveController:635 ] - Notifying event listeners: ZWaveConfigurationParameterEvent
17:24:58.137 [DEBUG] [.z.internal.ZWaveActiveBinding:433 ] - ZwaveIncomingEvent
17:24:58.138 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ] - NODE 19: Got a value event from Z-Wave network, endpoint = 0, command class = CONFIGURATION, value = org.openhab.binding.zwave.internal.protocol.ConfigurationParameter@16dc7c8
17:24:58.139 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:63 ] - Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 13 03 70 05 15
17:24:58.140 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:64 ] - Recv message Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 13 05 70 06 15 01 00
17:24:58.141 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:65 ] - Checking transaction complete: class=ApplicationCommandHandler, expected=ApplicationCommandHandler, cancelled=false
17:24:58.142 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:68 ] - transaction complete!
17:24:58.143 [DEBUG] [b.z.i.protocol.ZWaveController:635 ] - Notifying event listeners: ZWaveTransactionCompletedEvent
17:24:58.144 [DEBUG] [.z.internal.ZWaveActiveBinding:433 ] - ZwaveIncomingEvent
17:24:58.145 [DEBUG] [WaveController$ZWaveSendThread:1327 ] - NODE 19: Response processed after 97ms/3706ms.
becouse i switch the configuration to see what’s happend -
chris
(Chris Jackson)
December 19, 2015, 5:03pm
6
What do you mean? When you set the value, the binding makes 2 requests - the first is to set the value, and the second is to read it back - this is what I was after…
From this sequence, it looks like you have set the value to 0, and it has set this, and read it back correctly - is this what you’re doing?
17:24:57.957 [DEBUG] [.z.i.config.ZWaveConfiguration:1177 ] - Set parameter index '21' to '0'
17:24:58.136 [DEBUG] [ZWaveConfigurationCommandClass:121 ] - NODE 19: Node configuration report, parameter = 21, value = 0
Yes it is. I stop OH and started the z-way-server (i use a razberry board). On z-way there are problems too to store the configuration at the device - so i think it’s more a fibaro problem as an OH problem. The configuration parameters stay yellow … only after some reboots of oh they will get grey/white. Terrible …