It just doesn't matter that much in my experience. If an issued command didn't work, it's easy to tell anyway (it's hot/cold), and you can just repeat it. HomeAssistant also has bits of special handling for items that don't communicate their state back, called "assumed state".
For the rare times I want to control my AC when being away from home, I have an air monitor nearby. I can just check if the temperature/humidity has changed, and repeat the command if it didn't work. If you _really_ cared you probably could script it to do it automagically, but I didn't feel the need to bother.
Yeah there’s very few edge cases, imo, where you need the feedback.
I have home assistant controlling an air conditioner in one room. (Well, mostly Node-RED.)
Every couple minutes it checks the temperature in the room and makes a decision on whether to call for cooling and tells the AC to turn on or off.
If it’s already on and cooling and it tells it to turn on… it’s a no-op, nothing happens. If it tells it to turn on and the command doesn’t go through… the room will stay warm so it will try the same thing in a couple of minutes. Same thing the other way (turning it off).
It just doesn't matter that much in my experience. If an issued command didn't work, it's easy to tell anyway (it's hot/cold), and you can just repeat it. HomeAssistant also has bits of special handling for items that don't communicate their state back, called "assumed state".
For the rare times I want to control my AC when being away from home, I have an air monitor nearby. I can just check if the temperature/humidity has changed, and repeat the command if it didn't work. If you _really_ cared you probably could script it to do it automagically, but I didn't feel the need to bother.