Thanks. Why don't you need the port input? How would the Z2MQTT know the location of the hardware? Even autodetect requires as port: null. Documentation states # Required: location of the adapter (e.g. CC2531). # USB adapters - use format "port: /dev/ttyACM0" # To autodetect the USB port, set 'port: null'. # Ethernet adapters - use format "port: tcp://192.168.1.12:6638"
I don't know but I've had it configured without a port for over a year. I copied your screen verbatim (including port), and it gave me an error and wouldn't start. Then I noticed you did NOT list the port input in the video description, so I assumed you didn't intend for us to copy that part. So I deleted it and now it works again. Dunno what to tell you 🤷
Hi, First of all, thanks for the video's!!! I'm using the ezsp and matter support flashed with the tool you mentioned. Is there a way of having Ember and matter? I noticed the 'Silicon Labs Multiprotocol' is always ezsp driver and matter ?
Technically yes (ua-cam.com/video/3mlu4YluJRs/v-deo.html), however, recent recommendations suggest that it's a better practice to separate the radio's due to potential issues. So, I would not recommend it.
Your instructions are very good! One question: before migrating to ember, I used one dongle as a coordinator and another as a router, now I can no longer use it as a router with the ember firmware. Is there any way to do this?
Yes, you can use Ember firmware for certain Zigbee routers. For example, the Sonoff Dongle-E can be updated to use Ember firmware, which is officially supported by Zigbee2MQTT. This firmware provides better stability and performance for Zigbee devices.
I wasn't completely clear... I already use the Sonoff Dongle-E with the ember firmware as a zigbee2mqtt network centralizer. What I want is to use another zigbee2mqtt as a router/signal repeater. I couldn't do this with the ember firmware. The zigb2mqtt mesh is working perfectly, except the Sonoff Dongle-E as a repeater. It's stopped, off the grid. I don't know if I was clear.
Arhhh got you. OK the Ember firmware is specific to the coordinator, the router firmware is totally different (check the github repo). I'd recommend using the Darkxst web flasher (darkxst.github.io/sl-test/) and laod the router firmware and you should see it appear back on your network.
Hi there ! I am facing a problem while trying to connect from the Silabs Firmware Flasher. My dongle device is displayed in the selection list but the flasher is not being able to connect into it. After some time loading, the following message is being displayed: "Connection failed The running firmware could not be detected. Make sure the USB port works and if you are using a USB extension cable, make sure the cable can transfer data. Unplug the Sonoff ZBDongle-E and plug it back in to reset and try again." I've already verified everything I could. My dongle is the correct version, Zigbee Dongle-E The driver installed on my windows is the latest: 11.3.0.176 Tried the connection in all USB ports on my computer (USB3.0 and below) Could you give me some help ?
@@smart_home_australia yep, I've tried Edge as well. I've also tried in another computer. I saw things related to the dongle not being in boot mode, or something like that... Some guys were asking to open the device and press the boot button. I've just tried it and got the same result. How can I know if the dongle I have is V1 or V2 ? Would it be causing it ? To be honest... I don't know what version I have, but, as I just bought it... I'm assuming it should not be the issue :(
To find out the version you have assuming that it is connected to Home Assistant, Navigate to SETTING > SYSTEM > HARDWARE > ALL HARDWARE, scroll to ttyACM and you should see your ZBDongle listed. The name should say something like "ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2", indicating if its a V1 or V2. As for your issue, it must be relating to the Dongle, so your conclusion of the version might be correct. Check out the video description for a 15% discount code on Sonoff, might be time to treat yourself :)
@@smart_home_australia I have exactly the same problem, but i know i have the right version. I notice it doesnt show up in the device manager of windows. Had the P Version before ( wantedto replace that one with the V2 and if i connect it to the flasher website it even shows me the correct description on the com port. But it cant connect, cause i think it doesnt see the device itself. The P Version shows up in the device manager itself, the V2 somewow doesnt
Managed to flash it, but was a bit of a pain. Didnt hat much luck in windows with it, plugged it into a rasperrry pi, then it showed up as cdc_acm 1-1.4:1.0: ttyACM0: USB ACM device. Flashed the firmware with universal-silabs-flasher --device /dev/ttyACM0 --bootloader-reset sonoff flash --firmware ncp-uart-hw-v7.4.3.0-zbdonglee-115200.gbl and that work,ed tried to flash it again to be sure, but said its allready flashed with that version so it wont again. Had to screw it appart to be able to press the boot button when plugging in. That Universal Silabs Flasher isnt a lightweight too, you need pip to instal it and after that you can install it . If it complains about missing attrs module even if it installs it, run pip install --upgrade attrs. pip somehow messes this up
Another another great video - really well layed out. With your affiliate link - is that a v1 or v2 dongle? Just looking at it, as I've bricked my last one, it looks like a v1. Can you please confirm?
Hi Adrian, thanks 🙏 The link is to the ZBDongle v2. Check the spec comparison in the pictures as it shows the P and E variants in the chart and shows the V2 suffix.
Technically yes, this is the Zigbee firmware that is used by ZHA and Z2MQTT, its just with Z2MQTT it a lot more obvious as this is a more nuts and bolts deployment of the integration so you can see under the hood more. Although I have not looked I'm sure you'd see the same error message in the logs for ZHA. Can anyone else confirm??
@@smart_home_australia Thank you for the prompt reply. Usually these devices have different firmwares for the coordinate & router. Will give it a try. Thanks again.
Wow, you know I didn't know that, just shows you, we are just humble nerds :) Check out the following for instructions on how to do this: sonoff.tech/wp-content/uploads/2022/11/SONOFF-Zigbee-3.0-USB-dongle-plus-firmware-flashing-.pdf I feel another video coming ;) thanks for the hot tip.
Its not down to the dongle its down to radio and potential interference, but to answer your question, nope, not that I'm aware. But if anyone else knows differently then let us all know.
Yep, but slightly different update process. Here are the steps: 1) Go to - silabs-firmware-builder/firmware_builds/skyconnect at ember-nohw · darkxst/silabs-firmware-builder (github.com) (ref: github.com/darkxst/silabs-firmware-builder/tree/ember-nohw/firmware_builds/skyconnect) 2) Download this file: ncp-uart-hw-v7.4.3.0-skyconnect-115200.gbl (ref: github.com/darkxst/silabs-firmware-builder/blob/e1d19af3b83fefd16432d07bee97466403bbe22d/firmware_builds/skyconnect/ncp-uart-hw-v7.4.3.0-skyconnect-115200.gbl) 3) Go to the firmware updater: Home Assistant SkyConnect (home-assistant.io) (ref: skyconnect.home-assistant.io/firmware-update/) 4) Select the CUSTOM option and select the file you just downloaded and update.
I'd suggest reading the "Different firmware variants" section in github.com/darkxst/silabs-firmware-builder. This talks through the 3 different firmware options. You should select the one that is most appropriate for yourself. Pls note that OpenThread is Experimental (although I've never had an issue with it) and RCP Multi-PAN is no longer recommended, due to stability issues.
@@TheLawIX Yes you can use the Ember firmware for ZHA but it will show up as EZSP, check the Home Assistant page for ZHA, Ref: www.home-assistant.io/integrations/zha/
I don’t have any experience with Touchlink however the ember firmware for Zigbee2MQTT does support Touchlink functionality, but there are a few key points. - The ember driver is a newer alternative to the older EZSP. -Touchlink functionality was not available with the older EZSP driver, but is supported with the newer ember drivers. - Some users have reported issues with Touchlink scanning, receiving errors like "Scan request failed or was not answered". This suggests that while Touchlink is supported, there may still be some implementation challenges or bugs to work out. Therefore ember firmware does support Touchlink, but proper configuration and up-to-date firmware are required for it to work correctly.
When i plug my dongle in to a laptop and try to connect to it on the firmware flasher page is comes up as Sonoff Zigbee 3.0 USB Dongle Plus not Sonoff Zigbee 3.0 USB Dongle Plus V2. The website I purchased it at says it is a ZBDongle-E, the labelling on it says it is an ZBDongle-E, I have even measured the shell length and it matches the ZBDongle-E on Sonoffs website. Any ideas what is going on? are there two versions of the ZBDongle-E???
Hmmm are you thinking that this might be a rip off version? Try this 1) SETTINGS 2) SYSTEM 3) HARDWARE 4) ALL HARDWARE Scroll down to the ttyACM section You should see your ZBDongle listed, in the ID Section it should have something like /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_[NUMBERS] this denotes its a ZBDongle E. Its not a defintive ID but should give you a level of certainty. After that I'd reach out to Sonoff to confirm, they are super responsive and always happy to help.
@@smart_home_australia no idea if it is a rip off. everything looked legit with it. Looking back at the amazon listing, it doesn't actually say any where that is a 'Sonoff' just lists brand and manufacturer as 'Generic'. But all the images and device itself has 'Sonoff' on it. Very percuilar. i looked at the hardware, and it comes back as usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_ec[numbers] I will email Sonoff, but ordered another through your link
Does it say V1 or V2 after the plus? V1 is P and V2 is E. You can always crack it open and check the chipset. V1 (ZBDongle-P) uses a CC2652P chipset V2 (ZBDongle-E) uses an EFR32MG21 chipset
@@smart_home_australia no version number at all I'll probably crack it open. It's currently working fine in home assistant. But I was trying to get it to be a thread router too
If the Sonoff Zigbee dongle does not have a version number, it is likely the "P" variant. The "P" variant is based on the Texas Instruments CC2652P chip and was initially released without a specific version number. The "E" variant, on the other hand, is marketed as the "v2" dongle and uses a different chipset, the Silicon Labs EFR32MG21. Check out this article for similar stories: www.reddit.com/r/homeassistant/comments/192kv8m/2024_sonoff_zbdonglee_or_zbdonglep/
After updating my coordinator according to your video, LQI parameters are not displayed on the map in Zigbee@Mqtt for some devices. Do you know where the problem might be? Additionally, an error occurs when controlling the push-button relay: z2m: Publish 'set' 'state' to 'Przełącznik dopuszkowy (Z2M)' failed: 'Error: ZCL command 0xa4c13835fc3bdbb3/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Delivery failed for '34768'.)' How can this be solved?
For the LQI, this could be due to many reasons, usually related to network related issues. Try reading the device or adjusting the power ratings and restart HA. Regards the second point this error message indicates a failed attempt to control a Zigbee device through Zigbee2MQTT (Z2M). Specifically, it's trying to send an "on" command to a device named "Przełącznik dopuszkowy (Z2M)" (which appears to be a switch or relay), but the command delivery failed. Some possible causes could be network instability, Device out of range, coordinator overload or firmware issues. To resolve these, try the following steps: Restart Zigbee2MQTT and the coordinator, check for interference, improve network topology, reduce network load or re-pair the device. Outside of the above you'll need to search the community boards as the instruction listed are still relevant.
Unfortunately after upgrade zigbee won't start. i get only tekst in the log: Starting Zigbee2MQTT without watchdog. [08:21:50] INFO: Preparing to start... [08:21:50] INFO: Socat not enabled [08:21:51] INFO: Starting Zigbee2MQTT... Starting Zigbee2MQTT without watchdog. After this it stops
If the web based flasher won’t connect and allow the firmware upgrade then you can always do it the direct (link sonoff.tech/wp-content/uploads/2022/11/SONOFF-Zigbee-3.0-USB-dongle-plus-firmware-flashing-.pdf) but you will need to dismantle the device to press the boot button. More fiddly, but super easy to do.
Check out that link and it should tell you how to manually flash the firmware. I dont usually cover it as its very temperamental having to press a super small button inside of the case for a specific number of seconds to put the device into pairing mode etc. Check out Matt's instructions (ua-cam.com/video/4jqQCxjlRDU/v-deo.htmlsi=GkqzvWwFDHK9O9QA)
![[UA] NAVI vs MOUZ | BO5 | IEM Rio 2024](http://i.ytimg.com/vi/CMBYk0cbGoA/mqdefault.jpg)
The backup file was causing me problems and the steps in your video sorted it. Thanks!
Glad it helped! :)
thanks a bunch got it working in the end
You are most welcome, I think I might need to do another video for this as things have moved on a little since then.
This is the best video for updating to ember. The other popular video doesn't cover the backup part.
FYI the port input in config shouldn't be entered
Thanks.
Why don't you need the port input? How would the Z2MQTT know the location of the hardware? Even autodetect requires as port: null.
Documentation states
# Required: location of the adapter (e.g. CC2531).
# USB adapters - use format "port: /dev/ttyACM0"
# To autodetect the USB port, set 'port: null'.
# Ethernet adapters - use format "port: tcp://192.168.1.12:6638"
I don't know but I've had it configured without a port for over a year. I copied your screen verbatim (including port), and it gave me an error and wouldn't start. Then I noticed you did NOT list the port input in the video description, so I assumed you didn't intend for us to copy that part. So I deleted it and now it works again. Dunno what to tell you 🤷
Interesting, ok well more investigation needed on my side, thanks for the heads up :)
@@smart_home_australia thanks for getting my dongle updated with ember... even if it was accidental lol
You're welcome. :)
Hi,
First of all, thanks for the video's!!!
I'm using the ezsp and matter support flashed with the tool you mentioned. Is there a way of having Ember and matter?
I noticed the 'Silicon Labs Multiprotocol' is always ezsp driver and matter ?
Technically yes (ua-cam.com/video/3mlu4YluJRs/v-deo.html), however, recent recommendations suggest that it's a better practice to separate the radio's due to potential issues. So, I would not recommend it.
Your instructions are very good! One question: before migrating to ember, I used one dongle as a coordinator and another as a router, now I can no longer use it as a router with the ember firmware. Is there any way to do this?
Yes, you can use Ember firmware for certain Zigbee routers. For example, the Sonoff Dongle-E can be updated to use Ember firmware, which is officially supported by Zigbee2MQTT. This firmware provides better stability and performance for Zigbee devices.
I wasn't completely clear... I already use the Sonoff Dongle-E with the ember firmware as a zigbee2mqtt network centralizer. What I want is to use another zigbee2mqtt as a router/signal repeater. I couldn't do this with the ember firmware. The zigb2mqtt mesh is working perfectly, except the Sonoff Dongle-E as a repeater. It's stopped, off the grid. I don't know if I was clear.
Arhhh got you. OK the Ember firmware is specific to the coordinator, the router firmware is totally different (check the github repo). I'd recommend using the Darkxst web flasher (darkxst.github.io/sl-test/) and laod the router firmware and you should see it appear back on your network.
Thank you very much!
@@vaz2361 you are most welcome. Good luck on your smart home journey.
thanks for your guide! flashing was so easy this way. 😊
You're welcome!
Hi there !
I am facing a problem while trying to connect from the Silabs Firmware Flasher. My dongle device is displayed in the selection list but the flasher is not being able to connect into it.
After some time loading, the following message is being displayed:
"Connection failed
The running firmware could not be detected.
Make sure the USB port works and if you are using a USB extension cable, make sure the cable can transfer data. Unplug the Sonoff ZBDongle-E and plug it back in to reset and try again."
I've already verified everything I could.
My dongle is the correct version, Zigbee Dongle-E
The driver installed on my windows is the latest: 11.3.0.176
Tried the connection in all USB ports on my computer (USB3.0 and below)
Could you give me some help ?
Driver is the latest, so that's not the issue.
Have you tried a different browser? Chrome is the best for compatibility.
@@smart_home_australia yep, I've tried Edge as well. I've also tried in another computer.
I saw things related to the dongle not being in boot mode, or something like that... Some guys were asking to open the device and press the boot button. I've just tried it and got the same result.
How can I know if the dongle I have is V1 or V2 ?
Would it be causing it ?
To be honest... I don't know what version I have, but, as I just bought it... I'm assuming it should not be the issue :(
To find out the version you have assuming that it is connected to Home Assistant, Navigate to SETTING > SYSTEM > HARDWARE > ALL HARDWARE, scroll to ttyACM and you should see your ZBDongle listed. The name should say something like "ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2", indicating if its a V1 or V2.
As for your issue, it must be relating to the Dongle, so your conclusion of the version might be correct.
Check out the video description for a 15% discount code on Sonoff, might be time to treat yourself :)
@@smart_home_australia I have exactly the same problem, but i know i have the right version. I notice it doesnt show up in the device manager of windows. Had the P Version before ( wantedto replace that one with the V2 and if i connect it to the flasher website it even shows me the correct description on the com port. But it cant connect, cause i think it doesnt see the device itself. The P Version shows up in the device manager itself, the V2 somewow doesnt
Managed to flash it, but was a bit of a pain. Didnt hat much luck in windows with it, plugged it into a rasperrry pi, then it showed up as cdc_acm 1-1.4:1.0: ttyACM0: USB ACM device. Flashed the firmware with universal-silabs-flasher --device /dev/ttyACM0 --bootloader-reset sonoff flash --firmware ncp-uart-hw-v7.4.3.0-zbdonglee-115200.gbl and that work,ed tried to flash it again to be sure, but said its allready flashed with that version so it wont again. Had to screw it appart to be able to press the boot button when plugging in. That Universal Silabs Flasher isnt a lightweight too, you need pip to instal it and after that you can install it . If it complains about missing attrs module even if it installs it, run pip install --upgrade attrs. pip somehow messes this up
Thanks a lot for again a great video 👍
Thanks, I've only recently started so still learning how YT works... :)
Another another great video - really well layed out.
With your affiliate link - is that a v1 or v2 dongle? Just looking at it, as I've bricked my last one, it looks like a v1.
Can you please confirm?
Hi Adrian, thanks 🙏
The link is to the ZBDongle v2. Check the spec comparison in the pictures as it shows the P and E variants in the chart and shows the V2 suffix.
Tell me, do I need to flash the coordinator if ZHA is used?
Technically yes, this is the Zigbee firmware that is used by ZHA and Z2MQTT, its just with Z2MQTT it a lot more obvious as this is a more nuts and bolts deployment of the integration so you can see under the hood more. Although I have not looked I'm sure you'd see the same error message in the logs for ZHA.
Can anyone else confirm??
Hello,
Will this work as a router (repeater)?
Thanks
Yep. Any mains powered Zigbee device will act as a router (repeater), not just a coordinator.
@@smart_home_australia Thank you for the prompt reply.
Usually these devices have different firmwares for the coordinate & router.
Will give it a try.
Thanks again.
Wow, you know I didn't know that, just shows you, we are just humble nerds :)
Check out the following for instructions on how to do this: sonoff.tech/wp-content/uploads/2022/11/SONOFF-Zigbee-3.0-USB-dongle-plus-firmware-flashing-.pdf
I feel another video coming ;) thanks for the hot tip.
Is there a dongle that works with the 3 protocols : zb matter and zb2mqtt?..
Its not down to the dongle its down to radio and potential interference, but to answer your question, nope, not that I'm aware. But if anyone else knows differently then let us all know.
This would also be relevant for the SkyConnect dongles, right? From memory they're also running EZSP firmware...
Yep, but slightly different update process.
Here are the steps:
1) Go to - silabs-firmware-builder/firmware_builds/skyconnect at ember-nohw · darkxst/silabs-firmware-builder (github.com) (ref: github.com/darkxst/silabs-firmware-builder/tree/ember-nohw/firmware_builds/skyconnect)
2) Download this file: ncp-uart-hw-v7.4.3.0-skyconnect-115200.gbl (ref: github.com/darkxst/silabs-firmware-builder/blob/e1d19af3b83fefd16432d07bee97466403bbe22d/firmware_builds/skyconnect/ncp-uart-hw-v7.4.3.0-skyconnect-115200.gbl)
3) Go to the firmware updater: Home Assistant SkyConnect (home-assistant.io) (ref: skyconnect.home-assistant.io/firmware-update/)
4) Select the CUSTOM option and select the file you just downloaded and update.
Hello, I'm currently using Firmware: 7.3.1.0 build 0 working with Matter and ZHA and it works well. Are you suggest to update to v 7.4.2.0 anyway?
I'd suggest reading the "Different firmware variants" section in github.com/darkxst/silabs-firmware-builder. This talks through the 3 different firmware options. You should select the one that is most appropriate for yourself. Pls note that OpenThread is Experimental (although I've never had an issue with it) and RCP Multi-PAN is no longer recommended, due to stability issues.
@@smart_home_australia Still showing EZSP in ZHA for me. Are there steps to change this to Ember?
@@TheLawIX Check in the Z2M logs and you should see that the firmware used is now Ember.
@@smart_home_australia I'm using ZHA not Z2M. My question is about ZHA.
@@TheLawIX Yes you can use the Ember firmware for ZHA but it will show up as EZSP, check the Home Assistant page for ZHA, Ref: www.home-assistant.io/integrations/zha/
Can you use this software update for the P version of the dongle?
Nope sorry, it only supports the ZBDongle-E variant as it is specific to the Silicon Labs EFR32MG21 chipset.
Thanks!
Thanks😊
does the ember firmware support touchlink?
I don’t have any experience with Touchlink however the ember firmware for Zigbee2MQTT does support Touchlink functionality, but there are a few key points.
- The ember driver is a newer alternative to the older EZSP.
-Touchlink functionality was not available with the older EZSP driver, but is supported with the newer ember drivers.
- Some users have reported issues with Touchlink scanning, receiving errors like "Scan request failed or was not answered". This suggests that while Touchlink is supported, there may still be some implementation challenges or bugs to work out.
Therefore ember firmware does support Touchlink, but proper configuration and up-to-date firmware are required for it to work correctly.
When i plug my dongle in to a laptop and try to connect to it on the firmware flasher page is comes up as Sonoff Zigbee 3.0 USB Dongle Plus not Sonoff Zigbee 3.0 USB Dongle Plus V2.
The website I purchased it at says it is a ZBDongle-E, the labelling on it says it is an ZBDongle-E, I have even measured the shell length and it matches the ZBDongle-E on Sonoffs website.
Any ideas what is going on? are there two versions of the ZBDongle-E???
Hmmm are you thinking that this might be a rip off version? Try this
1) SETTINGS
2) SYSTEM
3) HARDWARE
4) ALL HARDWARE
Scroll down to the ttyACM section
You should see your ZBDongle listed, in the ID Section it should have something like
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_[NUMBERS]
this denotes its a ZBDongle E.
Its not a defintive ID but should give you a level of certainty. After that I'd reach out to Sonoff to confirm, they are super responsive and always happy to help.
@@smart_home_australia no idea if it is a rip off. everything looked legit with it.
Looking back at the amazon listing, it doesn't actually say any where that is a 'Sonoff' just lists brand and manufacturer as 'Generic'. But all the images and device itself has 'Sonoff' on it. Very percuilar.
i looked at the hardware, and it comes back as usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_ec[numbers]
I will email Sonoff, but ordered another through your link
Does it say V1 or V2 after the plus? V1 is P and V2 is E.
You can always crack it open and check the chipset.
V1 (ZBDongle-P) uses a CC2652P chipset
V2 (ZBDongle-E) uses an EFR32MG21 chipset
@@smart_home_australia no version number at all I'll probably crack it open. It's currently working fine in home assistant. But I was trying to get it to be a thread router too
If the Sonoff Zigbee dongle does not have a version number, it is likely the "P" variant. The "P" variant is based on the Texas Instruments CC2652P chip and was initially released without a specific version number. The "E" variant, on the other hand, is marketed as the "v2" dongle and uses a different chipset, the Silicon Labs EFR32MG21.
Check out this article for similar stories: www.reddit.com/r/homeassistant/comments/192kv8m/2024_sonoff_zbdonglee_or_zbdonglep/
Nice tutorial. Thx.
You're welcome! 😊👍
Thank you!! I solve my problem! ;-)
Glad I could help!
After updating my coordinator according to your video, LQI parameters are not displayed on the map in Zigbee@Mqtt for some devices. Do you know where the problem might be? Additionally, an error occurs when controlling the push-button relay:
z2m: Publish 'set' 'state' to 'Przełącznik dopuszkowy (Z2M)' failed: 'Error: ZCL command 0xa4c13835fc3bdbb3/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Delivery failed for '34768'.)'
How can this be solved?
For the LQI, this could be due to many reasons, usually related to network related issues. Try reading the device or adjusting the power ratings and restart HA.
Regards the second point this error message indicates a failed attempt to control a Zigbee device through Zigbee2MQTT (Z2M). Specifically, it's trying to send an "on" command to a device named "Przełącznik dopuszkowy (Z2M)" (which appears to be a switch or relay), but the command delivery failed. Some possible causes could be network instability, Device out of range, coordinator overload or firmware issues.
To resolve these, try the following steps:
Restart Zigbee2MQTT and the coordinator, check for interference,
improve network topology, reduce network load or re-pair the device.
Outside of the above you'll need to search the community boards as the instruction listed are still relevant.
Unfortunately after upgrade zigbee won't start. i get only tekst in the log: Starting Zigbee2MQTT without watchdog.
[08:21:50] INFO: Preparing to start...
[08:21:50] INFO: Socat not enabled
[08:21:51] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
After this it stops
If the web based flasher won’t connect and allow the firmware upgrade then you can always do it the direct (link sonoff.tech/wp-content/uploads/2022/11/SONOFF-Zigbee-3.0-USB-dongle-plus-firmware-flashing-.pdf) but you will need to dismantle the device to press the boot button. More fiddly, but super easy to do.
Same I dont know what to do in order to fix it
Check out that link and it should tell you how to manually flash the firmware. I dont usually cover it as its very temperamental having to press a super small button inside of the case for a specific number of seconds to put the device into pairing mode etc. Check out Matt's instructions (ua-cam.com/video/4jqQCxjlRDU/v-deo.htmlsi=GkqzvWwFDHK9O9QA)
@@smart_home_australia Thanks for the response actually what it works for my ZBDongle-P was setting up the adapter :zstack
Great that you got to the bottom of it. Can I ask , why did you go for the P as opposed to the E variant? Both great adaptors, just curious as to why.