Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After flash update to ember. Z2M configurationnot excepting ember #22582

Closed
canedje opened this issue May 10, 2024 · 4 comments
Closed

After flash update to ember. Z2M configurationnot excepting ember #22582

canedje opened this issue May 10, 2024 · 4 comments
Labels
problem Something isn't working

Comments

@canedje
Copy link

canedje commented May 10, 2024

What happened?

I just flashed my Sonoff ZBDongle-E to latest 7.4.2.0 build. Using this tutorial:
https://smarthomescene.com/guides/how-to-use-ember-driver-with-efr32mg21-zigbee-adapters/?fbclid=I
wZXh0bgNhZW0CMTAAAR3p8Cy-teqA7gg_Fn2xUkTDArGSTlTZRORNU7pgXl7__Rvuf9xVL1Dgtiw_aem_ASu41kv-OnrMVTE3Y8okCTbiHubgfS9SgUDMZtypAozlPWAd-tXbooK2_XYw36NmxHlptQOmm8gjzewfoWFZGqNV

Flashing worked fine.
But after changing mij configuration file adapter to ember.
My Z2M docker didn't start up with a CRC error.
image
I did change the adapter type back to ezsp and Z2M did start up again.
At "about" in Z2M it gives indeed EZSP instead of ember. It gives the right build version:
image

I did use: https://github.com/darkxst/silabs-firmware-builder/blob/main/firmware_builds/zbdonglee/ncp-uart-hw-v7.3.2.0-zbdonglee-none-115200.gbl as firmware update

EDIT: after first starting up after using ezsp as adapter I did change again to ember as adapter for a trial.
Now it is starting up in ember mode????
image

What did you expect to happen?

I Expected ember as type

How to reproduce it (minimal and precise)

See above. Just change adapter in ember instead of EZSP

Zigbee2MQTT version

1.37.1 commit: ea39d86

Adapter firmware version

7.4.2.0 build 0

Adapter

Sonoff ZBDongle-E

Setup

Z2M as a docker under Unraid

Debug log

No response

@canedje canedje added the problem Something isn't working label May 10, 2024
@wastez
Copy link

wastez commented May 10, 2024

I think that not the crc error was the reason why it wasn’t starting.
In the error shown below a old backup file triggered the error.

@canedje
Copy link
Author

canedje commented May 10, 2024

ahhhh okey.
Thanks. It could be possible because I did make a new backup file when running as EZSP.
After that I did retry the ember adapter

By the way: where to find the storage of the backup file?

@wastez
Copy link

wastez commented May 10, 2024

@canedje
The backup is stored in home folder of z2m.
In case you use it as home assistant addon it is in /config/zigbee2mqtt.

@Nerivec
Copy link
Collaborator

Nerivec commented May 14, 2024

An old backup file prevents ember from starting to avoid overwriting stuff without your knowledge and gives the error you posted that the version is not supported. If you move it out of the folder, or rename/delete it, then ember should start.
PS: A CRC error is common on start, it's just noise on the port, there is a retry mechanism just for that.

Please see https://www.zigbee2mqtt.io/guide/adapters/emberznet.html#logging-specific-to-this-stack for ember-specific logging details.

@Nerivec Nerivec closed this as completed May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants