I would start with the fact that they show up as unsupported in HA:
Moving forward, the available operations (hvac modes) are: heat/cool, heat/cool, heat, off. They obviously don’t do anything, I think instead of these, we should have what we find in the presets menu (which is also incomplete).
There is only one preset available: “holiday”
It should be: { “range”: [ “auto”, “manual”, “holiday”, “boost” ] }
The radiator has a sensor for temperature but it’s not available in HA as an entity.
If you check what’s available in HA, it’s nothing close to that. I hope it’s easier to understand now, I tried to explain but it gets confusing unless you see it with your own eyes.
ah yes, I thought I wrote it but I think I deleted it at some point; the devices use zigbee and they are connected to the zigbee gateway with which I communicate via wifi
For each of the radiators I get the following:
1 x climate entity
1 x sensor entity (battery percentage)
2 x switch entities (Child lock, Open window detection)
You have two preset modes, holiday and holidayready.
You have hvac_modes of off, heat_cool (twice for some reason) and heat. I am not sure what heat_cool does in the context of a radiator valve, it is probably auto, ie it heats if needed and goes to off if the room is hot enough.
Yes, and that’s why I was asking for a proper implementation; I think the current version doesn’t make that much sense. It is usable but it’s (in my opinion) an incomplete/broken integration. I searched a lot and when I saw the forum post I linked in my original post saying that we should request this, I requested it.
so should I move this to another section or what should I do? I think I managed to explain the situation well enough and I’m not sure what to do next to fix the problems
