Home Assistant 2023.10 - If you have issues, please share here.

[surakin]

I could not see any error message on the home assistant logs :-\ even after reloading the integration several times.

I reverted to 2023.9.3 and it works again.

[dotvezz]

I'll update my home assistant setup and validate/debug as needed. Thanks for the update.

While we're here, quick question: What method are you using to run Home Assistant? (Container, VM, Managed, etc)

[dotvezz]

Interesting - one of my devices fails, but the rest are all working.

[surakin]

I'll update my home assistant setup and validate/debug as needed. Thanks for the update.

While we're here, quick question: What method are you using to run Home Assistant? (Container, VM, Managed, etc)

It's a docker container

I only have one device (pure cool link)

[dotvezz]

docker-home-assistant-1  | Traceback (most recent call last):
docker-home-assistant-1  |   File "/usr/src/homeassistant/homeassistant/config_entries.py", line 399, in async_setup
docker-home-assistant-1  |     result = await component.async_setup_entry(hass, self)
docker-home-assistant-1  |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
docker-home-assistant-1  |   File "/config/custom_components/dyson_local/__init__.py", line 161, in async_setup_entry
docker-home-assistant-1  |     await hass.async_add_executor_job(
docker-home-assistant-1  | asyncio.exceptions.CancelledError: aiohttp connection lost

I was able to pull this from my docker logs. Not sure what this is, looking into it.

[dotvezz]

Oh, I'm being silly - that error from my logs (and that one fan that fails) is just because it was unplugged.

I'm not able to reproduce your error at the moment, but I don't want to dismiss your issue at all. I'll keep looking into new issues from 2023.10 (I didn't have the presence of mind to check for possible bugs before it was released this time around, totally forgot it was coming) and see if I can find anything that helps.

In the meantime, let's see if we can get other reports from other users seeing similar issues on 2023.10. And of course, let me know if you want to try to upgrade and enable debug logging, maybe we'll get some information from another attempt.

[surakin]

I can do that ( if you tell me how :P )

On Thu, 5 Oct 2023 at 20:52, Ben Vezzani @.***> wrote:

Oh, I'm being silly - that error from my logs (and that one fan that fails) is just because it was unplugged.

I'm not able to reproduce your error at the moment, but I don't want to dismiss your issue at all. I'll keep looking into new issues from 2023.10 (I didn't have the presence of mind to check for possible bugs before it was released this time around, totally forgot it was coming) and see if I can find anything that helps.

In the meantime, let's see if we can get other reports from other users seeing similar issues on 2023.10. And of course, let me know if you want to try to upgrade and enable debug logging, maybe we'll get some information from another attempt.

— Reply to this email directly, view it on GitHub https://github.com/libdyson-wg/ha-dyson/issues/72#issuecomment-1749466692, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFG5BA2WTZP25MB3HT7N5DX536WLAVCNFSM6AAAAAA5T2O6VWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZGQ3DMNRZGI . You are receiving this because you authored the thread.Message ID: @.***>

[surakin]

if I try 'enable debug logging' in the integration settings all I get is this 2023-10-05 21:13:06.580 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Living room' for dyson_local integration not ready yet: None; Retrying in background

[surakin]

Odd.... suddenly, it's working 🤷 it didn't for an entire day before I rollbacked

[dotvezz]

Hmmmm that's good but frustrating. Let's keep this issue open for the time being for others to possible post their issues if they have any (I'll rename it for discoverability).

If you have any further problems on 2023.10, feel free to pop back here and we can try to address it.

[surakin]

Yes, I'll keep poking around to see if it's a network fluke or something else

[SumiS91]

after updating HA to 2023.10 (installed on a raspberry pi with HA OS) and the addon to 1.2.0 my entities stoped working and everything was unavailable. I restored my HA back to 2023.09, were i still had version 1.1.0 installed and it didn’t work either. After that i upgraded HA back to the latest version, deleted the device completely and readded it (Dyson Pure Cool Link) while i was on version 1.1.0. After the update to 1.2.0 it still works and everything is back to normal.

it‘s a really strange behavior and i couldn’t find anything in the logs why it happened, but maybe it helps somebody who has the same problem.

[surakin]

I just realized my pure cool link was having trouble connecting to my wifi network from before the 2023.10 upgrade 🤔 (something about 20mhz/40mhz wifi channels) I'll see if future HA upgrades still show my issue now that I set it to 20mhz again

[dotvezz]

Seems like there aren't any prevalent issues with the new Home Assistant releases. I'll close this issue, and we can track any individual issues as normal.