Zigbee2Mqtt tcp RCP issue

What happened?

Z2M cannot start configured to use HA skyconnect with multiprotocol addon enabled.

data_path: /config/zigbee2mqtt
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: "-d -d"
  log: false
mqtt:
  server: mqtt://homeassistant:1883
serial:
  port: tcp://172.30.32.1:9999
  adapter: ezsp
frontend: true
last_seen: enable
homeassistant: true
advanced:
  log_level: debug
zigbee_herdsman_debug: true

What did you expect to happen?

Z2M starts and can use skyconnect in RCP mode

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.33.2-1/edge

Adapter firmware version

v4.3.1.0

Adapter

skyconnect

Debug log

[14:16:25] INFO: Preparing to start... [14:16:26] INFO: Socat not enabled [14:16:26] INFO: Zigbee Herdsman debug logging enabled [14:16:27] INFO: Starting Zigbee2MQTT... Zigbee2MQTT:info 2023-11-18 14:16:39: Logging to console and directory: '/config/zigbee2mqtt/log/2023-11-18.14-16-39' filename: log.txt Zigbee2MQTT:info 2023-11-18 14:16:39: Starting Zigbee2MQTT version 1.33.2 (commit #unknown) Zigbee2MQTT:info 2023-11-18 14:16:39: Starting zigbee-herdsman (0.21.0) 2023-11-18T13:16:40.929Z zigbee-herdsman:adapter:ezsp:debg Adapter concurrent: 8 2023-11-18T13:16:40.931Z zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11]},"serialPort":{"path":"tcp://172.30.32.1:9999","adapter":"ezsp"},"databasePath":"/config/zigbee2mqtt/database.db","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","backupPath":"/config/zigbee2mqtt/coordinator_backup.json","adapter":{"disableLED":false,"concurrent":null,"delay":null}}' 2023-11-18T13:16:40.936Z zigbee-herdsman:adapter:ezsp:uart Opening TCP socket with 172.30.32.1:9999 2023-11-18T13:16:40.961Z zigbee-herdsman:adapter:ezsp:uart Socket connected 2023-11-18T13:16:40.966Z zigbee-herdsman:adapter:ezsp:uart Socket ready 2023-11-18T13:16:40.968Z zigbee-herdsman:adapter:ezsp:uart Uart reseting 2023-11-18T13:16:40.971Z zigbee-herdsman:adapter:ezsp:uart --> Write reset 2023-11-18T13:16:40.975Z zigbee-herdsman:adapter:ezsp:uart --> [1ac038bc7e] 2023-11-18T13:16:40.978Z zigbee-herdsman:adapter:ezsp:uart -?- waiting reset 2023-11-18T13:16:40.984Z zigbee-herdsman:adapter:ezsp:uart <-- [c1020b0a527e] 2023-11-18T13:16:40.986Z zigbee-herdsman:adapter:ezsp:uart <-- RSTACK: c1020b0a527e 2023-11-18T13:16:40.986Z zigbee-herdsman:adapter:ezsp:uart RSTACK Version: 2 Reason: RESET_SOFTWARE frame: c1020b0a527e 2023-11-18T13:16:40.989Z zigbee-herdsman:adapter:ezsp:uart -+- waiting reset success 2023-11-18T13:16:40.991Z zigbee-herdsman:adapter:ezsp:ezsp ==> version: {"desiredProtocolVersion":4} 2023-11-18T13:16:40.992Z zigbee-herdsman:adapter:ezsp:ezsp ==> {"cls":"version","id":0,"isRequest":true,"desiredProtocolVersion":4} 2023-11-18T13:16:40.995Z zigbee-herdsman:adapter:ezsp:uart --> DATA (0,0,0): 00000004 2023-11-18T13:16:40.996Z zigbee-herdsman:adapter:ezsp:uart --> [004221a850ed2c7e] 2023-11-18T13:16:40.997Z zigbee-herdsman:adapter:ezsp:uart -?- waiting (1) 2023-11-18T13:16:42.998Z zigbee-herdsman:adapter:ezsp:uart --> Error: Error: {"sequence":1} after 2000ms 2023-11-18T13:16:42.999Z zigbee-herdsman:adapter:ezsp:uart -!- break waiting (1) 2023-11-18T13:16:42.999Z zigbee-herdsman:adapter:ezsp:uart Can't send DATA frame (0,0,0): 00000004 2023-11-18T13:16:43.501Z zigbee-herdsman:adapter:ezsp:uart ->> DATA (0,0,1): 00000004 2023-11-18T13:16:43.503Z zigbee-herdsman:adapter:ezsp:uart --> [084221a850ef017e] 2023-11-18T13:16:43.503Z zigbee-herdsman:adapter:ezsp:uart -?- rewaiting (1) 2023-11-18T13:16:45.155Z zigbee-herdsman:adapter:ezsp:uart <-- [c1020b0a527e] 2023-11-18T13:16:45.155Z zigbee-herdsman:adapter:ezsp:uart <-- RSTACK: c1020b0a527e 2023-11-18T13:16:45.155Z zigbee-herdsman:adapter:ezsp:uart RSTACK Version: 2 Reason: RESET_SOFTWARE frame: c1020b0a527e 2023-11-18T13:16:45.157Z zigbee-herdsman:adapter:ezsp:uart <-- [0142a1a8582805c1ae247e] 2023-11-18T13:16:45.157Z zigbee-herdsman:adapter:ezsp:uart <-- DATA (0,1,0): 0142a1a8582805c1ae247e 2023-11-18T13:16:45.158Z zigbee-herdsman:adapter:ezsp:uart --> ACK (1) 2023-11-18T13:16:45.159Z zigbee-herdsman:adapter:ezsp:uart --> [8160597e] 2023-11-18T13:16:45.161Z zigbee-herdsman:adapter:ezsp:ezsp <== Frame: 0080000c021073 2023-11-18T13:16:45.163Z zigbee-herdsman:adapter:ezsp:ezsp <== 0x0: {"cls":"version","id":0,"isRequest":false,"protocolVersion":12,"stackType":2,"stackVersion":29456} 2023-11-18T13:16:45.164Z zigbee-herdsman:adapter:ezsp:uart -+- rewaiting (1) success 2023-11-18T13:16:45.164Z zigbee-herdsman:adapter:ezsp:uart -+- waiting (1) success 2023-11-18T13:16:45.165Z zigbee-herdsman:adapter:ezsp:ezsp Switching to eszp version 12 2023-11-18T13:16:45.165Z zigbee-herdsman:adapter:ezsp:ezsp ==> version: {"desiredProtocolVersion":12} 2023-11-18T13:16:45.165Z zigbee-herdsman:adapter:ezsp:ezsp ==> {"cls":"version","id":0,"isRequest":true,"desiredProtocolVersion":12} 2023-11-18T13:16:45.167Z zigbee-herdsman:adapter:ezsp:uart --> DATA (0,1,0): 01000100000c 2023-11-18T13:16:45.168Z zigbee-herdsman:adapter:ezsp:uart --> [014321a9542a19be807e] 2023-11-18T13:16:45.170Z zigbee-herdsman:adapter:ezsp:uart -?- waiting (1) 2023-11-18T13:16:45.171Z zigbee-herdsman:adapter:ezsp:uart <-- [8160597e] 2023-11-18T13:16:45.172Z zigbee-herdsman:adapter:ezsp:uart <-- ACK (1): 8160597e 2023-11-18T13:16:45.172Z zigbee-herdsman:adapter:ezsp:uart -+- waiting (1) success 2023-11-18T13:16:46.155Z zigbee-herdsman:adapter:ezsp:uart <-- [a1443b7e] 2023-11-18T13:16:46.157Z zigbee-herdsman:adapter:ezsp:uart <-- NAK (1): a1443b7e 2023-11-18T13:16:46.158Z zigbee-herdsman:adapter:ezsp:uart NAK Unexpected packet sequence 1 2023-11-18T13:16:50.993Z zigbee-herdsman:adapter:ezsp:ezsp Time to watchdog ... 0 2023-11-18T13:16:50.993Z zigbee-herdsman:adapter:ezsp:ezsp ==> nop: null 2023-11-18T13:16:55.179Z zigbee-herdsman:adapter:ezsp:ezsp ==> {"cls":"nop","id":5,"isRequest":true} 2023-11-18T13:16:55.180Z zigbee-herdsman:adapter:ezsp:uart --> DATA (1,1,0): 0200010500 2023-11-18T13:16:55.182Z zigbee-herdsman:adapter:ezsp:uart --> [7d314021a9512a9a0d7e] 2023-11-18T13:16:55.184Z zigbee-herdsman:adapter:ezsp:uart -?- waiting (2) Zigbee2MQTT:error 2023-11-18 14:16:55: Error while starting zigbee-herdsman Zigbee2MQTT:error 2023-11-18 14:16:55: Failed to start zigbee Zigbee2MQTT:error 2023-11-18 14:16:55: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions Zigbee2MQTT:error 2023-11-18 14:16:55: Exiting... Zigbee2MQTT:error 2023-11-18 14:16:55: Error: Failure send version:{"type":"Buffer","data":[1,0,1,0,0,12]} at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:562:23 at Queue.executeNext (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32) 2023-11-18T13:16:55.342Z zigbee-herdsman:adapter:ezsp:uart <-- [1240a1a90c2a25bdf97e] 2023-11-18T13:16:55.343Z zigbee-herdsman:adapter:ezsp:uart <-- DATA (1,2,0): 1240a1a90c2a25bdf97e 2023-11-18T13:16:55.343Z zigbee-herdsman:adapter:ezsp:uart --> ACK (2) 2023-11-18T13:16:55.344Z zigbee-herdsman:adapter:ezsp:uart --> [82503a7e] 2023-11-18T13:16:55.344Z zigbee-herdsman:adapter:ezsp:ezsp <== Frame: 028001580030 2023-11-18T13:16:55.346Z zigbee-herdsman:adapter:ezsp:ezsp <== 0x58: {"cls":"invalidCommand","id":88,"isRequest":false,"reason":48} 2023-11-18T13:16:55.346Z zigbee-herdsman:adapter:ezsp:uart -+- waiting (2) success

Koenkk / zigbee2mqtt