Niko Home control I thermostat setpoint

BartSmet · January 12, 2022, 8:32pm

Hi,

I’m using Niko Home control V1, with a connected controller. Integration works fine for lights, switches and rollershutters but I can’t control my thermostats.

When I try to change the setpoint, either via the UI or via a script, this value gets immediately reset by the default day program.
So when my thermostat is in mode 5 with a setpoint of 22 °C and I set it to 23 °C, the command is received (I can see it on the bus communication debug window) and immediately restored to the default day temperature. Moreover, the program has changed as well to the day program (Mode 0).
When I try to change the mode this appears once on the bus, but has no effect at all.

What can be wrong, and how can I debug this further, I don’t have any Java experience.
Tested both on V3.1 and V3.2

Mherwege · January 12, 2022, 9:25pm

Hi Bart,

There has been limited testing with NHC I and thermostats. And I don’t have NHC V1 anymore myself, switched to V2.
There were a few changes recently in the binding on thermostats, but with a focus on V2. However, much of the logic is the same, and it may have an impact on how it behaves in V1 as well. So, you could try testing the development version of the binding I have here. Uninstall the binding from the UI and drop this version in the add-ons folder. Switch on TRACE logging on the binding and get provide the log file so I can have a further look if the development version of the binding does not solve it.

BartSmet · January 12, 2022, 9:54pm

Hi Mark,

Thanks for the swift reply. I removed the binding and placed the file in the add-ons folder. Restarted OpenHab, but can’t find the new version of the binding. How do I activate this one? I suppose I don’t have to reinstall it again through the UI.

Mherwege · January 12, 2022, 9:58pm

It should be there. Your previous configuration should still be there and work. Did you check your things?

One thing maybe, try installing the MQTT binding as well. You don’t have to configure that. It is not required for NHC V1, but MQTT is used with NHC V2 and therefore it is a pre-requisite for the binding. When installed through the UI that pre-requisite gets added automatically.

BartSmet · January 12, 2022, 10:11pm

I installed the MQTT binding as well now. But when I remove the Niko Home control binding through the UI, my current Niko Home control Bridge gets uninitialezed with a HANDLER_MISSING_ERROR

I’m running it on Windows 2019 with Zulu 11.0.13 btw

Mherwege · January 12, 2022, 10:32pm

First uninstall from the UI. The Handler Missing error would be expected. Then add the binding in the add-ons folder. The things should get initialized again with the new version. You can’t have both at the same time.

BartSmet · January 12, 2022, 11:59pm

That worked, after some tweaking to get the logging right , I got the following output :

00:53:47.500 [INFO ] [openhab.event.ItemCommandEvent       ] - Item 'thermostaatliving_Setpoint' received command 18.5
00:53:47.513 [DEBUG] [dler.NikoHomeControlThermostatHandler] - handle command 18.5 °C for nikohomecontrol:thermostat:440e00ee076f:0:setpoint
00:53:47.513 [DEBUG] [internal.protocol.nhc1.NhcThermostat1] - execute thermostat overrule 185 during 60 min for 0
00:53:47.513 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - send json {"id":0,"value1":0,"value2":0,"value3":0,"mode":0,"overrule":185,"overruletime":"01:00","cmd":"executethermostat","event":""}
00:53:47.530 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - received json {"cmd":"executethermostat", "data":{"error":0}}
00:53:47.530 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - execute thermostats success
00:53:47.575 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - received json {"event":"listthermostat","data":[ {"id":0,"measured":206,"setpoint":160,"mode":6,"overrule":185,"overruletime":"01:00","ecosave":0}]}
00:53:47.575 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - Niko Home Control: event execute thermostat 0 with measured 206, setpoint 160, mode 6, overrule 185, overruletime 60, ecosave 0, demand -1
00:53:47.575 [DEBUG] [ntrol.internal.protocol.NhcThermostat] - update channels for 0
00:53:47.638 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - received json {"event":"listthermostat","data":[ {"id":0,"measured":206,"setpoint":160,"mode":0,"overrule":0,"overruletime":"00:00","ecosave":0}]}
00:53:47.638 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - Niko Home Control: event execute thermostat 0 with measured 206, setpoint 160, mode 0, overrule 0, overruletime 0, ecosave 0, demand -1
00:53:47.653 [DEBUG] [ntrol.internal.protocol.NhcThermostat] - update channels for 0
00:53:47.685 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - received json {"event":"listthermostat","data":[ {"id":0,"measured":206,"setpoint":185,"mode":0,"overrule":0,"overruletime":"00:00","ecosave":0}]}
00:53:47.716 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - Niko Home Control: event execute thermostat 0 with measured 206, setpoint 185, mode 0, overrule 0, overruletime 0, ecosave 0, demand -1
00:53:47.716 [DEBUG] [ntrol.internal.protocol.NhcThermostat] - update channels for 0
00:53:47.747 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - received json {"event":"listthermostat","data":[ {"id":0,"measured":206,"setpoint":215,"mode":0,"overrule":0,"overruletime":"00:00","ecosave":0}]}
00:53:47.747 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - Niko Home Control: event execute thermostat 0 with measured 206, setpoint 215, mode 0, overrule 0, overruletime 0, ecosave 0, demand 1
00:53:47.747 [DEBUG] [ntrol.internal.protocol.NhcThermostat] - update channels for 0
00:53:49.076 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":427}}
00:53:49.076 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":427}}
00:53:51.098 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":423}}
00:53:51.098 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":423}}
00:53:53.115 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":423}}
00:53:53.115 [DEBUG] [ol.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":423}}

Mherwege · January 13, 2022, 8:24am

I think I have found what the issue is.
Try this version and see if it fixes it. The fix is already included in my development branch under review.

BartSmet · January 13, 2022, 12:46pm

Hi Mark,

This is a great fix. At first I thought that the overrule time feedback was not working, but it just takes a few minutes. I’ll test it later an give you some feedback.

Many thanks,

Bart.

BartSmet · January 13, 2022, 7:58pm

Still not completely there.
Changing setpoints, mode and overrule time directly works fine.
When changing the setpoint, overrule time is not updated on the channel. When checking at the thermostat, it’s fine at the thermostat and this also updates the overrule Time channel on the Thing. After a few minutes, the time becomes zero on the channel, but it remains counting down in the thermostat itself.

Likewise, when updating the overrule time, the channel is updated an the timer in the thermostat is updated as well.

2022-01-13 20:42:09.380 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":510}}
2022-01-13 20:42:11.369 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":521}}
2022-01-13 20:42:11.369 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":521}}
2022-01-13 20:42:12.322 [DEBUG] [ler.NikoHomeControlThermostatHandler] - handle command 14 for nikohomecontrol:thermostat:440e00ee076f:0:overruletime
2022-01-13 20:42:12.337 [DEBUG] [nternal.protocol.nhc1.NhcThermostat1] - execute thermostat overrule 200 during 14 min for 0
2022-01-13 20:42:12.337 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - send json {"id":0,"overrule":200,"overruletime":"00:14","cmd":"executethermostat"}
2022-01-13 20:42:12.353 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"cmd":"executethermostat", "data":{"error":0}}
2022-01-13 20:42:12.364 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - execute thermostats success
2022-01-13 20:42:12.411 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"listthermostat","data":[ {"id":0,"measured":215,"setpoint":200,"mode":6,"overrule":200,"overruletime":"00:14","ecosave":0}]}
2022-01-13 20:42:12.411 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - Niko Home Control: event execute thermostat 0 with measured 215, setpoint 200, mode 6, overrule 200, overruletime 14, ecosave 0, demand -1
2022-01-13 20:42:12.411 [DEBUG] [trol.internal.protocol.NhcThermostat] - update channels for 0
2022-01-13 20:42:13.366 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":506}}
2022-01-13 20:42:13.366 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":506}}

This value is now present in the thermostat and on the channel.
But after a few minutes, I start seeing this on the debug window :

2022-01-13 20:44:05.807 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":505}}
2022-01-13 20:44:06.494 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"listthermostat","data":[ {"id":1,"measured":230,"setpoint":230,"mode":5,"overrule":0,"overruletime":"00:00","ecosave":0}]}
2022-01-13 20:44:06.494 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - Niko Home Control: event execute thermostat 1 with measured 230, setpoint 230, mode 5, overrule 0, overruletime 0, ecosave 0, demand 0
2022-01-13 20:44:06.494 [DEBUG] [trol.internal.protocol.NhcThermostat] - update channels for 1
2022-01-13 20:44:07.792 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":511}}

(This is my 2nd thermostat, nothing changed on that one)
But then this :

2022-01-13 20:44:19.826 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":513}}
2022-01-13 20:44:19.842 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":513}}
2022-01-13 20:44:21.705 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"listthermostat","data":[ {"id":0,"measured":214,"setpoint":200,"mode":6,"overrule":200,"overruletime":"00:14","ecosave":0}]}
2022-01-13 20:44:21.705 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - Niko Home Control: event execute thermostat 0 with measured 214, setpoint 200, mode 6, overrule 200, overruletime 14, ecosave 0, demand -1
2022-01-13 20:44:21.705 [DEBUG] [trol.internal.protocol.NhcThermostat] - update channels for 0
2022-01-13 20:44:21.846 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":511}}
2022-01-13 20:44:21.846 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":511}}
2022-01-13 20:44:23.851 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":510}}
2022-01-13 20:44:23.867 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":510}}
2022-01-13 20:44:25.641 [DEBUG] [ikoHomeControlBridgeDiscoveryService] - discovery broadcast on 192.168.20.255
2022-01-13 20:44:25.641 [TRACE] [nal.protocol.NikoHomeControlDiscover] - bridge discovery response 443253F1CB00C0A814B5FFFFFF00
2022-01-13 20:44:25.641 [DEBUG] [nal.protocol.NikoHomeControlDiscover] - IP address is /192.168.20.181, unique ID is 443253f1cb00
2022-01-13 20:44:25.641 [DEBUG] [ikoHomeControlBridgeDiscoveryService] - NHC I bridge found at /192.168.20.181
2022-01-13 20:44:25.859 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":510}}
2022-01-13 20:44:25.859 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":510}}
2022-01-13 20:44:27.409 [DEBUG] [very.NikoHomeControlDiscoveryService] - getting devices on 440e00ee076f
2022-01-13 20:44:27.880 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":556}}
2022-01-13 20:44:27.880 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":556}}
2022-01-13 20:44:29.857 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":565}}
2022-01-13 20:44:29.872 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":565}}
2022-01-13 20:44:31.714 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"listthermostat","data":[ {"id":0,"measured":215,"setpoint":200,"mode":6,"overrule":200,"overruletime":"00:14","ecosave":0}]}
2022-01-13 20:44:31.714 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - Niko Home Control: event execute thermostat 0 with measured 215, setpoint 200, mode 6, overrule 200, overruletime 14, ecosave 0, demand -1
2022-01-13 20:44:31.714 [DEBUG] [trol.internal.protocol.NhcThermostat] - update channels for 0
2022-01-13 20:44:31.886 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":564}}
2022-01-13 20:44:31.886 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":564}}
2022-01-13 20:44:33.907 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":560}}
2022-01-13 20:44:33.907 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":560}}
2022-01-13 20:44:35.910 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":560}}
2022-01-13 20:44:35.910 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":560}}
2022-01-13 20:44:37.915 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":555}}
2022-01-13 20:44:37.915 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":555}}
2022-01-13 20:44:39.923 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":561}}
2022-01-13 20:44:39.923 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":561}}
2022-01-13 20:44:41.928 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":558}}
2022-01-13 20:44:41.943 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":558}}
2022-01-13 20:44:43.919 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":560}}
2022-01-13 20:44:43.919 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":560}}
2022-01-13 20:44:45.925 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":562}}
2022-01-13 20:44:45.925 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":562}}
2022-01-13 20:44:46.741 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"listthermostat","data":[ {"id":0,"measured":214,"setpoint":200,"mode":6,"overrule":200,"overruletime":"00:14","ecosave":0}]}
2022-01-13 20:44:46.741 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - Niko Home Control: event execute thermostat 0 with measured 214, setpoint 200, mode 6, overrule 200, overruletime 14, ecosave 0, demand -1
2022-01-13 20:44:46.741 [DEBUG] [trol.internal.protocol.NhcThermostat] - update channels for 0
2022-01-13 20:44:47.942 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":568}}
2022-01-13 20:44:47.942 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":568}}

As soon as these messages appear, the channel goes back to Zero.
What also seems strange is that the overrule time stays 14, even 2 minutes later.

This is not a big deal, but it seems that something is still missing…

Mherwege · January 13, 2022, 8:20pm

Indeed, something is still missing. You get these messages when the measured temperature changes. Unfortunately, NHC V1 sends the original overrule time with it, and not the remaining overrule time. And that causes the overrule time restart in OH UI. I need a smart way to figure out that the message is not for a change of the overrule directly on the thermostat.

Mherwege · January 14, 2022, 4:57pm

I am still not sure I fully understand what is going wrong here. Looking at the code again, I thought this would have been handled correctly.
I did a few changes that may improve it, but I am not sure it is fixed with this. Would you be willing to test again?
The new binding version is under the same link. Just replace yours with this one.

BartSmet · January 15, 2022, 9:54am

Hi Mark,

Installed the new code and triggered a temp increase. Works fine, but now the overruletime channel isn’t updated anymore at all.

2022-01-15 10:27:34.658 [DEBUG] [penhab.core.model.script.Temperatuur] - oldsetpoint: 23 °C to low
2022-01-15 10:27:34.658 [DEBUG] [penhab.core.model.script.Temperatuur] - Setting newsetpoint: 24.0
2022-01-15 10:27:34.658 [DEBUG] [penhab.core.model.script.Temperatuur] - End
2022-01-15 10:27:34.674 [DEBUG] [ler.NikoHomeControlThermostatHandler] - handle command 24 °C for nikohomecontrol:thermostat:440e00ee076f:1:setpoint
2022-01-15 10:27:34.674 [DEBUG] [nternal.protocol.nhc1.NhcThermostat1] - execute thermostat overrule 240 during 60 min for 1
2022-01-15 10:27:34.674 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - send json {"id":1,"overrule":240,"overruletime":"01:00","cmd":"executethermostat"}
2022-01-15 10:27:34.674 [DEBUG] [penhab.core.model.script.Temperatuur] - Temp not reached
2022-01-15 10:27:34.689 [DEBUG] [penhab.core.model.script.Temperatuur] - Already heating, be patient
2022-01-15 10:27:34.689 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"cmd":"executethermostat", "data":{"error":0}}
2022-01-15 10:27:34.705 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - execute thermostats success
2022-01-15 10:27:34.705 [DEBUG] [penhab.core.model.script.Temperatuur] - End
2022-01-15 10:27:34.752 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"listthermostat","data":[ {"id":1,"measured":230,"setpoint":230,"mode":5,"overrule":240,"overruletime":"01:00","ecosave":0}]}
2022-01-15 10:27:34.752 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - Niko Home Control: event execute thermostat 1 with measured 230, setpoint 230, mode 5, overrule 240, overruletime 60, ecosave 0, demand 0
2022-01-15 10:27:34.752 [DEBUG] [trol.internal.protocol.NhcThermostat] - update channels for 1
2022-01-15 10:27:34.752 [DEBUG] [penhab.core.model.script.Temperatuur] - Temp not reached
2022-01-15 10:27:34.752 [DEBUG] [penhab.core.model.script.Temperatuur] - oldsetpoint: 23 °C to low
2022-01-15 10:27:34.752 [DEBUG] [penhab.core.model.script.Temperatuur] - Setting newsetpoint: 24.0
2022-01-15 10:27:34.752 [DEBUG] [penhab.core.model.script.Temperatuur] - End
2022-01-15 10:27:34.768 [DEBUG] [ler.NikoHomeControlThermostatHandler] - handle command 24 °C for nikohomecontrol:thermostat:440e00ee076f:1:setpoint
2022-01-15 10:27:34.768 [DEBUG] [nternal.protocol.nhc1.NhcThermostat1] - execute thermostat overrule 240 during 60 min for 1
2022-01-15 10:27:34.768 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - send json {"id":1,"overrule":240,"overruletime":"01:00","cmd":"executethermostat"}
2022-01-15 10:27:34.768 [DEBUG] [penhab.core.model.script.Temperatuur] - Temp not reached
2022-01-15 10:27:34.783 [DEBUG] [penhab.core.model.script.Temperatuur] - Already heating, be patient
2022-01-15 10:27:34.783 [DEBUG] [penhab.core.model.script.Temperatuur] - End
2022-01-15 10:27:34.783 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"cmd":"executethermostat", "data":{"error":0}}
2022-01-15 10:27:34.783 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - execute thermostats success
2022-01-15 10:27:34.830 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"listthermostat","data":[ {"id":1,"measured":230,"setpoint":240,"mode":5,"overrule":240,"overruletime":"01:00","ecosave":0}]}
2022-01-15 10:27:34.846 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - Niko Home Control: event execute thermostat 1 with measured 230, setpoint 240, mode 5, overrule 240, overruletime 60, ecosave 0, demand 1
2022-01-15 10:27:34.846 [DEBUG] [trol.internal.protocol.NhcThermostat] - update channels for 1
2022-01-15 10:27:34.877 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"listthermostat","data":[ {"id":1,"measured":230,"setpoint":240,"mode":5,"overrule":240,"overruletime":"01:00","ecosave":0}]}
2022-01-15 10:27:34.893 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - Niko Home Control: event execute thermostat 1 with measured 230, setpoint 240, mode 5, overrule 240, overruletime 60, ecosave 0, demand 1
2022-01-15 10:27:34.893 [DEBUG] [trol.internal.protocol.NhcThermostat] - update channels for 1
2022-01-15 10:27:35.911 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"getlive","data":{"channel":0, "v":1585}}
2022-01-15 10:27:35.911 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":1585}

Triggering an update on the thermostaat itself, doesn’t change the overuletime channel neither.

2022-01-15 10:30:32.562 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - not acted on json {"event":"getlive","data":{"channel":0, "v":2880}}
2022-01-15 10:30:33.912 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"listthermostat","data":[ {"id":1,"measured":230,"setpoint":240,"mode":5,"overrule":235,"overruletime":"00:45","ecosave":0}]}
2022-01-15 10:30:33.912 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - Niko Home Control: event execute thermostat 1 with measured 230, setpoint 240, mode 5, overrule 235, overruletime 45, ecosave 0, demand 1
2022-01-15 10:30:33.912 [DEBUG] [trol.internal.protocol.NhcThermostat] - update channels for 1
2022-01-15 10:30:33.974 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - received json {"event":"listthermostat","data":[ {"id":1,"measured":230,"setpoint":235,"mode":5,"overrule":235,"overruletime":"00:45","ecosave":0}]}
2022-01-15 10:30:33.974 [DEBUG] [l.nhc1.NikoHomeControlCommunication1] - Niko Home Control: event execute thermostat 1 with measured 230, setpoint 235, mode 5, overrule 235, overruletime 45, ecosave 0, demand 1
2022-01-15 10:30:33.974 [DEBUG] [trol.internal.protocol.NhcThermostat] - update channels for 1
2022-01-15 10:30:34.006 [DEBUG] [penhab.core.model.script.Temperatuur] - Temp not reached
2022-01-15 10:30:34.006 [DEBUG] [penhab.core.model.script.Temperatuur] - Already heating, be patient

Mherwege · January 15, 2022, 3:59pm

Thanks Bart. Could you also provide the corresponding event.log? I want to see what is going on with the channels. What is in the logs looks normal, but it doesn’t log channel commands or updates here.