What is the feature?
This is NO duplicate of the existing external sensor push, but an addition:
Regularly and autonomously force push the external sensor's temperature the TRVZB thermostats if it did not change for too long.
Description
Why?
Because the Sonoff TRVZB will switch to fallback mode, meaning internal temperature sensor, when there's no update of the external sensor temperature for an hour, which will happen when temperature measured by the external sensor did not change for too long. The often used workaround is forcing Zigbee devices to update anyway. But when using other sensors, like Ecowitt WH31 you don't have this option.
At the moment I am using overly complex automation plans for working around this issue, but I think this obviously would be a very good and important quirk to integrate into BT's model specific fixes (TRVZB.py) .
The issue is that using the internal sensor after fallback of course is terrible, as it's temperature value always is far off.
Additional Information
The known time for the TRVZB to fallback is one hour. So it would be enough to push an forced update when the external sensor's temperature did not change for 59 minutes.
Otherwise the TRVZB will świtch from external to external_2, and way later, to external_3, which means it's getting updates again, buu indicates an outtime, where it acted unpleasantly, because it used it's internal sensors useless temperature.
What is the feature?
This is NO duplicate of the existing external sensor push, but an addition:
Regularly and autonomously force push the external sensor's temperature the TRVZB thermostats if it did not change for too long.
Description
Why?
Because the Sonoff TRVZB will switch to fallback mode, meaning internal temperature sensor, when there's no update of the external sensor temperature for an hour, which will happen when temperature measured by the external sensor did not change for too long. The often used workaround is forcing Zigbee devices to update anyway. But when using other sensors, like Ecowitt WH31 you don't have this option.
At the moment I am using overly complex automation plans for working around this issue, but I think this obviously would be a very good and important quirk to integrate into BT's model specific fixes (TRVZB.py) .
The issue is that using the internal sensor after fallback of course is terrible, as it's temperature value always is far off.
Additional Information
The known time for the TRVZB to fallback is one hour. So it would be enough to push an forced update when the external sensor's temperature did not change for 59 minutes.
Otherwise the TRVZB will świtch from external to external_2, and way later, to external_3, which means it's getting updates again, buu indicates an outtime, where it acted unpleasantly, because it used it's internal sensors useless temperature.