Yes, if you are using the snapshot version of OH (ie 2.4) then when you install the binding, it will use the latest snapshot.
And if it is already installed, I will have to delete and then add the z-wave binding? Will I then have to re-add all z-wave things?
I think if you are doing a complete upgrade, then it should also be updated, but you might need to clear the cache to ensure that old bindings are removed.
No - they will still be there. However, if the thing definition changes, then you will need to delete the thing, and add it back - otherwise the channels will be the same.
Alright, deleting cache, deleting thing, adding thing didnât work. But thatâs probably because it is a TF016 Multireg thermostat and not a HeatIt one⊠
So thatâs all on me. However, I believe it is (pretty much) the same thermostat as the heatit-one. Which might mean that the Multireg-thing can be ugraded in the same way as the HeatIt one. Is that correct?
We can add the channel, if the device sends the same data - the question is if it does this or not? Have you observed this in the debug logs?
It looks like the behavior is the same (and I do believe the two thermostats are the same except for the name).
Log when I set to lower heating setpoint so heating stopped:
2018-08-12 15:17:20.154 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 8: Application Command Request (ALIVE:DONE)
2018-08-12 15:17:20.158 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Starting initialisation from DONE
2018-08-12 15:17:20.166 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 8: Incoming command class BASIC
2018-08-12 15:17:20.170 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 8: Received Basic Request
2018-08-12 15:17:20.173 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 8: Basic Set sent to the controller will be processed as Basic Report
2018-08-12 15:17:20.177 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 8: Basic report, value = 0x00
2018-08-12 15:17:20.184 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-08-12 15:17:20.188 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 0
And on:
2018-08-12 15:19:13.510 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 08 03 20 01 FF 27
2018-08-12 15:19:13.514 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-08-12 15:19:13.516 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 08 03 20 01 FF 27
2018-08-12 15:19:13.518 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 08 03 20 01 FF 27
2018-08-12 15:19:13.521 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 08 03 20 01 FF
2018-08-12 15:19:13.523 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 8: Application Command Request (ALIVE:DONE)
2018-08-12 15:19:13.524 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 8: Starting initialisation from DONE
2018-08-12 15:19:13.526 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1a27a58 already registered
2018-08-12 15:19:13.529 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 8: Incoming command class BASIC
2018-08-12 15:19:13.530 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 8: Received Basic Request
2018-08-12 15:19:13.532 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 8: Basic Set sent to the controller will be processed as Basic Report
2018-08-12 15:19:13.534 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 8: Basic report, value = 0xFF
2018-08-12 15:19:13.536 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2018-08-12 15:19:13.538 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-08-12 15:19:13.540 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
2018-08-12 15:19:13.542 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 28: Transaction not completed: node address inconsistent. lastSent=28, incoming=255
There are two versions of this device - my guess is you have the one that has not been configured with this channel? Can you advise the version please?
Multireg 16A 3600W
I want to confirm the software version running in your device so we can be sure that this is the problem.
Under âFirmware Versionâ in HABmin it says: 1.8
Ok, thanks. This version doesnât have the channel configured in the database so it will need to be updated. Iâll do this now and the binding will be updated in a few days - hopefully it will fix the issue for you.
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/412
1 Like
Great, thanks and thanks for your (very) quick responses as well. When the binding is updated, will I then update to the new binding by running config tool -> openHAB related -> openHAB unstable to get the latest snapshot build?
Hmmm - Iâm not sure I can answer that - sorry. Iâm not sure what system youâre running and am not familiar with âconfig toolâ. What you normally do if you are using the snapshot branch (which is probably the unstable on your install) is to uninstall the binding in PaperUI, wait 30 seconds, then reinstall it.
You will need to delete the thing and add it back again (no need to exclude/include) so that it picks up the latest thing definition.
Gotcha.
Thanks - my devices also have Firmware version 1.8 (and I would also call them Multireg 16A 3600 W).
And when you delete the thing and then add it anew, you see the new channel? I donât (yet).
What version are you running?
I was on: openHAB 2.4.0~20180805114935-1 (Build #1326).
I upgraded now to: openHAB 2.4.0~20180813124523-1 (Build #1330)
Then:
- Deleted the thing in HABmin
- Discovered the thing in HABmin
I still see only the six channels that have been there all the time:
Sensor (temperature)
sensor_temperature Number
Thermostat mode
thermostat_mode Number
Setpoint (heating)
thermostat_setpoint_heating Number
Setpoint (heating economy)
thermostat_setpoint_heating_econ
Setpoint (furnace)
thermostat_setpoint_furnace
Sensor mode
config_decimal_param2 Number
This update was only done a few days ago, so it wonât actually be in the binding yet. Please wait a few days and it should be there.
I check every day, still no changes as of now. I am on openhbianpi, latest and greatest and what I am doing is:
Deleting the thing from PaperUI
Discovering the thing in PaperUI