Have been using this integration for a while now with my HAWJ24KR split unit - it works relatively well all thing considered.
However the reporting seems to not be quite right. When the unit is "on" (e.g. it's set to be cooling/heating/etc...) but not actively working it returns a state of off instead of idle. Distinguishing between the two is important for managing automatons and the like.
Additionally, it doesn't seem like the hvac_action attribute - the one that will stay as heat, cool, etc... while the unit is idling - is being reported at all. Again, this poses significant problems for automations and the like that depend on knowing what the intended function of the device is even if it's not actively doing work.
I'm a bit out of my depth when it comes to developing for this large of an integration but I'm happy to provide logs and do what I can!
Have been using this integration for a while now with my HAWJ24KR split unit - it works relatively well all thing considered.
However the reporting seems to not be quite right. When the unit is "on" (e.g. it's set to be cooling/heating/etc...) but not actively working it returns a state of
offinstead ofidle. Distinguishing between the two is important for managing automatons and the like.Additionally, it doesn't seem like the
hvac_actionattribute - the one that will stay asheat,cool, etc... while the unit is idling - is being reported at all. Again, this poses significant problems for automations and the like that depend on knowing what the intended function of the device is even if it's not actively doing work.I'm a bit out of my depth when it comes to developing for this large of an integration but I'm happy to provide logs and do what I can!