This is the one based on the same chip as Skyconnect
So does this mean that it provides the same coverage? Or is it better due to antenna design?
For zigbee coverage your better off utilizing the nature of the mesh with a mix of devices that route/repeat (most mains powered devices).
Also look at interference either near the coordinator or near the devices.
The external antenna may give you boost of about 3-5 dbi, I am not sure itās super significant when taking into consideration the comments I made above about a good mesh.
For me the big difference is that you can place the coordinator where it gives best coverage. I have mine in the middle of the house. And away from disturbance sources like usb. I will never go back.
Thank you very much for your comments. That makes sense. I will experiment with a repeater first since Iād like to have the coordinator in the network rack. Perhaps I also have to find a better position in the rack as well for the skyconnect.
Is it a problem to use a longer USB cable to get just the antenna out of the rack housing?
If you have the coordinator in the rack it probably explains your problems. There is ofc all kind of interference. Put it as far away as possible using a long usb cable
Thanks for the advice. I will try this one as well.
I have downloaded both addons and try to flash my "tubeszb-efr32-mgm210-poe-2022ā. But I consistently receive error:
Error: ā/root/firmware.gblā does not appear to be a valid GBL image: ValidationError(āImage is truncated: tag value is cut offā)
I have this URL configured: https://github.com/tube0013/tube_gateways/blob/2d581cd39adc086fed41d8413032f7dce1ab0b24/models/current/tubeszb-efr32-MGM210-poe/firmware/efr32_MGM210/ncp/MGM210PA32JIA_ncp-uart-sw_7.2.2_TubesZB_2022.gbl
Probably a beginners mistake?
Iām not on desktop so canāt grab the link right now, but you need the raw link from GitHub.
Yes, I checked the youtube movie and noted ārawā. Upgraded with success!
BIG THANKS for a good tool!
Been having an intermittent problem. I am using one of your coordinators ,Black,round.
tube-zb-gw-cc2652p2-v2
Recently zigbee2mqqt has stopped working. The error I get is
āError: Failed to connect to the adapterā
My config
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:
base_topic: zigbee2mqtt
serial:
port: tcp://10.0.0.91:6638
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
advanced:
log_level: info
pan_id: 6756
channel: 20
network_key:
- 1
- 3
- 5
- 7
- 9
- 11
- 13
- 15
- 0
- 2
- 4
- 6
- 8
- 10
- 12
- 13
availability_blocklist: []
availability_passlist: []
device_options: {}
blocklist: []
At first I thought a network issue
I can connect to the web interface so IP is correct
I pinged both the adapter and home assistant for about 15 min neither dropped a single packet.
It will sometimes work after multiple reboots and powercycling the coordinator. It stays working until I reboot usually.
Looking for any suggestions.
Thanks
Craig
I just listed CC2652 P7 based PoE coordinators in the storeā¦ I had 2 testers who have been testing/using them for the last few months I havenāt heard from them in awhile so figured it was good to finally list as I have way to many of these modules on hand to keep through the end of the year If you have a 2022 or 2023 p2 and want to update I hope to get a listing for that up soon!
Hi,
I use a tubeszb-efr32-MGM210-poe for several time now and always recognized some bad behavior after rebooting, device is pingable but no service like web or 6638 is available.
Several reboots usually fixes the behavior but with latest ESPhome update the 6638 port is always dead, portscans even do not find it. ESPhome log Button goes into connection timeouts, like my Z2M.
Anyone with an idea how to fix this?
Would love to supply logs but have no real clue how to get themā¦
Some additional question: does a radio update mean you have to re-pair every device or should all run as before?
Dan
Try flashing the original binary from github via USB
you can use the binary from there, lift the device up front he case to access the micro usb port on the side of the Olimex ESP32-PoE.
You can use the ESPHome flasher to flash to the device:
This describes the process, https://github.com/tube0013/tube_gateways/tree/main/models/current/tubeszb-cc2652-poe-2023#esp32-flashing
even though itās under the cc2652 model, its the same process.
I put device back to life flashing again the esphome fw generated by the addon via web page.
Now over night the 6638 port seems to be crashed, in the logs I noticed this:
10:50:20 [W] [component:214]
Component esphome.coroutine took a long time for an operation (0.05 s).
10:50:20 [W] [component:215]
Components should block for at most 20-30ms.
10:50:20 [W] [component:215]
Components should block for at most 20-30ms.
Can you also give an answer to the radio flashing? Does this enforce to repair the whole ZB clients?
Many thanks,
Dan
both zha and z2m make regulary backups so when a coordinator is flashed and reset in the process is detected they will write the last backup to the coordinator restoring itās state pre flash.
I believe best practicve for z2m is to stop and do a clean start of z2m before stopping it to do the flash, so it pulls a fresh backup at startup. ZHA you can pull a back up manually or restart HA as I believe it does a backup then as well, as well as every few hours.
Thanks for your explanations, the EFR Update worked fine via the HASS addon.
Z2M is running again but the above mentioned ālong timeā messages are happening quite often now.
When I flash the older esphome fw from your github, do I need to re-adopt it into my esphome?
Dan
Iām not 100% sure on that. Using an EFR32 radio with z2m is considered experimental so canāt guarantee there wonāt be issues there.
Last year I did buy one of your PoE coordinators. Iām running HASSIO on a Synology VVM. Used ZHA until now, but I want to change Z2M. Removed ZHA add on. Installed Z2M add on. On tubeszb-cc2652-poe-2022 consol I can see Client is connecting and disconnection continously. Z2M-upstart service is stucked. Last log entry of Z2M is Zigbee2MQTT info 2023-11-14 20:58:19 Starting zigbee-herdsman (0.21.0).
IP and ports seems okay. What to do?
NB: Thanks for a very nice product.
Nothing else in the log? you should see more as Z2M starts with an additional error if something is wrong.