"Unknown Error" when trying to add TubesZB to HomeAssistant #145
Replies: 3 comments 5 replies
-
|
Can you enable debug logging for zha: https://www.home-assistant.io/integrations/zha/#debug-logging and post those logs from trying to add. Also have you tried setting up manually instead of via the auto discovery? If you've successfully done a nvram reset I assume it was done over the network- socket:// connection? that would confirm the coordinator is working as it should. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, the NVRAM reset over the network works fine. Here are the logs for the auto-discovery attempt (I'll go and try the manual setup in a moment):
|
Beta Was this translation helpful? Give feedback.
-
|
And here are the logs for the manual setup: 2023-05-16 15:25:26.748 DEBUG (MainThread) [zigpy_znp.uart] Connecting to socket://192.168.1.21:6638 at 115200 baud |
Beta Was this translation helpful? Give feedback.
-
|
thanks. can you try the zigpy-cli: https://github.com/zigpy/zigpy-cli run the form command, and if that works run an energy-scan. looks like the serial connection is failing in HA. but the fact that you did a reset makes me think it's not the device, as the network nvram resets are a constant write to the device for way longer than this duration. |
Beta Was this translation helpful? Give feedback.
-
|
The first time I ran the form command it got stuck for around 15 seconds before spitting out a bunch of exceptions - one of which mentioned RF interference. I popped down to where the TubesZB device is located and sure enough the WiFi router was sitting closer than it had before. I moved it back to where it should be and ran the command again, and this time it seemed to be successful. I then ran the energy scan, which is (hopefully) below:
|
Beta Was this translation helpful? Give feedback.
-
|
Awesome. okay all is working. as it should. zigpy chose channel 25 to form the network based off an energy scan it does during the formation process. you should be able to now set up zha and have it keep the same formed network. hopefully it works, if not it's something with the network communication between HA and the coordinator. |
Beta Was this translation helpful? Give feedback.
-
|
Well - progress of sorts... the error message has now changed :-) Now showing "Failed to connect", and the logs show: 2023-05-16 17:10:08.406 DEBUG (MainThread) [zigpy_znp.uart] Connecting to socket://192.168.1.21:6638 at 115200 baud I can ping the device ok, but even trying to do the nvram_reset via zigpy in docker now fails with "socket.send() raised exception" |
Beta Was this translation helpful? Give feedback.
-
|
Update: now sorted! I unplugged the USB power cable from the TubesZB device for 30 seconds and plugged it back in. This seemed to help - I still got the "Unknown Error" but I was able to do the NVRAM_reset job. I was then able to add the new radio setup in the ZHA integration. There's two morals to this story I think: 1) Don't break your HA setup like I did, and 2) whomever decided Zigbee should run on the same frequency bands as 2.4GHz WiFi should be shot :-) |
Beta Was this translation helpful? Give feedback.
-
Hey! I have one of the CC2652P2 Ethernet/USB Serial Co-ordinators, and have had it working with Home Assistant for a good while.
For various reasons I've had to rebuild my HA setup, but I can't seem to get the TubesZB device to be adopted by HA. I've been through the Zigpy NVRAM Reset process about 5 times now, and after rebooting HA, the device gets auto-discovered, but when I configure it with the correct IP and port address, I get the red "Unknown Error" message.
I've also tried adding it via the "Setup another instance of ZHA", but this ends with the same outcome...
The onlt thing I can see in the logs when these things happen is:
2023-05-16 15:02:34.877 WARNING (MainThread) [asyncio] socket.send() raised exception. 2023-05-16 15:02:35.878 WARNING (MainThread) [asyncio] socket.send() raised exception. 2023-05-16 15:02:36.879 WARNING (MainThread) [asyncio] socket.send() raised exception. 2023-05-16 15:02:37.879 WARNING (MainThread) [asyncio] socket.send() raised exception. 2023-05-16 15:02:38.880 WARNING (MainThread) [asyncio] socket.send() raised exception. 2023-05-16 15:02:40.421 ERROR (MainThread) [aiohttp.server] Error handling requestWondering if anyone has any ideas?
Kevin
Beta Was this translation helpful? Give feedback.
All reactions