zh:zstack:znp: Socket error using SLZB-06 and tcp/ethernet #24154
Comments
|
has anyone looked at this yet, i have the same issue |
|
same here |
|
`[2024-10-12 06:58:46] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"offline"}' /app/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:264 |
|
I found my issue.
on my szlb06 .....
I chose to lock the network access to my local network only. which is fine
for accessing the Web page but maybe there is a bug in it allowing access
on sockets.
once I turned that off, connection was fine.
…On Sat, 12 Oct 2024, 13:22 gcs8, ***@***.***> wrote:
`[2024-10-12 06:58:46] info: z2m:mqtt: MQTT publish: topic
'zigbee2mqtt/bridge/state', payload '{"state":"offline"}'
[2024-10-12 06:58:46] info: z2m: Disconnecting from MQTT server
[2024-10-12 06:58:46] info: z2m: Stopping zigbee-herdsman...
[2024-10-12 06:58:57] info: zh:controller: Wrote coordinator backup to
'/config/zigbee2mqtt/coordinator_backup.json'
[2024-10-12 06:58:57] info: zh:zstack:znp: closing
[2024-10-12 06:58:57] info: z2m: Stopped zigbee-herdsman
[2024-10-12 06:58:57] info: z2m: Stopped Zigbee2MQTT
/app/node_modules/winston/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/node_modules/readable-stream/lib/_stream_writable.js:264:12)
at DerivedLogger.Writable.write
(/app/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:300:21)
at DerivedLogger.log
(/app/node_modules/winston/lib/winston/logger.js:231:12)
at Logger.log (/app/lib/util/logger.ts:198:25)
at Logger.info (/app/lib/util/logger.ts:211:14)
at Znp.onPortClose
(/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:96:16)
at Object.onceWrapper (node:events:632:26)
at Socket.emit (node:events:529:35)
at TCP. (node:net:350:12)
[06:58:57] INFO: Preparing to start...
[06:58:58] INFO: Socat not enabled
[06:58:59] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2024-10-12 06:59:01] info: z2m: Logging to console, file (filename:
log.log)
[2024-10-12 06:59:01] info: z2m: Starting Zigbee2MQTT version 1.40.2
(commit #unknown)
[2024-10-12 06:59:01] info: z2m: Starting zigbee-herdsman (2.1.3)
[2024-10-12 06:59:01] info: zh:zstack:znp: Opening TCP socket with
192.168.100.137:6638
[2024-10-12 06:59:01] info: zh:zstack:znp: Socket connected
[2024-10-12 06:59:01] info: zh:zstack:znp: Socket ready
[2024-10-12 06:59:01] info: zh:zstack:znp: Writing CC2530/CC2531 skip
bootloader payload
[2024-10-12 06:59:02] info: zh:zstack:znp: Skip bootloader for
CC2652/CC1352
[2024-10-12 06:59:02] info: z2m: zigbee-herdsman started (resumed)
[2024-10-12 06:59:02] info: z2m: Coordinator firmware version:
'{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20221226,"transportrev":2},"type":"zStack3x0"}'
[2024-10-12 06:59:02] info: z2m: 0x00158d008afe16cf (0x00158d008afe16cf):
Not supported (Unknown)
[2024-10-12 06:59:02] info: z2m: Currently 1 devices are joined.
[2024-10-12 06:59:02] info: z2m: Zigbee: disabling joining new devices.
[2024-10-12 06:59:02] info: z2m: Connecting to MQTT server at
mqtt://core-mosquitto:1883
[2024-10-12 06:59:02] info: z2m: Connected to MQTT server
[2024-10-12 06:59:02] info: z2m:mqtt: MQTT publish: topic
'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
[2024-10-12 06:59:02] info: z2m: Started frontend on port 8099
[2024-10-12 06:59:02] info: z2m:mqtt: MQTT publish: topic
'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
[2024-10-12 06:59:02] info: z2m: Zigbee2MQTT started!`
—
Reply to this email directly, view it on GitHub
<#24154 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABZMQZJ6GISWKS3RJQKIKNLZ3EA7TAVCNFSM6AAAAABPDBR7WOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYGUZDQMRWG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hey @magiva, could you elaborate a little on the steps you took? Were you blocking access at your router level? or were all your adjustments made via the SLZB settings page/z2m settings etc. just swtiched over to an SLZB-06 and also having this issue cheers, Lint |
|
slzb security page for ip whitelist
I turned that off and it was OK
…On Mon, 14 Oct 2024, 08:24 LintHart, ***@***.***> wrote:
I found my issue. on my szlb06 ..... I chose to lock the network access to
my local network only. which is fine for accessing the Web page but maybe
there is a bug in it allowing access on sockets. once I turned that off,
connection was fine.
… <#m_-6271539777277906788_>
On Sat, 12 Oct 2024, 13:22 gcs8, *@*.*> wrote: [2024-10-12 06:58:46]
info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload
'{"state":"offline"}' [2024-10-12 06:58:46] info: z2m: Disconnecting from
MQTT server [2024-10-12 06:58:46] info: z2m: Stopping zigbee-herdsman...
[2024-10-12 06:58:57] info: zh:controller: Wrote coordinator backup to
'/config/zigbee2mqtt/coordinator_backup.json' [2024-10-12 06:58:57] info:
zh:zstack:znp: closing [2024-10-12 06:58:57] info: z2m: Stopped
zigbee-herdsman [2024-10-12 06:58:57] info: z2m: Stopped Zigbee2MQTT
/app/node_modules/winston/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/node_modules/readable-stream/lib/_stream_writable.js:264:12)
at DerivedLogger.Writable.write
(/app/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:300:21)
at DerivedLogger.log
(/app/node_modules/winston/lib/winston/logger.js:231:12) at Logger.log
(/app/lib/util/logger.ts:198:25) at Logger.info
(/app/lib/util/logger.ts:211:14) at Znp.onPortClose
(/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:96:16) at
Object.onceWrapper (node:events:632:26) at Socket.emit (node:events:529:35)
at TCP. (node:net:350:12) [06:58:57] INFO: Preparing to start... [06:58:58]
INFO: Socat not enabled [06:58:59] INFO: Starting Zigbee2MQTT... Starting
Zigbee2MQTT without watchdog. [2024-10-12 06:59:01] info: z2m: Logging to
console, file (filename: log.log) [2024-10-12 06:59:01] info: z2m: Starting
Zigbee2MQTT version 1.40.2 (commit #unknown) [2024-10-12 06:59:01] info:
z2m: Starting zigbee-herdsman (2.1.3) [2024-10-12 06:59:01] info:
zh:zstack:znp: Opening TCP socket with 192.168.100.137:6638
<http://192.168.100.137:6638> [2024-10-12 06:59:01] info: zh:zstack:znp:
Socket connected [2024-10-12 06:59:01] info: zh:zstack:znp: Socket ready
[2024-10-12 06:59:01] info: zh:zstack:znp: Writing CC2530/CC2531 skip
bootloader payload [2024-10-12 06:59:02] info: zh:zstack:znp: Skip
bootloader for CC2652/CC1352 [2024-10-12 06:59:02] info: z2m:
zigbee-herdsman started (resumed) [2024-10-12 06:59:02] info: z2m:
Coordinator firmware version:
'{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20221226,"transportrev":2},"type":"zStack3x0"}'
[2024-10-12 06:59:02] info: z2m: 0x00158d008afe16cf (0x00158d008afe16cf):
Not supported (Unknown) [2024-10-12 06:59:02] info: z2m: Currently 1
devices are joined. [2024-10-12 06:59:02] info: z2m: Zigbee: disabling
joining new devices. [2024-10-12 06:59:02] info: z2m: Connecting to MQTT
server at mqtt://core-mosquitto:1883 [2024-10-12 06:59:02] info: z2m:
Connected to MQTT server [2024-10-12 06:59:02] info: z2m:mqtt: MQTT
publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
[2024-10-12 06:59:02] info: z2m: Started frontend on port 8099 [2024-10-12
06:59:02] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state',
payload '{"state":"online"}' [2024-10-12 06:59:02] info: z2m: Zigbee2MQTT
started! — Reply to this email directly, view it on GitHub <#24154
(comment)
<#24154 (comment)>>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZMQZJ6GISWKS3RJQKIKNLZ3EA7TAVCNFSM6AAAAABPDBR7WOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYGUZDQMRWG4
<https://github.com/notifications/unsubscribe-auth/ABZMQZJ6GISWKS3RJQKIKNLZ3EA7TAVCNFSM6AAAAABPDBR7WOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYGUZDQMRWG4>
. You are receiving this because you commented.Message ID: @.*>
Hey @magiva <https://github.com/magiva>, could you elaborate a little on
the steps you took? Were you blocking access at your router level? or were
all your adjustments made via the SLZB settings page/z2m settings etc.
just swtiched over to an SLZB-06 and also having this issue
cheers,
Lint
—
Reply to this email directly, view it on GitHub
<#24154 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABZMQZKEU7U3NAEDFK5U653Z3NPRFAVCNFSM6AAAAABPDBR7WOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJQGEZDQOBYGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Great, thank you :) I didn't have that on myself though I'd like too once things stabilise. I ended up changing the port number late afternoon and it was still alive this morning which is a first in a few days :) |
|
i do not have IP whitelist on, and tried changing the port too (from 6638 to 6639) but i still get the same error after a few minutes: |
|
Could you check with the |
|
Mine was fixed with #644 |
|
I am running on the SLZB-06 Core Firmware version v2.6.8.dev21 and still experience socket errors. Here is the last bit of a Zigbee2MQTT log file: Here the end of another Zigbee2MQTT log file: |
|
@schwalbe13 this is either an issue with the SLZB-06 (ESP32 side locking-up, known issue) or your WiFi/LAN network stability (not Zigbee), it cannot be fixed from Z2M. |
|
uncheck ip whitelist and everything is ok. |
when applying the HAOS update it breaks. i didn't have the whitelist on. I have applied and removed without any change.
|
|
I had the same problem with the SLZB-06. Solved by activating Is a new setting in firmware v2.7.1: |
|
this fixed it for me: (as per user rbotteon)- Release notes:
|
*** FINALLY! *** I've been trying to get Z2M to work for months, and this solved the 502: Bad Gateway issue for me. |
What happened?
after starting the Zigbee2MQTT addon for HA, it starts and opens socket successfully.
in log messages (INFO) indicate the successful start. usually within a few minutes, sometimes 30 minutes, it crashes
happens with:
below a snippet of the debug log. as you can see, it runs normally (first timestamp 13:04:39 about skipping discovery, then crashes 2 minutes later:
What did you expect to happen?
the addon keeps running / not crash
How to reproduce it (minimal and precise)
run the addon for a few minutes
Zigbee2MQTT version
1.40.1-1
Adapter firmware version
20240710
Adapter
SLZB-06 - CC2652P
core firmware version: v2.3.6 (latest stable)
zigbee OTA firmware revision: 20240710 (latest stable)
Setup
addon on home assistant, intel nuc x64 Hassio
Debug log
log (1).log
log.log
The text was updated successfully, but these errors were encountered: