I’ve manually followed the automated build process used in GitHub - NabuCasa/silabs-firmware-builder: Silicon Labs firmware builder (github actions) and indeed ANTENNA_0 is being configured (in config/sl_rail_util_rf_path_config.h) and used for MGM210PA32JIA
I managed to build the firmware, changing it to ANTENNA_1, but can’t try it out - my soldering skills are likely much worse than in software and i’m not immediately having any u.fl handy
By the way, has the J9 been connected to the ground before the soldering?
Anyway, having h/w modification already performed, i would definitely give it a try to updated firmware.
Essentially, I followed steps described in those 3 files:
.github/workflows/build.yaml
.github/workflows/silabs-firmware-build.yaml
for “ncp-uart-hw-yellow”.
I could also share the binary, but wouldn’t recommend to trust it and build it yourself instead.
Please let me know if you need any detailed instructions.
It is not totally grounded. I’m pretty sure, that there is some inductor/feeding thing to ground.
That software part is hard to me. I’d like to test, but i need more detailed instructions. Very noob.
Very interested to see if that works, please report back or let me know if there’s anything else to unblock it.
What’s you current firmware by the way? I’ve upgraded from default 6.x to 7.3.1.0 (silabs_flasher add-on) couple days ago and it seems to be working a little better. A few end devices - couple of third reality water leak sensors and hue motion sensor kept going unavailable, holding better so far. Too soon to tell though.
Ouch, there is now a small problem. I’m very old electrician from analog-era. I have no idea, what i should do? I can copy file, if i know to where, or edit file but how i locate correct one? Very noob, as i said. Yep, firmware version. Perhaps it can be found somewhere…
No worries.
The current version could be found at the coordinator’s device page.
In the Settings -> Devices & Services -> Zigbee Home Automation click on devices list and find the device. It should be named “Silicon Labs EZSP”.
Configure the add-on - ssh key or password, take a note the username
open web ui of the add-on and type pip install universal-silabs-flasher
from your computer copy the firmware to the addon file system, with smth like: scp ncp-uart-hw.gbl [email protected]:
(assuming the username is default for the add-on, and the firmware file name is it is the github action artifact zip)
Wondering if you recently restarted the home assistant or just installed the 2024.3 update?
It also showed as “Zigbee Coordinator” to me right after the update, then after several minutes it popped up back as “Silicon Labs EZSP” in the list.
It’s not an issue anyway, you could follow the steps to update the firmware as described in the post above.
You need the “Advanced SSH & Web Terminal”.
It would allow you to use python packages (pip) and provides access to the usb port (once the protection mode is disabled)
Ok. I will need the usb-port also? Transferring files or ? Sorry my stupidity, software things are never been my thing. Only programming language what i have learned, is Microchip assembler. Perhaps, when it is like turning switches…
Now i’m in this point. How i tell to terminal where this file is located? To where i should put it? I feel stupid again…
E: I uploaded it to /homeassistant with file editor. Now it is in the HA at least.
I have no idea, where this file is, or how i can find it… How i should type, when it should be in /homeassistant (or /config) folder?
E: Oh sh*t. One letter error, p can’t be b…
E2: Solved partially. Small problem left. $ is not regonized for command… When try to flash.
E3: Now i’m stuck in here. Device is wrong…
E4: It needed some modifications. Had to change start folder and device path. Now it is running again. Will see, what happened… A lot of work to forget dos commands… This is very different world.
E5: All seems be working still. Range tests go some other day… There was no silabs device mentioned in coordinator properties. But version changed, as should.
E6: Shortly now, it seems that there is now lot more direct connections to coordinator.
