After update 1.35.2 to 1.35.3 ZigBee2MQTT Started and next 30 second Stopped

[asan84]

Description of the issue

After update 1.35.2 to 1.35.3 ZigBee2MQTT Started and next 15-30 second Stopped :(((

In Log:

/app/node_modules/winston-transport/node_modules/readable-stream/lib/_stream_writable.js:264
var er = new ERR_STREAM_WRITE_AFTER_END();
^
Error: write after end
at writeAfterEnd (/app/node_modules/winston-transport/node_modules/readable-stream/lib/_stream_writable.js:264:12)
at File.Writable.write (/app/node_modules/winston-transport/node_modules/readable-stream/lib/_stream_writable.js:300:21)
at DerivedLogger.ondata (/app/node_modules/winston/node_modules/readable-stream/lib/_stream_readable.js:629:20)
at DerivedLogger.emit (node:events:517:28)
at DerivedLogger.Readable.read (/app/node_modules/winston/node_modules/readable-stream/lib/_stream_readable.js:451:26)
at flow (/app/node_modules/winston/node_modules/readable-stream/lib/_stream_readable.js:858:34)
at File.pipeOnDrainFunctionResult (/app/node_modules/winston/node_modules/readable-stream/lib/_stream_readable.js:690:7)
at File.emit (node:events:517:28)
at onwriteDrain (/app/node_modules/winston-transport/node_modules/readable-stream/lib/_stream_writable.js:453:12)
at afterWrite (/app/node_modules/winston-transport/node_modules/readable-stream/lib/_stream_writable.js:441:18)

How to downgrade or fix a this error?

Addon version

1.35.3

Platform

Home Assistant 2024.1.6
Supervisor 2024.01.1
Debian 12
OS Agent 1.6.0
Docker 25.0.3
Coordinator firmware version: 6.6.5.0 build 204, type: EZSP v7

Logs of the issue (if applicable)

No response

[Maro20000]

remove and insert the USB coordinator, it helped me

[asan84]

remove and insert the USB coordinator, it helped me

I tried it, completely disconnected the power, turned it on, the error did not go away.

How to go back to 1.35.2?
I don't understand what the problem is with the new version.

[tm8]

+1 The same here .
How to go back to 1.35.2?
Zigbee2MQTT-Version
1.35.3 commit: unknown
Coordinator-Typ
zStack3x0
Coordinator-Version
20230507
Coordinator IEEE Adresse
0x00124b002c3a6401
Frontend-Version
0.6.156
zigbee_herdsman_converters_version
18.28.3
zigbee_herdsman_version
0.33.8
Statistiken
Gesamt 58
Nach Typ
Router: 33
Endgerät: 25

[Rookman2022]

I have the same problem in version 135.2-1 and also in 135.3-1
Coordinator-Typ: Skyconnect EZSP v12
Coordinator-Version 7.3.2.0 build 212
Router: 63
Endgerät: 30

[tm8]

I tried to solve the problem by switching back to version 1.35.2-1 (backup of Home Assistant), but without success.

[Rookman2022]

Only 135.1-1 works for me, all subsequent versions have the problem. The 135.1-1 runs without any problems.

[gdesmott]

Same problem here with 1.35.3-1 but I don't have much details in /config/logs:

[17:59:29] INFO: Preparing to start...
[17:59:31] INFO: Socat not enabled
[17:59:37] INFO: Starting Zigbee2MQTT...

[Koenkk]

@asan84 can you provide me your z2m configuration.yaml?

[tm8]

@asan84 can you provide me your z2m configuration.yaml?

Hello Koenkk, here is my configuration.yaml. X = Secret :-)

homeassistant: true
advanced:
channel: 15
network_key:
- 207
- 0
- XXXXXX
- 96
- 29
- 55
- XXXXXX
- 33
- 4
- XXXXXX
- 26
- 54
- 85
- 60
- 15
- 67
pan_id: 42440
ext_pan_id:
- 247
- XXXXX
- 82
- XXXXX
- 40
- 32
- XXXXXX
- XXXXXX
homeassistant_legacy_entity_attributes: false
legacy_api: false
legacy_availability_payload: false
log_level: info
log_syslog:
app_name: Zigbee2MQTT
eol: /n
host: localhost
localhost: localhost
path: /dev/log
pid: process.pid
port: 514
protocol: udp4
type: '5424'
last_seen: ISO_8601_local
mqtt:
server: mqtt://core-mosquitto:1883
user: addons
password: XXXXXXXX
port: /dev/ttyUSB0
frontend:
port: 8099
device_options:
legacy: false
devices:
'0x00158d0008d0b120':
friendly_name: WM Pufferspeicher | Heizraum
'0xc4988600000cac5e':
friendly_name: WC Licht 1
'0x0ceff6fffedfd53e':
friendly_name: HKT WC
'0x0017880106f90047':
friendly_name: HUE Schrank Wohnzimmer
'0x001788010331074e':
friendly_name: HUE Uhr Wohnzimmer
'0x0017880103316314':
friendly_name: HUE Ecke Couch Wohnzimmer
'0x001788010330ad16':
friendly_name: HUE Terrassentür Wohnzimmer
'0x0017880106fd5a92':
friendly_name: HUE TV Rechts Wohnzimmer
'0x0017880106fd59b2':
friendly_name: HUE TV Links Wohnzimmer
'0x001788010406f022':
friendly_name: HUE Strip Bad
'0xb0c7defffeeb39cd':
friendly_name: HKT Schlafzimmer
'0x3410f4fffeb2a850':
friendly_name: HKT Schlafzimmer 2
'0x0ceff6fffeb95b4f':
friendly_name: HKT Flur OG
'0x0ceff6fffedc7876':
friendly_name: HKT Bad OG
'0x0ceff6fffedd9439':
friendly_name: HKT Büro
'0x0ceff6fffedc9fbe':
friendly_name: HKT Küche
'0x000d6f0014f7de56':
friendly_name: CO Sensor Wohnzimmer
'0x001788010bcff5d8':
friendly_name: BM Schlafzimmer 2
'0x001788010bcfe674':
friendly_name: BM Philips HUE
'0x00158d0008d095ee':
friendly_name: WM Waschmaschine Trockner | Eingang UG
'0x00158d0008dffb06':
friendly_name: WM Hauptwasseranschluss | Abstellraum
'0x0ceff6fffeb95b07':
friendly_name: HKT Flur UG
'0x0ceff6fffedcbe0f':
friendly_name: HKT Fitnessraum
'0x0ceff6fffedfd47f':
friendly_name: HKT Bad UG
'0x0ceff6fffedca2a3':
friendly_name: HKT Gästezimmer
'0x000d6f001491b1cb':
friendly_name: CO Sensor Heizraum
'0x001788010d3572f7':
friendly_name: FB Philips HUE Dial 1 Büro
'0x804b50fffee0df75':
friendly_name: R2 L1 Licht Lounge
'0x804b50fffee2917f':
friendly_name: R4 L5 Licht Lounge
'0x804b50fffee273d1':
friendly_name: R2 L3 Licht Lounge
'0x804b50fffee27ace':
friendly_name: R1 L2 Licht Lounge
'0x804b50fffee0e01f':
friendly_name: R2 L2 Licht Lounge
'0xcc86ecfffe1c6095':
friendly_name: R1 L5 Licht Lounge
'0x804b50fffee273c5':
friendly_name: R4 L6 Licht Lounge
'0x804b50fffee27360':
friendly_name: R1 L6 Licht Lounge
'0x804b50fffee0e5b6':
friendly_name: R1 L3 Licht Lounge
'0x804b50fffee0e6d0':
friendly_name: R1 L1 Licht Lounge
'0xcc86ecfffe1d7732':
friendly_name: R4 L1 Licht Lounge
'0xc498860000da354c':
friendly_name: ACDC Lampe Licht Lounge
'0x804b50fffee0e28e':
friendly_name: R4 L3 Licht Lounge
'0x804b50fffee2781d':
friendly_name: R1 L4 Licht Lounge
'0x00178801097a2680':
friendly_name: R3 L1 Licht Lounge
'0x0017880109719b3a':
friendly_name: R3 L3 Licht Lounge
'0x00178801096fdc51':
friendly_name: R3 L2 Licht Lounge
'0x804b50fffee274e6':
friendly_name: R2 L4 Licht Lounge
'0x001788010b80e724':
friendly_name: HUE Leselicht Lounge
'0x00178801033251c4':
friendly_name: HUE Iris Lounge
'0x00124b002342e139':
friendly_name: BM Treppenhaus EG
'0x00124b0023adff17':
friendly_name: BM Treppenhaus DG
'0xcc86ecfffedb35e4':
friendly_name: Licht Treppenhaus OG-DG
'0x0017880102d54bab':
friendly_name: FB Philips HUE 1 WC
legacy: true
'0x001788010406bbbd':
friendly_name: HUE Strip Büro
'0x804b50fffee0e6f2':
friendly_name: R4 L2 Licht Lounge
'0x84fd27fffe698237':
friendly_name: R4 L4 Licht Lounge
'0x00178801096fc16a':
friendly_name: R3 L4 Licht Lounge
'0x001788010dd00b6f':
friendly_name: FB Philips HUE Dial 2 Lounge
'0x001788010d8bb2dc':
friendly_name: FB Philips HUE 2
ota:
ikea_ota_use_test_url: false
zigbee_ota_override_index_location: https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/index.json

[tm8]

I have two Sonoff Dongles:

• Version P for Zigbee on Chanel 15
• Version E for Thread on Chanel 25 (FIrmware is Flash only for Thread, not vor Multiprotocol)

Zigbee2MQTT-Version
1.35.2 commit: unknown
Coordinator-Typ
zStack3x0
Coordinator-Version
20230507
Coordinator IEEE Adresse
0x00124b002c3a6401
Frontend-Version
0.6.152
Zigbee-herdsman-converters version
18.25.1
Zigbee-herdsman version
0.33.5

[asan84]

@asan84 can you provide me your z2m configuration.yaml?
I attached my config

configuration.zip

[Koenkk]

I think it's because of the log_syslog, can you remove it from your configuration.yaml and see if that fixes the problem?

[tm8]

I think it's because of the log_syslog, can you remove it from your configuration.yaml and see if that fixes the prob

Hi Koenkk, thanks for the feedback. Unfortunately no change in behavior. The adapter restarts every 3-4 minutes for me. I am back to version 1.35.1, no problems there, the adapter runs stable.

[PrzemsiMat]

the same issue Current version: 1.35.3-1
ZB-GW04 USB

[asan84]

I think it's because of the log_syslog, can you remove it from your configuration.yaml and see if that fixes the problem?

I didn't turn off the log_syslog. The service started automatically after stopping on the 10th attempt.
It has loaded and hasn't stopped yet.

I don't understand what the problem is with the new version.