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

Configuration Zigbee
1030

unfortunately that leads to the exact same behaviour.

1031

last try, please try flashing over serial/usb the esp32 with the binary found on github:

https://github.com/tube0013/tube_gateways/tree/main/models/current/tubeszb-cc2652-eth_usb/firmware/esphome

https://github.com/tube0013/tube_gateways/tree/main/models/current/tubeszb-cc2652-eth_usb#esp32-flashing-mode---esp32-serial-connection-via-usb

1032

when i try to flash via usb there is an error message:

Unexpected error: The firmware binary is invalid (magic byte=0A, should be E9)
Did i took the wrong firmware?

1033

Likely didn’t get the actually binary from Github, you have to make sure you click on the raw version to download the binary.

https://github.com/tube0013/tube_gateways/raw/main/models/current/tubeszb-cc2652-eth_usb/firmware/esphome/tubezb-cc2652p2-ethusb-2022%20(Rounded%20enclosure).bin

1034

thx again.
that worked.
Flash of the esp32 was successfull, but the disconnect still exists

any other option to try?

1035

Can you reach out to me at the store email - store @ tubeszb.com - I fear the radio may have died which I definitely have not seen occur in the past. But would like to work with you to get a working device.

1036

great news. it works again.
Not shure, why exactly.
i´ve connected the coordinator to another switch with another powersupply.
→ nothing changed
i switched the ip address of the coordinator and tried to reconfigure ZHA in HA.
→ stoped with an error message but ZHA tried to connect with the new IP
i switched the ip back to the old one and reconfigured ZHA again.
→ reconfigure process successful and connect to the cooardinator got back online.
restart ZHA
→ connection to the coordinater works like a charme.

But the error in Tubes ZB flasher add-in is still there:

Connecting to target...
ERROR: Timeout waiting for ACK/NACK after 'Synch (0x55 0x55)'
[19:47:46] INFO: cc2652-flasher-up script exited with code 1
s6-rc: warning: unable to start service cc2652-flasher: command exited 1
s6-rc: info: service banner: stopping
1 Like
1037

I learned the hard way that some network switches will cause a failure with some devices. I have no idea why. The Philips Hue hub specifically states not to use it with a switch and I’m guessing for this reason.

I have 3 network switches and found 1 will cause some devices to drop from the network randomly. The 1 I am using with my Tubes ZB coordinator works, but if I have a power outage it won’t connect after power is restored. I then have to unplug both power and network cables and plug them back in.

1038

Hi @tube0013, I have your PoE Coordinator (tube-zb-gw-cc2652p2-poe) purchased a couple years ago, I think running 20210708 firmware? Are you aware of any issues with pairing Ikea Tradfri Repeater E1746? I’ve never had any issues with pairing devices in the past but got a couple of these and not seeing any pairing attempt in Zigbee2MQTT logs at all. Many thanks

1039

I’m not aware of any issues. generally when you don’t see pairing attempts the network isn’t see them, as the device is responsible for broadcasting those. FWIW I ended up removing all the Ikea repeaters on my network a few months ago.

1040

I got them on a whim as want to have a couple of zigbee devices in my greenhouse, but it would seem the toughened glass completely drops the signal. So my thought was to put a repeater in my shed to see if it is strong enough to get thru the glass, as the signal from my house is about 8m further away. Do you know how the signal strength of your repeaters compares to the Ikea repeaters?

1041

it should be better, I’ve also been impressed with the third reality plugs as repeaters.

I put some soil sensors out in my garden. it’s about 8-10 meters from back of house. the sensors are joined to mesh through an ikea hue bulb in my attic though, so you may want to try staging a routing device high up to see if it gets better range. Inside the back wall of the house are a bunch of plugs and bulbs, and it still chose the attic bulb as the best router.

1042

I’m sure its the toughened glass that’s killing it. Will try in the roof of my shed, as its less than 2 metres away from the greenhouse - can’t get much closer! Not sure third reality is a thing in the UK. If I can prove some sort of signal in to the greenhouse I’ll order one of your repeaters, but need to confirm a reliable signal first.

1043

I have a P7 POE that stops responding at random intervals (most recent time was over a week, can be less than a day). I have re-flashed the P7 firmware and the esphome firmware to no change. Anything else I can check?

1044

try using a static IP.

I just set up a Github Repo to build fw for specific static IPs. https://github.com/tube0013/TubesZB-ESPHome-Builder/issues

image
image1574×262 15.7 KB

create a new issue, fill out the form with the requested information, and copy the model name from the list of available ones in the description of the field. For example:

image
image1646×1502 236 KB

after submitting which in about 5 minutes you should see an update to the issue with a download link for Firmware:

image
image1904×718 58.7 KB

The downloaded zip file will contain 2 binaries:

image

Use the firmware.factory.bin to flash via web.esphome.io
or use the firmware.ota.bin, if you have a coordinator with the OTA fw update available in the web front end (note any firmware base on the esp32-idf framework will not - this includes the p7 and mgm24)

1045

I’m having some issues getting a tubeszb-efr32-mgm210-poe-2023 working with HA and was wondering if anyone could point me in the right direction. I can’t get HA to talk to the unit.

Setup details:
HA Server IP: 10.30.70.10
HA Core: 2024.7.4
HA Supervisor: 2024.08.0
HA OS: 12.4
tubeszb-efr32-mgm210-poe-2023 10.30.70.20

Here is what I have tried so far:

  • Updated ESPHome via web UI successfully to tubeszb-efr32-mgm210-poe-2023_Legacy.bin

I have not attempted to update the bootloader as I am unsure which gbl to use given the ones I think could be are all labelled 2022.

ZHA:

  • Automatically detected by HA as tubeszb-efr32-mgm210-poe-2023
  • Clicked Configure
  • Serial device path socket://10.30.70.20:6638 Port speed 115200 Flow control software
  • Error: Failed to connect
  • Manually attempted the same via + Add Integration button resulting in the same error

Z2M:

  • Set serial config to port: tcp://10.30.70.20:6638

Log:

[2024-08-11 13:07:29] info: 	z2m: Logging to console, file (filename: log.log)
[2024-08-11 13:07:29] info: 	z2m: Starting Zigbee2MQTT version 1.39.1 (commit #unknown)
[2024-08-11 13:07:29] info: 	z2m: Starting zigbee-herdsman (0.55.3)
[2024-08-11 13:07:29] info: 	zh:zstack:znp: Opening TCP socket with 10.30.70.20:6638
[2024-08-11 13:07:29] info: 	zh:zstack:znp: Socket connected
[2024-08-11 13:07:29] info: 	zh:zstack:znp: Socket ready
[2024-08-11 13:07:29] info: 	zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2024-08-11 13:07:30] info: 	zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2024-08-11 13:07:48] error: 	z2m: Error while starting zigbee-herdsman
[2024-08-11 13:07:48] error: 	z2m: Failed to start zigbee
[2024-08-11 13:07:48] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-08-11 13:07:48] error: 	z2m: Exiting...
[2024-08-11 13:07:48] error: 	z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:119:27)
    at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:127:29)
    at Zigbee.start (/app/lib/zigbee.ts:63:27)
    at Controller.start (/app/lib/controller.ts:139:27)
    at start (/app/index.js:154:5)

  • Added adapter: ezsp to serial config

  • Error: [2024-08-11 12:32:39] warning: zh:ezsp: Deprecated driver 'ezsp' currently in use, 'ember' will become the officially supported EmberZNet driver in next release. If using Zigbee2MQTT see https://github.com/Koenkk/zigbee2mqtt/discussions/21462 [2024-08-11 12:32:49] error: zh:ezsp:uart: --> Error: Error: {"sequence":-1} after 10000ms

  • Tried adapter: ember instead

  • Error [2024-08-11 12:33:39] error: z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.

Any suggestions on what to try next would be most helpful.

I purchased the unit a while back and misplaced it before I had a chance to set it up, recently found it again and am trying to use it for a project at the school I work for.

1046

I have the tube-zb-gw-cc2652p2-poe and it would occasional need to be power cycled to get going. Not sure if it’s the HA x.8 update but it’s recently required me to power cycle a lot more than usual (3 times in the past week). In the past it would be a few months and I always assumed it might be because of UniFi updates.
@tube0013 any thoughts on the best way to troubleshoot this?

IMG_2694
IMG_26941290×2390 192 KB

1047

Can you try and re flash the NCP firmware?

I have an addon that does this: https://github.com/tube0013/tubeszb_addons/blob/3d90a7fd46ccf60393c3ee1d42ffcfde70ca83c6/tzb-silabs-flasher/DOCS.md

For the NCP firmware link, use this: https://github.com/tube0013/tube_gateways/raw/main/models/current/tubeszb-efr32-MGM210-poe/firmware/efr32_MGM210/ncp/7.4.3/tubeszb-mgm21-2022_7.4.3.gbl

1048

I’d try a ESPhome build with static IP. you can use the new repo I created and described above to generate the binaries: Tube's ZB Coordinators and Routers (was Zigbee router on steroids?) - #1044 by tube0013

I’d recomend using the factory.bin (with <web.esphome.io> ) file and flashing over the micro usb port on the Olimex board. (you have to partially remove from the enclosure to access). This will erase the full flash to start “Fresh”

1049

@tube0013
I created the “issue” to generate the firmware.
When you say “start fresh”….am I losing any config or settings?

Also…can I use the OTA update option on the coordinators webui?