Niko Home Control II

Mherwege · January 10, 2019, 4:43pm

Did it work as expected?

The log is hard to read. It looks like the linefeeds have been removed. Can you also put it in block quotes on this forum, makes it easier?

My first impression is that the right command are sent, but I don’t see anything coming back.

Can you switch on TRACE logging? It should also show the return messages I fail to interpret.

blatruwe · January 10, 2019, 5:55pm

There is indeed no reply. I executed the same with the trace enabled. I used the code tags, but the quote seems indeed more readable. Cleaned up my previous replies as well.

18:54:29.375 [INFO ] [smarthome.event.ItemCommandEvent     ] - Item 'ThermostaatLiving_Mode' received command 3
18:54:29.379 [DEBUG] [dler.NikoHomeControlThermostatHandler] - Niko Home Control: handle command 3 for nikohomecontrol:thermostat:443b00ee4b2a:d4187ab8-194b-492e-9770-6d1e986134f9:mode
18:54:29.390 [INFO ] [arthome.event.ItemStatePredictedEvent] - ThermostaatLiving_Mode predicted to become 3
18:54:29.404 [DEBUG] [internal.protocol.nhc2.NhcThermostat2] - Niko Home Control: execute thermostat mode 3 for d4187ab8-194b-492e-9770-6d1e986134f9
18:54:29.412 [DEBUG] [rnal.protocol.nhc2.NhcMqttConnection2] - Niko Home Control: connection state CONNECTED for 127_0_1_1-nikohomecontrol_bridge2_443b00ee4b2a-profile
18:54:29.416 [INFO ] [smarthome.event.ItemStateChangedEvent] - ThermostaatLiving_Mode changed from 1 to 3
18:54:29.420 [DEBUG] [rnal.protocol.nhc2.NhcMqttConnection2] - Niko Home Control: publish 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/cmd, {"Method":"devices.control","ErrCode":"","ErrMessage":"","Params":[{"Devices":[{"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9","Properties":[{"Program":"Off","OverruleActive":"False"}]}]}]}
18:54:29.439 [TRACE] [ol.nhc2.NikoHomeControlCommunication2] - Niko Home Control: not acted on received message topic 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/cmd, payload {"Method":"devices.control","ErrCode":"","ErrMessage":"","Params":[{"Devices":[{"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9","Properties":[{"Program":"Off","OverruleActive":"False"}]}]}]}

bccrew · January 10, 2019, 7:46pm

@blatruwe

Did you have connection problems because of the 127.0.1.1 IP address? What does ifconfig give as output on your system?

Because I notice that your client ID is still 127_0_1_1-nikohomecontrol_bridge2 and your network is 192.168.123.0/24 ?

blatruwe · January 10, 2019, 8:00pm

My network is indeed 192.168.123.0/24, the problem is gone everytime I enable the debug traces, so hard to troubleshoot… Now it works well with the 127_0_1_1 client ID.

I ran the openhab on 2 systems with similar behavior (1 RPi and a VM with ubuntu). I still have some wireshark traces from the first time I wanted to try to set up the openhab, there I see the encrypted TLS packets passing, so I assume the IP is not the issue. I will take again a tcpdump when the issue pops up again.

Mherwege · January 10, 2019, 8:34pm

@blatruwe
Brecht,
The last line is normal. It is the echo of the cmd, so should not do anything. I was expecting a control/devices/rsp or evt line, but don’t see one.
What happens in the log if you control the thermostat from somewhere else? Do you see an update in OH?

blatruwe · January 10, 2019, 8:48pm

this is when I change via the touchscreen app:

21:47:07.993 [DEBUG] [ol.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/evt, payload {"Method":"devices.status","Params":[{"Devices":[{"Properties":[{"OverruleActive":"True"},{"OverruleTime":"5"},{"SetpointTemperature":"19.00"},{"OverruleSetpoint":"19.00"}],"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9"}]}]}
21:47:08.013 [DEBUG] [ol.nhc2.NikoHomeControlCommunication2] - Niko Home Control: setting thermostat d4187ab8-194b-492e-9770-6d1e986134f9 with measured 200, setpoint 190, mode 0, overrule 190, overruletime 5, ecosave 0
21:47:08.064 [DEBUG] [ntrol.internal.protocol.NhcThermostat] - Niko Home Control: update channels for d4187ab8-194b-492e-9770-6d1e986134f9
21:47:08.091 [INFO ] [smarthome.event.ItemStateChangedEvent] - ThermostaatLiving_OverruleTime changed from 0 to 5
21:47:08.109 [INFO ] [smarthome.event.ItemStateChangedEvent] - ThermostaatLiving_Setpoint changed from 14.0 °C to 19.0 °C
21:47:08.114 [INFO ] [smarthome.event.ItemStateChangedEvent] - ThermostaatLiving_Mode changed from 1 to 0

Mherwege · January 10, 2019, 10:02pm

Thanks Brecht,

Do you see anything appearing in the logs 5 minutes later? I would expect an event setting OverruleActive to False.

bccrew · January 11, 2019, 3:32pm

Mark,

Since your change to the function addr.getHostAddress() that determines the IP addres for the clientID, I also have a clientID starting with 127_0_1_1

Not that the clientID matters that much but just so you know… I guess there will always be exceptions depending on the host OS for openHAB. So maybe it’s good as it is now?

blatruwe · January 11, 2019, 6:00pm

correct, 5 mins later the OverruleActive becomes false:

2019-01-10 21:51:47.337 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic public/system/evt, payload {"Method":"time.published","Params":[{"TimeInfo":[{"GMTOffset":"3600","Timezone":"Europe/Brussels","IsDST":"0","UTCTime":"20190110205147"}]}]}
2019-01-10 21:51:47.343 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic 4faaca81-4034-494d-afc3-b7d2c676039f/system/evt, payload {"Method":"time.published","Params":[{"TimeInfo":[{"GMTOffset":"3600","Timezone":"Europe/Brussels","IsDST":"0","UTCTime":"20190110205147"}]}]}
2019-01-10 21:52:07.992 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/evt, payload {"Method":"devices.status","Params":[{"Devices":[{"Properties":[{"OverruleActive":"False"}],"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9"}]}]}
2019-01-10 21:52:07.998 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: setting thermostat d4187ab8-194b-492e-9770-6d1e986134f9 with measured 200, setpoint 190, mode 0, overrule 0, overruletime 0, ecosave 0
2019-01-10 21:52:08.004 [DEBUG] [trol.internal.protocol.NhcThermostat] - Niko Home Control: update channels for d4187ab8-194b-492e-9770-6d1e986134f9
2019-01-10 21:52:08.052 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/evt, payload {"Method":"devices.status","Params":[{"Devices":[{"Properties":[{"SetpointTemperature":"14.00"}],"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9"}]}]}
2019-01-10 21:52:08.058 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: setting thermostat d4187ab8-194b-492e-9770-6d1e986134f9 with measured 200, setpoint 140, mode 0, overrule 0, overruletime 0, ecosave 0
2019-01-10 21:52:08.063 [DEBUG] [trol.internal.protocol.NhcThermostat] - Niko Home Control: update channels for d4187ab8-194b-492e-9770-6d1e986134f9
2019-01-10 21:52:17.337 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic public/system/evt, payload {"Method":"time.published","Params":[{"TimeInfo":[{"GMTOffset":"3600","Timezone":"Europe/Brussels","IsDST":"0","UTCTime":"20190110205217"}]}]}
2019-01-10 21:52:17.344 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic 4faaca81-4034-494d-afc3-b7d2c676039f/system/evt, payload {"Method":"time.published","Params":[{"TimeInfo":[{"GMTOffset":"3600","Timezone":"Europe/Brussels","IsDST":"0","UTCTime":"20190110205217"}]}]}
2019-01-10 21:52:33.525 [DEBUG] [ikoHomeControlBridgeDiscoveryService] - Niko Home Control: discovery broadcast on 192.168.123.255

Mherwege · January 11, 2019, 7:04pm

It is not ideal. The purpose of including the ip address in the first place was to have a unique client id if I connect with 2 different OH instances from different machines (think prod and test environments), to avoid mqtt issues. The client id is used by the server to know what clients have subscribed to what. If the client id is the same, we would run into problems.
I understand why it happens now, just need to find the most efficient fix.

Mherwege · January 11, 2019, 7:08pm

@blatruwe Can you put the binding back in trace mode and do the full sequence again? Do it once from the touchscreen, and then the same from OH. In trace mode, I would also see the cmd messages. I can then compare an see if there is a difference. At the moment I don’t understand why it does not work from OH.

bccrew · January 11, 2019, 7:18pm

@Mherwege

Maybe take a look at this? It should be platform independant.

I suppose the hard disk’s serialnumber would be an idea? Then, calculate a hash from that to generate a unique string? A hard drive doesn’t change that much in a system right? Or a CPU serial number? Of course it should work on Windows, Linux, OSX, ARM devices.

The OpenHAB systeminfo binding already uses this

Mherwege · January 11, 2019, 7:28pm

@bccrew It is an idea.
It is also possible to get the real host ip used for the communication with the CoCo from the connection info when reading the discovery package response. But that happens at another place in the code, so I would have to pass it around with some extra method calls.
There is also a network service in the Eclipse framework that can list all ip addresses for a host (I contributed to it, as I did need it for this binding, when doing the UDP discovery). I don’t want to call this directly from the place in the code where I need it though, as I have kept this layer of the code, on purpose, only loosely coupled with the OH framework (to make independent use easier).

blatruwe · January 11, 2019, 7:33pm

the above output were taken with trace mode enabled. There is no more output than this. Is there something else I should enable?

openhab> log:get
Logger                                             │ Level
───────────────────────────────────────────────────┼──────
ROOT                                               │ WARN
javax.jmdns                                        │ ERROR
nikohomecontrol                                    │ TRACE
org.apache.karaf.jaas.modules.audit                │ INFO
org.apache.karaf.kar.internal.KarServiceImpl       │ ERROR
org.apache.karaf.shell.support                     │ OFF
org.apache.sshd                                    │ ERROR
org.eclipse.lsp4j                                  │ OFF
org.eclipse.smarthome                              │ INFO
org.jupnp                                          │ ERROR
org.openhab                                        │ INFO
org.openhab.binding.nikohomecontrol                │ TRACE
org.ops4j.pax.url.mvn.internal.AetherBasedResolver │ ERROR
org.ops4j.pax.web.pax-web-runtime                  │ OFF
smarthome.event                                    │ INFO
smarthome.event.InboxUpdatedEvent                  │ ERROR
smarthome.event.ItemAddedEvent                     │ ERROR
smarthome.event.ItemRemovedEvent                   │ ERROR
smarthome.event.ItemStateEvent                     │ ERROR
smarthome.event.ThingAddedEvent                    │ ERROR
smarthome.event.ThingRemovedEvent                  │ ERROR
smarthome.event.ThingStatusInfoEvent               │ ERROR
openhab>

Mherwege · January 11, 2019, 7:34pm

OK. Did you use the same profile on the touchscreen was with OH? If not, that could explain why the cmd messages are not visible to OH.

blatruwe · January 11, 2019, 7:42pm

It was indeed on a different profile. Now with the same profile, this is the output when the touchscreen changes anything

20:40:50.250 [DEBUG] [ol.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic public/system/evt, payload {"Method":"time.published","Params":[{"TimeInfo":[{"GMTOffset":"3600","Timezone":"Europe/Brussels","IsDST":"0","UTCTime":"20190111194050"}]}]}
20:40:50.264 [DEBUG] [ol.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic 4faaca81-4034-494d-afc3-b7d2c676039f/system/evt, payload {"Method":"time.published","Params":[{"TimeInfo":[{"GMTOffset":"3600","Timezone":"Europe/Brussels","IsDST":"0","UTCTime":"20190111194050"}]}]}
20:41:02.953 [TRACE] [ol.nhc2.NikoHomeControlCommunication2] - Niko Home Control: not acted on received message topic 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/cmd, payload {"Params":[{"Devices":[{"Traits":[],"Parameters":[],"Properties":[{"OverruleActive":"True"},{"OverruleSetpoint":"20"},{"OverruleTime":"60"}],"PropertyDefinitions":[],"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9","Technology":null,"Type":null,"Model":null,"Name":null}]}],"Method":"devices.control","ErrCode":"","ErrMessage":""}
20:41:03.078 [DEBUG] [ol.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/evt, payload {"Method":"devices.status","Params":[{"Devices":[{"Properties":[{"OverruleActive":"True"},{"OverruleTime":"60"},{"OverruleSetpoint":"20.00"}],"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9"}]}]}
20:41:03.097 [DEBUG] [ol.nhc2.NikoHomeControlCommunication2] - Niko Home Control: setting thermostat d4187ab8-194b-492e-9770-6d1e986134f9 with measured 195, setpoint 200, mode 0, overrule 200, overruletime 60, ecosave 0
20:41:03.103 [DEBUG] [ntrol.internal.protocol.NhcThermostat] - Niko Home Control: update channels for d4187ab8-194b-492e-9770-6d1e986134f9
20:41:03.158 [INFO ] [smarthome.event.ItemStateChangedEvent] - ThermostaatLiving_Mode changed from 1 to 0
20:41:20.251 [DEBUG] [ol.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic public/system/evt, payload {"Method":"time.published","Params":[{"TimeInfo":[{"GMTOffset":"3600","Timezone":"Europe/Brussels","IsDST":"0","UTCTime":"20190111194120"}]}]}

Mherwege · January 11, 2019, 8:28pm

@blatruwe A loaded a new version with some code changes. There was a difference in the message format. I hope it is solved now.
@bccrew The code also contains a fix for the ip address. I didn’t use the HD serial number suggestion, as it would introduce a new library dependency in the binding just for this.
Let me know how far we get with this, before I push an update to github.

blatruwe · January 11, 2019, 8:39pm

it works Changes on the openhab now also reflect on the touchscreen

2019-01-11 21:34:28.951 [DEBUG] [ler.NikoHomeControlThermostatHandler] - Niko Home Control: handle command 20.5 °C for nikohomecontrol:thermostat:443b00ee4b2a:d4187ab8-194b-492e-9770-6d1e986134f9:setpoint
2019-01-11 21:34:28.963 [DEBUG] [nternal.protocol.nhc2.NhcThermostat2] - Niko Home Control: execute thermostat overrule 205 during 5 min for d4187ab8-194b-492e-9770-6d1e986134f9
2019-01-11 21:34:28.981 [DEBUG] [nal.protocol.nhc2.NhcMqttConnection2] - Niko Home Control: connection state CONNECTED for 192_168_123_204-nikohomecontrol_bridge2_443b00ee4b2a-profile
2019-01-11 21:34:28.987 [DEBUG] [nal.protocol.nhc2.NhcMqttConnection2] - Niko Home Control: publish 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/cmd, {"Method":"devices.control","ErrCode":"","ErrMessage":"","Params":[{"Devices":[{"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9","Properties":[{"OverruleActive":"True"},{"OverruleSetpoint":"20"},{"OverruleTime":"5"}]}]}]}
2019-01-11 21:34:28.998 [TRACE] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: not acted on received message topic 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/cmd, payload {"Method":"devices.control","ErrCode":"","ErrMessage":"","Params":[{"Devices":[{"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9","Properties":[{"OverruleActive":"True"},{"OverruleSetpoint":"20"},{"OverruleTime":"5"}]}]}]}
2019-01-11 21:34:29.123 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/evt, payload {"Method":"devices.status","Params":[{"Devices":[{"Properties":[{"OverruleActive":"True"},{"OverruleTime":"5"},{"OverruleSetpoint":"20.00"}],"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9"}]}]}
2019-01-11 21:34:29.127 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: setting thermostat d4187ab8-194b-492e-9770-6d1e986134f9 with measured 200, setpoint 200, mode 0, overrule 200, overruletime 5, ecosave 0
2019-01-11 21:34:29.131 [DEBUG] [trol.internal.protocol.NhcThermostat] - Niko Home Control: update channels for d4187ab8-194b-492e-9770-6d1e986134f9
2019-01-11 21:34:39.050 [DEBUG] [ikoHomeControlBridgeDiscoveryService] - Niko Home Control: discovery broadcast on 192.168.123.255
2019-01-11 21:34:39.063 [DEBUG] [nal.protocol.NikoHomeControlDiscover] - Niko Home Control: IP address is /192.168.123.184, unique ID is 443b00ee4b2a
2019-01-11 21:34:39.070 [DEBUG] [ikoHomeControlBridgeDiscoveryService] - Niko Home Control: NHC II bridge found at /192.168.123.184
2019-01-11 21:35:10.765 [DEBUG] [ler.NikoHomeControlThermostatHandler] - Niko Home Control: handle command 1 for nikohomecontrol:thermostat:443b00ee4b2a:d4187ab8-194b-492e-9770-6d1e986134f9:mode
2019-01-11 21:35:10.776 [DEBUG] [nternal.protocol.nhc2.NhcThermostat2] - Niko Home Control: execute thermostat mode 1 for d4187ab8-194b-492e-9770-6d1e986134f9
2019-01-11 21:35:10.787 [DEBUG] [nal.protocol.nhc2.NhcMqttConnection2] - Niko Home Control: connection state CONNECTED for 192_168_123_204-nikohomecontrol_bridge2_443b00ee4b2a-profile
2019-01-11 21:35:10.798 [DEBUG] [nal.protocol.nhc2.NhcMqttConnection2] - Niko Home Control: publish 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/cmd, {"Method":"devices.control","ErrCode":"","ErrMessage":"","Params":[{"Devices":[{"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9","Properties":[{"OverruleActive":"False"},{"Program":"Night"}]}]}]}
2019-01-11 21:35:10.811 [TRACE] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: not acted on received message topic 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/cmd, payload {"Method":"devices.control","ErrCode":"","ErrMessage":"","Params":[{"Devices":[{"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9","Properties":[{"OverruleActive":"False"},{"Program":"Night"}]}]}]}
2019-01-11 21:35:10.947 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/evt, payload {"Method":"devices.status","Params":[{"Devices":[{"Properties":[{"OverruleActive":"False"},{"Program":"Night"}],"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9"}]}]}
2019-01-11 21:35:10.956 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: setting thermostat d4187ab8-194b-492e-9770-6d1e986134f9 with measured 200, setpoint 200, mode 1, overrule 0, overruletime 0, ecosave 0
2019-01-11 21:35:10.963 [DEBUG] [trol.internal.protocol.NhcThermostat] - Niko Home Control: update channels for d4187ab8-194b-492e-9770-6d1e986134f9
2019-01-11 21:35:11.090 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/evt, payload {"Method":"devices.status","Params":[{"Devices":[{"Properties":[{"SetpointTemperature":"14.00"},{"Demand":"None"}],"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9"}]}]}
2019-01-11 21:35:11.101 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: setting thermostat d4187ab8-194b-492e-9770-6d1e986134f9 with measured 200, setpoint 140, mode 0, overrule 0, overruletime 0, ecosave 0
2019-01-11 21:35:11.110 [DEBUG] [trol.internal.protocol.NhcThermostat] - Niko Home Control: update channels for d4187ab8-194b-492e-9770-6d1e986134f9
2019-01-11 21:35:19.508 [DEBUG] [ler.NikoHomeControlThermostatHandler] - Niko Home Control: handle command 2 for nikohomecontrol:thermostat:443b00ee4b2a:d4187ab8-194b-492e-9770-6d1e986134f9:mode
2019-01-11 21:35:19.520 [DEBUG] [nternal.protocol.nhc2.NhcThermostat2] - Niko Home Control: execute thermostat mode 2 for d4187ab8-194b-492e-9770-6d1e986134f9
2019-01-11 21:35:19.526 [DEBUG] [nal.protocol.nhc2.NhcMqttConnection2] - Niko Home Control: connection state CONNECTED for 192_168_123_204-nikohomecontrol_bridge2_443b00ee4b2a-profile
2019-01-11 21:35:19.534 [DEBUG] [nal.protocol.nhc2.NhcMqttConnection2] - Niko Home Control: publish 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/cmd, {"Method":"devices.control","ErrCode":"","ErrMessage":"","Params":[{"Devices":[{"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9","Properties":[{"OverruleActive":"False"},{"Program":"Eco"}]}]}]}
2019-01-11 21:35:19.548 [TRACE] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: not acted on received message topic 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/cmd, payload {"Method":"devices.control","ErrCode":"","ErrMessage":"","Params":[{"Devices":[{"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9","Properties":[{"OverruleActive":"False"},{"Program":"Eco"}]}]}]}
2019-01-11 21:35:19.707 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/evt, payload {"Method":"devices.status","Params":[{"Devices":[{"Properties":[{"OverruleActive":"False"},{"Program":"Eco"},{"SetpointTemperature":"17.00"}],"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9"}]}]}
2019-01-11 21:35:19.711 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: setting thermostat d4187ab8-194b-492e-9770-6d1e986134f9 with measured 200, setpoint 170, mode 2, overrule 0, overruletime 0, ecosave 0
2019-01-11 21:35:19.715 [DEBUG] [trol.internal.protocol.NhcThermostat] - Niko Home Control: update channels for d4187ab8-194b-492e-9770-6d1e986134f9
2019-01-11 21:35:37.719 [DEBUG] [ler.NikoHomeControlThermostatHandler] - Niko Home Control: handle command 18 °C for nikohomecontrol:thermostat:443b00ee4b2a:d4187ab8-194b-492e-9770-6d1e986134f9:setpoint
2019-01-11 21:35:37.726 [DEBUG] [nternal.protocol.nhc2.NhcThermostat2] - Niko Home Control: execute thermostat overrule 180 during 60 min for d4187ab8-194b-492e-9770-6d1e986134f9
2019-01-11 21:35:37.738 [DEBUG] [nal.protocol.nhc2.NhcMqttConnection2] - Niko Home Control: connection state CONNECTED for 192_168_123_204-nikohomecontrol_bridge2_443b00ee4b2a-profile
2019-01-11 21:35:37.753 [DEBUG] [nal.protocol.nhc2.NhcMqttConnection2] - Niko Home Control: publish 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/cmd, {"Method":"devices.control","ErrCode":"","ErrMessage":"","Params":[{"Devices":[{"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9","Properties":[{"OverruleActive":"True"},{"OverruleSetpoint":"18"},{"OverruleTime":"60"}]}]}]}
2019-01-11 21:35:37.766 [TRACE] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: not acted on received message topic 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/cmd, payload {"Method":"devices.control","ErrCode":"","ErrMessage":"","Params":[{"Devices":[{"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9","Properties":[{"OverruleActive":"True"},{"OverruleSetpoint":"18"},{"OverruleTime":"60"}]}]}]}
2019-01-11 21:35:37.925 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: received topic 4faaca81-4034-494d-afc3-b7d2c676039f/control/devices/evt, payload {"Method":"devices.status","Params":[{"Devices":[{"Properties":[{"OverruleActive":"True"},{"OverruleTime":"60"},{"SetpointTemperature":"18.00"},{"OverruleSetpoint":"18.00"}],"Uuid":"d4187ab8-194b-492e-9770-6d1e986134f9"}]}]}
2019-01-11 21:35:37.929 [DEBUG] [l.nhc2.NikoHomeControlCommunication2] - Niko Home Control: setting thermostat d4187ab8-194b-492e-9770-6d1e986134f9 with measured 200, setpoint 180, mode 0, overrule 180, overruletime 60, ecosave 0

cwegh · January 11, 2019, 8:39pm

@bccrew: I set the loglevel on TRACE and make sure the PIR is activated and using energy monitoring (maybe I’ll film what I am doing on the touchscreen so you can see).

bccrew · January 11, 2019, 8:43pm

@cwegh Good luck