I am desperate. I just spent 2 days configuring a generic thermostat but I keep getting stuck (and I am pretty sure that at some point in the past two days it was working … until I “fixed” something).
The situation:
I have a group of thermostats for my office radiators. The work fine as group in a climate entity (climate.kellerburo_group). I then purchased an external temperature sensor (sensor.lumi_lumi_weather_temperature_2) and wanted to combine it with said group. It is my understanding (but maybe I am wrong?) that I have to put climate and sensor together in a generic_thermostat (climate.kellerthermostat ) to have the climate entity use the external sensor as temperature reference (instead of the internal one). I also figured out that I would have to build a template switch (switch. toggle_heater_office) to toggle between “heat” and “off” – because that is how the generic_thermostat works.
To further complicate things, I added a slider (input_number.slider_external_max) for setting the max temperature via UI. But that does not seem to be the problem, as it works fine when trying everything in the dev tools.
The result:
For testing, I added a thermostat card for the climate_group, one for the generic_thermostat and a button for toggling the switch to the UI.
The switch and the group work together just fine. When I toggle via button, the climate_group turns on (“heat”) and off just fine. Also: When I heat via the thermostat card, the toggle correctly represents the current on/off state.
Turning off the group (and the toggle) via the generic_thermostat also works just fine.
Turning on the group (and the toggle) via the generic_thermostat does not work though. When I paste the service call (“turn_on” section from the fake switch) from above in the home assistant dev tools, it turns the climate_group on as expected – but via the thermostat card in the UI, it fails. Turning on the generic_thermostat with the same service-call (I just replaced the group entity with the generic one) via dev tools also fails.
I just can’t get my head around what is happening here. There is no error entry in the logs, and the logbook also doesn’t help. Does anybody have an idea what’s going one here?
It looks correct to me.
I have not set mine up that way, I have used just a boolean as the switch.
Then have an automation that sets the TRVs on or off.
I honestly can’t say that should make a difference because that is pretty much what your template does also.
But is there anything in the logs?
What happens if you copy your turn on to an automation and trigger it ( or script), does that create any errors?
Nothing in the logs that I can link to these devices. I have not tried to put the service call into an automation … only in the dev tools. But I will test that right away!
UPDATE: It does toggle the switch and turn on the climate group – but it won’t turn on the generic_thermostat. Maybe the value_template there is wrong? But when I copy that part over to the dev tools, it shows the expected results.
I just now thought about something.
Could it be that it runs to fast.
Turn on is too slow that the temperature set happens before it’s on and it fails?
Okay, I just figured out: It seems like the generic thermostat stay in preset “idle” – and that somehow messed things up. I added the entity_id of the generic thermostat to all service-calls (that should be redundant, but now it works, so I will definitely leave it that way!), and also added another service-call for changing the climate preset to “comfort”.
Now, I have a Shelly temperature sensor in a bedroom (coldest), that i want to use as threshold tu turn on the heater using a generic thermostat, but when I put upper temperature than the Shelly sensor temperature, the heater never turn on using the gerenic_thermostat card.
.
