Problem initiating an Elelabs zigbee dongle; Application frame 83 (setConfigurationValue) received: b'35' #266
Comments
|
1.that is not the most recent version of bellows, this log was collected before Apr 15th? The out of memory is strange, cause I'm running on my HUSBZB with 32 source routes without any issues and the same initializes fine on the older elelabs stick I have. I'd escalate with Elelabs, must be something related to this specific firmware as a lot of people are running these parameters without issues. Alternatively, try a separate venv with |
|
or try changing the source route table size to bellows/bellows/config/ezsp.py Line 77 in 191cafe |
|
Thanks, i did clone the code today, git describe might be misleading if no new tag is set, this is 20 commits after the tag
I’ll try the older version tomorrow
//M
Skickat från min iPhone
… 26 maj 2020 kl. 17:58 skrev Alexei Chetroi ***@***.***>:
or try changing the source route table size to 8 or decrease the number EZSP_CONFIG_MAX_END_DEVICE_CHILDREN is https://github.com/zigpy/bellows/blob/191cafe5ffad9bcb3dfe72dedeb78c25c2760b9c/bellows/config/ezsp.py#L77
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Running on old versions work, can I do this in a recent homeassistant install in any way? This did not work (not sure I did it correctly though, I changed the constant in bellows/types/named.py |
|
Nope, that's wrong. You should change default values for that parameter in https://github.com/zigpy/bellows/blob/191cafe5ffad9bcb3dfe72dedeb78c25c2760b9c/bellows/config/ezsp.py Alternatively, if using with home assistant 0.110 or newer, add to configuration.yaml Although personally, I'd reduce the number of max end devices, 32 is way too high and increase source routes number to 16 |
|
Thanks I'm getting somewhere now, but without the dash in the config: Is there a way to set the channel and network key this way to? I'm running hassio and I cant get the bellows to install without gcc (pycryptodome setup). |
|
you would need to form the network again, meaning you would have to re-pair all the devices. ATM not possible to update the network key or channel.
or you could put under and restart HA |
|
@Adminiuga should network key & channel configuration be in current or next ZHA integration docs? https://www.home-assistant.io/integrations/zha/ https://github.com/home-assistant/home-assistant.io/blob/current/source/_integrations/zha.markdown https://github.com/home-assistant/home-assistant.io/blob/next/source/_integrations/zha.markdown |
|
Don't think so, it's not supported by all radios yet |
|
Hi, I'm still struggling a bit. now I can start bellows most of the times but it is sometimes failing on startup/initiation When I get it past that I'm experiencing some other fault that might be related but also might be due to the fact that I'm trying to join a new door lock that I am developing. any hints on why it is leaving the network after the initial handshake is greatly appreciated. (should I open a new ticket for this? kept it here until the startup is rock solid). When running the door lock with another controller (nrodic nrf52840 cli example applicatrion) then it is working. debug output and sniffer log: |
|
Hard to say why it is leaving. Take zigbee packet capture when joining both to bellows and to Nordic controller and compare. Unfortunately with zigbee, when device is leaving is does not provide a reason to the other party. If you can enable debug on the lock itself, then maybe it could provide more insight in what exactly it did not like. |
|
Elelabs stick seems to be running protocol version 6, EZSP 6.0.3 stack. Could be related to ZB3.0 interop? |
|
Thanks, I'm new to this and have little knowledge on the EZSP stack versions. Is 6.0.3 an old or new one? Can I get hold of a correct version somehow? (Elelabs have yet to answer my first email, but might respond if I have a more specific question, but my hopes are not to high at the moment) What usb-adapter / rpi-shield is best today? I mainly selected the elelabs since there were hints of support for the closure/door_lock cluster which is my main interest at this time. |
|
EZSP stack version 6 had a significant change for the end-device-poll-timeout registry compared to 5. |
|
thanks, the version seems to be 24 624 (0x6030) Should the old way be used? or was the check >= 0x64ff in error? |
|
This should be fixed in 0.18.0 (ha 0.113.x) |
|
I get the exact same issue on bellows 0.18.1 and homeassistant 0.114.4 with Elelabs USB adaptor: |
|
Should be fixed HA beta version. zha:
zigpy_config:
ezsp_config:
CONFIG_SOURCE_ROUTE_TABLE_SIZE: 8 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I have just purchased the Elelabs USB-dongle and also their RPi shield. both have the same issue and I would appreciate any help in what is going on.
There seems to be a problem setting the channel?
Im just beginning with bellows and home assistant (same problem there) so any hints are appreciated
The text was updated successfully, but these errors were encountered: