Upgrade to Home Assistant 2022.8.0 may break integration?
See original GitHub issueAfter upgrading to HA 2022.8.0, I’m seeing the following issues:
async_setup errors
Logger: homeassistant.config_entries
Source: custom_components/ge_home/update_coordinator.py:174
Integration: GE Home (documentation)
First occurred: 2:39:53 PM (1 occurrences)
Last logged: 2:39:53 PM
Error setting up entry <email address> for ge_home
Traceback (most recent call last):
File "/homeassistant/custom_components/ge_home/update_coordinator.py", line 172, in async_setup
await self.initialization_future
asyncio.exceptions.CancelledError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/hass/homeassistant/lib/python3.10/site-packages/homeassistant/config_entries.py", line 357, in async_setup
result = await component.async_setup_entry(hass, self)
File "/homeassistant/custom_components/ge_home/__init__.py", line 45, in async_setup_entry
if not await coordinator.async_setup():
File "/homeassistant/custom_components/ge_home/update_coordinator.py", line 174, in async_setup
raise HaCannotConnect("Initialization timed out")
custom_components.ge_home.exceptions.HaCannotConnect: Initialization timed out
Repeating messages regarding “Attribute hass is None for”:
RuntimeError: Attribute hass is None for <Entity R319139N Laundry Machine State>
2022-08-03 22:09:16.099 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
raise RuntimeError(f"Attribute hass is None for {self}")
RuntimeError: Attribute hass is None for <Entity ZR158981G Laundry Machine State>
A message in the logs regarding use of deprecated methods: fixed in dev
2022-08-03 20:17:58.788 WARNING (MainThread) [homeassistant.components.number] custom_components.ge_home.entities.common.ge_erd_number::GeErdNumber is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom integration author.
I switched to the latest dev in hacs to see, but same issues on v0.6.3-dev3
Issue Analytics
- State:
- Created a year ago
- Comments:40 (12 by maintainers)
Top Results From Across the Web
2022.8: You can fix it! - Home Assistant
First-class support for Bluetooth, get notified about detected issues and how to repair them, find integrations by brand name, and maps with ...
Read more >2022.8.0 completely breaks Home Assistant - Configuration
In the logs I see that the agent is started again and again, but there is no more information. Probably it crashes.
Read more >2022.12: It does matter! - Home Assistant
Breaking Changes; Farewell to the following; All changes ... This means integration can now provide entities that ask for a textual input in ......
Read more >Full Changelog for Home Assistant Core 2022.8
Detailed changelog for the Home Assistant Core 2022.8 release.
Read more >2022.11: A heck of a release! - Home Assistant
Mireds are still working and automatically converted when needed, so this is not a breaking change. Additionally, integrations can now ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That one is resolved in the newest dev release, so you should be good. I think I still might need to rework initialization, seems there still might be some issues with some installations.
so far so good, it’s definitely working for me now!