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

tube0013 · October 11, 2022, 1:04am

can we take this to DM? you will need to identify the USB.

use /dev/serial/by-id and you should see something with 971207DO in the name.

petrepa · October 15, 2022, 10:18am

Sorry for the late response! Busy days!

I haven’t been able to test it yet, but will try debug and test more next week. My spare Zigbee dongle has been working ok in the meantime, so I guess that is also why I haven’t been as quick to fix the big boss PoE coordinator. Will get back to you with the results.

bouwew · October 15, 2022, 3:53pm

@tube0013 Thanks for providing the beta firmware and update files!
To make it work for my tubeszb-cc2652-eth_usb coordinator I only needed to replace name: tubezb-cc2652p2-ethusb-2022 by name: tube-zb-gw-cc2652p2-v2 in the yaml file.

ledhed · October 17, 2022, 10:23pm

@tube0013
First off I’d like to say thanks. I’ve had your CC2652P2 ZB PoE Coordinator V2 for almost a year now and its probably the most stable Smart Home gadget I have, absolutely rock solid.

My question is, since this device has an Olimex ESP32-POE inside, can this device serve double duty as both a Zigbee Coordinator and a Bluetooth Proxy?

Thanks!

nickrout · October 17, 2022, 11:23pm

There has been quite a bit of traffic about bluetooth proxy being a pretty heavy usage hit for an esp32. Tales of stuff randomly going offline. I would be careful of interfering with my zigbee usage.

tube0013 · October 17, 2022, 11:39pm

it can be enabled if you use the newest yaml I have posted which allows the use of the most recent esphome releases (finally). I won’t support it as I echo what @nickrout says but if you want to explore it on your own no one is going to stop you.

ledhed · October 17, 2022, 11:44pm

I only have 3 Zigbee devices currently, so there isn’t much traffic at the moment. If the BT Proxy works out I’ll install some dedicated hardware.

Thanks!

phidauex · October 18, 2022, 6:50pm

Hi, I recently got one of the new cc2652-poe-2022’s, and while the initial setup worked well, I’m struggling with some devices.

Initially I had a devil of a time getting Aqara devices to pair. I chalked it up to Aqara being somewhat janky in general, but now my Sengled E1C-NB7 plugs aren’t working at all (pair, but fail to interview, and are left in a partially connected, but not functional state).

This issue has details including a herdsman log: Sengled E1C-NB7 smart plug fails to interview · Issue #14524 · Koenkk/zigbee2mqtt · GitHub

So far I’ve updated the CC2652 to the most recent zstack (20220928), and I updated the ESP to the latest version linked in your documentation. Both updates seemed to go fine, and the CC2652 made and restored backups fine.

I’m on channel 11, which an energy scan shows to be a low energy channel in my house, and all my devices are close (the plugs in question are less than 15’ from the device).

Any idea from the logs on what I should look at next? Does it seem to be a coordinator issue, a Z2M issue, or a device issue?

Thanks - Sam

tube0013 · October 18, 2022, 8:14pm

hmm. those plugs are generally pretty well supported (I have like 8 of them) You mention the energy scan looks okay at the coordinator, but what about where the plug is? I’ve seen something as silly as a logitech wireless keyboard usb module take out a whole zigbee network due to it’s proximity to the coordinator. it also was intermittent as the it channel hopped, so the energy scan didn’t show anything as it was scanning when it was on different channels.

ogiewon · October 18, 2022, 8:23pm

It should be noted that not all Zigbee devices are compatible with all Zigbee channels. If possible, I always try to stick with Zigbee channels 15, 20, and 25. These are least likely to conflict with 2.4GHz WiFi, assuming you’ve chosen WiFi channels 1, 6, and/or 11 with a 20MHz channel width to avoid interference with the aforementioned Zigbee channels.

tube0013 · October 18, 2022, 8:31pm

I will never understand why Z2M’s default is 11

phidauex · October 18, 2022, 11:32pm

Hmm, thanks, I’ll run the energy scan again and try to move to a more commonly used channel. I believe 15 was fairly low energy as well, so it could be a good candidate. I also realized I should probably change my Z2M network key, so picking a better channel and rebuilding the network is probably a reasonable next step, especially since I’m now hearing several reports of these plugs working fine for people.

phidauex · October 19, 2022, 3:23am

Well, moving to channel 25 seems to have helped. One of the units was still very reluctant to join, and now one of my Sengled bulbs doesn’t want to rejoin either, but I do have basic functionality from the Sengled plugs now.

They still do not report power (just getting null) but I’ll leave the network for a while to settle and hopefully they start to report.

Thanks for the help!

EDIT: For future searchers, this was indeed the problem. Once on channel 25 all my devices ended up working. It took a little while in operation for the Sengled bulbs to start sending power data, and for the last bulb to pair up, but once the network “settled” for a day then everything was working as expected.

phidauex · November 6, 2022, 10:02pm

Is there any way to dim/disable the LEDs on the POE 2022 devices? Quite bright at night. I also assume the vents are needed for heat dissipation, and shouldn’t be blocked?

nickrout · November 7, 2022, 5:21am

If you block them, you may need to unblock them to let the magic smoke completely out.

tube0013 · November 7, 2022, 8:45pm

they are part of the Olimex hardware and are not controllable. you can cover with electrical tape or a dark nail polish.

They get hot, and the slots are required for venting the heat.

nickrout · November 7, 2022, 9:27pm

Or something like this perhaps https://www.amazon.com/LIGHTDIMS-LD002-LightDims-Black-Edition/dp/B009WSN8PK (depends where the leds are, I don’t have this board.)

phidauex · November 7, 2022, 10:41pm

Sounds good! I’ll keep them well ventilated, and just put a little dark paint pen on the LEDs to significantly dim them.

elminster13 · November 23, 2022, 9:58pm

I am having some serious trouble getting Z2M running with the POE device. I have historically had it working on a QNAP server with a USB Conbee II and hoping to move over to the network device to allow me to move the device away from my server. I have brought up a new VM on a new server in Proxmox and installed HAOS on there and added the MQTT and Z2M addons.

When I start Z2M I get an error message 502: Bad Gateway and in my logs I get:

[12:11:33] INFO: Preparing to start... [12:11:33] INFO: Socat not enabled [12:11:33] INFO: Starting Zigbee2MQTT... Zigbee2MQTT:info 2022-11-23 12:11:35: Logging to console and directory: '/config/zigbee2mqtt/log/2022-11-23.12-11-35' filename: log.txt Zigbee2MQTT:info 2022-11-23 12:11:35: Starting Zigbee2MQTT version 1.28.2 (commit #unknown) Zigbee2MQTT:info 2022-11-23 12:11:35: Starting zigbee-herdsman (0.14.68) Zigbee2MQTT:error 2022-11-23 12:12:44: Error while starting zigbee-herdsman Zigbee2MQTT:error 2022-11-23 12:12:44: Failed to start zigbee Zigbee2MQTT:error 2022-11-23 12:12:44: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions Zigbee2MQTT:error 2022-11-23 12:12:44: Exiting... Zigbee2MQTT:error 2022-11-23 12:12:44: Error: network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby at ZnpAdapterManager.beginCommissioning (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:347:23) at ZnpAdapterManager.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:92:17) at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29) at Zigbee.start (/app/lib/zigbee.ts:58:27) at Controller.start (/app/lib/controller.ts:101:27) at start (/app/index.js:109:5)

Now I have done a fair bit of reading and initially I thought that maybe my old setup was interfering with the new device so I added the following to my Z2M configuration:

mqtt: server: mqtt://core-mosquitto:1883 user: mqtt password: password serial: port: tcp://ipofPOE:6638 advanced: log_level: debug pan_id: GENERATE ext_pan_id: - 105 - 114 - 113 - 53 - 46 - 105 - 111 - 32 channel: 24 network_key: GENERATE

this didnt work so I thought well ill shutdown the QNAP server to prevent power to the conbee, uninstall Z2M in HAOS, reboot the TubesZB and then try again but alas tna.

I had a go at changing my pan_id to ‘pan_id: 6755’ last night but continue to get the same error.

I can see in the device log that Z2M is connecting to the TubeZB so the connection details are good to that at least.

I have also connected to my MQTT broker with MQTT-Explorer and that is working although I cant determine whether Z2M is connecting to it as I can’t see anything in the logs.

I should add that I have flashed the TubesZB stick with the firmware recommended in the Z2M instructions.

Any help or ideas would be great!

tube0013 · November 23, 2022, 10:03pm

undo the antenna and try, or unplug nearby mains powered routers.