Closed tassadar81 closed 2 years ago
Hey there @dmulcahey, @adminiuga, 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)
This line caught my eye
raise RuntimeError(
RuntimeError: Network formation refused, RF environment is likely too noisy. Temporarily unscrew the antenna or shield the coordinator with metal until a network is formed.
Have you tried using an USB extension cable?
@puddly shouldn't this be propagated above?
shouldn't this be propagated above?
Do you mean logging it explicitly as an error message instead of just as part of traceback?
This line caught my eye
raise RuntimeError( RuntimeError: Network formation refused, RF environment is likely too noisy. Temporarily unscrew the antenna or shield the coordinator with metal until a network is formed.
Have you tried using an USB extension cable?
@puddly shouldn't this be propagated above?
Yes, it's connected with a 1 metre extension cable. but is this the problem? I can't get working the dongle itself not to scan for new devices
I can get working know just configuring it manually and specifying the port and the rate, leaving the data flow control blank
zigpy-znp gives the stick 30s to form a network. Instead of forming a network, the stick locks up (likely because the network formation scan fails). It's an environment problem. While it works for now, I would suggest investigating why a network can't be formed because that same problem will likely prevent you from adding new devices and communicate effectively with the ones you manage to join.
Do you have it plugged into a USB 3.0 port? Near a 3.0 port? Near a SSD? A 2.4GHz WiFi router? Raspberry Pi? Another computer? Is it being powered from an external USB hub?
It's plugged into a usb 2.0 port. now it's working and quite close to a WiFi router. I also was able to add two ikea bulb and to do some turn off/on roundtrip and change the light level. The adapter is attached into a rpi4 4gb ram booted from an SSD
shouldn't this be propagated above?
Do you mean logging it explicitly as an error message instead of just as part of traceback?
No, i mean if the runtime exception is thrown, then there shouldn't be a timeout in request_cb_response? Alternatively, the timeout exception should be risen from the runtime exception
The runtime error is a result of a timeout: Z-Stack never sends a final response callback to the network formation command and the 30s timeout is triggered. There's no "failed" status indication, the RuntimeError
is just adding some text to the otherwise unhelpful TimeoutError
that happens when Z-Stack's internal formation scans fail.
The problem
Just after choosing the tty, the configuration crashes after a while, it seems a timeout
What version of Home Assistant Core has the issue?
core-2021.12.5
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
https://www.home-assistant.io/integrations/zha/
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response