Replies: 11 comments 17 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.
-
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