SLZB-06M, ember driver, z2m doesn't start #23120
Comments
|
Can you solve the MQTT issue first ( |
|
I think the MQTT problem message is related to fact, that z2m not starting correctly. When the adapter is set to ember frontent it also does not work (bad gateway). After switching to ezsp, everything works (both frontend and mqtt). below debug: |
|
Following- similar issue |
|
Can you confirm what devices are these (link to the docs pages would be great):
From your log, these two sent nearly 1500 messages in under 2 minutes, before Z2M even finished starting properly. Something's definitely wrong/bad there. |
|
here you are :) those two devices are electricity meters https://www.zigbee2mqtt.io/devices/SPM01.html#tuya-spm01 I have disabled them and got logs. The same symptoms :/ both frontend and zigbee network didn't work... |
|
ok, I have solved problem :) In my case if log level is set to warning and in the same time adapter is set to ember z2m doesn't start (bad gateway). I case of ezsp frontend works. The solution is to set log level to warn. In both cases frontent works. It's very strange... |
|
Did you modify anything else? Since you provided a log with |
|
ok, you are right log level is dead end. I restarted addon and again both frontend and z2m didn't work.
|
|
I had same issues when switching from My impression from the logs was that one cannot switch properly from one driver to the other. What really s*cks that the config values shown via HA web GUI do not reflect the actual content of the |
|
@mmokrejs If the file and the UI are "synced", it shouldn't be a problem, but yeah, some operations break that link and the UI no longer reflects the content properly (like switching from regular to edge or vice versa). Otherwise, switching from one driver to the other is just a matter of changing the adapter config. @Herreropl Seems to be indeed something with those devices that start spamming very early ( |
|
@voc0der Looks like your issue might be related to this one. Any chance you can provide a log with |
|
Here's what happens to me: On a docker stop/start, update, reboot, etc... it has a 50/50 chance to start in this failed state. I can't tell if it's failing because it can't connect to Mosquito (same host, compose), but I doubt it, because Mosquito says its healthy, zwave works fine, Mosquito has a healthcheck that's well defined, and I've also had it wait 20 seconds just to see, and this error can happen when Mosquito has been running for a long time. And here (after I issue
This might not be the right thread for my issue as well, I'm now realizing. @Nerivec thanks for getting me to the right thread. Here it is. This is the 'failed' state of it not starting properly. Logs |
|
Looks the same indeed (the retries on startup are just the hardware flow control issues -known to silabs-, only way to get rid of them entirely at the moment is to flash a firmware without hardware flow control -and use |
|
This following segment repeats. I never see the Requested Logs |
|
I think this message "z2m:mqtt: Not connected to MQTT server!" appears when the addon is going to shutdown or restart. It seems that even frontend is offline something under the hood is working. |
|
Can either of you try the dev branch/edge, see if you get better results? |
|
Same exact results with |
I tried this no_hw firmware. After flashing first boot was ok, but after restart the same problem as before :/
|
|
Following- similar issue |
|
The no-hw was only for SkyConnect. @voc0der How familiar are you with docker? Any chance you could edit a few files so we can figure out where exactly the darn thing is stopping? |
|
I am not the original reporter but as a side note, I received yesterday from SMLIGHT current dev OTA update 2.4.2_dev applicable to both SLZB-06 and -06M. I still see: From SMLIGHT SLZB-06M web admin GUI [-> Admin tools -> Logs] (http://192.168.xx.xxx/settings/system_log) Note the [Edit: SMLight says these |
|
@Nerivec I'm pretty comfortable around docker/git/build, so if you have anything in mind I am open to trying. I still need to try the no HW firmware and post more logs but well, ideally it would work either way? |
|
@mmokrejs According to darkxst, these @voc0der The no-hw firmware will only cleanup the startup sequence (very beginning, the |
|
Here's the log: not exactly the same error, so I won't try to make any assumptions. It does fail to start as before. Logs |
|
@voc0der Any chance you can find me on Discord (can DM me from zigbee2mqtt server)? It'll be easier to share stuff without polluting this thread too much (weird appears to only be getting weirder... 😅). |
|
@robotsmarthomes and @MilesTEG1 can you confirm your adapter type/model, and setup for z2m and if it's exactly the same, or just similar? |
Hello 👋🏻 If you need more info , tell me, if I can provide them I will (I'm not a developer 😊). |
|
As user of the SLZB-06M I can also confirm that I need to start at least twice the z2m container in order to properly use it. Especially due to updates of the containers, it regularly occurs. See my log attached. Bad start, Z2M fails to start: And the second "clean" start: |
@TDCroPower Correct. No repairing needed. It all works. I do get the odd fault every couple weeks or so (then I need to power cycle either the device itself or the coordinator), but otherwise it works. Not the OTA, mind you. That is always broken and I get loads of uart errors in the logs when I try to OTA anything. |
|
I experienced similar issues with the SLZB-06M and seem to have things working with a slightly newer version combo than @DorjeDorf (and using
|
|
An update from me - since the issues never went away - especially with OTAs and regular reboots needed - I trashed the SLZB-06M and went back to Slaesh's trusty USB adapter. All problems went away. I could finally OTA my devices and in general, the overall feeling is of a much better system. I don't know where the problem is - whether it's the SLZB or the driver or something else - in my case - I am happy now, finally after what I consider an unsuccessful experiment. |
|
Yeah im over my SLZB-06M what a unstable piece of shit. |
|
For me the latest firmware update 2.5.6 works: together with ZigBee update 20240510: |
|
Hello, But since I recreate my Zigbee Network from scratch, changing channel, and all other values I had with the SkyConnect, I don't have anymore the start problem of Z2M. I also flashed this Zigbee firmware : https://github.com/Nerivec/silabs-firmware-builder/releases/tag/v2024.6.2 |
|
Hi, i have some Ethernet connectivity issue and coordinator freeze/crashes. Disconnect / reconnect the Ethernet cable (power off/on), the web interface work again. I managed to dump logs via USB and https://www.anticyclone-systems.co.uk/aslwebterm.php SMLIGHT support give the a 2.5.8 firmware to test but it was the same issue, after a few days, the adapter crash again. Any idea ? |
|
Are there any news? Like an updated firmware or an official statement in which the issue is officialy acknowledged? |
|
Following |
|
Following - have the same issue |
1 similar comment
|
Following - have the same issue |
|
Following - same issue... |
|
Following - bummer there are no consistent work arounds currently it seems. |
|
Following - bummer there are no consistent work arounds currently it seems. Is there any information or help that can be provided to help resolve this @Nerivec? I'm not too familiar with this hardware so I'm not totally sure where to go next, but have debugged and tried what I can so far, but am happy to provide needed information. |
|
For the SLZB06/06M, SMLight has been working on fixing a bug introduced around Core 2.5.6 that causes the ESP to slow down to the point where it either crashes, or really messes up the Zigbee side (timeouts, errors, etc.). We've yet to receive feedback on whether it was fixed or not. Some users have had better result with 2.3.6 I believe, but that's about as much information as we have right now. That part is out of Z2M's control. Some issues in this thread have been fixed, some not, it's a bit of a mix-of-things at this point. |
|
I'm in the process of upgrading to an SLZB-07MG24, any chance that this more recent HW isn't suffering from this problems? |
|
@Ra72xx 07 isn't TCP-based, so no ESP side at all (no core firmware involved, just the serial driver on your machine). |
|
Tbanks for the info. I'm using SkyConnect right now, but am suffering from various instabilities like the one here in this thread (which, however, seems to have gotten better recently), so I'm a bit hoping that the newer hardware will make my network more stable. |
|
Following - same issue... |
|
Out of curiosity (I don't have the 06m, I cannot test it myself), has anyone tried the esphome firmware for this model instead of the core firmware for the ESP side? For reference, here is an example with the MGM24 from TubesZB: |
|
Following - hopefully a update soon. |
|
following after smlight install and z2m not starting ( with any adapter ezsp,ember or zstack ). |
|
Hello everyone!
|
|
Hi takbo3000 thanks for the info, are you connected via ethernet or usb? |
|
via IP/Ethernet |
That should mostly depend on "what else is running", since Z2M itself consumes a fairly low amount of resources (70-100MB of RAM, which should be more than fine for these specs), but HA, and some addons (especially AI-related) can consume quite a lot, and large spikes in resources usage can affect overall stability. Last I heard (before the holidays), the core firmware bug had not been identified by SMLight yet. Note: Beware, proxmox has been linked to a few too many issues recently (confirmed or suspected), so, if setting up a new machine, you may want to look elsewhere. NIC issues. For USB users, passthrough also has issues, see this. |
|
Version 2.0 of z2m appears to have fixed the issue for me. I'm now running zigbee firmware revision: 20241127 and core firmware version: v2.3.6 with no issues via ethernet. Only updated today so unsure how stable it will be in the long run. |
|
Basically the same problem. Logs and conf #25537 |
|
Mine crashed several hours later. |
|
I built some ESPHome firmware for a couple of adapters. I have only tested the TubesZB MGM24, I do not have the SLZB06M. The SLZB06M firmware is modeled from the TubesZB one (with a few extras). If someone is willing & able to test it to replace the core firmware, let me know. https://nerivec.github.io/esphome-firmware-builder/ (web flasher via USB, similar to the SMLight one for core firmware) If you want to test this, you can find me on Discord if you want some help or can provide some detailed feedback (can DM me from the zigbee2mqtt server). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
What happened?
I decided to switch to ember driver on my SLZB-06M. I flashed firmware via OTA (20240510 ). Unfortunately Zigbee2MQTT fails to start... I have checked different baud rates but without success. With ezsp driver works, but with errors.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
port: tcp://10.10.10.245:6638
baudrate: 115200
adapter: ember
rtscts: false
Zigbee2MQTT version
1.38.0-1
Adapter firmware version
7.4.1.0 build 0
Adapter
ember
Setup
Add-on on Home Assistant OS on RPI4
Debug log
[10:09:27] INFO: Preparing to start...
[10:09:28] INFO: Socat not enabled
[10:09:30] INFO: Starting Zigbee2MQTT...
[2024-06-21 10:09:36] error: zh:ember:uart:ash: Received frame with CRC error
[2024-06-21 10:09:36] error: zh:ember:uart:ash: Received ERROR from NCP while connecting, with code=ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT.
[2024-06-21 10:09:36] error: zh:ember:uart:ash: ASH disconnected | NCP status: ASH_NCP_FATAL_ERROR
[2024-06-21 10:09:36] error: zh:ember:uart:ash: Error while parsing received frame, status=ASH_NCP_FATAL_ERROR.
[2024-06-21 10:09:38] warning: zh:ember:uart:ash: Frame(s) in progress cancelled in [1ac1020b0a527e]
[2024-06-21 10:09:38] error: zh:ember:uart:ash: Received unexpected reset from NCP, with reason=RESET_SOFTWARE.
[2024-06-21 10:09:38] error: zh:ember:uart:ash: ASH disconnected: ASH_ERROR_NCP_RESET | NCP status: ASH_NCP_FATAL_ERROR
[2024-06-21 10:09:38] error: zh:ember:uart:ash: Error while parsing received frame, status=HOST_FATAL_ERROR.
[2024-06-21 10:09:38] error: zh:ember: !!! NCP FATAL ERROR reason=HOST_FATAL_ERROR. ATTEMPTING RESET... !!!
[2024-06-21 10:14:37] error: z2m:mqtt: Not connected to MQTT server!
[2024-06-21 10:14:37] error: z2m:mqtt: Cannot send message: topic: 'zigbee2mqtt/bridge/state', payload: '{"state":"offline"}
[10:14:38] INFO: Preparing to start...
[10:14:39] INFO: Socat not enabled
[10:14:41] INFO: Starting Zigbee2MQTT...
[2024-06-21 10:14:47] warning: zh:ezsp: Deprecated driver 'ezsp' currently in use, 'ember' will become the officially supported EmberZNet driver in next release. If using Zigbee2MQTT see #21462
[2024-06-21 10:14:47] error: zh:ezsp:uart: <-- CRC error: 5593499cc3af15c6d19874f0cf3488fce23ea5ebc9de6fa220c3e6e27e|e6e2|8816
[2024-06-21 10:14:47] error: zh:ezsp:uart: Error while parsing to NpiFrame 'Error: <-- CRC error: 5593499cc3af15c6d19874f0cf3488fce23ea5ebc9de6fa220c3e6e27e|e6e2|8816
at Frame.checkCRC (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/frame.ts:87:19)
at SerialDriver.onParsed (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:169:19)
at Parser.emit (node:events:517:28)
at Parser._transform (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/parser.ts:49:26)
at Parser.Transform._write (node:internal/streams/transform:175:8)
at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10)
at Parser.Writable.write (node:internal/streams/writable:337:10)
at Socket.ondata (node:internal/streams/readable:809:22)
at Socket.emit (node:events:517:28)'
The text was updated successfully, but these errors were encountered: