Releases: AlbertWeterings/WThermostatBeca
v1.1.1-Beta
Issue klausahrenberg#286 Solved - Tested on ME102H
reported by @dwarning
WiFi symbol missing, but connection to web config was possible (Solved Tested on ME102H)
Info page not accessible, other pages OK (Solved Tested on ME102H)
MQTT connection seems broken - no update (Solved Tested on ME102H)
v1.1.0-Beta
Issue klausahrenberg#239 Solved
Issue klausahrenberg#282 Solved
For some Thermostats the temperature field size in schedualer increased by 1 digit.
Thermostat ME102H "QueryMCU actively" can be checked and un-checked both are now working.
All thermostats that do not update automaticaly need "QueryMCU actively" checked.
v1.0.9-Beta
Changed Query MCU interval to 5 seconds.
v1.0.8-Beta
With the help of @PhilipTS we made changing to make available settings via Mozilla Webthings and MQTT
Set TemperatureCorrection - any value positive and negative
Set MinHeatTemperature - values from 5 to 20
Set MaxHeatTemperature - vaules from 30 to 95
Set SwitchDifference - values from 1 to 5
Set De-Frost - value on and off
v1.0.7-Beta
With the help of @PhilipTS we made changing over MQTT passible for the following settings
- TemperatureCorrection
- MinHeatTemperature
- MaxHeatTemperature
V1.0.6-Beta
In this release the mechanism of querying the MCU is change.
When "QueryMCU actively" in the GUI under "Configure thermostat" is enabled the WIFI module will query in between heartbeats the MCU for it's status. The query activity is repeated every x time as defined in QUERY_INTERVAL, by default every 2 seconds. For some thermostats this is not needed as they will transmit their status based on a timer in the MCU.
For example the ME102H is behaving wrong when QueryMCU actively is enabled.
V1.0.3-alpha
Possible solution for klausahrenberg#239
V1.0.2-alpha
Changed intervals to solve issue klausahrenberg#239 and get the UART quiet
#define HEARTBEAT_INTERVAL 10000
Changed to #define HEARTBEAT_INTERVAL 20000
#define MINIMUM_INTERVAL 2000
Changed to #define MINIMUM_INTERVAL 10000
HEARTBEAT_INTERVAL is being send to the MCU to tell the TUYA device is still alive, I doubled the time as it still seems enough for the MCU to know the TUYA device is still alive.
MINIMUM_INTERVAL is querying the MCU for settings. It is useful to have this at a 2 second interval during debug activities but it is meaningless during normal operation.
V1.0.1-alpha
Added relay state to output