Replies: 62 comments 452 replies
-
|
Thanks. Note: If you are getting Here are a few things you can watch out for and report on (other than general usage reports, and of course, as long as you feel comfortable testing this):
Know issues:
Note: If you are running two networks in close proximity (live+test), make sure to have completely different settings in Note: Devices manufactured before 2020 (approx.), that did not get major firmware updates since, can create trouble. New security features may even prevent them from joining the network entirely. I'll keep this list updated as much as possible with current progress. |
Beta Was this translation helpful? Give feedback.
-
|
@wastez I saw you mentioned you had some issues with a change in firmware supplier (xsp1989 > darkxst). Do you mind giving a quick recap here on the procedure that worked for you? In case anyone else needs it. Thanks. 😉 |
Beta Was this translation helpful? Give feedback.
-
|
Yes of course. After nothing is working anymore (also no data on serial console)it is possible to flash the nvm3init firmware from here: You need to use the silabs firmware flasher which has a special reset ezsp flag. (Otherwise you have to reset stick manually) But be warned, a backup of your stick is necessary, otherwise you have to repair every device. If you want to I can add a step by step how to. |
Beta Was this translation helpful? Give feedback.
-
|
Question : Is Home Assistant Yellow (with its on-board zigbee coordinator) covered by this topic? 🤔 |
Beta Was this translation helpful? Give feedback.
-
|
@mkosmo |
Beta Was this translation helpful? Give feedback.
-
|
@Nerivec I'm happy to test on Yellow and provide feedback, I have 73 devices. Just to confirm; I should use this firmware and Z2M Edge add-on? |
Beta Was this translation helpful? Give feedback.
-
|
@jkpe Great! Use this firmware (most recent). Edge or Release should work, but currently only Edge has the delay config lowered; that provides smoother usage in some cases. |
Beta Was this translation helpful? Give feedback.
-
|
I think I flashed the "nohw" firmware ... but since I used "--force" , how can I check if It really worked? How do I know If I have the "nohw" or the original one ? Also ... I have some new conclusions, but I will write in the specific tickets immediately.
One more general feedback: I have ~1week on ember (with initial -hw- 7.4.1 firmware) and overall it works fine. I had some cases when It seemed to me that it worked faster, but I had also new (comparing with ezsp experience) small issues (like delays, or something very very strange with aqara switch which I can't replicate anymore). But the most important: no more crashes with an overall similar functionality-level as before, which is ok. But in my case I need to resolve those aqara issues to be able to test more ... |
Beta Was this translation helpful? Give feedback.
-
|
@adynis |
Beta Was this translation helpful? Give feedback.
-
|
According to your thread, I would be happy to help as I can. I have a zigbeeGreen PTM216Z laying for testing...😉 (Don't ask me to code anything, I don't have such knowledge, sorry) |
Beta Was this translation helpful? Give feedback.
-
|
@dduransseau There is an error in your converter unfortunately |
Beta Was this translation helpful? Give feedback.
-
|
ptm216z.js.txt |
Beta Was this translation helpful? Give feedback.
-
|
@Nerivec Your converter is perfectly working and no error is shown when pairing. As usual and for records, you will find a log below to check what is send by the PTM216Z when pairing. I checked if all the commands where sent correctly and it works as expected. Thank you guys for your work ! |
Beta Was this translation helpful? Give feedback.
-
|
@Nerivec yep |
Beta Was this translation helpful? Give feedback.
-
|
Guessing you guys already saw. But this should be fixed in Koenkk/zigbee-herdsman-converters#7127 😉 |
Beta Was this translation helpful? Give feedback.
-
|
I'd like to help testing, thought about using a spare adapter and forming a new ZigBee network with some devices I have here. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the help! It should be simpler to test this outside of Home Assistant (don't risk your home network!), even a simple laptop can do, you just need to make sure to get the |
Beta Was this translation helpful? Give feedback.
-
|
First congratulation @Nerivec for your hard work, looks promising. I'll be happy to help to test, especially GreenPower since I have some spare switch and a ZBDongle-e. To keep history: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Feedback on GreenPower is definitely good; I expect a few troubles there at the beginning, since I couldn't test any of it 😉 I believe I've identified where this fails. But I am far more interested in why this happened, I can't see a reason why it would, it's loading perfectly right up until the end of the init sequence. Let me know if the firmware re-flash makes it disappear. If you are using darkxst's web flasher, makes sure it loads properly after you've flashed it (it asks to continue and then gives you the new info on your adapter). EDIT: If it still happens, latest PR (once avail.) should give you the error message more clearly. Although I decoded it manually already (if it stays the same), it is a general |
Beta Was this translation helpful? Give feedback.
-
|
Just to keep track, mentioning here that this initial error disappeared on its own, without much of an explanation (kind of like the reason for it to show up in the first place...). |
Beta Was this translation helpful? Give feedback.
-
|
Hey, |
Beta Was this translation helpful? Give feedback.
-
|
@puddly, sorry this thread is a bit hard to find anything! The core issue seems to be this WATCHDOG error, this log is from SLZB-07 but apparently the same error is occurring on SkyConnect (both when using the config you linked above): I had thought the SLZB-07 has same pinout as SkyConnect, but when I checked SLZB schematics CTS/RTS were reversed compared to the SkyConnect config. So I rebuilt SLZB-07 with these pins swapped and the errors disappeared. Finally @Nerivec suggests there have been issues with flow control on skyconnect in Z2M going back to atleast 7.3.x such as this. But I am sure he can provide you more details on this! |
Beta Was this translation helpful? Give feedback.
-
|
I flashed the skyconnect with the custom firmware and tested the following: after this i also revert back to the official 7.4.0: I tested each setting at least 20-30 restarts. So with the custom FW i was not able to reproduce the issue |
Beta Was this translation helpful? Give feedback.
-
|
Which custom firmware are you referring to? |
Beta Was this translation helpful? Give feedback.
-
|
@puddly this one from @darkxst
|
Beta Was this translation helpful? Give feedback.
-
|
Let's move the hw flow control stuff here Koenkk/zigbee-herdsman#943 if you don't mind guys. I regrouped everything I could remember in one thread. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Nerivec I think I identified an issue with OTA, at least for Signify light. I have received following issue:
However I was able to upgrade on z2m with conbeeII |
Beta Was this translation helpful? Give feedback.
-
|
Yes please, debug logs would be helpful. I couldn't find a single device that needs OTA in my house to test with... |
Beta Was this translation helpful? Give feedback.
-
|
I tried to run a test using SMLight SLZB07, flashed to version 7.4.0, but Z2M fails to start: |
Beta Was this translation helpful? Give feedback.
-
|
It seems your adapter doesn't want to talk to Z2M. serial:
adapter: ember
path: /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_a215650c853bec119a079e957a0af07f-if00-port0
rtscts: trueAlso make sure the baudrate settings matches the firmware you flashed (if it's not the default |
Beta Was this translation helpful? Give feedback.
-
|
the baudrate is the default that said, I did manage to get it to start after a full restart of the host itself, I'll restart it again and post a new log, hoping it will give a clue (below is the log with |
Beta Was this translation helpful? Give feedback.
-
|
nvm, it doesn't start now after a full restart (it did start once before :/ ) any more debug logs I can fetch? |
Beta Was this translation helpful? Give feedback.
-
|
@Nerivec let me know if this is what you meant. |
Beta Was this translation helpful? Give feedback.
-
|
@Nerivec I think I managed to get the full log via terminal using docker logs (I also upgraded to the latest edge version) |
Beta Was this translation helpful? Give feedback.
-
|
Great, thanks! PS: Since you're on HA, you can look in Settings>System>Logs and switch to Z2M in top-right corner dropdown. |
Beta Was this translation helpful? Give feedback.
-
|
I tried it, but I don't see the beginning of the ZH logs as I see it in the Logs tab of the add-on and via the docker log from the terminal |
Beta Was this translation helpful? Give feedback.
-
Yeh I didnt look into it further, but I could reliably get it to start by deleting the JSON file. Then second start after that would fail. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Everything seems to work on my side (with a network of 120 devices, yes i know :)) except (obviously) my IKEA Tradfri E1525/E1745 detector (https://www.zigbee2mqtt.io/devices/E1525_E1745.html). The occupancy no longer work (I have 2 detectors blocked in “detected” and 3 without detection since the switch). Small bug? Thx :) |
Beta Was this translation helpful? Give feedback.
-
That would somewhat make sense if the problem is a conflicting broken route (that double-reset it does on pairing), because by triggering the device, you are triggering more routing failures, which is eventually forcing the network to re-discover routes. But the strange thing is that parts of it seem to work and not others, and the behavior seems different from one user to the next 🤦 |
Beta Was this translation helpful? Give feedback.
-
|
@Nerivec |
Beta Was this translation helpful? Give feedback.
-
|
@Nerivec Edit: Ok seems it got everytime direct connected to the coordinator if running ember. |
Beta Was this translation helpful? Give feedback.
-
|
@Nerivec |
Beta Was this translation helpful? Give feedback.
-
|
If you can provide herdsman-debug logs of the pairing procedure plus a couple of attempts to get it to trigger (make sure to let it cooldown -3min- after pairing, and in between triggers, even if you don't see it), I'll take a look, though previous logs I got on this device didn't prove very useful unfortunately... Any chance you can provide logs of the pairing (+ dance to get it working 😅) with |
Beta Was this translation helpful? Give feedback.
-
|
I'd like to confirm, that I've downloaded the correct firmware files. As I tried 2 and both fail to load Z2M. I took these two files from here: https://github.com/darkxst/silabs-firmware-builder/tree/main/firmware_builds/zbdonglee and the files I tested were: ncp-uart-hw-v7.4.0.0-zbdonglee-115200.gbl After setting the serial adapter to ember Z2M can't start anymore. So Either I used the wrong files or I did something else wrong. silabs_flasher.log Unfortunately I forgot to make a flasher log of 7.4.0 and I only have the 7.4.1 which I tried first. The Z2M log is from the 7.4.0 version, but ends with the same error message. 2024-03-01T22:42:53.139Z zigbee-herdsman:adapter:ember:adapter [INIT TC] Current NCP network: networkKey=01030507090b0d0f00020406080a0c0d Now I switched back to Z2M with "adapter: EZSP" and that fortunately still works. |
Beta Was this translation helpful? Give feedback.
-
|
It seems you have a backup file in your configuration folder that is too old for The code is currently hard failing on this, to prevent users from assuming a backup has been restored and to allow them to double-check the backup file in question before going any further. |
Beta Was this translation helpful? Give feedback.
-
|
Did that, now it started with ember, but in the beginning he complained about something failing because of a timeout. I hadn't copied it and when I looked into it to copy it, it was no longer in the log. Tomorrow I will test the version 7.4.1, now it is too late or too early?? As we have 220hrs I will go to bed. Thanks for your help. |
Beta Was this translation helpful? Give feedback.
-
|
Good! |
Beta Was this translation helpful? Give feedback.
-
|
I swapped my skyconnect network from ezsp to ember. It came up fine and seems good, will give it some runtime but I have a pretty simple network 👍 One question I have is am I able to make a backup and look at it once I have done this? My coordinator backup .json has an empty array for devices and I am wondering if this is expected. |
Beta Was this translation helpful? Give feedback.
-
|
A backup is automatically made on start/stop and daily (and if you request one manually). As for the NVM3 backup/restore (adapter1>adapter2, adapter1>zigbeed), while it is implemented in |
Beta Was this translation helpful? Give feedback.
-
|
Hello. Adapter: SkyConnect |
Beta Was this translation helpful? Give feedback.
-
|
Ok i thought he is talking about a wlan access point, because it looks like one. |
Beta Was this translation helpful? Give feedback.
-
|
When it comes to repeaters. I have one Dongle-E as a repeater just connected to a power supply. Should I update that too and to what firmware if yes? |
Beta Was this translation helpful? Give feedback.
-
|
@Loeffelmaster As far as I know, firmware builders have not yet built any more recent router firmware. So you can keep 6.10.3 from Sonoff for now. |
Beta Was this translation helpful? Give feedback.
-
I've not built any router firmware yet, as the Sonoff build seems to work reliably so far. |
Beta Was this translation helpful? Give feedback.
-
|
Update: Removed the 2 repeaters and everything is now working perfectly. Thanks for the quick and thorough responses @Nerivec , I don't think I've seen such a genuinely helpful set of responses to a GitHub issue in a decade of usage, amazing. |
Beta Was this translation helpful? Give feedback.
-
|
is the SLZB-06M supported ? |
Beta Was this translation helpful? Give feedback.
-
|
Looks like it was merged yesterday. This is such an active discussion I missed the responses and order the sonoff p version. On the flipside, I had already pulled that version and still had the same issues. It's Easter so probably won't have a lot of time but will give it a go after making sure I have the updated drivers. |
Beta Was this translation helpful? Give feedback.
-
|
Same issue. It disconnects within an hour. I'm returning it. Not sure if the device itself is buggy. |
Beta Was this translation helpful? Give feedback.
-
|
It is rock solid on slzb-06m with 30 devices, only hue and aqara. |
Beta Was this translation helpful? Give feedback.
-
|
That's good. I guess maybe I just got a buggy one. |
Beta Was this translation helpful? Give feedback.
-
|
Running for 27 hours with no crash. I will add more devices to the test network, but for now everything runs smooth |
Beta Was this translation helpful? Give feedback.
-
|
I am also getting the ASH errors, when i switch config from ezsp to ember. - Description of the issue Addon version Platform Core Logs of the issue (if applicable) [22:25:18] INFO: Preparing to start... |
Beta Was this translation helpful? Give feedback.
-
|
True, reading the notes thought that just applied for the sonoff but makes sense if it's both of course - I guess the SkyConnect webflasher isn't on the latest |
Beta Was this translation helpful? Give feedback.
-
|
Also, you should set serial:
port: /dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_20eb691b7318ec11bf19b19347486eb0-if00-port0
adapter: ember
baudrate: 115200
rtscts: trueBeware that the SkyConnect & Yellow are currently experiencing trouble with firmware. I pushed a temp fix attempt, it should be available in edge as soon as Koenkk/zigbee-herdsman#946 is merged. |
Beta Was this translation helpful? Give feedback.
-
|
Up and running with Ember config now as per your instructions. Never heard of this rtscts so shout and showing my R-E-S-P-E-C-T to you HAHA. Thanks for going out of your way with further explanation than the original details and dealing with me being dumb using not the latest firmware. Using 7.4.1.0 everything good so far - the usually whining from one of my Aqara VOC displays but without any other issues thus far which is an improvement! Cheers! |
Beta Was this translation helpful? Give feedback.
-
|
Perfect! Let me know if you run into issues. |
Beta Was this translation helpful? Give feedback.
-
|
I just did what you suggested. Used https://github.com/darkxst/silabs-firmware-builder/raw/sky-swap/firmware_builds/skyconnect/ncp-uart-hw-v7.4.1.0-skyconnect-115200.gbl and its working fine now. thank you so much |
Beta Was this translation helpful? Give feedback.
-
|
First... TYSM guys for your work ! Few days ago, I decided to upgrade my home network from ZBDongle-P to the shiny new ZBDongle-E. Thought I was being all tech-savvy, hopping onto the latest hardware bandwagon ^^. Little did I know, trouble was brewing in the most unexpected places – my good old power strips! Two of them decided to throw a fit, causing chaos in my otherwise serene digital kingdom. Current issue:
Setup:
Z2M:
info 2024-03-29 00:03:26: Logging to console and directory: '/app/data/log/2024-03-29.00-03-26' filename: log.txt |
Beta Was this translation helpful? Give feedback.
-
|
few hours later I found one little issue... Setup:
Z2M:
Issue: I check it and this support should be supported. State reported by Z2M: I restart my docker with herdsman debug enabled and retried. In the log you have this one : _TZ3000_cfnprab5 / TS011F / 0xa4c138c81664b24a |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback! You will want to open an issue for that powerstrip, if you've checked that it isn't already reported: https://github.com/Koenkk/zigbee2mqtt/issues |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I found... I remembered your comment about performance. I admit, as I didn't have any identified problems, I left the dev branch aside... and in fact, it's true, by going to Ember it's actually the best for the moment.
After that it reconfigure the power strips automatically (poker face when I saw the messages ^^) and now I can set this parameter... It was not a big deal for me but yes it improved the performance. |
Beta Was this translation helpful? Give feedback.
-
|
The converter for that device likely was fixed in |
Beta Was this translation helpful? Give feedback.
-
|
I saw the 1.36.1-1 release and quickly after it was available on Docker ! |
Beta Was this translation helpful? Give feedback.
-
|
Updated the Docker image (latest:dev), that includes 0.40.2 of Herdsman, and all started just perfect. Have migrated 42 of my 312 devices over without issue. Joining is super fast so far and the network is performing well. Biggest concern will be as I get to 70+ devices and see if the joining continues to be smooth. That is usually where it would break with Z2M and EZSP devices before. If it does, I will grab herdsman logs and send them over. Great work! |
Beta Was this translation helpful? Give feedback.
-
|
LOL...that is what I get for saying things are going well. Just tried to add the following Signify flood light: and got this error: |
Beta Was this translation helpful? Give feedback.
-
|
...and this error loops and kills Z2M. It is down now and will not start properly. |
Beta Was this translation helpful? Give feedback.
-
|
...rolled back from latest:dev to latest and it comes back online now. So something in the dev stack. |
Beta Was this translation helpful? Give feedback.
-
|
I bet this relates to the product number. There are 5 entities in this product. Each one of them starts with the same number: 929003621301 and then is _1, _2, _3, _4, _5. The _1 is one style of light and then _2 through _4 is a spot light. So I bet each one has a unique OTA update for 2 possible updates if you do not take the full part number in to account, including the _x when determining the update options. Perhaps?? |
Beta Was this translation helpful? Give feedback.
-
|
Latest converters solve the immediate issue for this device. Still might break in specific scenarios if there is not a proper converter, but you are aware. |
Beta Was this translation helpful? Give feedback.
-
|
Fixed the issue in 1.36.1 |
Beta Was this translation helpful? Give feedback.
-
|
This morning found that z2m crashed. Below are the logs for that run, hopefully there is some good information for you in there. Didn't have Zigbee-herdman enabled for my docker container for the logs above. "Can you be more precise on "laggy" and "respond late", are we talking a few ms, or is that counted in seconds?" "Is the tubeszb roughly in the same location as the sonoff was before?" "Might want to check the network map, see if anything looks strange, like anything that should be connected directly to the coordinator but moved to a nearby router instead (might want to re-pair those to force them to re-evaluate the best link)." "Did you happen to have a different transmit_power with the sonoff that you now have with the tubeszb?" |
Beta Was this translation helpful? Give feedback.
-
|
OK - what do you mean by "the other side"? So I will know where to look :) Also - yeah you sort of know my network - tuya devices, crashed Sonoff-P and UZG-01, chatty network, some wifi interference, de-crypt errors, overall error being pretty high compared to other networks. However, having said that the Sonoff-E coordinator never missed a bit. Also since I have moved to tubeszb device I have noticed that 4 devices totally disappeared from the network (GUI don't show them at all). Also overall devices are pretty laggy - some respond late (like 2/3 others like 5/9 seconds late). Devices do go offline regularly and some time later they do come back. Others never come back. I have seen this exact thing happening in my tests with @Koenkk for the Sonoff-P and UZG-01 coordinators. Almost like a deja-vu for me. But, as mentioned before, Sonoff-E is pretty much free of all these issues. |
Beta Was this translation helpful? Give feedback.
-
The ethernet network the adapter is on, or the TCP connection itself on the adapter would appear to have gone wrong. Do you have any logs on that side that may help figure out what happened at that time?
I saw you hit the ID conflict (two devices with same network address on the network forces the network to kick both). I've disabled the code to have Z2M sync the removal, this should help devices rejoin until we can find a better solution (0.40.3). You may have to try to start with a fresh new network ( |
Beta Was this translation helpful? Give feedback.
-
|
@Nerivec Here is the Zigbee-herdman My plan is to go now go back to Sonoff-E (which did run super stable for me) and get the logs over a 24 hour period so you can compare them. After that I might need to consider going back to tubeszb and start with a fresh network, after doing the 2.4Ghz scan to see is the best channel for me. Thanks for you help!! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Nerivec below is the link to the Sonoff-E coordinator logs as mentioned before. Will start on rebuilding my network now - 1st step wifi scan :) |
Beta Was this translation helpful? Give feedback.
-
|
@Nerivec been running on the new network for about 24 hours: Zigbee2MQTT version: 1.36.1-dev commit: 5077b03 Devices: 47 Below is the latest stats line - it seems that even with channel 20 (which was OK around the house when I did the wifi scan (and also in the past worked really well for me) "the standard" for my system includes higher errors than in other systems. Looking at the tubeszb-mgm24 ESPHome output the window it is full of this:
@thk-socal - what is your tubeszb-mgm24 showing in the device's ESPHome window? Edit: the above is an ESPHome related issue. I got a new ESPHome firmware that is supposed to fix the issue. On a good note stopping and restarting z2m worked really well. It went through the devices really quick and in less than a minutes all devices were back online. But everything still works fine. 172.50.255.252 IP address is the IP address for the virtual server that is running zigbee2mqtt and mqtt (docker versions for both) Next (perhaps after the above issue is sorted) I am planning to add some end devices I have (light switches) and see the impact these will have. If no impact for about 24 hours, then I will add the more "chatty" devices to the networks - my 12 power monitoring breakers and the whole of house power monitoring on my 3 phases. |
Beta Was this translation helpful? Give feedback.
-
|
im sorry for an offtopic , but where I can find a documentation for the latest converters format? Right now I see git switch sample is different from the documentation https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html#_2-creating-the-external-definition and as well 'generate new difinition' |
Beta Was this translation helpful? Give feedback.
-
|
Hi folks, Flashed my SLZB-06M to this firmware von @darkxst and changed the driver to ember in the frontend. Here my setup. z2m is running on my proxmox server inside an LXC. z2m accesses the SLZB-06M via TCP. Zigbee2MQTT version 1.36.0 commit: 9c505fd Devices Everything works fine since then. From time to time I see some errors in the log like this. Error 2024-03-31 18:28:43Publish 'set' 'state' to 'BJ Lüfter Heizung' failed: 'Error: Command 0xa4c13824b720893b/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed ({"target":55432,"apsFrame":{"profileId":260,"clusterId":6,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":78},"zclSequence":101,"commandIdentifier":11} timed out after 10000ms)' |
Beta Was this translation helpful? Give feedback.
-
Thx, I will have a look into that and then come back with the Zigbee-herdsman debug logs logs if I figure it out ;) |
Beta Was this translation helpful? Give feedback.
-
finally managed to get the zigbee-herdsman debug logs for you to have a look: |
Beta Was this translation helpful? Give feedback.
-
|
Just updated to latest 1.36.1 commit: ffc2ff1. |
Beta Was this translation helpful? Give feedback.
-
|
@Nerivec just a couple more zigbee-herdsman debug logs from today for you. |
Beta Was this translation helpful? Give feedback.
-
|
Just ran the ./update.sh to check if there is something new. EDIT: In the end I fixed that by rolling back to a known working snapshot of my z2m LXC and updating again to latest version. |
Beta Was this translation helpful? Give feedback.
-
|
Zigbee2MQTT version I noticed that there were some inconsistacies with adding devices. I added 4 devices: Most of the devices interviewed fine, except the sengled bulb, it did not expose the color section option. I also could not toggle the innr switch from the dashboard, but I could from the exposes tab. After switching back the standard branch and re-interviewing, everything appeared to work properly. Error 2024-03-31 16:38:00No converter available for 'color' ({"hex":"#2db526"}) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback! The frontend |
Beta Was this translation helpful? Give feedback.
-
|
@parish99 could you create a new issue for the Sengled one? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
I can confirm that OTA is working for Tuya TS011F both local and online :-) I've felt very adventurous so I updated 7 plugs at the same time.....just to spam the network. That was too much to handle :-) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback!
7 plugs * 5000 messages (on average), yeah, that'd be too much! |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately no log, but it crashed completely. I guess it was max overload :-) |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, FYI, I just update the Z2M addon to 1.36.1-1 release with ember adapter and Skyconnect in EmberZNet 7.4.1 [GA] firmware and all seems fine until here. I would report if something goes wrong. Unfortunatly, I stil don't have the power reported by Aqara T1 but it is certainly another root cause (see: #20895) |
Beta Was this translation helpful? Give feedback.
-
|
I'm affraid I ruined my Sonoff E dongle. [edit] I managed to get it running again on 7.3 using the methode of Smart Home Junky https://www.youtube.com/watch?v=BU9ha0Uaduc. |
Beta Was this translation helpful? Give feedback.
-
|
The file size is (239.520 bytes) If I look inside it looks like a binary file. It starts with: ë�¦�� � ô |
Beta Was this translation helpful? Give feedback.
-
|
what command did you use to pull the file? if the URL you used was
|
Beta Was this translation helpful? Give feedback.
-
|
I did not use a command. I Simply went to the website en followd the links |
Beta Was this translation helpful? Give feedback.
-
|
This is the one you want to download and flash for Sonoff Dongle-E: https://github.com/darkxst/silabs-firmware-builder/blob/main/firmware_builds/zbdonglee/ncp-uart-hw-v7.4.1.0-zbdonglee-115200.gbl Try to flash that one, and then try to start Z2M with it. You will know for sure if the firmware flashing worked or not. If the firmware isn't flashed properly, it will prevent Z2M from starting, same if the firmware stayed on 7.3 (can't start |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, that was the trick. It is workin now |
Beta Was this translation helpful? Give feedback.
-
|
Hello guys, @Nerivec @Koenkk Also, I noticed this: |
Beta Was this translation helpful? Give feedback.
-
|
Do we still need to be using the edge version to upgrade to this, or has it been implemented in the latest Z2M release two days ago? |
Beta Was this translation helpful? Give feedback.
-
|
It has been available in release since March release. April release focused a bit more on performance fixes. |
Beta Was this translation helpful? Give feedback.
-
|
So it's not required to run the dev branch, as stated in the first post in this thread? :-) |
Beta Was this translation helpful? Give feedback.
-
|
So if I just change the adapter settings on my sonoff e, it’s already on the latest version as per this thread, that is all that is needed now? Not to run z2m via edge? |
Beta Was this translation helpful? Give feedback.
-
|
Adapter: SMLIGHT SLZB-07 @Nerivec I've noticed something. I had a lot of different errors. I started a new network from scratch and tested all my devices one by one until the errors occurred again. I then noticed that a few of my IKEA ON/OFF switches (E1743) had an old firmware and I was unable to update them. I then manually updated them with my Black Magic Probe to the latest firmware, and I have had ZERO errors since. @Koenkk I don't know if that also affect your firmware? I did also noticed that when binding and unbinding from the GUI, it throws an error for my IKEA Rodret (E2201) but no error at all directly from MQTT.
|
Beta Was this translation helpful? Give feedback.
-
|
Last night I was struggeling with a, by me, wrong flashed Sonoff stick. I managed to flash it correctly with the help of @Nerivec. |
Beta Was this translation helpful? Give feedback.
-
|
This thread has served its initial testing purpose and has become far too large to be productive. We are now closing it. If you found an issue, please report it in the usual place (always check that it was not reported already!). |
Beta Was this translation helpful? Give feedback.
and others
-
Update 2024-04-03
** The
emberadapter is available in Zigbee2MQTT 1.36.0 + (no need to switch to the dev branch) **This thread has served its initial testing purpose and has become far too large to be productive. We are now closing it.
If you found an issue, please report it in the usual place (always check that it was not reported already!).
If you require assistance, or you found something but are not quite sure what to make of it, check the forum or Discord.
In order to make the Ember (EZSP) adapter more stable and performant, @Nerivec reimplemented the driver in Koenkk/zigbee-herdsman#918 (more details for the reasons behind the split can also be found there, along with currently applicable limitations).
Some features that are currently missing in the
ezspadapter have been added, like network backup/restore.The purpose of this thread is to gather feedback on the new driver.
Note that nothing will change for users that are currently using
serial.adapterezsp, this will stay as is.Supported adapters
To keep things simple, this driver currently only supports EmberZNet firmware 7.4.x (EZSP 13), older versions will not be supported. Initially, multi-protocol will also not be supported as this is not considered stable yet.
How to start testing
Custom URLwith a 7.4 firmwareconfiguration.yaml, set theadaptertoember.How to provide feedback
When providing feedback, fill in the following template:
Where:
Beta Was this translation helpful? Give feedback.
All reactions