Open superinj opened 3 years ago
I'm not sure this would be the best approach for this.
The climate entity is already supposed to support this. The HVAC action is supposed to distinguish between (for instance) HVAC_MODE_HEAT
+CURRENT_HVAC_HEAT
and HVAC_MODE_HEAT
+CURRENT_HVAC_IDLE
.
If you have only one valve actuator per zone, then it should already work; but admittedly I can't properly test this part since I don't have a MyHome compatible heating system.
Does the difference while heating and while idle not show in the climate entity for you?
In the climate entity I can see when idle or heating and it represents a single zone, but I think could be useful to have an external binary sensor represents single actuators. Actuators can control single zone, but, like you said, you can have multiple actuators in a single zone or also have an actuator to control central pumps (in this case they have a special 00 zone).
I suppose it could be quite simple, the configuration should be like this:
binary_sensor:
- platform: myhome
devices:
actuator_pump:
who: '4'
where: '99#1' (zone 99, actuators 1)
name: Pump
You have just to read *#4*99#1*20*1##
to turn it on, and *#4*99#1*20*0##
to turn it off.
What do you think about?
What is your usecase for this?
In myhomeserver1 you can add a radiator (for example in the bathroom), and set the schedule to turn it on and off. It would be nice to be able to set such a schedule also in home assistant. MHS1 sets the the radiator actuator as a separate zone - to which no thermostat is assigned. You know - it can be done on ordinary actors (e.g. f411 / 4) but they occupy addresses in the system, and as you know, their number is limited to 175 on one bus, having many lights and blinds - as in my case - it may be slowly missing addresses, I personally already have 168 used. So when the radiator is set as a zone then they does not occupy the light address, only the heating zone address :)
As far as I'm aware, you can have the same WHERE
for two different WHO
, no?
So even if it's a bit of a dirty hack, covers and lights can share the same address?
Hmm. I haven't tried it... MHS1 sets addresses one by one for roller shutters and lighting, they never overlap. But anyway - it's great if you could create an on / off control entity for the thermoregulation actor :)
In my house I have some F430s controlled by thermostats. I will like to know each actuator status, this is described at paragraph 1.5.8 in WHO 4 manual.
Do you want to add this as sensors or binary sensors?
I will appreciate.