Closed DarthGaymer closed 1 year ago
Hey there @dmulcahey, @adminiuga, @puddly, 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!
(message by CodeOwnersMention)
zha documentation zha source (message by IssueLinks)
What hardware are you running Home Assistant OS on?
Were you ever able to add the ZHA integration, or is this happening during the initial setup?
Raspberry Pi 4 (4G RAM currently maxing out around 1.2G used) running on an SSD.
This happened during initial setup of the Sky Connect and have never been able to get ZHA to work, even after uninstalling & reinstalling the add on
Can you take a screenshot of the specific addon you're installing?
Ah, I see. The SkyConnect ships with Zigbee firmware but since you've installed the multi-protocol addon, you've flashed it with the multi-protocol firmware.
The Multiprotocol addon is a little experimental at the moment and the user-friendly setup flow is going to be re-enabled in the upcoming beta release. For now, you will have to manually set up ZHA to connect to the addon:
socket://core-silabs-multiprotocol:9999
and continue with the default settings.Following the above still results in an error
Do you have any other addons running that could be accessing the radio (i.e. Zigbee2MQTT)?
Physically unplug the SkyConnect, plug it back in, and try clicking the "Submit" button again in 30s. If that doesn't work, can you post the addon debug log?
I do not believe I have any other addons or integrations that are attempting to access the radio, all are listed below. AdGuard Home AsusWRT Cloudflared Home Assistant Google Drive Backup HACS Homekit Controller (Ecobee) Keymaster (HACS smart lock manager) MyQ TP-Link Kasa (wifi plugs) Z-Wave JS Z-Wave JS UI Silicon Labs Multiprotocol (error persists with add on uninstalled, not running, and running)
I am unable to find an addon debug log as Zigbee Home Automation does not show up in Add Ons and can only be found by the Add Integration button, but fails on setup
Installing the multiprotocol addon flashes special firmware to your SkyConnect. Without the addon running, ZHA cannot talk to the SkyConnect.
The addon debug log is in the same area as where you took the screenshot of the addon configuration, just in a different tab:
Can you take a screenshot of your Silicon Labs Multiprotocol addon configuration as well?
Below is the Log info
s6-rc: info: service banner successfully started s6-rc: info: service universal-silabs-flasher: starting [12:50:42] INFO: Checking /dev/ttyUSB1 identifying SkyConnect v1.0 from Nabu Casa [12:50:42] INFO: Starting universal-silabs-flasher with /dev/ttyUSB1 (baudrate 57600) 2023-01-26 12:50:43 core-silabs-multiprotocol universal_silabs_flasher.flash[218] INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version=<AwesomeVersion SemVer '4.1.4'>, ezsp_version=None, fw_type=<FirmwareImageType.RCP_UART_802154: 'rcp-uart-802154'>) 2023-01-26 12:50:43 core-silabs-multiprotocol universal_silabs_flasher.flasher[218] INFO Probing ApplicationType.GECKO_BOOTLOADER 2023-01-26 12:50:45 core-silabs-multiprotocol universal_silabs_flasher.flasher[218] INFO Probing ApplicationType.CPC 2023-01-26 12:50:49 core-silabs-multiprotocol universal_silabs_flasher.flasher[218] INFO Probing ApplicationType.EZSP Error: Failed to probe running application type 2023-01-26 12:50:54 core-silabs-multiprotocol concurrent.futures[218] ERROR exception calling callback for <Future at 0x7f8cd7aa30 state=finished returned NoneType> Traceback (most recent call last): File "/usr/lib/python3.9/concurrent/futures/_base.py", line 329, in _invoke_callbacks callback(self) File "/usr/lib/python3.9/asyncio/futures.py", line 398, in _call_set_state dest_loop.call_soon_threadsafe(_set_state, destination, source) File "/usr/lib/python3.9/asyncio/base_events.py", line 791, in call_soon_threadsafe self._check_closed() File "/usr/lib/python3.9/asyncio/base_events.py", line 510, in _check_closed raise RuntimeError('Event loop is closed') RuntimeError: Event loop is closed s6-rc: warning: unable to start service universal-silabs-flasher: command exited 1 /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. prog: fatal: stopping the container. s6-rc: info: service mdns: stopping s6-rc: info: service banner: stopping Default: mDNSResponder (Engineering Build) (Jan 23 2023 22:49:33) stopping s6-rc: info: service banner successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped [12:50:55] INFO: mDNS ended with exit code 4 (signal 0)... s6-rc: info: service mdns successfully stopped
And here is the Configuration. All items not shown are default values
Set the barbiturate to 115200 and (re)start the addon and look in the log.
Thank you, everything now appears to be working correctly.
When I first attempted to set up the Sky Connect, I tried searching for what the baudrate should be set at but was unable to find anything.
Had the same problem with having Multiprotocol installed and unknowingly flashing the skyconnect.
Got errors like Error: spawn udevadm ENOENT
and the timeout Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
But reverting the firmware to the original did the trick for me. https://skyconnect.home-assistant.io/firmware-update/
The problem
Recently received Sky Connect. When trying to set up with included USB extention, Home Assistant errors out and is unable to start/set it up. This continues with all USB ports, and two other USB extention cords (both work with Zwave stick). This issue also persists through hardware restarts. Error log attached.
What version of Home Assistant Core has the issue?
2023.1.7
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
No response
Diagnostics information
home-assistant_zha_2023-01-25T19-01-30.354Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response