Closed soyxan closed 1 year ago
I'm using Thermostat day by day and it has a lot of different parameters, but I must admit that sometimes, on my side it has strange issue also such as powering for 1/2 seconds without understanding why.
Also you need to check that your device does not reboot because in this case in need back calculation on fresh start.
May be another option would be to switch to PID mod to compare.
I left all the Tasmota thermostat parameters by default (that means hybrid mode: ramp-up + PI). The thing is that as you can see in the trends I am not talking about some seconds, the thermostat actuates for more than 15 minutes (constantly)
I suggest that you log to a syslog server continuously with syslog 3 to have details It may explain why tasmota decide to heat when not needed
This issue has been automatically marked as stale because it hasn't any activity in last few weeks. It will be closed if no further activity occurs. Thank you for your contributions.
This issue was automatically closed because of being stale. Feel free to open a new one if you still experience this problem.
PROBLEM DESCRIPTION
I am using the Tasmota thermostat implementation (https://tasmota.github.io/docs/Thermostat/) and overall is working ok, but the following screenshots show a strange situation that is occurring very often:
As it can be seen in the first screenshot, the heating action is working as expected from 18:00 to 21:00 (the setpoint is 23ºC and the current temperature is below, so the heating action gets activated) but at around 5:30 the heating action is activated again when according to the setpoint is not needed.
In the second screenshot, it is shown a room with constant temperature setpoint for all day (19ºC) and from time to time the heating action is activated when not expected.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
#define USE_THERMOSTAT
)Backlog Template; Module; GPIO 255
:Status 0
:TO REPRODUCE
Steps to reproduce the behavior:
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
SCREENSHOTS
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)