You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, i've a few MOES TRV-100 that didn't really function until I got your solution, so now most of them are working nice, thank you very much for this project, together with the scheduling components by nielsfaber, a very nice addition to my setup!
However, I also have two rooms that are not often used and have not an own temperature sensor. I'd like to use the internal TRV sensor to at least get a bit of a feel for these rooms.
Since not supplying a T sensor, i could of course just use the better thermostat lovelace card and use this for the actual climate entry of the TRV. However, i then miss the nice window open - stop heating function. And especially this is a not often used room, the window sometime stays open far too long to my liking.
As a work-around, i created a template sensor taking the attribute "local_temperature" out of the TRV and used this as the "external" sensor. This seems to at least enable the better thermostat features, but I'm guessing this now results in some kind of dead loop in the calibration process, I see a -6 now in the temperature_calibration, which reflects in a very wrong temperature...
Of course, easy way is to buy a few more T sensors, but maybe this is not needed. Is is for instance possible to do a calibration period temporarily using a spare sensor, then saving all the necessary information/calibrations and be able to keep using it afterwards without the feedback loop in place?
Also: is it possible to automatically use the internal local_temperature in the climate object so one doesn't need to create an extra template sensor?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, i've a few MOES TRV-100 that didn't really function until I got your solution, so now most of them are working nice, thank you very much for this project, together with the scheduling components by nielsfaber, a very nice addition to my setup!
However, I also have two rooms that are not often used and have not an own temperature sensor. I'd like to use the internal TRV sensor to at least get a bit of a feel for these rooms.
Since not supplying a T sensor, i could of course just use the better thermostat lovelace card and use this for the actual climate entry of the TRV. However, i then miss the nice window open - stop heating function. And especially this is a not often used room, the window sometime stays open far too long to my liking.
As a work-around, i created a template sensor taking the attribute "local_temperature" out of the TRV and used this as the "external" sensor. This seems to at least enable the better thermostat features, but I'm guessing this now results in some kind of dead loop in the calibration process, I see a -6 now in the temperature_calibration, which reflects in a very wrong temperature...
Of course, easy way is to buy a few more T sensors, but maybe this is not needed. Is is for instance possible to do a calibration period temporarily using a spare sensor, then saving all the necessary information/calibrations and be able to keep using it afterwards without the feedback loop in place?
Also: is it possible to automatically use the internal local_temperature in the climate object so one doesn't need to create an extra template sensor?
Beta Was this translation helpful? Give feedback.
All reactions