Wink & Quirky Aros AC stopped working latest upgrade

Just upgraded to Home Assistant 0.96.5 and lost access to my Quirky Aros air conditioner that is being controlled by my Wink Hub.

Going back to Home Assistant 0.95.4 and I can once again access the Quirky Aros AC.

Any ideas where to look for help?

I believe somethings have changed with Climate modules as I had to fix my Honeywell Lyric as well.

Hey! Sorry about that most likely from the climate upgrade like you said, I fixed some stuff with thermostats already but didn’t see anything wrong with the Aros stuff, can you send me a log? Should point me to where the error is.

Thanks, I believe these are the key lines in the log file:

> 2019-07-28 07:21:45 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
> Traceback (most recent call last):
>   File "/usr/src/homeassistant/homeassistant/helpers/", line 365, in _async_add_entity
>     await entity.async_update_ha_state()
>   File "/usr/src/homeassistant/homeassistant/helpers/", line 226, in async_update_ha_state
>     self._async_write_ha_state()
>   File "/usr/src/homeassistant/homeassistant/helpers/", line 256, in _async_write_ha_state                                                                         
>     attr.update(self.state_attributes or {})
>   File "/usr/src/homeassistant/homeassistant/components/climate/", line 169, in state_attributes
>     ATTR_HVAC_MODES: self.hvac_modes,
>   File "/usr/src/homeassistant/homeassistant/components/wink/", line 425, in hvac_modes
>     modes = self.wink.hvac_modes()
> AttributeError: 'WinkAirConditioner' object has no attribute 'hvac_modes'

What version of HA are you running? The crash doesn’t line up with what I show in dev. Meaning if you haven’t done so already an upgrade should fix this. Looks like someone has already fixed it should be in the next release.

I’m running Home Assistant 0.96.5, but sounds like I should wait for the next release?

Correct, should be in 096.6 I believe.

1 Like

Thanks for the help. I did take a look at the fix, definitely relates to my problem. I will keep an eye on the update.