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

Skyconnect fresh out of box gets "unsupported firmware"-error then trying to set it up #127138

Open
Senilare opened this issue Sep 30, 2024 · 1 comment

Comments

@Senilare
Copy link

Senilare commented Sep 30, 2024

The problem

Bought a Skyconnect and plugged it in to my host server (running HA core in a VM on a VMWare server, and yes I made the usb device available for the vm), Started up HA and I get a Notification that it has found a new device. Great!
Then It says it found the Home Assistent SkyConnect. I'm clicking the "Configure" button, Gets to the "Pick your firmware", selecting zigbee, as instructed, and then.. "Unsupported firmware" (get the same if i choose Thread).

Saw a previous thread with simular problem, they had flashed the usb-device, but following that link it says it's unavaible now.
What shall I do?

The only other device that is connected is my IKEA dirigera. Other then that, nothing changed or added. Just played around with the dashboard.

Here is the "process" and system info. Nothing in the logs.
OH YEAY! New device!
part 1

A Skyconnect, lets config!
part 2

Zigbee sounds nice
part 3

OH, crap!
part 4

Sysinfo:
system

Core 2024.8.1
Frontend 20240809.0

What version of Home Assistant Core has the issue?

core-2024.8.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Core

Integration causing the issue

Skyconnect

Link to integration documentation on our website

https://www.home-assistant.io/connectzbt1/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Nope, not a single logentry to see :/

Additional information

No response

@Senilare
Copy link
Author

Found a solution in another thread about the same thing. That worked for me.
Maybe change the error message to give more info? For it's not a firmwareproblem, it's a permission problem.

##119101 (comment)

Adding the user to the dialout group (and relogging in!) fixed it (debian):
sudo usermod -a -G dialout homeassistant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant