-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Newest update no longer turns on and off heating based on temp #67
Comments
Can you please share your config? I can't reproduce the error on my end. It works with and without |
I have one idea why this might be. I still have one PR open #66 that properly implements - service: climate.turn_off
target:
entity_id: climate.your_dual_mode_generic_climate_entity In this case, yes, the newest update may have changed the behavior. If that is the case, you should see some error messages in the log, indicating that the integration If you can confirm that the above is how you interact with this integration, I'll go ahead and merge #66 which implements the on/off actions |
The For now, the workaround is to call the |
Hi, sorry for the late reply and thanks for all the suggestions! I reverted to a previous update. I have now tried updating and my dual-mode thermostats are still broken. However, I have discovered interesting behaviour. When my Home Assistant instance is first started, the dual-mode thermostat does not work. I changed my config to no longer use climate.turn_off but that didn't fix it unfortunately. To make it work, I go to the thermostat, select either heat or cool, then it will work based on the temperature I set. Then I switch back to heat/cool and it works perfectly. It's just after restarting that it doesn't work. I took a video of this happening to hopefully clarify: https://www.youtube.com/watch?v=ebmFzV2CT5Y Changing this to heat or cool only works on a per thermostat basis, if I change it for one thermostat it doesn't fix the others that I have.
|
Just figured out that when I call the climate.set_temperature event on my thermostat, I get an error if I only set target_temp_high or only target_temp_low, I always have to set both. When I set both target_temp_high and target_temp_low, my switch still doesn't work as my heater and cooler stay off. When I also send "temperature" my heater or cooler finally run. After that, the thermostat and widget work fine again. |
Sorry, I can't help troubleshooting any further. After a week without heating or cooling working I've switched to the dual-smart-thermostat add-on from Swingerman. |
After updating in HACS to ee73489 my thermostats no longer turn the heating on or off based on temperature. I understand the latest update changed some things, but the readme has not been updated yet. Am I supposed to change something in my configuration yaml?
The text was updated successfully, but these errors were encountered: