-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't control via HA climate entity any more, various errors... #16
Comments
Here's another error from the logs: This error originated from a custom integration.
|
Hi, Thank you for your logs, that helps for sure! |
Hey Daniel, if it's any help - this seems to be only be affecting one of my three units. I think it MIGHT have been something to do with it being operating (fan mode) when HA was restarted. Maybe has got out of sync or something. Still getting the the 'int() argument must be a string.... not 'NoneType'' error any time I try and change the climate entity for the unit in question. In HA it is now permanently showing as in 'fan only'. |
Correction! It is affecting all three units, my mistake. |
Same here, all my 5 units could't be controlled anymore. I had to restore a backup prior to the latest updates. |
Hmm yes think I might have to do the same. |
Are you referring to homeassistant updates or airstage integration? |
## [1.1.7](v1.1.6...v1.1.7) (2023-11-02) ### Bug Fixes * **climate:** Quickfix target temperature is none, issue [#16](#16) ([fc2e313](fc2e313))
Hi guys! |
Feedback: after applying the updates, the systems now keep on working without any problems as far as I can see. |
Yep seems to have fixed it for me too, thanks Daniel! |
I also confirm that 1.17 fixed all issues. Thanks @danielkaldheim , beer incoming :) |
Since the last update I seem to have issues using the integration's base 'climate entity' that allows setting of temp, modes etc. All the 'seperate' entities like switching the LED on and off, powerful mode, etc seem to work fine. Hope I'm describing this clearly enough, sorry!
Getting lots of errors in the logs along these lines:
It feels like probably something changed in HA core that has caused an issue but I'm in no way smart enough to figure it out!
The text was updated successfully, but these errors were encountered: