Replies: 29 comments 57 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.
-
|
Have you solved the realtek start up , or have you issued the J 80C00000 manually to allow the zigbee module to communicate? |
Beta Was this translation helpful? Give feedback.
-
|
Not yet, but I might have found a possible reason. See my last comment on the post to the Silab community forum. However, I haven't figured out how to revert the RTS pin using the SSV5 pin tool yet :-( On the other hand, the RCP version works perfectly well with RTS/CTS disabled in the firmware, and I am able to run zigbee2mqtt and the Ember adapter successfully with EmberZNet 7.4.5.0. I am convinced this is the best approach since the 256K limit of the Silvercrest/Lidl chip will always be a real constraint for a NCP-UART design. With a zigbeed daemon running on the host, there are no more limits, and you are even in a position to run Matter (though I haven't tested this yet :-)... |
Beta Was this translation helpful? Give feedback.
-
|
I finally found a simple solution to the Realtek entering boot mode when RCP/NCP UART is configured with CTS/RTS enabled. Et voilà.. The problem is gone. I have updated my RCP firmware accordingly and will try to document the whole RCP stuff in the coming days. |
Beta Was this translation helpful? Give feedback.
-
|
A more elegant, Gecko compatible, approach: |
Beta Was this translation helpful? Give feedback.
-
|
@jnilo1 Good Job, so it just a question of timing. I will try to flash as well and be back. RCP of course it is a more simpler firmware as uses only the radio part of the EFR, but requires a zigbee daemon somewhere else. I am wondering if at the end it is a good solution for portability as the zigbee stack will not be in the chip... |
Beta Was this translation helpful? Give feedback.
-
|
Just compiled and ran the NCP sw. It is my old project, I will see if it is possible to update. Starting Zigbee2MQTT without watchdog. |
Beta Was this translation helpful? Give feedback.
-
|
TYZS4_ncp-uart-hw_4.zip |
Beta Was this translation helpful? Give feedback.
-
|
is it possible to upgrade firmware remotely as done previously? what should be the proper command with the universal-silabs-flasher? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks you, tested and approved. |
Beta Was this translation helpful? Give feedback.
-
|
universal-silabs-flasher --device socket://192.168.1.XXX:8888 --ezsp-baudrate 115200 flash --firmware "D:YOURPATH\TYZS4_ncp-uart-hw_4.gbl" this is the basic command for the flasher, please remeber to disconnect zigbee2mqtt or ZHA before from port 8888 |
Beta Was this translation helpful? Give feedback.
-
|
TYZS4_ncp-uart-hw_5.zip |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I was able to flash and it is working great zigbee2mqtt | [2025-02-24 12:30:51] info: z2m: Logging to console, file (filename: log.log) zigbee2mqtt | [2025-02-24 12:40:40] info: z2m: Zigbee: allowing new devices to join. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @gpaesano ! I too updated the firmware (using the old script with ssh from https://github.com/Ordspilleren/lidl-gateway-freedom , because universal-silabs-flasher was refusing to do it). My Silvercrest gateway is now working fine, using the last zigbee2mqtt release (2.1.1) with the "ember" driver. Cool! |
Beta Was this translation helpful? Give feedback.
-
|
Have you used the zip or the gbl inside?Il 24 feb 2025 18:23, thedudefxp ***@***.***> ha scritto:
Anyone can help me ?
I succefully flash TYZS4_ncp-uart-hw_4.zip and everything was ok
but i tried today TYZS4_ncp-uart-hw_5.zip, the flash succeffuly but now i got error and gateway not working anymore
C:\Windows\System32>bellows -d socket://10.29.10.199:8888 info
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in run_code
File "C:\Program Files\Python313\Scripts\bellows.exe_main.py", line 7, in
sys.exit(main())
~~~~^^
File "C:\Program Files\Python313\Lib\site-packages\click\core.py", line 1161, in call
return self.main(*args, **kwargs)
~~~~~~~~~^^^^^^^^^^^^^^^^^
File "C:\Program Files\Python313\Lib\site-packages\click\core.py", line 1082, in main
rv = self.invoke(ctx)
File "C:\Program Files\Python313\Lib\site-packages\click\core.py", line 1697, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
File "C:\Program Files\Python313\Lib\site-packages\click\core.py", line 1443, in invoke
return ctx.invoke(self.callback, **ctx.params)
~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Program Files\Python313\Lib\site-packages\click\core.py", line 788, in invoke
return __callback(*args, **kwargs)
File "C:\Program Files\Python313\Lib\site-packages\click\decorators.py", line 33, in new_func
return f(get_current_context(), *args, **kwargs)
File "C:\Program Files\Python313\Lib\site-packages\bellows\cli\util.py", line 39, in inner
loop.run_until_complete(f(*args, **kwargs))
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
File "C:\Program Files\Python313\Lib\asyncio\base_events.py", line 725, in run_until_complete
return future.result()
~~~~~~~~~~~~~^^
File "C:\Program Files\Python313\Lib\site-packages\bellows\cli\ncp.py", line 69, in info
s = await util.setup(ctx.obj["device"], ctx.obj["baudrate"])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Program Files\Python313\Lib\site-packages\bellows\cli\util.py", line 100, in setup
await app.connect()
File "C:\Program Files\Python313\Lib\site-packages\bellows\zigbee\application.py", line 153, in connect
await self.ezsp.connect(use_thread=self.config[CONF_USE_THREAD])
File "C:\Program Files\Python313\Lib\site-packages\bellows\ezsp_init.py", line 134, in connect
self._gw = await bellows.uart.connect(self._config, self, use_thread=use_thread)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Program Files\Python313\Lib\site-packages\bellows\uart.py", line 146, in connect
protocol, connection_done = await thread.run_coroutine_threadsafe(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
_connect(config, api)
^^^^^^^^^^^^^^^^^^^^^
)
^
File "C:\Program Files\Python313\Lib\site-packages\bellows\uart.py", line 125, in _connect
transport, _ = await zigpy.serial.create_serial_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<6 lines>...
)
^
File "C:\Program Files\Python313\Lib\site-packages\zigpy\serial.py", line 117, in create_serial_connection
transport, protocol = await loop.create_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<3 lines>...
)
^
File "C:\Program Files\Python313\Lib\asyncio\base_events.py", line 1166, in create_connection
raise exceptions[0]
File "C:\Program Files\Python313\Lib\asyncio\base_events.py", line 1141, in create_connection
sock = await self._connect_sock(
^^^^^^^^^^^^^^^^^^^^^^^^^
exceptions, addrinfo, laddr_infos)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Program Files\Python313\Lib\asyncio\base_events.py", line 1044, in _connect_sock
await self.sock_connect(sock, address)
File "C:\Program Files\Python313\Lib\asyncio\proactor_events.py", line 726, in sock_connect
return await self._proactor.connect(sock, address)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Program Files\Python313\Lib\asyncio\windows_events.py", line 804, in _poll
value = callback(transferred, key, ov)
File "C:\Program Files\Python313\Lib\asyncio\windows_events.py", line 600, in finish_connect
ov.getresult()
~~~~~~~~~~~~^^
ConnectionRefusedError: [WinError 1225] Le système distant a refusé la connexion réseau
C:\Windows\System32>
Thanks you
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, everything is correct. |
Beta Was this translation helpful? Give feedback.
-
|
If that can help friend got also time-out for gbl v5 ( but not gbl v4 ) cd /tuya/ 4 now python on windows or whatever you use 5 after reboot with putty access gateway and do cd /tuya/ PS: I'm totally noob maybe will not solve your problem, I'm just following commands I found left and right |
Beta Was this translation helpful? Give feedback.
-
|
I have done it several times... but one time for power unplug, maybe another try. I'm thinking, could it be another |
Beta Was this translation helpful? Give feedback.
-
|
Would recommend to test already in this order: on your archlinux:
on your hub on your archlinux on your hub the process is showing some line completing and when reaching 100% -> i get a shit load of error on my desktop. on your archlinux: if you still get timeout may be try to put a switch on your desktop so you can plus the hub on it and have them talk to each other directly :-) |
Beta Was this translation helpful? Give feedback.
-
Nothing, timeout error each time. I change baudrate in case, same.
It's the same. One time, I see
It's already on a switch with the TyDom box, my HASS serveur and my computer ^^ |
Beta Was this translation helpful? Give feedback.
-
|
Timeouts are very frequents when you try to update the firmware through the network which is the case when someone tries to do it through bellows or universal-silabs-flasher. That is why I recommand Paul Bank's original approach through the firmware_upgrade.sh ash script where the update process is carried out from the gateway after having transferred the relevant files (sx, gbl files) to the gateway through ssh. It will automatically kill the serialgateway process before updating the firmware which is absolutely necessary. Also you should avoid to have other connections active (ssh, serial through ttyS0) and finally I strongly recommend to introduce sleep statement in Paul's script to make it 100% reliable (my own version of the script is attached). |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @jnilo1 for the new script. I used the old version of firmware_upgrade.sh and it worked well ( universal-silabs-flasher was almost always having timeouts). At the time, and looking at the (old) script, it seemed to me that the EZSP_VERSION (V6 or V7) variable was not used (I used V7). The gateway is running fine apparently, but from your new script it seems the CONFIGURATION_FRAME is different. What does that do exactly? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @jnilo1. |
Beta Was this translation helpful? Give feedback.
-
|
My |
Beta Was this translation helpful? Give feedback.
-
|
My TYZS4 module is inaccessible. |
Beta Was this translation helpful? Give feedback.
-
|
@psolyca : the original (EmberZnet 6.5) firmware is attached. It is the full image including bootloader so you will need a JLINK debugger connected to the gateway through SWD and silabs commander. The command to restore the firmware is: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks ^^ |
Beta Was this translation helpful? Give feedback.
-
|
For your information, I managed to flash original firmware. I just connect like the schematics in page 19 https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf Fire a terminal n°2 : Disconnect, reboot and check : Now, I tried to flash directly version 5 and it's slow and does not go to end. To be continued... |
Beta Was this translation helpful? Give feedback.
-
|
After 2nd attempt, I'm on ember. BTW, I have to reconnect all my modules ^^; |
Beta Was this translation helpful? Give feedback.
-
|
I did not have to repair any device. But I still have a problem that joining some new devices won't work. |
Beta Was this translation helpful? Give feedback.
-
|
Does anyone experience the same issues? I see this on a release and dev branch. |
Beta Was this translation helpful? Give feedback.
-
|
Went through the update (if you have ssh problems: -oHostKeyAlgorithms=+ssh-rsa ) ! And I have an ember connection! |
Beta Was this translation helpful? Give feedback.
-
|
In case someone need the bootloader alone, please find the attached zip. As a general info, the 7.4.x gbl files do not include the bootloader as it is by default initially included the zigbee module. as the adapter is no more EZSP you may have to re-pair some devices (sorry..), once you are on ember it will be more easy in the future. |
Beta Was this translation helpful? Give feedback.
-
|
If pairing of some devices still has issues, and timeouts sometimes still occur, what would you recommend? |
Beta Was this translation helpful? Give feedback.
-
|
some devices need to stay close to coordinator (or a router) at pairing time |
Beta Was this translation helpful? Give feedback.
-
|
That solution has been tried... the device is (actually two) a doorbell. It worked before, but I cannot get it to pair any more. Not at the coordinator, not at a powerplug. |
Beta Was this translation helpful? Give feedback.
-
Same here.I have the same good log output as you @gpaesano poster earlier Except, I have Z2m 2.1.3, and hm 3.2.7 but only minor version change is probably not an issue.
I am moving from ZHA EZSP, so lots of new things for me. I managed to pair to one of my switches but the interview failed, and there was some comm errors, so added baud, and rtscts (exact)config as you mentioned. With ZHA EZSP I could connect the switch in seconds with no problem, so I'm sure it is not a radio/signal issue. If someone has any idea what could still be checked I'd highly appreciate it. |
Beta Was this translation helpful? Give feedback.
-
|
do not consider: info: zh:controller: Coordinator address changed, updating to '0x60a423fffe0887a0' , as I had another coordinator before |
Beta Was this translation helpful? Give feedback.
-
|
I managed to solve it. Tried a few things but... I forgot to backup the serialgateway into the serialgateway.save file. So I:
|
Beta Was this translation helpful? Give feedback.
-
|
Good to hear! |
Beta Was this translation helpful? Give feedback.
-
|
i've edited a "classic" firmware_upgrade.sh by adding "sleep 1" as it's done in jnilo1's script (there's a mistake(?) that tries to kill ser2mon but there's only serialgateway) files needed: so i managed to upgrade to 7.4.5 with these steps:
i didn't managed to upgrade to 7.4.5 directly because i got ACKs like:
don't forget to have fun with pairing all devices again :) |
Beta Was this translation helpful? Give feedback.
-
My bad :-) In my configuration I am using ser2net instead of serialgateway and forgot to change that in the script I posted. I have edited my post and corrected the attached script. |
Beta Was this translation helpful? Give feedback.
-
|
it seems that repairing is not needed as i see a previously paired device to ezsp 6.5.5 that appeared automatically in z2m (ember 7.4.5) after some time |
Beta Was this translation helpful? Give feedback.
-
|
firmware_upgrade.zip |
Beta Was this translation helpful? Give feedback.
-
|
I can also confirm that the error at the end of universal-silabs-flasher is not an issue, small timeout/protocol issue at the very end. |
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