Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms) #430
Comments
|
I seem to be experiencing this after a fresh install of Home Assistant and recovery of my old setup. However, I cannot work around it by installing the proxy. ETA: I have the slae.sh CC2652R stick. The system recognizes that the USB dongle is attached. It worked perfectly fine on a docker setup before I switched to plain HAOSS. I tried ZHA as well. ZHA gives me a disconnect fail, too. |
|
Just got the SkyConnect device. Get same error message when I try to start zigbee2mqtt: Zigbee2MQTT:error 2022-12-11 11:52:17: Error while starting zigbee-herdsman |
SkyConnect worked with ZHA, but after removing ZHA and trying to use the SkyConnect with Zigbee2MQTT I get the same error. |
|
Havind the same problem ,clean install on a raspberry pi with HA. zigbee stick that worked before. whole hardware setup belongs to a friend...weird... |
|
I have the same problem. I am using a Sonoff Zigbee Stick. I disabled and deleted ZHA. I have tried through the terminal addon if the Serial connection works (test -w /dev/ttyUSB0 && echo success || echo failure) and it does. I don't really know what else i can try |
|
Same here with the ZBDongle-E. I installed z2m edge add-on, but it won't work. Nor can I add ezsp adapter to the config file... |
|
If you get the serial:
port: /dev/THEPORT # <- change this accordingly
adapter: ezsp |
|
Hi, Runing dongle with AH on Raspberry Pi 3b+. please help? |
That did the trick :) |
|
it got rid of the SRSP SYS ping error. Now I only have the 502: Bad Gateway left.... Is the Configuration section of the add-on meant to coexist with a configuration.yaml, or override it? |
I can confirm that. The logs unfortionatly dind't give more insight into the error 502 I am using a Sonoff ZB Stick and the following config in HA: The |
9 Hours. I have been trying to fix this for 9 Straight Hours and this is what fixed it for me. For reference, I am running HAS OS on an Xpenology DS920+ HackiNAS with zigbee2mqtt via the HAS Add-On. The Zigbee dongle I'm using is the "_Aubess ZigBee 3.0", and spent at least 4 of those hours which I'll never get back were attempting to get the CH-341 drivers from archive.org (which from my research do......something, maybe) running. "The listing has the Zigbee2MQTT logo on it" I thought, "This will definitely not be worse than getting waterboarded" they said. This is my first foray in to zigbee2mqtt after reading so many threads about it's superiority to ZHA - which, for the record, worked automatically with my Zigbee USB. My rhythmic face smashing into SSH was in hopes of getting passthrough to a Docker instance of Z2M working after running in to OP's issue in the Add-On, which also didn't fix this. It's nearly 6:30am and I haven't slept. I refuse to be defeated by a £9 Aliexpress dongle, though I should have given up. I don't have a firstborn, but I would go out and make a whole pile of dumpster babies to sacrifice if it could make me un-experience the disgust I feel right now. Now matter how hard I scrub that Linux command line dirt just won't come off. To be clear to anyone else as inexperienced / sleep deprived as I am, @Koenkk means that this should go in the 'configuration.yaml' located in the '/zigbee2mqtt' subfolder, not your main Home Assistant config. I think I'm going to just go ahead and rip out my brand new Cat 6A runs and replace all my smart bulbs with Candles. Thank you @Koenkk for freeing me from these 7 (layers of dip, and 7) layers of hell, but good god I think I'd rather go through getting off of painkillers than troubleshoot Zigbee. Computers were a mistake. |
|
Adding |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
|
when i add "adapter: ezsp" then save it will print error as follow Failed to save add-on configuration, does not match regular expression ^zstack|deconz|zigate$. Got {'data_path': '/config/zigbee2mqtt', 'external_converters': [], 'devices': 'devices.yaml', 'groups': 'groups.yaml', 'homeassistant': True, 'permit_join': False, 'mqtt': {'base_topic': 'zigbee2mqtt'}, 'serial': {'port': '/dev/ttyUSB1', 'adapter': 'ezsp'}, 'advanced': {'log_level': 'warn', 'pan_id': 6754, 'channel': 11, 'network_key': [1, 3, 5, 7, 9, 11, 13, 15, 0, 2, 4, 6, 8, 10, 12, 13], 'availability_blocklist': [], 'availability_passlist': []}, 'device_options': {}, 'blocklist': [], 'passli... |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
I had a different issue where my Sonoff ZigBee 3.0 V2 (E model) dongle wasn't available, but I could see it in HA. The above fixed it. |
|
Why isn't this automatic? |
really??!! hours and hours and just move the adapter under serial!!! come on!! thnks!! love you jaja |
|
My god. I just found this and it's the answer to my SLZB-06 mqtt startup issues. Why is this not in the zigbee2mqtt quick start guide? |
|
This solved my problem using Skyconnect on a Proxmox installation after setting the USB interface in Proxmox hardware USBdevice itself: Use USB Port In HA Zigbee2MQTT config: mqtt serial |
|
for me, this worked: for a conbee 3 |
|
Everything worked for a long time and reliably. I tried to add: Didn't help. Didn't help. Rebooting stick by the power help me. Rebooting from web - does not help |
|
i have exactly the same issue. |
and others
Description of the issue
Installing zigbee2mqtt as home helper addon gives error Error: SRSP - SYS - ping after 6000ms
It looks like the reason is that /run/udev is not mounted in the container.
It works if you separately install koenkk/zigbee2mqtt + addon zigbee2mqtt proxy.
I want to understand how the default addon zigbee2mqtt works for others. Perhaps it needs to be installed in some other way.
Addon version
1.28.4-1
Platform
Core: 2022.11.5
Supervisor: 2022.11.2
Operating system: Linux raspberrypi 5.15.76-v8+ #1597 SMP PREEMPT Fri Nov 4 12:16:41 GMT 2022 aarch64 GNU/Linux
Logs of the issue (if applicable)
No response
The text was updated successfully, but these errors were encountered: