Pre-compiled firmware files on github

[ksjh]

Pre-compiled firmware files are available on github, but rather hard to find (github builds them automatically after commits to the repo). On the top of the github page, under "Actions", you can find previous runs and "Artifacts" (lower part of the page of one run). The names of the resulting files are not that clear, the file rcp-uart-802154-zbdonglee.zip is the right one for a ZBDongle-E with RTS-CTS handshaking with 115200 baud. Among other things, it contains the required firmware file build/release/rcp-uart-802154.gbl. The naming convention is similar for other hardware. The ZB-GW04 v1.1 is the only firmware file that does not use hardware (RTS-CTS) handshaking.

Please make sure that you select appropriate options in the Silicon Labs Multiprotocol Home Assistant add-on.

[MichaelMaex]

Thank you very much! I flashed the rpc multipan firmware to my ZBDongle-E on Saturday and so far it's working great with my modest setup consisting of a handful thread and Zigbee devices.

[jusicgn]

I want to thank you too. I just flashed my ZBDongle-E with rcp-uart-802154-zbdonglee-none a few minutes ago. Had to manually disable the hardware flow control in the multiprotocol addon settings. Then reconfiguring the zha radio settings and uploading the backup worked like a charm. So far everything seems to work fine including OT. I'll now flash one of my eve devices to matter firmware to see if I can connect it using thread.

[jusicgn]

@ksjh thx for the quick reply. I will try to delete zha und repair the devices from scratch then. Do you think I should do this with the actual rcp-uart-802154-zbdonglee-460 or should I flash the rcp-uart-802154-zbdonglee-230 variant before doing so?
Don't know if it's important but I grabbed the -460 variant from your last run https://github.com/ksjh/silabs-firmware-builder/actions/runs/4520545220.

[ksjh]

I think it should not matter too much, but I compiled the 460800 only yesterday, so this new variant has not been tested for long, whereas a number of persons have successfully used the 230400 baud version for a bit longer. I do not expect large problems with the 460800 baud variant, but have only little experience with it.

[jusicgn]

@ksjh alright, flashed the -230 variant and deleted the zha config. Then added a new zha config and repaired all devices. Seems to work for the moment even though the log still displays some of the errors/warnings. Will let that run a little and observe if it's more stable now and then report here.

[ksjh]

Are there still warnings/errors about the wrong protocol versions appearing?
When just the wireless communication is unreliable, perhaps these tips might help to improve wireless reception. Of course, this does not help with the communication between the Pi and the dongle.

[jusicgn]

@ksjh yes, the warning about the protocol version is still there but seems to come up only once when starting zha:

Logger: bellows.ezsp
Source: components/zha/core/gateway.py:185
First occurred: 26. März 2023 um 21:05:25 (1 occurrences)
Last logged: 26. März 2023 um 21:05:25

Protocol version 11 is not supported, using version 10 instead

I also see the following error right before that warning

Logger: bellows.uart
Source: runner.py:179
First occurred: 26. März 2023 um 21:05:00 (2 occurrences)
Last logged: 26. März 2023 um 21:05:20

Lost serial connection: OSError('Server closed connection')
Received an unexpected reset: <NcpResetCode.RESET_SOFTWARE: 11>

Besides these everything seems to work after the reset of zha and repairing all devices.
Can't say much about the reliability, that needs some more time I think. But atm everything seems to work.