Open trullock opened 1 year ago
How does the API report the current heating/cooling action when in auto (Heat/Cool) mode?
Diagnostics simply reports it as "on" and in "auto" mode...
"onOffMode": {
"settable": true,
"values": [
"on",
"off"
],
"value": "on"
},
"operationMode": {
"settable": true,
"value": "auto",
"values": [
"fanOnly",
"heating",
"cooling",
"auto",
"dry"
]
},
I don't know this has anything to do with the issue I'm having but:
I want to check the hvac_mode
to use in an automation (if the unit is cooling, then...)
However, in the automations I can't get the status of this. I can see them in the developer tools but they don't show up in the automations list. The rest shows up just fine.
Any ideas?
EDIT:
Found it, I just needed to leave out attribute: hvac_modes
(which is a bit counterintuitive)
@kimme1024 the action isn't always correct, so beware.
When its in auto mode, the api doesnt say if its cooling/idle/heating, I've had to infer that based on the mode, setpoints and temperature
Maybe the indoor unit deltaD
, suctionTemperature
, and heatExchangerTemperature
can be used to determine whether the unit is really cooling/heating?
Maybe the indoor unit
deltaD
,suctionTemperature
, andheatExchangerTemperature
can be used to determine whether the unit is really cooling/heating?
Where do they live, on the API?
I'm pretty happy with my setpoint vs current temp workaround, works well enough for me.
Ive noticed the official ONCETA app doesnt show any indication of what its doing in Auto mode
We should support setting the current HVAC_Action so that HA can properly represent the current operation.
I'll have a go at this myself, however my AC units are misconfigured by the installer so that when theyre on HEAT or COOL mode, they are always HEATING or COOLING, i.e. once they reach the setpoint they dont stop.
I'll flesh out the body of this and then perhaps someone with a working system can add or advise on the final bits