Odd behaviour . . .
Yesterday I turned on the heating to 19º in a room which has a single radiator with TRV and wireless temperature sensor, the zone controller is a wireless receiver.
The room began heating as expected but after a while I noticed the sensor was recording the temperature as 16.5º although it was clear the room had become warmer than that.
In an effort to "wake the sensor up" I set the heating of the room to off and then turned it on again but to no avail. Finally I tried reassigning the temperature sensor to a new virtual room at which point it responded and immediately showed the real temperature in the room as 22º. The TRV, which had assigned itself as the controller when the temperature sensor was taken away, also registered the temperature as 22º and closed at once because, as stated above, the temperature had been set to 19º.
I then assigned the temperature sensor back to the correct room and it then continued to function properly, taking over control again.
Looking at the graphs I had noted that when the overheating was happening a straight line was being drawn at 16.5º despite the room continuing to heat. After I re-established the temperature sensor the graph re-drew and (correctly) showed a spike up to 22º. Screen grab attached.
I presume that the wireless temperature sensor had lost touch with the bridge (or the latter with the server) but at no time did the app. reflect this and no error lamps came on in any part of the system.
I wonder what happened . . .
Comments
-
Hello @hugbilly I've not seen anything like that here. I see the occassional (random) loss of connection to a TRV. At a guess, something lost connection to the server, somewhere.
1 -
Yes, that's what I suspect, I hope it was a one off . . .
0
