I did run a NVRAM Backup. But when I restore it the devices in HA still don’t seem to work…
enable debug logging for zigpy and zigpy-znp per the HA ZHA docs. then restart HA.
check your homeassistant.log - it will be noisy but you can search for “channel” to get close you should see the networks setting printed out. take note of them and compare them to the backup file to make sure they are the same.
Looking for a bit of help here, I have a Conbee II, that I replaced with a TubesZB yesterday (POE Coordinator) by deleting and readding the ZHA device.
The entire process went pretty smoothly - I only have two devices, so nice and quick really.
However, nothing really worked. The motion sensor (Philips SML002) failed trigger motion within Home Assistant. From the logs I can see it was sending “something” when there was motion, and the door lock wasn’t reliable at updating its status.
An example of the motion sensor - this is creating motion (waving hand in front of sensor) when using the TubesZB
2022-06-19 12:18:33 DEBUG (MainThread) [zigpy.zcl] [0xDAAD:1:0x0006] Received command 0x42 (TSN 32): on_with_timed_off(on_off_control=0, on_time=3000, off_wait_time=0)
2022-06-19 12:18:33 DEBUG (MainThread) [zigpy.zcl] [0xDAAD:1:0x0006] No explicit handler for cluster command 0x42: on_with_timed_off(on_off_control=0, on_time=3000, off_wait_time=0)
vs on the Conbee II:
2022-06-19 12:42:24 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_INDICATION|2: 170>, 0]
2022-06-19 12:42:24 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_indication (1, 1)
2022-06-19 12:42:24 DEBUG (MainThread) [zigpy_deconz.api] APS data indication response: [30, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x0000>, 1, <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x970f>, 2, 260, 1030, b'\x08"\n\x00\x00\x18\x01', 0, 175, 255, 225, 77, 13, 0, -62]
2022-06-19 12:42:24 DEBUG (MainThread) [zigpy.zcl] [0x970F:2:0x0406] Received ZCL frame: b'\x08"\n\x00\x00\x18\x01'
2022-06-19 12:42:24 DEBUG (MainThread) [zigpy.zcl] [0x970F:2:0x0406] Decoded ZCL frame header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.GLOBAL_COMMAND: 0>, is_manufacturer_specific=0, is_reply=1, disable_default_response=0, reserved=0, *is_cluster=False, *is_general=True), tsn=34, command_id=10, *is_reply=True)
2022-06-19 12:42:24 DEBUG (MainThread) [zigpy.zcl] [0x970F:2:0x0406] Decoded ZCL frame: OccupancyCluster:Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=bitmap8, value=<bitmap8.1: 1>))])
2022-06-19 12:42:24 DEBUG (MainThread) [zigpy.zcl] [0x970F:2:0x0406] Received command 0x0A (TSN 34): Report_Attributes(attribute_reports=[Attribute(attrid=0x0000, value=TypeValue(type=bitmap8, value=<bitmap8.1: 1>))])
2022-06-19 12:42:24 DEBUG (MainThread) [zigpy.zcl] [0x970F:2:0x0406] Attribute report received: occupancy=<bitmap8.1: 1>
2022-06-19 12:42:24 DEBUG (MainThread) [zigpy.zcl] [0x970F:2:0x0406] Sending reply header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.GLOBAL_COMMAND: 0>, is_manufacturer_specific=False, is_reply=1, disable_default_response=1, reserved=0, *is_cluster=False, *is_general=True), tsn=34, command_id=<GeneralCommand.Default_Response: 11>, *is_reply=True)
2022-06-19 12:42:24 DEBUG (MainThread) [zigpy.zcl] [0x970F:2:0x0406] Sending reply: Default_Response(command_id=10, status=<Status.SUCCESS: 0>)
2022-06-19 12:42:24 DEBUG (MainThread) [zigpy_deconz.zigbee.application] Sending Zigbee request with tsn 34 under 94 request id, data: b'18220b0a00'
2022-06-19 12:42:24 DEBUG (MainThread) [zigpy_deconz.api] 'aps_data_indication' response from <DeconzAddress address_mode=ADDRESS_MODE.NWK address=0x970f>, ep: 2, profile: 0x0104, cluster_id: 0x0406, data: b'08220a00001801'
2022-06-19 12:42:24 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_request (20, 94, <DeconzSendDataFlags.NONE: 0>, <DeconzAddressEndpoint address_mode=2 address=38671 endpoint=2>, 260, 1030, 1, b'\x18"\x0b\n\x00', <DeconzTransmitOptions.USE_NWK_KEY_SECURITY: 2>, 0)
2022-06-19 12:42:24 DEBUG (MainThread) [zigpy_deconz.api] APS data request response: [2, <DeviceState.APSDE_DATA_REQUEST_SLOTS_AVAILABLE|2: 34>, 94]
2022-06-19 12:42:25 DEBUG (MainThread) [zigpy_deconz.api] Device state changed response: [<DeviceState.128|APSDE_DATA_REQUEST_SLOTS_AVAILABLE|APSDE_DATA_CONFIRM|2: 166>, 0]
2022-06-19 12:42:25 DEBUG (MainThread) [zigpy_deconz.api] Command Command.aps_data_confirm (0,)
2022-06-19 12:42:25 DEBUG (MainThread) [zigpy_deconz.api] APS data confirm response for request with id 94: 00
2022-06-19 12:42:25 DEBUG (MainThread) [zigpy_deconz.api] Request id: 0x5e 'aps_data_confirm' for <DeconzAddressEndpoint address_mode=ADDRESS_MODE.NWK address=0x970f endpoint=2>, status: 0x00
This probably has nothing to do with the TubesZB hardware, but im at a loss as to next steps, and therefore any pointers or ideas would be awesome.
Thanks
First I would try repairing the SML002. If it still reports the same may a post in #zigbee over in discord as I know a few people there have the device working with a cc2652 based coordinator.
Thanks - I should of been clearer - the issue also occurred with the Yale lock… YDD-D4F0 TSDB
With the lock, I could send the command to lock the door; and the door would lock; but the update would never appear in Home Assistant - unfortunately I didn’t capture the logs for this.
Yeah, pull some debug logging from the lock. Id still also try to re-join it in case something didn’t completely go right the first time.
I’ve tried adding and removing a few times… each time It adds, but as an example the motion sensor adds in 20-30 seconds using the Conbee, but takes minutes with the 2652.
I’ll try to have another attempt later today.
One thing that i found, liq is much lower with the 2652, on all devices. But I found something that indicated the Conbee isn’t showing this correctly… so possibly a red herring (230 vs 61)
LQI is calculated differently by the different radio chips so would not read to much into that.
The pairing it a bit odd, haven’t seen that before.
Thanks.
I moved back to the POE device…
The lock added fine: [core-ssh //]$ tail -f /config/home-assistant.log | grep zigpy2022-06-19 14:28 - Pastebin.com
However I cant control the lock:
2022-06-19 14:43:38 DEBUG (MainThread) [zigpy.zcl] [0x7114:1:0x0101] Sending request header: ZCLHeader(frame_control=FrameControl(frame_type=<FrameType.CLUSTER_COMMAND: 1>, is_manufacturer_specific=False, is_reply=0, disable_default_response=0, reserved=0, *is_cluster=True, *is_general=False), tsn=50, command_id=1, *is_reply=False)
2022-06-19 14:43:38 DEBUG (MainThread) [zigpy.zcl] [0x7114:1:0x0101] Sending request: unlock_door(pin_code=None)
2022-06-19 14:43:38 DEBUG (MainThread) [zigpy.device] [0x7114] Extending timeout for 0x32 request
2022-06-19 14:43:38 DEBUG (MainThread) [zigpy_znp.api] Sending request: AF.DataRequestExt.Req(DstAddrModeAddress=AddrModeAddress(mode=<AddrMode.NWK: 2>, address=0x7114), DstEndpoint=1, DstPanId=0x0000, SrcEndpoint=1, ClusterId=257, TSN=50, Options=<TransmitOptions.SUPPRESS_ROUTE_DISC_NETWORK|ACK_REQUEST: 48>, Radius=30, Data=b'\x01\x32\x01')
2022-06-19 14:43:38 DEBUG (MainThread) [zigpy_znp.api] Received command: AF.DataRequestExt.Rsp(Status=<Status.SUCCESS: 0>)
2022-06-19 14:43:39 DEBUG (MainThread) [zigpy_znp.api] Received command: AF.DataConfirm.Callback(Status=<Status.NWK_NO_ROUTE: 205>, Endpoint=1, TSN=50)
2022-06-19 14:43:39 DEBUG (MainThread) [zigpy_znp.zigbee.application] Request failed (Unsuccessful request status code: <Status.NWK_NO_ROUTE: 205>), retry attempt 1 of 5
2022-06-19 14:43:41 DEBUG (MainThread) [zigpy_znp.api] Sending request: AF.DataRequestExt.Req(DstAddrModeAddress=AddrModeAddress(mode=<AddrMode.NWK: 2>, address=0x7114), DstEndpoint=1, DstPanId=0x0000, SrcEndpoint=1, ClusterId=257, TSN=50, Options=<TransmitOptions.SUPPRESS_ROUTE_DISC_NETWORK|ACK_REQUEST: 48>, Radius=30, Data=b'\x01\x32\x01')
2022-06-19 14:43:41 DEBUG (MainThread) [zigpy_znp.api] Received command: AF.DataRequestExt.Rsp(Status=<Status.SUCCESS: 0>)
2022-06-19 14:43:42 DEBUG (MainThread) [zigpy_znp.api] Received command: AF.DataConfirm.Callback(Status=<Status.NWK_NO_ROUTE: 205>, Endpoint=1, TSN=50)
2022-06-19 14:43:42 DEBUG (MainThread) [zigpy_znp.zigbee.application] Request failed (Unsuccessful request status code: <Status.NWK_NO_ROUTE: 205>), retry attempt 2 of 5
2022-06-19 14:43:42 DEBUG (MainThread) [zigpy_znp.api] Sending request: AF.DataRequestSrcRtg.Req(DstAddr=0x7114, DstEndpoint=1, SrcEndpoint=1, ClusterId=257, TSN=50, Options=<TransmitOptions.SUPPRESS_ROUTE_DISC_NETWORK|ACK_REQUEST: 48>, Radius=30, SourceRoute=[], Data=b'\x01\x32\x01')
2022-06-19 14:43:42 DEBUG (MainThread) [zigpy_znp.api] Received command: AF.DataRequestSrcRtg.Rsp(Status=<Status.SUCCESS: 0>)
2022-06-19 14:43:43 DEBUG (MainThread) [zigpy_znp.api] Received command: AF.DataConfirm.Callback(Status=<Status.NWK_NO_ROUTE: 205>, Endpoint=1, TSN=50)
2022-06-19 14:43:43 DEBUG (MainThread) [zigpy_znp.api] Sending request: ZDO.ExtRouteDisc.Req(Dst=0x7114, Options=<RouteDiscoveryOptions.UNICAST: 0>, Radius=30)
2022-06-19 14:43:43 DEBUG (MainThread) [zigpy_znp.api] Received command: ZDO.ExtRouteDisc.Rsp(Status=<Status.SUCCESS: 0>)
2022-06-19 14:43:45 DEBUG (MainThread) [zigpy_znp.zigbee.application] Request failed (Unsuccessful request status code: <Status.NWK_NO_ROUTE: 205>), retry attempt 3 of 5
2022-06-19 14:43:45 DEBUG (MainThread) [zigpy_znp.api] Sending request: AF.DataRequestExt.Req(DstAddrModeAddress=AddrModeAddress(mode=<AddrMode.NWK: 2>, address=0x7114), DstEndpoint=1, DstPanId=0x0000, SrcEndpoint=1, ClusterId=257, TSN=50, Options=<TransmitOptions.SUPPRESS_ROUTE_DISC_NETWORK|ACK_REQUEST: 48>, Radius=30, Data=b'\x01\x32\x01')
2022-06-19 14:43:45 DEBUG (MainThread) [zigpy_znp.api] Received command: AF.DataRequestExt.Rsp(Status=<Status.SUCCESS: 0>)
2022-06-19 14:43:46 DEBUG (MainThread) [zigpy_znp.api] Received command: AF.DataConfirm.Callback(Status=<Status.NWK_NO_ROUTE: 205>, Endpoint=1, TSN=50)
2022-06-19 14:43:46 DEBUG (MainThread) [zigpy_znp.zigbee.application] Request failed (Unsuccessful request status code: <Status.NWK_NO_ROUTE: 205>), retry attempt 4 of 5
2022-06-19 14:43:47 DEBUG (MainThread) [zigpy_znp.api] Sending request: AF.DataRequestExt.Req(DstAddrModeAddress=AddrModeAddress(mode=<AddrMode.IEEE: 3>, address=00:0d:6f:00:10:8d:cf:c9), DstEndpoint=1, DstPanId=0x0000, SrcEndpoint=1, ClusterId=257, TSN=50, Options=<TransmitOptions.SUPPRESS_ROUTE_DISC_NETWORK|ACK_REQUEST: 48>, Radius=30, Data=b'\x01\x32\x01')
2022-06-19 14:43:47 DEBUG (MainThread) [zigpy_znp.api] Received command: AF.DataRequestExt.Rsp(Status=<Status.SUCCESS: 0>)
2022-06-19 14:43:48 DEBUG (MainThread) [zigpy_znp.api] Received command: AF.DataConfirm.Callback(Status=<Status.NWK_NO_ROUTE: 205>, Endpoint=1, TSN=50)
2022-06-19 14:43:48 DEBUG (MainThread) [zigpy_znp.zigbee.application] Request failed (Unsuccessful request status code: <Status.NWK_NO_ROUTE: 205>), retry attempt 5 of 5
for clarity, both coordinators are in the same location, only one powered on at any one time.
Before I get carried away running cables is my efr32 pro version 1 PoE capable?
No, you can use a PoE to microUSB + Ethernet splitter though.
1 Like
Cheers mate
Hi Tube0013, I recently purchase a TubesZB 2022 POE coordinator to replace my Conbee II. I’m having issued connecting with zigbee2mqtt, please see following HA log:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/socat.sh
[20:12:19] INFO: Socat not enabled, marking service as down
cont-init: info: /etc/cont-init.d/socat.sh exited 0
cont-init: info: running /etc/cont-init.d/zigbee2mqtt.sh
cont-init: info: /etc/cont-init.d/zigbee2mqtt.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun socat (no readiness notification)
services-up: info: copying legacy longrun zigbee2mqtt (no readiness notification)
[20:12:20] INFO: Handing over control to Zigbee2mqtt Core …
[email protected] start
node index.js
Zigbee2MQTT:info 2022-06-29 20:12:22: Logging to console and directory: ‘/config/zigbee2mqtt/log/2022-06-29.20-12-22’ filename: log.txt
Zigbee2MQTT:info 2022-06-29 20:12:22: Starting Zigbee2MQTT version 1.25.2 (commit #unknown)
Zigbee2MQTT:info 2022-06-29 20:12:22: Starting zigbee-herdsman (0.14.34)
CREATED DECONZ ADAPTER
Zigbee2MQTT:error 2022-06-29 20:12:33: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-06-29 20:12:33: Failed to start zigbee
Zigbee2MQTT:error 2022-06-29 20:12:33: Check Zigbee2MQTT fails to start | Zigbee2MQTT for possible solutions
Zigbee2MQTT:error 2022-06-29 20:12:33: Exiting…
Zigbee2MQTT:error 2022-06-29 20:12:33: undefined
[20:12:34] INFO: Handing over control to Zigbee2mqtt Core …
[email protected] start
node index.js
Zigbee2MQTT:info 2022-06-29 20:12:36: Logging to console and directory: ‘/config/zigbee2mqtt/log/2022-06-29.20-12-36’ filename: log.txt
Zigbee2MQTT:info 2022-06-29 20:12:36: Starting Zigbee2MQTT version 1.25.2 (commit #unknown)
Zigbee2MQTT:info 2022-06-29 20:12:36: Starting zigbee-herdsman (0.14.34)
CREATED DECONZ ADAPTER
Zigbee2MQTT:error 2022-06-29 20:12:46: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-06-29 20:12:46: Failed to start zigbee
Zigbee2MQTT:error 2022-06-29 20:12:46: Check Zigbee2MQTT fails to start | Zigbee2MQTT for possible solutions
Zigbee2MQTT:error 2022-06-29 20:12:46: Exiting…
Zigbee2MQTT:error 2022-06-29 20:12:46: undefined
[20:12:47] INFO: Handing over control to Zigbee2mqtt Core …
[email protected] start
node index.js
Zigbee2MQTT:info 2022-06-29 20:12:50: Logging to console and directory: ‘/config/zigbee2mqtt/log/2022-06-29.20-12-50’ filename: log.txt
Zigbee2MQTT:info 2022-06-29 20:12:50: Starting Zigbee2MQTT version 1.25.2 (commit #unknown)
Zigbee2MQTT:info 2022-06-29 20:12:50: Starting zigbee-herdsman (0.14.34)
CREATED DECONZ ADAPTER
and TubesZB log:
[D][serial_server:068]: Client 192.168.0.30 disconnected
[D][binary_sensor:036]: ‘Serial Connected’: Sending state OFF
[D][serial_server:103]: New client connected from 192.168.0.30
[D][binary_sensor:036]: ‘Serial Connected’: Sending state ON
[D][serial_server:068]: Client 192.168.0.30 disconnected
[D][binary_sensor:036]: ‘Serial Connected’: Sending state OFF
[D][serial_server:103]: New client connected from 192.168.0.30
[D][binary_sensor:036]: ‘Serial Connected’: Sending state ON
[D][serial_server:068]: Client 192.168.0.30 disconnected
[D][binary_sensor:036]: ‘Serial Connected’: Sending state OFF
[D][serial_server:103]: New client connected from 192.168.0.30
[D][binary_sensor:036]: ‘Serial Connected’: Sending state ON
[D][serial_server:068]: Client 192.168.0.30 disconnected
[D][binary_sensor:036]: ‘Serial Connected’: Sending state OFF
[D][serial_server:103]: New client connected from 192.168.0.30
[D][binary_sensor:036]: ‘Serial Connected’: Sending state ON
[D][serial_server:068]: Client 192.168.0.30 disconnected
[D][binary_sensor:036]: ‘Serial Connected’: Sending state OFF
Hi, can you up the log level in z2m to see if it shows anymore than just can’t start?
Hi, I may have the same issue as @bryan1983 my log looked basically the same at-least with debug off.
This is using HAOS and the Zigbee2MQTT as per hassio-zigbee2mqtt#installation guide
Below is my log with debug on
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/socat.sh
[01:39:38] INFO: Socat not enabled, marking service as down
cont-init: info: /etc/cont-init.d/socat.sh exited 0
cont-init: info: running /etc/cont-init.d/zigbee2mqtt.sh
cont-init: info: /etc/cont-init.d/zigbee2mqtt.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun socat (no readiness notification)
services-up: info: copying legacy longrun zigbee2mqtt (no readiness notification)
[01:39:38] INFO: Zigbee Herdsman debug logging enabled
[01:39:38] INFO: Handing over control to Zigbee2mqtt Core ...
> [email protected] start
> node index.js
Zigbee2MQTT:debug 2022-07-01 01:39:40: Can't load state from file /config/zigbee2mqtt/state.json (doesn't exist)
Zigbee2MQTT:info 2022-07-01 01:39:40: Logging to console and directory: '/config/zigbee2mqtt/log/2022-07-01.01-39-40' filename: log.txt
Zigbee2MQTT:debug 2022-07-01 01:39:40: Removing old log directory '/config/zigbee2mqtt/log/2022-07-01.01-39-10'
Zigbee2MQTT:info 2022-07-01 01:39:40: Starting Zigbee2MQTT version 1.25.2 (commit #unknown)
Zigbee2MQTT:info 2022-07-01 01:39:40: Starting zigbee-herdsman (0.14.34)
Zigbee2MQTT:debug 2022-07-01 01:39:40: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/config/zigbee2mqtt/coordinator_backup.json","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","databasePath":"/config/zigbee2mqtt/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{}}'
2022-06-30T13:39:40.875Z zigbee-herdsman:adapter No path provided, auto detecting path
Zigbee2MQTT:error 2022-07-01 01:39:40: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-07-01 01:39:40: Failed to start zigbee
Zigbee2MQTT:error 2022-07-01 01:39:40: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2022-07-01 01:39:40: Exiting...
Zigbee2MQTT:error 2022-07-01 01:39:40: Error: spawn udevadm ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:478:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
[01:39:40] INFO: Zigbee Herdsman debug logging enabled
[01:39:41] INFO: Handing over control to Zigbee2mqtt Core ...
Configuration:
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: {}
serial:
serial:
port: tcp://tubeszb-cc2652-poe-2022.local:6638
zigbee_herdsman_debug: true
try using the ip address not the mdns host name with the z2m docker. for the device. this may be the issue.
Sorry I should have mentioned I had tired this too but same result unfortunately, I have tried again and also with the development branch “Zigbee2MQTT Edge” but the error looks largely the same although I notice has a little bit more data
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/socat.sh
[07:54:37] INFO: Socat not enabled, marking service as down
cont-init: info: /etc/cont-init.d/socat.sh exited 0
cont-init: info: running /etc/cont-init.d/zigbee2mqtt.sh
cont-init: info: /etc/cont-init.d/zigbee2mqtt.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun socat (no readiness notification)
services-up: info: copying legacy longrun zigbee2mqtt (no readiness notification)
[07:54:37] INFO: Zigbee Herdsman debug logging enabled
[07:54:37] INFO: Handing over control to Zigbee2MQTT Core ...
> [email protected] start
> node index.js
Zigbee2MQTT:debug 2022-07-01 07:54:40: Can't load state from file /config/zigbee2mqtt/state.json (doesn't exist)
Zigbee2MQTT:info 2022-07-01 07:54:40: Logging to console and directory: '/config/zigbee2mqtt/log/2022-07-01.07-54-40' filename: log.txt
Zigbee2MQTT:debug 2022-07-01 07:54:40: Removing old log directory '/config/zigbee2mqtt/log/2022-07-01.07-54-03'
Zigbee2MQTT:info 2022-07-01 07:54:40: Starting Zigbee2MQTT version 1.25.2-dev (commit #3d406c3)
Zigbee2MQTT:info 2022-07-01 07:54:40: Starting zigbee-herdsman (0.14.40)
Zigbee2MQTT:debug 2022-07-01 07:54:40: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/config/zigbee2mqtt/coordinator_backup.json","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","databasePath":"/config/zigbee2mqtt/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{}}'
2022-06-30T19:54:40.586Z zigbee-herdsman:adapter No path provided, auto detecting path
Zigbee2MQTT:error 2022-07-01 07:54:40: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-07-01 07:54:40: Failed to start zigbee
Zigbee2MQTT:error 2022-07-01 07:54:40: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2022-07-01 07:54:40: Exiting...
Zigbee2MQTT:error 2022-07-01 07:54:40: Error: spawn udevadm ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:478:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
Just recently received your coordinator, but I have had a change of plans. is there a way to convert it to a router?
Yes, you can flash the router firmware either from the z-stack repo or the same one I use on the routers I sell available here https://github.com/tube0013/tube_gateways/tree/main/tube_cc_router/firmware Which is slightly modified from the zstack repo one.
If you have the non PoE Ethernet board you can pull the Ethernet module off and move the jumpers to zigbee to usb and flash that way (hold bsl button while plugging in usb). And no reason to keep the Ethernet module on if doing that.
PoE you’ll need to flash over tcp (can be done with usb to serial adaptor as well if you have one)
1 Like