#Help using Zigbee2MQTT using TubesZB PoE coordinator?

1 messages · Page 1 of 1 (latest)

worldly gyro
#

Hey Folks! I am trying to setup a TubesZB PoE coordinator with Zigbee2MQTT. The tutorial I am following is based on a USB connected zigbee stick where I am instead using the TubesZB which is PoE powered and not directly connected to the HA unit.

The instructions on TubeZB site just instruct that you add:

  port: 'tcp://IPADDRESS:6638'```
to the serial portion in the Zigbee2MQTT  configuration.yaml file. Being as how most of the troubleshooting is focused on folks using USB zigbee sticks, I was hoping someone here might be able to give me a hint on how to get this working..?

The log file and the failure is detailed here:
```Zigbee2MQTT:info  2022-09-28 17:56:01: Starting zigbee-herdsman (0.14.53)
Zigbee2MQTT:info  2022-09-28 17:56:04: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2022-09-28 17:56:04: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20220219,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2022-09-28 17:56:04: Currently 0 devices are joined:
Zigbee2MQTT:info  2022-09-28 17:56:04: Zigbee: disabling joining new devices.
Zigbee2MQTT:info  2022-09-28 17:56:04: Connecting to MQTT server at mqtt://core-mosquito:1883
Zigbee2MQTT:error 2022-09-28 17:56:08: MQTT failed to connect: getaddrinfo ENOTFOUND core-mosquito
Zigbee2MQTT:error 2022-09-28 17:56:08: Exiting...
Zigbee2MQTT:info  2022-09-28 17:56:08: Stopping zigbee-herdsman...
Zigbee2MQTT:info  2022-09-28 17:56:33: Stopped zigbee-herdsman
[17:56:35] INFO: Handing over control to Zigbee2MQTT Core ...
Zigbee2MQTT:info  2022-09-28 17:56:40: Logging to console and directory: '/config/zigbee2mqtt/log/2022-09-28.17-56-40' filename: log.txt
Zigbee2MQTT:info  2022-09-28 17:56:40: Starting Zigbee2MQTT version 1.27.2 (commit #unknown)```
frank pasture
#

This is an MQTT error

#

MQTT failed to connect

#

Do you have the mqtt addon installed and configured?

worldly gyro
#

I have Mosquitto Broker running... is that the addon I need ?

#

hey wait a sec.. are you the "tubes" in TubesZB?! If so COOL!! 😁😂🤣

frank pasture
#

Ha yes I made the device you are using lol

worldly gyro
#

sweet! I really dig it.. very compact and a nifty 3d printed case and everything. 👍🙂

frank pasture
worldly gyro
#

I bought it like.. a week ago..

frank pasture
#

Here’s a snap of a z2m addon. Config

#

Thanks!

#

Mosquito

worldly gyro
#

ok, the tutorial I was following had me create a HA user and add user and password fileds under MQTT is that something I didn't need to do?

frank pasture
#

Is all the defaults

#

The addons can talk to each other I’m not sure all the mechanics

worldly gyro
#

I had this:

#

huh.. so cant paste images here.. neat. 😛

#

mqtt
server: mqtt://core-mosquito:1883
user: mqtt-user
password: <redacted>

frank pasture
#

Someone gave me the power lol

worldly gyro
#

serial
serial:
port: tcp://192.168.77.234:6638

frank pasture
#

Id try with out the mqtt port

worldly gyro
#

in the "serial" area I put in the word "serial" with the colon on the end.. is that redundant..?

frank pasture
#

And if you have the users defined in the mqtt addon I think you can leave that

#

No serial, it can be easier to look at the pure yaml view

worldly gyro
#

The mosquitto log is repeating these errors:

2022-09-28 17:43:09: New client connected from 172.30.32.1:45513 as 1VYo1jagXpGS9D2hIIqk9i (p2, c1, k60, u'homeassistant').
2022-09-28 17:44:45: New connection from 172.30.32.2:50404 on port 1883.
2022-09-28 17:44:45: Client <unknown> closed its connection.
2022-09-28 17:46:45: New connection from 172.30.32.2:56216 on port 1883.
2022-09-28 17:46:45: Client <unknown> closed its connection.
2022-09-28 17:48:45: New connection from 172.30.32.2:60496 on port 1883.
2022-09-28 17:48:45: Client <unknown> closed its connection.
2022-09-28 17:50:45: New connection from 172.30.32.2:48684 on port 1883.
2022-09-28 17:50:45: Client <unknown> closed its connection.
2022-09-28 17:52:30: Saving in-memory database to /data//mosquitto.db.
2022-09-28 17:52:45: New connection from 172.30.32.2:50628 on port 1883.
2022-09-28 17:52:45: Client <unknown> closed its connection.
2022-09-28 17:54:45: New connection from 172.30.32.2:46018 on port 1883.
2022-09-28 17:54:45: Client <unknown> closed its connection.
2022-09-28 17:56:45: New connection from 172.30.32.2:58618 on port 1883.
2022-09-28 17:56:45: Client <unknown> closed its connection.
2022-09-28 17:58:45: New connection from 172.30.32.2:42372 on port 1883.```
frank pasture
#

You might want to delete the mqtt addon and then reinstall. Clear out the user pass in the z2m install

#

I’m not an expert on this part of things, I just know what worked I’m my test system. I run zha in production.

worldly gyro
#

I had zha working then decided to try to switch over to zigbee2mqtt being as how the various demos and tutorials seemed to lean that way and I wanted to see how it worked.. maybe I made a mistake 🤔

frank pasture
#

It’s all good. I’m not here to tell you to use one over the other

#

Just was trying to let you know my overall ability with z2m setup 😂

worldly gyro
#

I'm wondering why the mosquito is showing connects from a subnet that isnt in my network.. the 172.30.32.2 address 🤔

#

I am 192.168.x.x

glossy raft
#

Post your yaml minus your mqtt password

worldly gyro
#

heh.. I just ripped it out to start over 😛

glossy raft
#

Look in my server

#

Copy and paste mine and change the last part with serial

worldly gyro
#

heh.. cool it still kept the config files .. this is the yaml:

mqtt:
  server: mqtt://core-mosquito:1883
  user: mqtt-user
  password: redacted
serial:
  port: tcp://192.168.77.234:6638
frontend:
  port: 8099
advanced:
  homeassistant_legacy_entity_attributes: false
  legacy_api: false
  legacy_availability_payload: false
device_options:
  legacy: false
glossy raft
#

Looks wrong lol

worldly gyro
#

ok- just reinstalled mosquito... now guna install zigbee2mqtt.. then try your config file

#

the file I posted above is the "/config/zigbee2mqtt/configuration.yaml" file. is that the one I should be editing?

glossy raft
#

Are you not doing it in the ui?

worldly gyro
#

I was.. but I thought u said it was easier.. or like.. siompler to edit the yaml..? 🤔

#

I can use the configuration tab in the ui

glossy raft
#

I posted an image in my server of how to get to the yaml in the ui

worldly gyro
#

hmm.. I am using chrome on a PC not a phone so it looks different..

#

AH! found it (triple dot menu top right)

glossy raft
#

I even circled that in the image I shared

#

Lol

worldly gyro
#

same fail 😛

#
[18:40:39] INFO: Handing over control to Zigbee2MQTT Core ...
Zigbee2MQTT:info  2022-09-28 18:40:44: Logging to console and directory: '/config/zigbee2mqtt/log/2022-09-28.18-40-44' filename: log.txt
Zigbee2MQTT:info  2022-09-28 18:40:44: Starting Zigbee2MQTT version 1.27.2 (commit #unknown)
Zigbee2MQTT:info  2022-09-28 18:40:44: Starting zigbee-herdsman (0.14.53)
Zigbee2MQTT:info  2022-09-28 18:40:46: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2022-09-28 18:40:46: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20220219,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2022-09-28 18:40:46: Currently 0 devices are joined:
Zigbee2MQTT:info  2022-09-28 18:40:46: Zigbee: disabling joining new devices.
Zigbee2MQTT:info  2022-09-28 18:40:47: Connecting to MQTT server at mqtt://core-mosquito
Zigbee2MQTT:error 2022-09-28 18:40:50: MQTT failed to connect: getaddrinfo ENOTFOUND core-mosquito
Zigbee2MQTT:error 2022-09-28 18:40:50: Exiting...
Zigbee2MQTT:info  2022-09-28 18:40:50: Stopping zigbee-herdsman...```
#

removing the :1883 on the URL is the way that some threads I am reading used to solve the issue.. but it didn't for me... 😦

#

ok.. I add3ed back the user/pw and it goes.. further..? I am now getting:

s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service z2m: stopping
s6-rc: info: service socat: stopping
s6-rc: info: service z2m successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service socat successfully stopped
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Zigbee2MQTT:error 2022-09-28 18:44:06: Failed to call 'Frontend' 'stop' (TypeError: Cannot read properties of null (reading 'clients')
    at Frontend.stop (/app/lib/extension/frontend.ts:59:39)
    at Controller.callExtensions (/app/lib/controller.ts:315:40)
    at Controller.stop (/app/lib/controller.ts:192:9)
    at stop (/app/index.js:113:5)
    at process.handleQuit (/app/index.js:119:9))
Zigbee2MQTT:error 2022-09-28 18:44:06: Not connected to MQTT server!
Zigbee2MQTT:error 2022-09-28 18:44:06: Cannot send message: topic: 'zigbee2mqtt/bridge/state', payload: '{"state":"offline"}
Zigbee2MQTT:info  2022-09-28 18:44:06: Disconnecting from MQTT server
Zigbee2MQTT:info  2022-09-28 18:44:06: Stopping zigbee-herdsman...
Zigbee2MQTT:info  2022-09-28 18:44:13: Stopped zigbee-herdsman```
frank pasture
#

🤷🏼‍♂️ delete the z2m addon, delete the z2m config folder - reinstall and just enter the bare minimum

#

ie the MQTT server/user/pass and the port: tcp://ip:6638

#

And that’s it

worldly gyro
#

omg.. I think I found someone that made the same mistake I did! arg... here's the fix they posted:
I accidentally fixed it and found the issue… I am quite rather embarrassed. Happy to solve it though. Three hours of my life wasted… LOL. server: mqtt://core-mosquito:1883 should be mqtt://core-mosquitto:1883, that’s mosquitto with TWO T’s. OOPS.

#

I spelled mosquito instead of mosquitto as well 🤦‍ !!!

frank pasture
#

Ha I missed that too lol

worldly gyro
#

ok.. new errors.. we're making progress! 😉

#

so now, it says:

    at Object.openSync (node:fs:585:3)
    at Object.readFileSync (node:fs:453:35)
    at Object.read (/app/lib/util/yaml.ts:7:29)
    at read (/app/lib/util/settings.ts:311:20)
    at getInternalSettings (/app/lib/util/settings.ts:418:21)
    at Object.reRead (/app/lib/util/settings.ts:696:5)
    at start (/app/index.js:93:14)
[18:49:09] INFO: Handing over control to Zigbee2MQTT Core ...
Error: ENOENT: no such file or directory, open 'null/configuration.yaml'
    at Object.openSync (node:fs:585:3)
    at Object.readFileSync (node:fs:453:35)
    at Object.read (/app/lib/util/yaml.ts:7:29)
    at read (/app/lib/util/settings.ts:311:20)
    at getInternalSettings (/app/lib/util/settings.ts:418:21)
    at Object.reRead (/app/lib/util/settings.ts:696:5)
    at start (/app/index.js:93:14)
[18:49:12] INFO: Handing over control to Zigbee2MQTT Core ...```
#

over and over

frank pasture
#

So now it can’t find its config

#

Id recommend what I said above delete it all and retry

worldly gyro
#

mkay... here we go-

#

Uninstalling zigbee2MQTT

frank pasture
#

The only difference to what I have in the screenshots is the addition of the user/pass for mqtt

#

Delete /config/zigbee2mqtt as well to start all fresh

worldly gyro
#

yup.. doing now...

#

ok, uninstalling mosquitTo broker now..

glossy raft
#

I think you have to restart the addon after editing the config and on mine it bugged out and didn’t ask me one time

worldly gyro
#

I figure I will remove everything then restart HA for good measure, then do the setup very basic.. like u said..

#

when I uninstalled mosquitto broker, I don't see a folder called mosquitto in the config folder.. is it the "zigbee.db" file the only thing it had..?

frank pasture
#

Zigbee.db is from zha

worldly gyro
#

I killed it anyway. it had to die so that others could live.. or something.. ? lol

#

ok.. progress. it is now failing with:

Zigbee2MQTT:error 2022-09-28 19:05:49: MQTT failed to connect: Connection refused: Not authorized
Zigbee2MQTT:error 2022-09-28 19:05:49: Exiting...
Zigbee2MQTT:info  2022-09-28 19:05:49: Stopping zigbee-herdsman...```
#

so I think I need t oadd my user/pass stuff back.. lemme try that

glossy raft
#

Why wouldn’t you have included your Mqtt info?!

worldly gyro
#

so far.. so... goood..? 🙂

[19:07:59] INFO: Handing over control to Zigbee2MQTT Core ...
Zigbee2MQTT:info  2022-09-28 19:08:05: Logging to console and directory: '/config/zigbee2mqtt/log/2022-09-28.19-08-05' filename: log.txt
Zigbee2MQTT:info  2022-09-28 19:08:05: Starting Zigbee2MQTT version 1.27.2 (commit #unknown)
Zigbee2MQTT:info  2022-09-28 19:08:05: Starting zigbee-herdsman (0.14.53)
Zigbee2MQTT:info  2022-09-28 19:08:07: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2022-09-28 19:08:07: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20220219,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2022-09-28 19:08:07: Currently 0 devices are joined:
Zigbee2MQTT:info  2022-09-28 19:08:07: Zigbee: disabling joining new devices.
Zigbee2MQTT:info  2022-09-28 19:08:07: Connecting to MQTT server at mqtt://core-mosquitto
Zigbee2MQTT:info  2022-09-28 19:08:08: Connected to MQTT server
Zigbee2MQTT:info  2022-09-28 19:08:08: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
Zigbee2MQTT:info  2022-09-28 19:08:08: Started frontend on port 0.0.0.0:8099
Zigbee2MQTT:info  2022-09-28 19:08:08: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"unknown","coordinator":{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20220219,"transportrev":2},"type":"zStack3x0"},"log_level":"info","network":{"channel":11,"extendedPanID":"0x00124b0025903865","panID":6754},"permit_join":false,"version":"1.27.2"}'
Zigbee2MQTT:info  2022-09-28 19:08:08: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'```
frank pasture
#

That looks like it started okay

worldly gyro
#

woohoo! the sidebar zigbee2mqtt link now works!! YAY! 😁😂🤣

frank pasture
#

Have fun