Skip to content
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

HZA - Skyconnect "Unsupported Firmware" #119101

Closed
edge0815 opened this issue Jun 7, 2024 · 21 comments
Closed

HZA - Skyconnect "Unsupported Firmware" #119101

edge0815 opened this issue Jun 7, 2024 · 21 comments

Comments

@edge0815
Copy link

edge0815 commented Jun 7, 2024

The problem

After Update to core-2024.6.1, the HZA Skyconnect is not recognised anymore. Status on the Zigbee Page is "Unsupported Firmware"
Firmware on the Stick is untouched, since it was shipped. No update available.
Screenshot_20240607-220543

What version of Home Assistant Core has the issue?

core-2024.6.1

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

HZA

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Jun 7, 2024

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (homeassistant_sky_connect) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of homeassistant_sky_connect can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign homeassistant_sky_connect Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


homeassistant_sky_connect documentation
homeassistant_sky_connect source
(message by IssueLinks)

@Boppie1976

This comment was marked as duplicate.

@ftreil

This comment was marked as duplicate.

@timmills

This comment was marked as duplicate.

@Breaveheard

This comment was marked as duplicate.

@timmills
Copy link

timmills commented Jun 11, 2024 via email

@mib1185
Copy link
Contributor

mib1185 commented Jun 11, 2024

Hi all,
please use the +1 reaction on the initial post, over "same here" post, thx 👍

@home-assistant
Copy link

Hey there @dmulcahey, @Adminiuga, @puddly, @TheJulianJES, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


zha documentation
zha source
(message by IssueLinks)

@mib1185
Copy link
Contributor

mib1185 commented Jun 11, 2024

@edge0815 could you please provide the home-assistant.log and the zha debug information as mentioned in the docs?

@puddly
Copy link
Contributor

puddly commented Jun 11, 2024

Status on the Zigbee Page is "Unsupported Firmware"

It sounds like you're already using the SkyConnect and have been for some time.

Did you get a SkyConnect discovery and then click "use as Zigbee" while already using the SkyConnect?

@Tyst

This comment was marked as duplicate.

@edge0815
Copy link
Author

It works again without changing anything. Currently I haven't anything in the logs and forgot to save ealier.
Maybe someone with the same issue can upload?

@Tyst
Copy link

Tyst commented Jun 16, 2024

I'm still having this issue. Should I create a new post?

@mib1185
Copy link
Contributor

mib1185 commented Jun 16, 2024

no new post, but if you have any helpful information like logfiles (see #119101 (comment)) or more concrete error messages, than please post them here, thx 👍

@noxiii
Copy link

noxiii commented Jun 20, 2024

I had the same issue. From home assistent I got only the information that the firmware is not supported. I found out that I never updatet my skyconnect and still installed version 1.0. and I had configuerd zigbee and openthreat.

I updatet the skyconnect up to 7.0 followd by this github projekt: https://github.com/NabuCasa/universal-silabs-flasher

The stick was usable again but all connection was lost. I restored the last homeassisten backup from before the upgrade to 2024.6 and could also restore all my zigbee device.

I hope this help you.

@Tyst
Copy link

Tyst commented Jun 20, 2024


2024-06-20 16:37:37.019 DEBUG (MainThread) [homeassistant.components.zha.repairs.wrong_silabs_firmware] Failed to probe application type
File "/usr/src/homeassistant/homeassistant/components/zha/repairs/wrong_silabs_firmware.py", line 87, in probe_silabs_firmware_type
2024-06-20 16:37:41.590 DEBUG (MainThread) [homeassistant.components.zha.repairs.wrong_silabs_firmware] Failed to probe application type
File "/usr/src/homeassistant/homeassistant/components/zha/repairs/wrong_silabs_firmware.py", line 87, in probe_silabs_firmware_type

@zoechi
Copy link

zoechi commented Jun 20, 2024

I changed the baud rate to 230400 in OTBR and then the error was gone.
When I later checked the baud rate in OTBR it was 460800 again (after a reboot).
I'm pretty sure I forgot press the "save" button.
Perhaps just loading the OTBR configuration page fixed it.

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 11, 2024
@EmielM
Copy link

EmielM commented Jul 16, 2024

Had a similar issue with home assistant core, enabling debug logging indicated it was a permission problem for the homeassistant user:

2024-07-16 12:25:35.143 DEBUG (MainThread) [zigpy.serial] Opening a serial connection to '/dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_d61db152f5e1ed11b2b4eb5162c613ac-if00-port0' (115200 baudrate)

PermissionError: [Errno 13] Permission denied: '/dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_d61db152f5e1ed11b2b4eb5162c613ac-if00-port0'
    self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Adding the user to the dialout group (and relogging in!) fixed it (debian):

sudo usermod -a -G dialout homeassistant

Hopefully this helps some folks (this is the top Google hit for skyconnect unsupported_firmware).

For home-assistant, it would be a nice improvement to give a better error message in the web UI.

@vednolacni
Copy link

is there any update on this?

@t-luetkenhaus
Copy link

In my case I disabled CuXD in Homematic Addon. It seems that this addon is blocking the interface.

@github-actions github-actions bot locked and limited conversation to collaborators Sep 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.