I noticed v1.3.0 was uploaded by someone connected to sonoff, where as this is by someone who has only recenlty started doing anything on the site - that might be normal, but since we never get changelogs I got a little bit curious so went and dug in to it a little.
I can’t see any sonoff forum posts or anything about it.
"Boost mode: Activates maximum TRV temperature for a user-defined duration, enabling rapid heating. "
“Timer Mode: Allows customization of temperature and duration for precise heating control.”
“After the set duration, the system will return to its previous normal mode and temperature.”
Unlike 1.3.0 which added external temp sensor - a big improvement, this, to me, is not that important, so I will skip it until spring since I don’t want to mess with the TRVs at the begging of winter.
I upgraded to firmware 1.4.0 but I did not notice any concrere changes in the settings.
I hoped this version will bring Adaptive Mode (valve modulation) PID, but unfrotunately it is not the case.
What I observed instead is that one interesting option from 1.3.0 dissapeared: Temperature Calibration (giving the possibility to calibrate +/- the temperature detected by built-in sensor). This is yoo bad because I was using it and now, with new version, I cannot rollback the setting.
More that post the recent supply chain attacks I review things before approving them onto my own devices, however OTAs are already prepackaged, and looking at the approval route for z2m it appears to be automated, as compared to HA which has a very strict flow for approvals, so more trust in HA approvals due to this.
I believe a small amount checking should be done for closed (hash check on downloads / validation of correct site) or open source (validation of what was added etc).
Indeed seems a major issue, especially for the users that used that function in the past, curently with the new upgrade you cannot change the temperature calibration values anymore.
Perhaps a factory reset will set the calibration value back to 0, anyhow Temperature Calibration is not anymore present, so you cannot use it in 1.4.0.
maybe remove it from Z2M first since in database.db you have an entry for the TRV which contains localTemperatureCalibration, or at least it does with 1.3.0. If the value remains there I think Z2M tries to re-push it to the device when re-adding, and it might lead to some issues.
well, first of all, its not fully closed/opened, you can play with the valve % in that regard.
Second, I guess it just goes - more degrees than needed, hoping the heater will take the temp difference into account and heat the room faster? which most don’t anyway.
