Inconsistent behaviour
Inconsistent behaviour
Hi Jon, Might be missing something there, but these 2 rooms seem to be behaving differently
At approx 15:00 the temp sensor goes above the Stat SP and the TRV SP is set to 8 c from its overriden value 3 degrees above the Stat SP and the valve goes off.
However on this one
The plug in doesnt seem to adjust the TRV SP to 8 and so it continues to manage the temperature to the overriden TRV SP using the valve % so the room maintains at a higher temperature than the desired set point.
Both use remote temperature sensors and appear to have the same settings.
Any ideas?
Thanks
Simon
At approx 15:00 the temp sensor goes above the Stat SP and the TRV SP is set to 8 c from its overriden value 3 degrees above the Stat SP and the valve goes off.
However on this one
The plug in doesnt seem to adjust the TRV SP to 8 and so it continues to manage the temperature to the overriden TRV SP using the valve % so the room maintains at a higher temperature than the desired set point.
Both use remote temperature sensors and appear to have the same settings.
Any ideas?
Thanks
Simon
Re: Inconsistent behaviour
Hi Simon.
Happy New Year to you.
Looking at the second image, both the Remote and TRV set-points seem to be going to 8C between 14:00 and 17:00?
So unless I am missing something, it looks OK?
Happy New Year to you.
Looking at the second image, both the Remote and TRV set-points seem to be going to 8C between 14:00 and 17:00?
So unless I am missing something, it looks OK?
Inconsistent behaviour
Happy new year to you too.
It’s at 18:00 where I’d expect the TRV set point to go to 8 as the room temp was higher than the desired set point
It’s at 18:00 where I’d expect the TRV set point to go to 8 as the room temp was higher than the desired set point
Re: Inconsistent behaviour
I agree, it doesn't seem correct.
Are you sure that the Remote Stat is being used to monitor the temperature? I know you probably are, but just double checking.
Because, if it was using the TRV temperature to monitor the temp, it would be correct.
Are you sure that the Remote Stat is being used to monitor the temperature? I know you probably are, but just double checking.
Because, if it was using the TRV temperature to monitor the temp, it would be correct.
Re: Inconsistent behaviour
Hi Jon. Its that time of year again and realised that this strange behaviour is still happening on the twins' thermostat.
Its not setting the setpoint on the TRV to 8 once the remote temperature reaches the plugin setpoint of 20.
Any ideas what might be going wrong?
Its not setting the setpoint on the TRV to 8 once the remote temperature reaches the plugin setpoint of 20.
Any ideas what might be going wrong?
- Attachments
-
- Screenshot 2021-11-10 at 09.03.18.png (402.74 KiB) Viewed 4240 times
-
- Screenshot 2021-11-10 at 09.03.05.png (441.63 KiB) Viewed 4240 times
-
- Screenshot 2021-11-10 at 08.59.15.png (51.82 KiB) Viewed 4240 times
Re: Inconsistent behaviour
Interestingly I was getting this behaviour on another room and created a new TRV controller device with what I thought were same settings, moved all the dependencies over and deleted the original device.
The behaviour is now as expected, ie the TRV setpoint goes to 8 when the remote temperature sensor is higher than the controller setpoint.
Is it possible that the old device has not properly captured the remote sensor despite it showing in the GUI?
The behaviour is now as expected, ie the TRV setpoint goes to 8 when the remote temperature sensor is higher than the controller setpoint.
Is it possible that the old device has not properly captured the remote sensor despite it showing in the GUI?
Re: Inconsistent behaviour
Hi Simon,
I agree it looks odd.
Is there anything special about the Twin Temp piBeacon and is that the same stat in other room that is working OK?
You could try the procedure you use in the other room to correct it on the twins' room, to see if that resolves it.
Other than that, I would probably need to see some debugging logs for the time period it happens in order to see if that throws any light on the issue?
I agree it looks odd.
Is there anything special about the Twin Temp piBeacon and is that the same stat in other room that is working OK?
You could try the procedure you use in the other room to correct it on the twins' room, to see if that resolves it.
Other than that, I would probably need to see some debugging logs for the time period it happens in order to see if that throws any light on the issue?
Re: Inconsistent behaviour
Yes I’ve recreated a trv controller device. Copied settings from the screenshots on here and deleted the old one. Initial impressions are that it now work as expected whereas the old one didn’t.
Re: Inconsistent behaviour
I have turned on debugging on the plugin and will try some tests this evening. One of the rooms where I recreated a new device is still not setting the TRV SP back to 8 so will try and capture an event to share.
Re: Inconsistent behaviour
I set the trv controller to 21 at 19:20 and it did some weird behaviour. The TRV isnt 5 degrees higher and the the TRV is not set to 8 when the remote temp exceeds the set point.
- Attachments
-
- Screenshot 2021-11-11 at 23.22.19.png (74.33 KiB) Viewed 4139 times
Re: Inconsistent behaviour
Morning Jon,
This is strange.. schedule set to set study to 21 with a 5 degree offset. Except the setpoint on the trv controller as well as the trv itself are both set to 26.
edit: when I reloaded the TRV plugin, the controller SP was reverted to 21 as it should be and the valve then went to off.
This seems to be the relevant bit of code. The setpointHeat was at 21 and setPointTRV at 26 for a second or 2, then the TRV seems to go to TRV hardware control and the setpointHeat goes to 26. There is a weird line with the setpoint at 119.8 at 08:00:17.348
This is strange.. schedule set to set study to 21 with a 5 degree offset. Except the setpoint on the trv controller as well as the trv itself are both set to 26.
edit: when I reloaded the TRV plugin, the controller SP was reverted to 21 as it should be and the valve then went to off.
This seems to be the relevant bit of code. The setpointHeat was at 21 and setPointTRV at 26 for a second or 2, then the TRV seems to go to TRV hardware control and the setpointHeat goes to 26. There is a weird line with the setpoint at 119.8 at 08:00:17.348
Code: Select all
======================================================================================================================================================
==
== Method: 'deviceUpdated'
== Sequence: 78302
== Device: TRV - 'Study TRV'
== Last Communication: 2021-11-12 08:00:05
== List of states to be queued for update by TRVHANDLER:
== > Description = UPDATE ZWAVE EVENT SENT TRV, Value = 2021-11-12 08:00:17
== Description of updates that will be performed by TRVHANDLER:
== > TRV Z-Wave event sent. Time updated to '2021-11-12 08:00:17'. Sent count now totals: 158
==
======================================================================================================================================================
2021-11-12 08:00:17.296 DEBUG Plugin.trvHandler.controlTrv controlTrv: 'Study Thermostat' internal states [1] are: controllerMode = 1, setpointHeat = 21.0, setPointTrv = 26.0
2021-11-12 08:00:17.298 DEBUG Plugin.trvHandler.controlTrv controlTrv: 'Study Thermostat' internal states [2] are: controllerMode = 1, setpointHeat = 21.0, setPointTrv = 26.0
2021-11-12 08:00:17.300 DEBUG Plugin.trvHandler.controlTrv controlTrv: 'Study Thermostat' internal states [3] are: HVAC_FULL_POWER = False
2021-11-12 08:00:17.301 THREADDEBUG Plugin.method.zwaveCommandReceived Main Plugin Method
2021-11-12 08:00:17.301 THREADDEBUG Plugin.method.controlTrvHeatingOn TrvHandler Method
2021-11-12 08:00:17.304 DEBUG Plugin.general.zwaveCommandReceived
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZ
ZZ TRV Z-WAVE > RECEIVE INTERCEPTED: 01 0C 00 04 00 7F 06 31 05 01 42 06 9B 64 (node 127)
ZZ TRV Z-WAVE > TRANSLATION: Name = 'Study TRV', Address = 127, Length = 12, Class = Sensor Multilevel, Verb = Verb 05, Temperature = 16.91
ZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
2021-11-12 08:00:17.312 THREADDEBUG Plugin.method.deviceUpdated Main Plugin Method
2021-11-12 08:00:17.310 THREADDEBUG Plugin.method.controlHeatingSource TrvHandler Method
2021-11-12 08:00:17.320 DEBUG Plugin.general.deviceUpdated =======> RACE DETECTION FOR TRV 'Study TRV': SECONDS SINCE MIDNIGHT = '28817', COUNT = '4' [MAX = '8'] <=======
2021-11-12 08:00:17.326 DEBUG Plugin.trvHandler.controlHeatingSource Control Heating Source: Thermostats calling for heat from Variable 'HeatReqdHallway':
> Dining Room Thermostat
> Study Thermostat
2021-11-12 08:00:17.327 DEBUG Plugin.general.deviceUpdated
======================================================================================================================================================
==
== Method: 'deviceUpdated'
== Sequence: 78303
== Device: TRV - 'Study TRV'
== Last Communication: 2021-11-12 08:00:05
== List of states to be queued for update by TRVHANDLER:
== > Description = UPDATE ZWAVE EVENT RECEIVED TRV, Value = 2021-11-12 08:00:17
== Description of updates that will be performed by TRVHANDLER:
== > TRV Z-Wave event received. Time updated to '2021-11-12 08:00:17'. Received count now totals: 165
==
======================================================================================================================================================
2021-11-12 08:00:17.332 DEBUG Plugin.trvHandler.run
TRVHANDLER: 'Study Thermostat' DEQUEUED COMMAND 'UPDATE TRV STATES'
2021-11-12 08:00:17.333 THREADDEBUG Plugin.method.updateDeviceStates TrvHandler Method
2021-11-12 08:00:17.339 DEBUG Plugin.trvHandler.updateDeviceStates
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XX Method: 'updateDeviceStates'
XX Sequence: 78301
XX Device: TRV CONTROLLER - 'Study Thermostat'
XX List of states to be updated:
XX > Description = UPDATE ZWAVE EVENT RECEIVED TRV, Value = 2021-11-12 08:00:17
XX States to be updated in the TRV Controller device:
XX > {'value': '2021-11-12 08:00:17', 'key': 'zwaveEventReceivedDateTimeTrv'}
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
2021-11-12 08:00:17.339 THREADDEBUG Plugin.method.zwaveCommandSent Main Plugin Method
2021-11-12 08:00:17.339 THREADDEBUG Plugin.method.controlTrv TrvHandler Method
2021-11-12 08:00:17.348 DEBUG Plugin.general.zwaveCommandSent
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZ
ZZ TRV Z-WAVE > SEND INTERCEPTED: 01 0A 00 13 7F 03 43 02 01 25 77 88 (node 127 ACK after 17 milliseconds)
ZZ TRV Z-WAVE > TRANSLATION: Name = 'Study TRV', Address = 127, Length = 10, Class = Thermostat Setpoint, Verb = Get, Setpoint = 119.0
ZZ 'TRV' device Z-WAVE > Pending: True, Sequence: '2', Setpoint: '26.0'
ZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
2021-11-12 08:00:17.352 DEBUG Plugin.trvHandler.controlTrv controlTrv: 'Study Thermostat' is set to Controller Mode 'TRV UI Control'
2021-11-12 08:00:17.353 THREADDEBUG Plugin.method.deviceUpdated Main Plugin Method
2021-11-12 08:00:17.355 DEBUG Plugin.trvHandler.controlTrv controlTrv: 'Study Thermostat' internal states [1] are: controllerMode = 4, setpointHeat = 21.0, setPointTrv = 26.0
2021-11-12 08:00:17.360 DEBUG Plugin.general.deviceUpdated =======> RACE DETECTION FOR TRV 'Study TRV': SECONDS SINCE MIDNIGHT = '28817', COUNT = '5' [MAX = '8'] <=======
2021-11-12 08:00:17.363 DEBUG Plugin.trvHandler.controlTrv controlTrv: 'Study Thermostat' internal states [2] are: controllerMode = 4, setpointHeat = 26.0, setPointTrv = 26.0
2021-11-12 08:00:17.365 DEBUG Plugin.general.deviceUpdated
======================================================================================================================================================
==
== Method: 'deviceUpdated'
== Sequence: 78304
== Device: TRV - 'Study TRV'
== Last Communication: 2021-11-12 08:00:05
== List of states to be queued for update by TRVHANDLER:
== > Description = UPDATE CONTROLLER MODE, Value = 4
== > Description = UPDATE ZWAVE EVENT SENT TRV, Value = 2021-11-12 08:00:17
== Description of updates that will be performed by TRVHANDLER:
== > Controller Mode updated from Auto Schedule Control to TRV UI Control
== > TRV Z-Wave event sent. Time updated to '2021-11-12 08:00:17'. Sent count now totals: 159
==
======================================================================================================================================================
2021-11-12 08:00:17.368 DEBUG Plugin.trvHandler.controlTrv controlTrv: 'Study Thermostat' internal states [3] are: HVAC_FULL_POWER = False
2021-11-12 08:00:17.369 THREADDEBUG Plugin.method.controlTrvHeatingOn TrvHandler Method
2021-11-12 08:00:17.382 THREADDEBUG Plugin.method.controlHeatingSource TrvHandler Method
2021-11-12 08:00:17.390 DEBUG Plugin.trvHandler.controlHeatingSource Control Heating Source: Thermostats calling for heat from Variable 'HeatReqdHallway':
> Dining Room Thermostat
> Study Thermostat
2021-11-12 08:00:17.390 THREADDEBUG Plugin.method.zwaveCommandReceived Main Plugin Method
2021-11-12 08:00:17.395 DEBUG Plugin.trvHandler.run
TRVHANDLER: 'Study Thermostat' DEQUEUED COMMAND 'UPDATE TRV STATES'
2021-11-12 08:00:17.402 DEBUG Plugin.general.zwaveCommandReceived
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZ
ZZ TRV Z-WAVE > RECEIVE INTERCEPTED: 01 0C 00 04 00 7F 06 43 03 01 22 00 50 BD (node 127)
ZZ TRV Z-WAVE > TRANSLATION: Name = 'Study TRV', Address = 127, Length = 12, Class = Thermostat Setpoint, Verb = Report, Setpoint = 8.0, Pending Controller Mode = TRV Hardware Control
ZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
2021-11-12 08:00:17.402 THREADDEBUG Plugin.method.updateDeviceStates TrvHandler Method
2021-11-12 08:00:17.409 DEBUG Plugin.trvHandler.updateDeviceStates
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XX Method: 'updateDeviceStates'
XX Sequence: 78302
XX Device: TRV CONTROLLER - 'Study Thermostat'
XX List of states to be updated:
XX > Description = UPDATE ZWAVE EVENT SENT TRV, Value = 2021-11-12 08:00:17
XX States to be updated in the TRV Controller device:
XX > {'value': '2021-11-12 08:00:17', 'key': 'zwaveEventSentDateTimeTrv'}
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
2021-11-12 08:00:17.410 THREADDEBUG Plugin.method.deviceUpdated Main Plugin Method
2021-11-12 08:00:17.410 THREADDEBUG Plugin.method.controlTrv TrvHandler Method
2021-11-12 08:00:17.425 DEBUG Plugin.general.deviceUpdated =======> RACE DETECTION FOR TRV 'Study TRV': SECONDS SINCE MIDNIGHT = '28817', COUNT = '6' [MAX = '8'] <=======
2021-11-12 08:00:17.430 DEBUG Plugin.trvHandler.controlTrv controlTrv: 'Study Thermostat' is set to Controller Mode 'TRV Hardware Control'
2021-11-12 08:00:17.432 DEBUG Plugin.general.deviceUpdated
======================================================================================================================================================
==
== Method: 'deviceUpdated'
== Sequence: 78305
== Device: TRV - 'Study TRV'
== Last Communication: 2021-11-12 08:00:05
== List of states to be queued for update by TRVHANDLER:
== > Description = UPDATE ZWAVE EVENT RECEIVED TRV, Value = 2021-11-12 08:00:17
== > Description = UPDATE CONTROLLER MODE, Value = 3
== Description of updates that will be performed by TRVHANDLER:
== > TRV Z-Wave event received. Time updated to '2021-11-12 08:00:17'. Received count now totals: 166
== > Controller Mode updated from Auto Schedule Control to TRV Hardware Control
==
======================================================================================================================================================
2021-11-12 08:00:17.435 DEBUG Plugin.trvHandler.controlTrv controlTrv: 'Study Thermostat' internal states [1] are: controllerMode = 3, setpointHeat = 26.0, setPointTrv = 26.0
2021-11-12 08:00:17.438 DEBUG Plugin.trvHandler.controlTrv controlTrv: 'Study Thermostat' internal states [2] are: controllerMode = 3, setpointHeat = 26.0, setPointTrv = 26.0
2021-11-12 08:00:17.438 THREADDEBUG Plugin.method.zwaveCommandSent Main Plugin Method
2021-11-12 08:00:17.441 DEBUG Plugin.trvHandler.controlTrv controlTrv: 'Study Thermostat' internal states [3] are: HVAC_FULL_POWER = False
2021-11-12 08:00:17.446 DEBUG Plugin.general.zwaveCommandSent
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
ZZ
ZZ TRV Z-WAVE > SEND INTERCEPTED: 01 09 00 13 7F 02 26 02 25 78 E1 (node 127 ACK after 7 milliseconds)
ZZ TRV Z-WAVE > TRANSLATION: Name = 'Study TRV', Address = 127, Length = 9, Class = Switch Multilevel, Verb = Get, Get Valve Status
ZZ
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
- Attachments
-
- Screenshot 2021-11-12 at 08.22.10.png (57.43 KiB) Viewed 4150 times
-
- Screenshot 2021-11-12 at 08.24.29.png (369.33 KiB) Viewed 4150 times
Re: Inconsistent behaviour
I have now started plotting the controllerMode in grafana and 2 of the TRV controllers are in mode 3, ie TRV Hardware Control, even though they havent been touched and have child lock on.
Restarting the plugin resets them to mode 0 Auto, but then they flip back to mode 3. Is this expected behaviour?
Restarting the plugin resets them to mode 0 Auto, but then they flip back to mode 3. Is this expected behaviour?
Re: Inconsistent behaviour
Hi Simon,
I don't think it is expected behaviour? I would expect it to go into that mode if the setpoint was changed on the TRV.
I will investigate for you. The trouble is, when I have touched the code for ages, it takes a while to remind myself how it all works, or doesn't as the case may be.
EDIT:
What version of the plugin are you running to make sure that I am looking at the relevant version?
Just catching up with posts.siclark wrote:I have now started plotting the controllerMode in grafana and 2 of the TRV controllers are in mode 3, ie TRV Hardware Control, even though they havent been touched and have child lock on.
Restarting the plugin resets them to mode 0 Auto, but then they flip back to mode 3. Is this expected behaviour?
I don't think it is expected behaviour? I would expect it to go into that mode if the setpoint was changed on the TRV.
I will investigate for you. The trouble is, when I have touched the code for ages, it takes a while to remind myself how it all works, or doesn't as the case may be.
EDIT:
What version of the plugin are you running to make sure that I am looking at the relevant version?
Re: Inconsistent behaviour
I did check with my wife that she didn’t touch the trv and in the other room I Was sat there the whole time.
The logging shows a lot of changing between modes on the 2 devices I recreated.

The logging shows a lot of changing between modes on the 2 devices I recreated.

Re: Inconsistent behaviour
Yes, definitely looks odd; well spotted.
So, what version of the plugin are you running (you might have missed the edit on my previous post)?
So, what version of the plugin are you running (you might have missed the edit on my previous post)?