Hi, currently with the new firmware 2025.04 I see now following
What I have to do ? I want use it as zigbee but don’t want lost my current network and don’t want reinit all devices
You need to be patient and wait.
It will index the firmware every x amount of hours.
I have two HA Connect ZBT-1, one of them shows the 7.4.4.0 firmware the other still shows ‘Unknown’ and it will eventually recheck and show the correct firmware.
See releases notes of HA 2025.4 .
Oh okay thanks that I didn’t read
The stick I’m using with ZHA shows the correct version.
The stick I’m using with Z2M shows unknown as well after 24h.
Will try to reboot the host to see if that changes. I know they are both running 7.4.4.0 as I updated them myself through the Add-On.
There are more people with issues:
opened 12:53PM - 03 Apr 25 UTC
integration: zha
integration: homeassistant_hardware
### The problem
Home Assistant is displaying that there is a firmware update ( … 7.4.4.0) for my Home Assistant SkyConnect ZBT-1, however I am unable to install it due to an error that is triggering causing any ZHA integrations to fail. The device is currently on 7.1.1.0, however after the firmware update failed. the device is no longer operational, even after being unplugged and plugged back in.
### What version of Home Assistant Core has the issue?
core-2025.4.0
### What was the last working version of Home Assistant Core?
_No response_
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
ZHA
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha/
### Diagnostics information
[home-assistant_homeassistant_sky_connect_2025-04-03T12-42-39.939Z.log](https://github.com/user-attachments/files/19587461/home-assistant_homeassistant_sky_connect_2025-04-03T12-42-39.939Z.log)
### Example YAML snippet
```yaml
```
### Anything in the logs that might be useful for us?
```txt
homeassistant.exceptions.HomeAssistantError: Failed to flash firmware
2025-04-03 13:42:20.031 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: {('zha', '01J1YRHGEZRDZAMRE99FV8VYAT'): 187100.757087061}
2025-04-03 13:42:35.761 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [281472046390656] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/homeassistant_hardware/update.py", line 300, in async_install
await flasher.enter_bootloader()
File "/usr/local/lib/python3.13/site-packages/universal_silabs_flasher/flasher.py", line 272, in enter_bootloader
await self.probe_app_type()
File "/usr/local/lib/python3.13/site-packages/universal_silabs_flasher/flasher.py", line 229, in probe_app_type
result = await probe_funcs[probe_method](baudrate=baudrate)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/universal_silabs_flasher/flasher.py", line 118, in probe_gecko_bootloader
async with self._connect_gecko_bootloader(baudrate) as gecko:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/local/lib/python3.13/contextlib.py", line 214, in __aenter__
return await anext(self.gen)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/universal_silabs_flasher/common.py", line 136, in connect_protocol
_, protocol = await zigpy.serial.create_serial_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<4 lines>...
)
^
File "/usr/local/lib/python3.13/site-packages/zigpy/serial.py", line 137, in create_serial_connection
raise exc.__context__ from None
File "/usr/local/lib/python3.13/site-packages/serial/serialposix.py", line 385, in _reconfigure_port
fcntl.flock(self.fd, fcntl.LOCK_EX | fcntl.LOCK_NB)
~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
BlockingIOError: [Errno 11] Resource temporarily unavailable
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<7 lines>...
)
^
File "/usr/src/homeassistant/homeassistant/core.py", line 2794, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2837, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1007, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
hass, entity, func, data, call.context
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1079, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 157, in async_install
await entity.async_install_with_progress(version, backup)
File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 489, in async_install_with_progress
await self.async_install(version, backup)
File "/usr/src/homeassistant/homeassistant/components/homeassistant_hardware/update.py", line 307, in async_install
raise HomeAssistantError("Failed to flash firmware") from err
```
### Additional information
_No response_
It worked for me after updating to HA 2025.4.1 .
For ZHA it will auto disable the radio to update and re-enable it after update is finished.
For Z2M you need to stop Z2M while you update the Zigbee FW, and afterwards you can start Z2M again.
I have the Unknown state too.
HA 2025.4.3 using Zigbee2MQTT.
According to the history this is since the last week now.
Tried rebooting with both the MQTT Add-On’s stopped to see if that would matter.
Question to anyone: How would the ZBT-1 firmware be updated normally?
Everything works and I like the “do not fix what ain’t broken” approach.
Another way is to use the HA Add-on.
It’s one of the official Add-ons available.
I’ve used it in the past to update the HA Yellow and several HA Connect ZBT-1 sticks.