HABmin - can't set calibration value back to default (0)

Add-ons Other
,
#1

I’ve recently received an Aeotec Multisensor 6. At first the temperature calibration seemed out so I adjusted the calibration parameter using HABmin2 and things seemed OK. Now the readings seem to have settled but now the readings are out by roughly the calibration change I entered so I need to change the calibration parameter back to default/0.

However using HABmin2 I’m unable to reset this parameter. Having checked the logs I can see this happens when I enter an offset successfully:

2015-12-30 00:50:38.668 [DEBUG] [.z.i.config.ZWaveConfiguration:1091]- doSet domain 'nodes/node4/parameters/configuration201' to '-35'
2015-12-30 00:50:38.922 [DEBUG] [.z.i.config.ZWaveConfiguration:1177]- Set parameter index '201' to '-35'
2015-12-30 00:50:38.925 [DEBUG] [ZWaveConfigurationCommandClass:188 ]- NODE 4: Creating new message for application command CONFIGURATIONCMD_SET
2015-12-30 00:50:38.927 [DEBUG] [o.b.z.i.protocol.SerialMessage:109 ]- NODE 4: Creating empty message of class = SendData (0x13), type = Request (0x00)
2015-12-30 00:50:38.929 [DEBUG] [b.z.i.protocol.ZWaveController:938 ]- Callback ID = 23
2015-12-30 00:50:38.930 [DEBUG] [b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 1
2015-12-30 00:50:38.930 [DEBUG] [WaveController$ZWaveSendThread:1211]- Took message from queue for sending. Queue length = 0
2015-12-30 00:50:38.931 [DEBUG] [ZWaveConfigurationCommandClass:160 ]- NODE 4: Creating new message for application command CONFIGURATIONCMD_GET
2015-12-30 00:50:38.933 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 0C 00 13 04 05 70 04 C9 01 DD 25 17 B2 
2015-12-30 00:50:38.933 [DEBUG] [o.b.z.i.protocol.SerialMessage:109 ]- NODE 4: Creating empty message of class = SendData (0x13), type = Request (0x00)
2015-12-30 00:50:38.935 [DEBUG] [WaveController$ZWaveSendThread:1268]- NODE 4: Sending REQUEST Message = 01 0C 00 13 04 05 70 04 C9 01 DD 25 17 B2 
2015-12-30 00:50:38.936 [DEBUG] [b.z.i.protocol.ZWaveController:938 ]- Callback ID = 24
2015-12-30 00:50:38.938 [DEBUG] [b.z.i.protocol.ZWaveController:620 ]- Enqueueing message. Queue length = 1
2015-12-30 00:50:38.945 [DEBUG] [eController$ZWaveReceiveThread:1481]- Receive Message = 01 04 01 13 01 E8 
2015-12-30 00:50:38.947 [DEBUG] [eController$ZWaveReceiveThread:1405]- Receive queue ADD: Length=1
2015-12-30 00:50:38.947 [DEBUG] [b.z.i.protocol.ZWaveController:1163]- Receive queue TAKE: Length=0
2015-12-30 00:50:38.948 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 04 01 13 01 E8 
2015-12-30 00:50:38.949 [DEBUG] [b.z.i.protocol.ZWaveController:1164]- Process Message = 01 04 01 13 01 E8 
2015-12-30 00:50:38.950 [DEBUG] [b.z.i.protocol.ZWaveController:192 ]- Message: class = SendData (0x13), type = Response (0x01), payload = 01 
2015-12-30 00:50:38.951 [DEBUG] [b.z.i.p.s.SendDataMessageClass:38  ]- NODE 4: Sent Data successfully placed on stack.
2015-12-30 00:50:38.962 [DEBUG] [eController$ZWaveReceiveThread:1481]- Receive Message = 01 07 00 13 17 00 00 02 FE 
2015-12-30 00:50:38.967 [DEBUG] [eController$ZWaveReceiveThread:1405]- Receive queue ADD: Length=1
2015-12-30 00:50:38.967 [DEBUG] [b.z.i.protocol.ZWaveController:1163]- Receive queue TAKE: Length=0
2015-12-30 00:50:38.969 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 09 00 13 17 00 00 02 00 00 F0 
2015-12-30 00:50:38.970 [DEBUG] [b.z.i.protocol.ZWaveController:1164]- Process Message = 01 09 00 13 17 00 00 02 00 00 F0 
2015-12-30 00:50:38.971 [DEBUG] [b.z.i.protocol.ZWaveController:192 ]- Message: class = SendData (0x13), type = Request (0x00), payload = 17 00 00 02 
2015-12-30 00:50:38.972 [DEBUG] [b.z.i.p.s.SendDataMessageClass:74  ]- NODE 4: SendData Request. CallBack ID = 23, Status = Transmission complete and ACK received(0)
2015-12-30 00:50:38.973 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:63  ]- Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 04 05 70 04 C9 01 DD 
2015-12-30 00:50:38.974 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:64  ]- Recv message Message: class = SendData (0x13), type = Request (0x00), payload = 17 00 00 02 
2015-12-30 00:50:38.975 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:65  ]- Checking transaction complete: class=SendData, expected=SendData, cancelled=false
2015-12-30 00:50:38.976 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:68  ]-          transaction complete!
2015-12-30 00:50:38.976 [DEBUG] [b.z.i.protocol.ZWaveController:635 ]- Notifying event listeners: ZWaveTransactionCompletedEvent
2015-12-30 00:50:38.977 [DEBUG] [.z.internal.ZWaveActiveBinding:433 ]- ZwaveIncomingEvent
2015-12-30 00:50:38.977 [DEBUG] [WaveController$ZWaveSendThread:1327]- NODE 4: Response processed after 41ms/3389ms.
2015-12-30 00:50:38.978 [DEBUG] [WaveController$ZWaveSendThread:1211]- Took message from queue for sending. Queue length = 0
2015-12-30 00:50:38.979 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 0A 00 13 04 03 70 05 C9 25 18 60 
2015-12-30 00:50:38.981 [DEBUG] [WaveController$ZWaveSendThread:1268]- NODE 4: Sending REQUEST Message = 01 0A 00 13 04 03 70 05 C9 25 18 60 
2015-12-30 00:50:38.990 [DEBUG] [eController$ZWaveReceiveThread:1481]- Receive Message = 01 04 01 13 01 E8 
2015-12-30 00:50:38.992 [DEBUG] [eController$ZWaveReceiveThread:1405]- Receive queue ADD: Length=1
2015-12-30 00:50:38.992 [DEBUG] [b.z.i.protocol.ZWaveController:1163]- Receive queue TAKE: Length=0
2015-12-30 00:50:38.994 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 04 01 13 01 E8 
2015-12-30 00:50:38.994 [DEBUG] [b.z.i.protocol.ZWaveController:1164]- Process Message = 01 04 01 13 01 E8 
2015-12-30 00:50:38.995 [DEBUG] [b.z.i.protocol.ZWaveController:192 ]- Message: class = SendData (0x13), type = Response (0x01), payload = 01 
2015-12-30 00:50:38.996 [DEBUG] [b.z.i.p.s.SendDataMessageClass:38  ]- NODE 4: Sent Data successfully placed on stack.
2015-12-30 00:50:39.007 [DEBUG] [eController$ZWaveReceiveThread:1481]- Receive Message = 01 07 00 13 18 00 00 02 F1 
2015-12-30 00:50:39.009 [DEBUG] [eController$ZWaveReceiveThread:1405]- Receive queue ADD: Length=1
2015-12-30 00:50:39.009 [DEBUG] [b.z.i.protocol.ZWaveController:1163]- Receive queue TAKE: Length=0
2015-12-30 00:50:39.010 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 09 00 13 18 00 00 02 00 00 FF 
2015-12-30 00:50:39.011 [DEBUG] [b.z.i.protocol.ZWaveController:1164]- Process Message = 01 09 00 13 18 00 00 02 00 00 FF 
2015-12-30 00:50:39.012 [DEBUG] [b.z.i.protocol.ZWaveController:192 ]- Message: class = SendData (0x13), type = Request (0x00), payload = 18 00 00 02 
2015-12-30 00:50:39.013 [DEBUG] [b.z.i.p.s.SendDataMessageClass:74  ]- NODE 4: SendData Request. CallBack ID = 24, Status = Transmission complete and ACK received(0)
2015-12-30 00:50:39.026 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:63  ]- Sent message Message: class = SendData (0x13), type = Request (0x00), payload = 04 03 70 05 C9 
2015-12-30 00:50:39.028 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:64  ]- Recv message Message: class = SendData (0x13), type = Request (0x00), payload = 18 00 00 02 
2015-12-30 00:50:39.029 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:65  ]- Checking transaction complete: class=SendData, expected=ApplicationCommandHandler, cancelled=false
2015-12-30 00:50:39.031 [DEBUG] [eController$ZWaveReceiveThread:1481]- Receive Message = 01 0B 00 04 00 04 05 70 06 C9 01 DD 92 
2015-12-30 00:50:39.033 [DEBUG] [eController$ZWaveReceiveThread:1405]- Receive queue ADD: Length=1
2015-12-30 00:50:39.033 [DEBUG] [b.z.i.protocol.ZWaveController:1163]- Receive queue TAKE: Length=0
2015-12-30 00:50:39.035 [DEBUG] [o.b.z.i.protocol.SerialMessage:233 ]- Assembled message buffer = 01 0B 00 04 00 04 05 70 06 C9 01 DD 92 
2015-12-30 00:50:39.037 [DEBUG] [b.z.i.protocol.ZWaveController:1164]- Process Message = 01 0B 00 04 00 04 05 70 06 C9 01 DD 92 
2015-12-30 00:50:39.038 [DEBUG] [b.z.i.protocol.ZWaveController:192 ]- Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 04 05 70 06 C9 01 DD 
2015-12-30 00:50:39.039 [DEBUG] [ApplicationCommandMessageClass:38  ]- NODE 4: Application Command Request (ALIVE:DONE)
2015-12-30 00:50:39.040 [DEBUG] [ApplicationCommandMessageClass:56  ]- NODE 4: Incoming command class CONFIGURATION
2015-12-30 00:50:39.040 [DEBUG] [ZWaveConfigurationCommandClass:76  ]- NODE 4: Received Configuration Request
2015-12-30 00:50:39.041 [DEBUG] [ZWaveConfigurationCommandClass:121 ]- NODE 4: Node configuration report, parameter = 201, value = -35
2015-12-30 00:50:39.042 [DEBUG] [b.z.i.protocol.ZWaveController:635 ]- Notifying event listeners: ZWaveConfigurationParameterEvent
2015-12-30 00:50:39.043 [DEBUG] [.z.internal.ZWaveActiveBinding:433 ]- ZwaveIncomingEvent
2015-12-30 00:50:39.044 [DEBUG] [.z.internal.ZWaveActiveBinding:450 ]- NODE 4: Got a value event from Z-Wave network, endpoint = 0, command class = CONFIGURATION, value = org.openhab.binding.zwave.internal.protocol.ConfigurationParameter@4a0994
2015-12-30 00:50:39.085 [DEBUG] [.b.z.i.p.i.ZWaveNodeSerializer:107 ]- NODE 4: Serializing to file ./userdata/zwave/node4.xml

However when I try and set the calibration back to ‘0’ this happens:

2016-01-01 15:57:15.899 [DEBUG] [.z.i.config.ZWaveConfiguration:1091]- doSet domain 'nodes/node4/parameters/configuration201' to ''
2016-01-01 15:57:16.131 [DEBUG] [.z.i.config.ZWaveConfiguration:1177]- Set parameter index '201' to ''

but it doesn’t create the message to send to the device to amend the config. Is this a bug? Or is there another way to reset this specific configuration without factory resetting the device?

Thanks

#2

any ideas @chris?

#3

bump

#4

Sorry - missed this.
It’s strange - I don’t see any reason for this. I guess HABmin is filtering out the 0, but I’m not sure why. What happens if you use a value of 1 instead - does it still do the sae, or does that work?

#5

Hi Chris

A value of 1 is accepted, which is what I’ve set it at for the time being. Do you want me to raise an issue for this?

#6

I think for now you might need to live with it as I’m not maintaining this HABmin2 branch now (ie the branch of HABmin2 that works with the openhab1 zwave binding). The current HABmin2 branch is only for the OH2 zwave binding which I hope (!!) to get out as soon as I resolve the issue with the database (hopefully very soon).

(I hope that makes sense - it’s probably confusing). If the problem still persists when I release the new version, which I hope it won’t, then yes, please raise an issue.

#7

Thanks for looking into this.

Is there a repo that we can already try the new zwave binding? If not I’ll be patiently waiting as I’m trying to move over to OH2 binding as soon as possible.

#8

If you want to compile it yourself, and add database entries, then it’s in my repo on github, but it’s not released as a binary yet…

#9

Which repo and branch? I had a nose there earlier but couldn’t find any recently updated branches in the HABmin2 repo so I assume I wasn’t looking in the right place.

#10

It’s here…
https://github.com/cdjackson/openhab2/tree/zwave-master

I’m still working through the final database issues as per my posting yesterday -;