Tube's ZB Coordinators and Routers (was Zigbee router on steroids?)

bryan1983 · June 29, 2022, 10:14am

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

tube0013 · June 29, 2022, 11:22am

Hi, can you up the log level in z2m to see if it shows anymore than just can’t start?

Ricardo-0101 · June 30, 2022, 1:51pm

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

tube0013 · June 30, 2022, 2:02pm

try using the ip address not the mdns host name with the z2m docker. for the device. this may be the issue.

Ricardo-0101 · June 30, 2022, 7:50pm

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)

tube0013 · June 30, 2022, 11:47pm

Check your config file, you have serial twice:

iculookn · July 1, 2022, 3:45am

Just recently received your coordinator, but I have had a change of plans. is there a way to convert it to a router?

tube0013 · July 1, 2022, 12:33pm

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)

bryan1983 · July 2, 2022, 12:43pm

Hi Tube0013, logs don’t show anymore detail. I uninstalled Zigbee2MQTT and changed to ZHA everything seems to work, can connect and control all devices without any issue.

tube0013 · July 2, 2022, 4:14pm

Okay, I suspect this was something with the config file for Z2M. Glad its working okay with ZHA.

Ricardo-0101 · July 7, 2022, 1:42am

That was it, I added below to the configuration via the UI

and hadn’t noticed/realised it resulted in the YAML having below

ian.k · August 2, 2022, 2:36pm

@tube0013 - Love what you’re doing here.

Quick question though - Does your POE coordinator ship with your current firmware or should I firmware update before starting to pair my devices?

Thanks in advance!

tube0013 · August 2, 2022, 2:50pm

It ships with the current Z-Stack release. (not the development branch). - I typically will start shipping a new release after a week or so from it’s release so any bugs not caught during the dev/beta can be addressed.

ian.k · August 2, 2022, 3:02pm

Thank you for that incredibly quick response . My order is placed! Very interested to see how your module stacks up against my older ZigBee module.

liminal · August 3, 2022, 5:47am

Hey all,

Im having an issue with my coordinator. The USB has come loose-ish. I have to bend the cable down to keep it powered on. and sometimes it turns off.

Is there a way to fix this, relatively easily? Or an alternate way to power the device. Other than this issue (which came from the device falling off a shelf) its been great

jodewee · August 3, 2022, 5:55am

Hi,

i received my tube’s zb gateway,
but the radio continually send state on & off to HA;

Firmware: 2021.9.0 (Sep 17 2021, 19:58:30)
2022-08-03_07-48-04

Any suggestions on this one?

tube0013 · August 3, 2022, 11:32am

If you have a soldering iron you may be able to add a bit of solder to hold stabilize the port.

If not it can be powered from a 3.3v source like a usb> serial device over some pins on the pcb.

Let me know the model you have and DM a pic of the port and I’ll see if I have any further advice I can give.

tube0013 · August 3, 2022, 11:34am

This usually happens when 2 things try to access it at once.

Are you using zHA or Zigbee2mqtt? Be sure only one is trying to access the device.

And logging (debug) from whichever one you are using will help pinpoint the issue.

liminal · August 3, 2022, 11:16pm

Thanks mate.

Pictures are not great LOL, its kinda stable right now. So didnt want to mess with it too much.

Could you do me a favor and mark the best places that its ok to put a little solder?

Thanks mate,

Also I understand that its probably hard to say without holding it in your hard, so best guess is fine

tube0013 · August 3, 2022, 11:33pm

Well here’s sort of the outline of things:

The GND and 5V pins are all that matter from the usb connection on this model. The blue arrows point to some “posts” that go through the pcb and can have some solder added to them to help stabilize the port (from the bottom).

If it becomes more of an issue and you don’t have the ability to do it, a local cell phone or computer repair place could probably do it for minimal cost.