1.37.0

[Koenkk]

Feel free to discuss the v1.37.0 release here!

[sam3487]

With the new ember settings, do we still need to be running the edge version of z2m or is the normal version fine to use now? Thanks!

[Nerivec]

ember has been available in release version since 1.36.

@Koenkk can you update the discussion to mention this (since the first post mentions dev branch, it appears to be causing confusion)?

[sam3487]

Thanks for clarifying! :)

[Koenkk]

Done!

[sam3487]

All of my devices have dissapeared from the frontend. They still appear to be working in the background though and are still listed in the devices yaml.

[sam3487]

[2024-05-02 14:12:47] error: zh:ember: !!! NCP FATAL ERROR reason=ERROR_WRONG_DIRECTION. ATTEMPTING RESET... !!! [2024-05-02 14:12:47] error: zh:ember:ezsp: ERROR Transaction failure; status=ERROR_WRONG_DIRECTION. Last: [FRAME: ID=52:"SEND_UNICAST" Seq=54 Len=26]. [2024-05-02 14:12:47] error: zh:controller:device: Default response to 0xf4b3b1fffeed1c6d failed [2024-05-02 14:12:48] error: zh:ember:uart:ash: Received frame with CRC error [2024-05-02 14:13:04] error: zh:ember: ~x~> [ZCL BROADCAST] Failed to send with status=NETWORK_BUSY. [2024-05-02 14:13:05] error: zh:ember: ~x~> [ZCL BROADCAST] Failed to send with status=NETWORK_BUSY. [2024-05-02 14:13:05] error: zh:ember: ~x~> [ZCL BROADCAST] Failed to send with status=NETWORK_BUSY. [2024-05-02 14:13:06] error: zh:ember: ~x~> [ZCL BROADCAST] Failed to send with status=NETWORK_BUSY. [2024-05-02 14:13:06] error: zh:ember: ~x~> [ZCL BROADCAST] Failed to send with status=NETWORK_BUSY. [2024-05-02 14:13:07] error: zh:ember: ~x~> [ZCL BROADCAST] Failed to send with status=NETWORK_BUSY. [2024-05-02 14:13:07] error: zh:ember: ~x~> [ZCL BROADCAST] Failed to send with status=NETWORK_BUSY. [2024-05-02 14:13:08] error: zh:ember: ~x~> [ZCL BROADCAST] Failed to send with status=NETWORK_BUSY. [2024-05-02 14:13:08] error: zh:ember: ~x~> [ZCL BROADCAST] Failed to send with status=NETWORK_BUSY. [2024-05-02 14:13:09] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:13:09] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:13:10] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:13:10] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:13:11] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:13:11] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:13:12] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:13:12] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:13:13] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:13:15] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:13:15] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:13:16] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:13:16] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:13:17] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:13:17] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:13:18] error: zh:ember: [ZDO] Failed permit joining request with status=NETWORK_BUSY. [2024-05-02 14:14:05] error: z2m: Failed to configure 'Guest Bathroom Bathtub Switch', attempt 1 (Error: ZCL command 0x00158d00041d1b17/11

[xelemorf]

Same for me, all devices dissapeared but working after a couple of hours. Tried to stop Z2M, delete database and coordinator backup file then reinstalling Z2M from scratch results the same. The UI also has some misplaced elements, permit join button under setting (not the dropdown) no longer visible. The dropdown permit join no longer works. Need to rollback it seems as it's completely dead at this point as cannot add any devices.

[Patricen1]

I do also have 49 devices in database.db files but only 45 appearing on frontend.
It looks like it was already the case with V1.36

[rwronski]

What does it mean when it's said that 'The ezsp driver is now deprecated'? Does it mean that it is no longer supported? Will my Sonoff dongle E still work with the EZSP driver?

[rwronski]

I am currently using version 6.10.3 of this firmware:
https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware/Zigbee3.0_Dongle-NoSigned/EZSP, and it works perfectly fine without any issues. Which version should I upgrade to that is well-tested and likely to ensure I encounter no problems?

[FuzzyMistborn]

I literally just updated my Sonoff -E's firmware using this site on Monday: https://darkxst.github.io/silabs-firmware-builder/ . But the firmware version installed is 7.3.1.0 build 176. Where can I get a 7.4.x firmware to install?

[N3rdix]

I literally just updated my Sonoff -E's firmware using this site on Monday: https://darkxst.github.io/silabs-firmware-builder/ . But the firmware version installed is 7.3.1.0 build 176. Where can I get a 7.4.x firmware to install?

I used this file via custom url:
https://github.com/darkxst/silabs-firmware-builder/blob/main/firmware_builds/zbdonglee/ncp-uart-hw-v7.4.2.0-zbdonglee-115200.gbl

[Jonybat]

Can the firmware be updated without having to re-pair all the devices?

[Ra72xx]

I updated my SkyConnect several times now from the repo above without having to re-pair.

[jamesonuk]

Should I be expecting to see anything in logs in the front end?
Running in Docker and since moving to 1.37 and starting I have had zero log entries

I see the release notes say debug logs are no longer in front end but normally there are lots of INFO logs I was still expecting to see...

In fact even looking inside the container the last entry was 30 minutes ago when I did the update.

Just to add restarting the container I see

[2024-05-02 08:48:58] info:     z2m: Kitchen Cooker Window (0x30fb10fffed7c8a4): LED2005R5/LED2106R3 - IKEA TRADFRI bulb GU10, white spectrum, 345/380 lm (Router)
[2024-05-02 08:48:58] info:     z2m: Kitchen Island Window (0x60b647fffe5b2885): LED2005R5/LED2106R3 - IKEA TRADFRI bulb GU10, white spectrum, 345/380 lm (Router)
[2024-05-02 08:48:58] info:     z2m: Kitchen Island Door (0x60b647fffe8fa08f): LED2005R5/LED2106R3 - IKEA TRADFRI bulb GU10, white spectrum, 345/380 lm (Router)
[2024-05-02 08:48:58] info:     z2m: Kitchen Cooker Door (0x60b647fffe259b5e): LED2005R5/LED2106R3 - IKEA TRADFRI bulb GU10, white spectrum, 345/380 lm (Router)
[2024-05-02 08:48:58] info:     z2m: Sonoff Button (0x38398ffffeec7642): SNZB-01P - SONOFF Wireless button (EndDevice)
[2024-05-02 08:48:58] info:     z2m: Zigbee: disabling joining new devices.
[2024-05-02 08:48:59] info:     z2m: Connecting to MQTT server at mqtts://mosquitto.xxx:8883
[2024-05-02 08:48:59] info:     z2m: Connected to MQTT server
[2024-05-02 08:48:59] info:     z2m: Started frontend on port zigbee2mqtt.xxx:8080
[2024-05-02 08:48:59] info:     z2m: Zigbee2MQTT started!

but nothing else.

Is this expected now and we shouldn't expect to see things like (just some old logs I had around(

Info 2024-04-08 17:02:39Update of 'Spare Room TRV' at 100.00%
Info 2024-04-08 17:02:39MQTT publish: topic 'zigbee2mqtt/Spare Room TRV', payload '{"battery":100,"battery_low":null,"child_lock":"UNLOCK","closing_steps":414,"frost_protection_temperature":7,"idle_steps":38,"last_seen":"2024-04-08T16:02:36.409Z","linkquality":255,"local_temperature":19.6,"local_temperature_calibration":0,"occupied_heating_setpoint":16.5,"open_window":"OFF","running_state":"idle","system_mode":"heat","update":{"installed_version":4353,"latest_version":4357,"progress":100,"remaining":9,"state":"updating"},"update_available":false,"valve_closing_limit_voltage":2405,"valve_motor_running_voltage":1382,"valve_opening_limit_voltage":1260,"weekly_schedule":{"friday":"00:00/16 07:00/19 10:00/16 10:00/16 17:00/19 23:00/16","monday":"00:00/16 07:00/19 10:00/16 10:00/16 17:00/19 23:00/16","saturday":"00:00/16 07:00/19 10:00/19 10:00/19 10:00/19 23:00/16","sunday":"00:00/16 07:00/19 10:00/19 10:00/19 10:00/19 23:00/16","thursday":"00:00/16 07:00/19 10:00/16 10:00/16 17:00/19 23:00/16","tuesday":"00:00/16 07:00/19 10:00/16 10:00/16 17:00/19 23:00/16","wednesday":"00:00/16 07:00/19 10:00/16 10:00/16 17:00/19 23:00/16"}}'
Info 2024-04-08 17:02:39MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Update of 'Spare Room TRV' at 100.00%","meta":{"device":"Spare Room TRV","progress":100,"status":"update_progress"},"type":"ota_update"}'

[Nerivec]

z2m: Zigbee2MQTT started! These (and before) would happen before frontend can register them.
MQTT publish These lines have been moved to debug since it was very spammy.
Update of That would be OTA, so not frequent.

Depending on the adapter type you are using, it could be pretty quiet, unless some valuable info needs to be logged 😉
If you want to make sure it is working, you can try Permit Join, that should add an info line.
info level logging: https://github.com/search?q=org%3AKoenkk+logger.info+language%3ATypeScript&type=code&l=TypeScript

[martyzeq]

I understand that it is a matter of "point of view", but this feels like info is almost useless to me, it should be more talkative imho - we have Info, Warn, Error and Debug - I am usually interested in state changes in log, and it was included in Info log level, which was just fine for me. Now I have to switch to Debug, which makes logs flooded. Would it be possible to extend loglevel setting to 8 values like severity levels in syslog ? I am really missing previous logging behaviour.... Thank you

[RCorsaletti]

i can't see devices messages even in debug, it was very useful at times to debug automations and stuff

[Ra72xx]

Are you certain that it is already prime time for the new ember driver? As much as I'm looking forward to it, as of now it is still unusable for me (#22249, while the old ezsp driver at least works most of the time.

[Milinator]

I can't rename devices anymore, the "edit" button is missing and the friendly name under settings tab is a read-only textfield.

[S33G]

Oh that's my bad.
Working on a fix right now.

[S33G]

nurikk/zigbee2mqtt-frontend#2012

[KimpiegamesYT1]

I can no longer change the names of the devices?

[S33G]

Fixed here:
nurikk/zigbee2mqtt-frontend#2012

[diesel437]

With this new update, will I have to repair all my devices if I change my coordinator hardware? Like I have a Sonoff Dongle-E dongle, and I would like to change to SMLight SLZB-06M. I'm avoiding this since there are 80 devices to re-pair.

[S33G]

No you should not need to re-pair providing you are using the same .db

[diesel437]

Ok, thats great. So docs need to be updated then: https://www.zigbee2mqtt.io/guide/faq/#how-do-i-migrate-from-one-adapter-to-another

[ministryofsillywalks]

Also would really like to know if this is true.
My slzb-05 just died and now I would have to switch to a sonoff ZBDongle-E.
Can i make this switch without having to repair everything?

[N3rdix]

Just paired one Bosch device with install code to test the new ember, this basically went fine. But a new warning confuses me. Is this related to ember or is it the device telling that it's only compliant to an older revision and nothing to worry about?

[2024-05-03 10:42:20] warning: zh:ember: [ZDO] Node descriptor for "35771" reports device is only compliant to revision "22" of the ZigBee specification (current revision: 23).

EDIT: using a Sonoff Dongle-E with EZSP ncp-uart-hw-v7.4.2.0-zbdonglee-115200

[Nerivec]

It's just a warning when a device's firmware doesn't match current Zigbee revision; in case you ever have trouble with a device, that can sometimes be the cause. It should not cause problems as long as the versions aren't too far apart. If you see one with 'pre-21', that's when things usually get complicated.

[merlinpimpim]

Hello,
There's something I don't understand about EZSP versus EMBER:
I use a SkyConnect coordinator in multiprotocol mode with this firmware (successfully for 3 months): https://github.com/darkxst/silabs-firmware-builder/blob/main/firmware_builds/skyconnect/rcp-uart-802154-v4.3.3-skyconnect-460800.gbl
It works fine with EZSP but not at all with EMBER, and I read that in the next release EZSP will no longer be supported.
What should I do?

[Koenkk]

and I read that in the next release EZSP will no longer be supported

This is not true, it will stay in but stop receiving maintenance. Still it is recommended to switch to ember.

[Nerivec]

You will definitely want to see https://youtu.be/8-YwXkgD3CY?t=2976 too. I'd advise you eventually switch out of multiprotocol, if you want to continue receiving timely updates.

[merlinpimpim]

Sorry Nerivec, I misinterpreted this information in the logs: "Deprecated driver 'ezsp' currently in use, 'ember' will become the officially supported EmberZNet driver in next release".

OK, I'll plan to switch back to Zigbee only.

[litecross91]

I got this in logs:

[2024-05-03 17:10:54] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_INDIRECT_TRANSACTION_EXPIRY for "11906".
[2024-05-03 17:11:28] warning: 	zh:ember:ezsp: Received network/route error ROUTE_ERROR_NON_TREE_LINK_FAILURE for "11906".

What does it mean? It's a problem?

Zigbee2MQTT version
1.37.0 commit: unknown
Coordinator type
EmberZNet
Coordinator revision
7.4.2 [GA]
Coordinator IEEE Address
0xe0798dfffed1ba31
Frontend version
0.6.165
19.32.0
0.45.0

[litecross91]

I added several devices and the next line always came up since I set the "ember".

Node descriptor for "6402" reports device is only compliant to revision "21" of the ZigBee specification (current revision: 23).
or
zh:ember: [ZDO] Node descriptor for "37678" reports device is only compliant to revision "pre-21" of the ZigBee specification (current revision: 23).
or
zh:ember: [ZDO] Node descriptor for "31837" reports device is only compliant to revision "22" of the ZigBee specification (current revision: 23).

Regardless, the devices work.

Info 2024-05-04 12:28:14Zigbee: allowing new devices to join.
Info 2024-05-04 12:28:14[STACK STATUS] Network opened.
Info 2024-05-04 12:28:54Interview for '0xa4c1381fa72ade21' started
Info 2024-05-04 12:28:54Device '0xa4c1381fa72ade21' joined
Info 2024-05-04 12:28:54Starting interview of '0xa4c1381fa72ade21'
Warning 2024-05-04 12:28:57[ZDO] Node descriptor for "6402" reports device is only compliant to revision "21" of the ZigBee specification (current revision: 23).
Info 2024-05-04 12:29:03Succesfully interviewed '0xa4c1381fa72ade21'
Info 2024-05-04 12:29:03Successfully interviewed '0xa4c1381fa72ade21', device has successfully been paired
Info 2024-05-04 12:29:03Device '0xa4c1381fa72ade21' is supported, identified as: Custom devices (DiY) Xiaomi temperature & humidity sensor with custom firmware (LYWSD03MMC)
Info 2024-05-04 12:29:03Configuring '0xa4c1381fa72ade21'
Info 2024-05-04 12:29:17Successfully configured '0xa4c1381fa72ade21'

[Nerivec]

See the Help section here for details on ember-specific logging. Some of this will be added to Z2M docs as appropriate, but in the meantime, I gathered it all there.

[litecross91]

I cannot find a similar error message

[Nerivec]

Devices identified as having an older Zigbee revision. These can be the source of problems, especially if "pre-21".
In short, this is just indicative, in case you ever encounter issues with that device, that could be the cause.

[litecross91]

Thank you!

[kvmgz]

Hi there. In this update my Symfonsik (sound) remote - I use it to turn on/off & dim lights - stopped working on button press, only the rotation is registered.
If I roll back to the previous version it works.
Any ideas?

[jowinthe]

Could someone please have a look at this error log? Everything in my system has the latest update as of today (e.g. HA core 2024.5.2). All Zigbee devices has the latest FW. When I'm running an automation to turn on, or off, or set brightness, these errors are appearing in the log, but (most of the time) the lights are adjusting correctly. Not sure if this is normal behavior and can be ignored?

Error 2024-05-08 15:31:21Publish 'set' 'brightness' to 'ikea_pære1' failed: 'Error: ZCL command 0x2c1165fffee454a0/1 genLevelCtrl.moveToLevelWithOnOff({"level":102,"transtime":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (41))'

Error 2024-05-08 15:31:21Publish 'set' 'brightness' to 'ikea_pære2' failed: 'Error: ZCL command 0x2c1165fffedd2019/1 genLevelCtrl.moveToLevelWithOnOff({"level":102,"transtime":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (40))'

Error 2024-05-08 15:31:21Publish 'set' 'brightness' to 'ikea_vask' failed: 'Error: ZCL command 0x000b57fffef4e644/1 genLevelCtrl.moveToLevelWithOnOff({"level":102,"transtime":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (35))'

My Zigbee2MQTT setup:

Zigbee2MQTT version 1.37.0 commit: unknown
Coordinator type ConBee2/RaspBee2
Coordinator revision 0x26700700
Coordinator IEEE Address 0x00212effff0780fe
Frontend version 0.6.165, 19.32.0, 0.45.0
Stats
Total 19
By device type
Router: 11
End devices: 8
By power source
Mains (single phase): 11
Battery: 8
By vendor
IKEA of Sweden: 19
By model
TRADFRI remote control: 5
FLOALT panel WS 60x60: 4
FLOALT panel WS 30x90: 2
TRADFRIbulbE27WSglobeopal1055lm: 2
TRADFRI Driver 30W: 2
TRADFRI motion sensor: 1
TRADFRI on/off switch: 1
TRADFRI control outlet: 1
Remote Control N2: 1

Thank you.