Nabu_Casa_SkyConnect "No Such file or directory Directory" - Where should I start looking?

My Zigbee network has been stable for a coupe of years with no changes, additions or modifications, but all of a sudden I’m getting failures.

I loose communication with all of my Zigbee devices, and when I look at the Zigbee integration I see the following error message:

SkyConnect v1.0, s/n: 5433d0fb1b97ed119083c998a7669f5d - Nabu Casa

Failed setup, will retry: [Errno 2] No such file or directory: ‘/dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_5433d0fb1b97ed119083c998a7669f5d-if00-port0’

Reloading the automation does not resolve the issue, but rebooting HA does. Sometimes this is effective for a couple of days, sometimes a couple of hours, but it eventually drops out again.

I’m using ZHA, some of my devices (44) don’t play well with MQTT.

There are no entries in the Home Assistant Core log for the time period.
There are no entries in the Home Assistant Supervisor log for the time period.
There are no entries in the Home Assistant Host log for the time period.

I’m using the latest stable build.

How old is that stick?
If it was bought in a certain age range, some had a manufacturing defect and were replaced.
You should search that here and see if this stick is in the affected group.

Do you have a link, or more information on what I would need to know to check my sky connect against he defective batch?

It’s the blue dongle, purchased in late 2023, and has been running flawlessly up until last week.

Put this into a search engine:

site:www.home-assistant.io SkyConnect replacement

Something is wrong, it’s only showing this page.

A search engine like google or duckduckgo

According to this, I don’t have one of the effected units.

I think that this started after one for the recent updates, but I’m not certain as there were a string of them close together.

Mine has done the same

You’re experiencing the same sudden disconnects as me on a system that’s been stale for ages?

Yes many years been perfectly fine, then after os upgrade to 17.2 zigbee broke, you can downgrade the ha os to 17.1 or upgrade the eeprom bootloader to fix the issue. Basically the usb devices are not being recognised. I updated the bootloader by using thr raspberry pi imager tool and now its working. See link below

My problems started with 17.0 rather than 17.2, and I’m using a VM rather than a Pi, so there may be a common thread to our problems but I’m not sure if the fix would be similar.

I think that my issue may be due to a Windows update that’s causing my VM to either lose connection to the USB controller (It’s not just effecting devices, it’s the entire controller), or Windows isn’t releasing the controller back to the VM quickly enough for HA to recover after a handover.

I went back to a previous version from a backup with 16.3 and it was still dropping, even though that version had previously been rock solid stable for me on the USB front. Making it unlikely to be an HA issue.

I ended up putting in an automation that would reboot HA if the firmware on my Skyconnect became unavailable or Unknown for a period of time.

It didn’t stop the USB from disconnecting, but it automated bringing them back up.

The automation hasn’t been activated in a while, so the problem has likely been fixed by a subsequent update from Microsoft.