Replies: 47 comments 95 replies
-
Beta Was this translation helpful? Give feedback.
-
|
Great. |
Beta Was this translation helpful? Give feedback.
-
|
The |
Beta Was this translation helpful? Give feedback.
-
|
This is the firmware used with it: https://github.com/grobasoz/zigbee-firmware/tree/master/EFR32%20Series%201/EFR32MG1B-256k/NCP. It's the NCP_UHW_MG1B232_678_PA0-PA1-PB11_PA5-PA4 variant. In the readme, it says that it supports EZSP V8. Hope that helps! |
Beta Was this translation helpful? Give feedback.
-
|
@mbjd05 do you by any chance know if it's safe to update from V7 to V8 in general, and for this SOC in particular? From what I read on this page the gateway ships with V7. It also says it might not be possible to revert to stock etc. Don't want to brick the gateway by updating to V8. Instructions here also indicate to flash V7: |
Beta Was this translation helpful? Give feedback.
-
|
@mbjd05 The firmware you mention (and that I am using) to update the Lidl Gateway is EmberZNet 6.7.8.0 and correspond to EZSP V8 version: In order to be able to use the new Ember driver on a Lidl Gateway you would need to be able to flash it with - at least - an EmberZNet 7.4 firmware (EZSP version 13) as stated in this @Koenkk message. |
Beta Was this translation helpful? Give feedback.
-
@guzzard I followed the same instructions as you linked, that's where I got the link from. When I matched the filename in the firmware link provided to the filename in readme of the repository that it is in, I read in its description that it uses EZSP V8, like @jnilo1 said. I am not sure where the instructions indicate that the update to flash sets the EZSP version to V7. I get the confusion, however, as the title of that section of the guide confuses EmberZNet version with EZSP version: "Upgrade the EZSP Version to 6.7.8.0" which got me confused at first too. Unfortunately, using EZSP V8 makes no difference with regards to being able to use the new driver, because as @jnilo1 said as well, we would need at least EZSP V13 for that |
Beta Was this translation helpful? Give feedback.
-
Hello again, Same stuff in logs on my side. I don't exactly know when they started appearing though. I'd say they're not so recent. They've been somehow pretty harmless (i.e. no particular instability/malfunction) until now but starting much more recently, some new ones started appearing stating something like (sorry, haven't got my machine around) :
Everything could've gone on as if nothing happened but it seems like one (and only one until now) of my devices started behaving erratically since then. It's a Philips Hue Iris 7099930PH (which, by the way, is identified as a 7199960PH, could be related...). The device goes "offline" quite often and most of the time, a restart of zigbee2mqtt does the trick : it's back online. But sooner or later will get off the grid again, can be 10 minutes or 24 hours... I can tell the device is not totally dead because one of my switches (Ikea E1744) which is bound to it manages to turn it on/off and to change its brightness. But still : no control from z2m (or Home Assistant FWIW) until z2m restart. I'd be happy to provide more feedback on this issue but I actually don't know how. If it's only related to ezsp driver depracation, oh well that's a pity. But as @Koenkk says things should working as is, I'm wondering if that could be something else... Don't hesitate to give me hints on how to provide more precise feedback. But hey : z2m is still a precious and wonderful piece of software and I can't thank you all enough for keeping it that way. I really mean it. |
Beta Was this translation helpful? Give feedback.
-
|
Same situation here. I have tried to compile a NCP-UART updated version with Simplicity Studio but it seems not available. Only the multi protocol Openthread / Zigbee is available, but I get some errors during compilation. Indeed a Silabs expert would help. |
Beta Was this translation helpful? Give feedback.
-
|
Have you tried to compile the RCP-UART version associated with the Lidl Gateway chip as an example ? It should be, from what I understand, possible to use it with home assistant and would bring EmberZnet 7.4.3 . See my recent post in this forum. |
Beta Was this translation helpful? Give feedback.
-
|
RCP Uart will need an external host to handle the ember stack. You will be required to install an additional add-on to handle the zigbee stack. RCP uses only the radio part of device. Anyway I compiled succesfully a 7.4.3, the only issue at the moment is that you have to start the mcu manually via the jump command J 80C00000. Trying to understand the differend with the old 6.7 firmware |
Beta Was this translation helpful? Give feedback.
-
|
Congrats ! I think you are getting close... On my side I compiled the RCP-UART with Simplicity Studio 5 as well but I am not too sure about the pin assignment and I still have a warning at the end of the compilation. I assigned PA0 to USART0_TX, PA1 to USART0_RX, PA4 to USART0_RTS, PA5 to USART0_CTS and PB11 to GPIO mode. But I still have a out of boundary warning left. 'memcpy' forming offset 32 is out of the bounds [0, 32] of object 'shared_secret' with type 'uint8_t[32]' {aka 'unsigned char[32]'} [-Warray-bounds] psa_crypto.c /rcp-uart-802154_3/gecko_sdk_4.4.3/util/third_party/mbedtls/library line 6789 C/C++ Problem Also I have to figure out to generate the .gbl file from the .hex or the .bin files and finally I was not too sure about bootloader... Still a total newbie to this... Any guidance will be appreciated ! |
Beta Was this translation helpful? Give feedback.
-
Could it be a checksum issue ? See this post where the user is stuck within the bootloader and has to use the same trick to jumpstart. A solution seems provided here in the same discussion |
Beta Was this translation helpful? Give feedback.
-
|
I finally succeeded to compile the RCP-UART-802154 project for the EFR32MG1B232F256GM48 chip without any errors and warnings. I then generated the .gbl file with the commander utility and flashed it to the Lidl gateway with this script. I did that over a formerly hacked Lidl gateway and had to use the V8 parameter to flash the firmware. |
Beta Was this translation helpful? Give feedback.
-
|
serial: |
Beta Was this translation helpful? Give feedback.
-
|
@jnilo1 to configure a tcp port in the Silicon Labs Multiprotocol module in Home Assistant you need to use the advanced button. Anyway I did it previosly and it seems that the RCP-UART-802154 is too recent (v5) fot the add-on (v4).. Have a look and let me know. |
Beta Was this translation helpful? Give feedback.
-
|
Also if you discover what is halting the boot of the Realtek ... |
Beta Was this translation helpful? Give feedback.
-
|
RCP on my side is working but it seems the version is not compatible with ythe HA add on, here is the log: |
Beta Was this translation helpful? Give feedback.
-
|
What about using the official Silicon Labs multiprotocol docker image rather than the HA plugin ? The image is updated frequently and should in sync with v5 CPCd Protocol. Only available for ARM/V7 architecture though... I tried that on my side but without any succes so far. I probably did something wrong either with the Simplicity Studio parameters and/or the flashing process. @gpaesano can you share your Simplicity Studio parameters (USART0 or 1, pin assignements, other serial parameters, ...) and the way used to flash the gateway ? |
Beta Was this translation helpful? Give feedback.
-
|
I confirm that the current Silabs multiprotocol docker image runs CPCd with RCP Protocol V5: |
Beta Was this translation helpful? Give feedback.
-
|
still trying to understand why while ncp stop loading |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
@jnilo1 see above for the main settings of the rcp |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @gpaesano ! Your settings match mine and are similar to the one used by @grobasoz to generate the original NCP firmware used to update the Silvercrest/Lidl gateway (see his README). Specific Settings: |
Beta Was this translation helpful? Give feedback.
-
|
Not sure if I'm meant to ask general question, but would you guys still advise getting this silvercrest bridge and hacking it to use it for Zigbee2Mqtt? It's criminally cheap atm (€15 for the bridge, a dimmer switch and 3 bulbs!). Or should I just get a standalone coordinator at this stage? |
Beta Was this translation helpful? Give feedback.
-
|
I am stuck in my tests. While trying to understand the cause of the halt in the boot sequence I probably corrupted my bootloader since it now stops without completing its process: Any idea/suggestion on how to recover my boot prompt ? |
Beta Was this translation helpful? Give feedback.
-
|
I finally recovered my boot prompt by desoldering the memory flash and restoring the original firmware with a CH341A programmer and flashrom with the ch341a_spi adapter. I was fortunate enough to have a full backup of the gateway 5 mtd original partitions :-) |
Beta Was this translation helpful? Give feedback.
-
|
Hi, if it is so I will try to finalize the NCP firmware that is already running. Indeed there is a rationale if via the CPC connection an ESC is sent... |
Beta Was this translation helpful? Give feedback.
-
|
A NCP firmware running ? That would be an excellent news. Much simple to handle that the RCP stuf and all the daemons on host side. No size issue with the *.gbl file ? |
Beta Was this translation helpful? Give feedback.
-
|
ncp-uart-hw_3.zip |
Beta Was this translation helpful? Give feedback.
-
|
@gpaesano could you export the corresponding Simplicity Studio V5 project ? |
Beta Was this translation helpful? Give feedback.
-
Not very comfortable in a production environment (power failure and the like...) :-) |
Beta Was this translation helpful? Give feedback.
-
|
ncp-uart-hw_3.zip |
Beta Was this translation helpful? Give feedback.
-
|
Many thanks @gpaesano . I'll try that out and let you know. |
Beta Was this translation helpful? Give feedback.
-
|
have a look: |
Beta Was this translation helpful? Give feedback.
-
|
Hi @gpaesano . I tried both your ncp-uart-hw_3.gbl file and the whole folder.
I also tried with a 1.40.0 version of Z2M (to exclude the possibility of a 2.0 version issue) with same results |
Beta Was this translation helpful? Give feedback.
-
|
TYZS4_ncp-uart-hw_6.zip |
Beta Was this translation helpful? Give feedback.
-
|
Could you maybe share what kind of things 'differ' between the different verions? The reason why I wanted to upgrade was ezsp to ember and then have better compatibility. Higher versions, suggests, features, bugfixes, etc. curious what they are. |
Beta Was this translation helpful? Give feedback.
-
|
Look on GitHub |
Beta Was this translation helpful? Give feedback.
-
Thanks updated now everything good
|
Beta Was this translation helpful? Give feedback.
-
|
Can confirm as well, TYZS4_ncp-uart-hw_6.zip / 7.5.0.0 works fine on the Lidl box |
Beta Was this translation helpful? Give feedback.
-
|
Worked like a charm with flash_ezsp13.sh script. [2025-05-24 10:31:26] info: z2m: Coordinator firmware version: '{"meta":{"build":0,"ezsp":13,"major":7,"minor":5,"patch":0,"revision":"7.5.0 [GA]","special":0,"type":170},"type":"EmberZNet"}' Cheap sub 10 euro otherwise obsolete device has been repurposed and working great with my garden zigbee lights, cool value prop and thanks for efforts! |
Beta Was this translation helpful? Give feedback.
-
|
@slkreuzer. In case you want to try I can upload the latest folder. I had to resize memory and other parameters, in principle everything should be there, but in the SimplicityStudio it is hard to understand where exactly things are stored. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @gpaesano yes, please, worth a try, thank you! - just reinstalled SimplicityStudio5, with most basic settings, loaded your folder from above again, GeckoSDK 4.4.3, compiling, but when i try to debug, i am not getting past status = emberInit(); - it should be 0, but its 194 for me, :(. Your compiled fw works. Do you have to configure SimplicityStudio5 in a particular way to be able to compile the project specifically for the Lidl board? Any other settings that are not stored with the project? I feel like i am forgetting something really basic here - but yes, SS5 is rather confusing at times... Btw. how do you generate the .gbl at the end? I am not getting one when I compile everything - is this done in a separate step? |
Beta Was this translation helpful? Give feedback.
-
|
Nvm @gpaesano, I investigated into the error - seems that the 194/0xC2 status is EMBER_NVM3_ERR_ALIGNMENT_INVALID, from there it was easy. I have now compiled a working 7.5.0.0 with GSDK 4.4.6 aswell, thanks to you and @jnilo1! |
Beta Was this translation helpful? Give feedback.
-
|
Nice to hear. No I did not make any special arrangement, but my project is the porting of the previous one, which was working as well. Was it a memory address to by resized? |
Beta Was this translation helpful? Give feedback.
-
|
Here is the release. @skinkie it is not a big bang, just an update. https://www.silabs.com/documents/public/release-notes/emberznet-release-notes-7.5.0.0.pdf |
Beta Was this translation helpful? Give feedback.
-
|
Even running the entire script locally, does not work. I am really curious if other people have a workaround for this problem. |
Beta Was this translation helpful? Give feedback.
-
|
If your current firmware is 7.4.5 and you are trying to upgrade it to 7.5 it won't work with the V8 option of |
Beta Was this translation helpful? Give feedback.
-
|
@jnilo1 that would make sense. Where did you got the V13 from in this case? |
Beta Was this translation helpful? Give feedback.
-
|
EmberZNet is the Zigbee stack that runs on Silicon Labs chips like EFR32MG1B232F256 |
Beta Was this translation helpful? Give feedback.
-
|
@jnilo1 and how would one typically find out the sequence that differs from V7, V8, V13 or is it predicable in some way? |
Beta Was this translation helpful? Give feedback.
-
|
I see 2 options: |
Beta Was this translation helpful? Give feedback.
-
|
I think I have the hardware at home, including jtag etc. but the point is, I'll not walk that route for the upgrades on the other hardware. So I want to upgrade the script too. |
Beta Was this translation helpful? Give feedback.
-
|
Here is a Download, unzip, make it executable (chmod +x). Only 2 arguments. |
Beta Was this translation helpful? Give feedback.
-
|
Still curious how you found the sequences :-) p.s. Upgrade worked. |
Beta Was this translation helpful? Give feedback.
-
Thank you very much, I was able to update without issues (sx binary needs to be present in folder) bellows -d socket://192.168.xx.xx:8888 info Please continue making firmware updates |
Beta Was this translation helpful? Give feedback.
-
|
Whoua, very impressed and interested of all I read here, as I use a LidlBox too. I hope to be able to keep it long time, as this works like a charm ! Using the Ember driver would halp to keep Z2M up to date with my LidlBoxes ! I wouldn't abuse of your time, but, could any of You have a quick look on another thread related to using many LidlBox connected to the same MQTT server (#26689) ? Thank You so much ! |
Beta Was this translation helpful? Give feedback.
-
|
@slkreuzer Here the full folder, Just in case... |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @gpaesano, 👍! |
Beta Was this translation helpful? Give feedback.
-
|
Dear @jnilo1, Is the script suitable for all types of LIDLBox, as mine doesn't have any ventilation holes at the top (just two green LEDs). Ideally, it would be really nice to have an archive containing everything. Thank you in advance, |
Beta Was this translation helpful? Give feedback.
-
|
Mine also has no holes, only two green LEDs. Check inside that your zigbee module is a TYZS4. MCU processor is a RealTek(RTL8196E), box has no importance. If it is already free from tuya check before if the command line: |
Beta Was this translation helpful? Give feedback.
-
|
Just succesfully flashed (ignore all the errors after 100% of the progress bar): |
Beta Was this translation helpful? Give feedback.
-
|
To understand, and potentially solve, the errors throwed at the end of the flashing process check my discussion with @gpaesano |
Beta Was this translation helpful? Give feedback.
-
|
Here is the probe after flashing: |
Beta Was this translation helpful? Give feedback.
-
|
Hey everyone, Check it out here. Feel free to share feedback or contribute! |
Beta Was this translation helpful? Give feedback.
-
|
Wow! |
Beta Was this translation helpful? Give feedback.
-
|
Real nice to have all this in one place! Convinced me take the step to update my hacked LIDL gateway to 7.5.0 and it went flawless :) |
Beta Was this translation helpful? Give feedback.
-
|
Good evening, I finally managed the update of one of my LIDLBoxes successfully : firmware upgrade to 7.5.0 (many thanks goes to @jnilo1), upgrade to the latest Z2M docker container version (v2.2.1) and using the "ember" driver. The before-migration connected devices still remain available from the frontend of the Web-UI and connect to my broker. I did exactly the same steps to a second LIDLBox, but I lost all of the before-migration connected devices from the Web-UI now ... When looking at the migration logs (3 files), no errors appears. When looking at the configuration yaml file, all the devices are present ... Is there a know bug related to the 2.2.1 version maybe ? Please help, as I wouldn't have to connect again all my devices ... |
Beta Was this translation helpful? Give feedback.
-
|
@titoum-be @skinkie Thanks guys for the tip, but is not working for me ... |
Beta Was this translation helpful? Give feedback.
-
Most devices appeared automatically after some time |
Beta Was this translation helpful? Give feedback.
-
|
@muzzy124 Since yesterday evening, none of the lost devices appeared. I think that I have to connect them all gain 👎 |
Beta Was this translation helpful? Give feedback.
-
|
silly question but have you made a backup of mqtt before migrating? |
Beta Was this translation helpful? Give feedback.
-
|
@titoum-be No backup made as the tests were successful ... Will do it next time for sure ! Well, all the devices were suppressed and added again, all's working fine again now :-) Thanks for that great software to all the developers <3 |
Beta Was this translation helpful? Give feedback.
-
|
Hello all, I'm trying to OTA update device ICPSHC24-10EU-IL-1 via Lidl Gateway and I'm getting error. Is it connected to firmware of Lidl gateway or is it device issue that it's being updated ` |
Beta Was this translation helpful? Give feedback.
-
|
Apparently you are experiencing timeouts (see ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT). Does your gateway ethernet cable goes through a router ? are you using unshielded ethernet cables ? In my experience this can be at the origin of such problems. The best way to test that hypothesis is to setup a direct ethernet connection (the shorter the better) between the gateway and the host and try again: Gateway <--ethernet cable-->Host<--internet access through wifi |
Beta Was this translation helpful? Give feedback.
-
|
Thank you jnilo1, it looks like this is happening when my RPI 3 is low on resources. As I'm running lots of docker containters, stopping them all allowed me to OTA update without any issues. Thank you for your insights. |
Beta Was this translation helpful? Give feedback.
-
|
A brand new, tuya free, root filesystem is available for your favorite gateway. Check-it out ! |
Beta Was this translation helpful? Give feedback.
-
|
Wow |
Beta Was this translation helpful? Give feedback.
-
|
For those interested a fully open GCC 8.5 toolchain and a brand new linux 5.10 kernel are now available for your favorite gateway. |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I've been a (very,) very happy zigbee2mqtt user for serveral years now.
Using 2 Silvercrest/Lidl hacked network gateways located in 2 parts of the house covered by wired network but no zigbee continuity between them (several floors are in between) - hence the 2 networked gateways.
This configuration works flawlessly : my 2 Zigbee networks are solid, my (various brand) devices work really nicely and Home Assistant works as a perfect coordinator between all of them.
All in all a very good experience (-:
Theses days, I've read notifications and news which lead me to understand that I wouldn't be able to use these gateways at one point because :
Sorry for asking such a basic question but I'm having a hard time consolidating all the info I've come across on the web.
Am I right in assuming that my adapters are doomed if I go on using/updating zigbee2mqtt ?
If so, that actually sounds weird because... everything actually works perfect and I can't actually see what could be improved (in my own particular situation).
Thanks in advance for any precision on this !
Beta Was this translation helpful? Give feedback.
All reactions