Thank you for the detailed reply – that’s excellent information! So far, everything is going smoothly. I bought two of your routers in addition to the coordinator, and have been adding devices through them (zha). Even in my yet-unfinished state, my mesh map already looks better 
1 Like
I will likely cut and paste most of this to my GitHub as I’ve been slacking on getting the docs for the these up🤦♂️
I have another question – this doesn’t seem to be impacting anything, but I have some unusual devices added after I setup ZHA. One seems to be the coordinator itself (which I would expect to see, only maybe not in this state?), and I’ve no idea what the other one is supposed to be. Both show up as “unk_manufacturer unk_model”:
They both appeared immediately after I initially setup ZHA, before adding any other devices.
Any ideas?
I’ve only ever seen that when pairs do not go through completely. Do you have any other devices identified as SiliconLabs? this is what my test one looks like:
No, just those two unknowns, the two TI routers, and my other sensors/switches/etc.
Hey @tube0013…
I’m trying to setup the CC2652p2 router through ZHA and I’m getting the following (running HA Core 2021.3.4). I gave it a static IP, so I’m not using mDNS to access it.
17h50m10s││2021-03-20 11:09:57 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry socket://192.168.1.11:6638 for zha │
17h50m10s││Traceback (most recent call last): │
17h50m10s││ File "/usr/src/homeassistant/homeassistant/config_entries.py", line 248, in async_setup │
17h50m10s││ result = await component.async_setup_entry(hass, self) # type: ignore │
17h50m10s││ File "/usr/src/homeassistant/homeassistant/components/zha/__init__.py", line 100, in async_setup_entry │
17h50m10s││ await zha_gateway.async_initialize() │
17h50m10s││ File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 157, in async_initialize │
17h50m10s││ self.application_controller = await app_controller_cls.new( │
17h50m10s││ File "/usr/local/lib/python3.8/site-packages/zigpy/application.py", line 64, in new │
17h50m10s││ await app._load_db() │
17h50m10s││ File "/usr/local/lib/python3.8/site-packages/zigpy/application.py", line 56, in _load_db │
17h50m10s││ await self._dblistener.load() │
17h50m10s││ File "/usr/local/lib/python3.8/site-packages/zigpy/appdb.py", line 474, in load │
17h50m10s││ await self._load_attributes() │
17h50m10s││ File "/usr/local/lib/python3.8/site-packages/zigpy/appdb.py", line 489, in _load_attributes │
17h50m10s││ dev = self._application.get_device(ieee) │
17h50m10s││ File "/usr/local/lib/python3.8/site-packages/zigpy/application.py", line 390, in get_device │
17h50m10s││ return self.devices[ieee] │
17h50m10s││KeyError: 00:17:88:01:03:5c:e2:e9
I can hit it through the browser though:
Any ideas?
[EDIT]: I should add that I was able to get it partially working in z2m, but if I change the channel from 11 to anything else (15, 20, etc), the routers can partially connect (using the bst button on them to reset). They will connect initially, but then they won’t ping after that.
Let us see if we can work through this.
Coordinator is set up with a static IP, and reachable over the web, but when trying to connect to it with serial via ZHA it throws the error above?
It seemed to work with Z2M but the routers seemed to disconnect from the mesh? - did the z2m logs show any errors about loosing connection to the coordinator?
I had a report of one coordinator come in last night that would not hold serial connections. We tried a lot of things to no change so I am swapping it out with a new one once more PCBs arrive (Finally shipped today).
That’s correct. Just as a test, I toggled both BST and RST on the coordinator, but same result from HA.
Also correct. However, I was using the Availability Timeout check in z2m, so they were probably still on the mesh, but weren’t available for pinging. I changed it to 0 just to make sure that wasn’t interfering with things.
As a final test, I setup a clean copy of z2m on a different server, with a newly generated PAN and network id. I can get both routers to connect, but right now, nothing else is on channel 20. I’m testing with 2 devices, a Philips Hue motion sensor and a Centralite (Iris) 3320-L. Neither one will pair on channel 20.
okay. on the website of the coordinator in the log window - when you start up a new network - z2m or zha does the log every say Serial Disconnected before you’ve actually shut down the controller application?
Nope. I shutdown z2m and tried just now to add zha through HA: This is all that’s in the coordinator logs:
Just dropped an order for the router. Looks pretty.
3 Likes
After a bit of confusion yesterday (I had a leftover zigbee.db from an old ZHA integration), I got my coordinator and 2 routers hooked up and working fantastically. I still have 3 Ikea drivers that I want to remove (I hate Ikea devices as routers) and 1 Hue bulb that’s going away as well. But overall, the fact that each Tube router is handling well between 10-15 child devices each is above and beyond what I expected. My mesh has been settling in for about 18 hours now.
2 Likes
Received my router today. Speedy shipping, well designed and attractive. Joined my mesh instantly.
Look forward to seeing it get some lines drawn to it as the mesh works it’s way around it.
Thanks
3 Likes
It’s a special day, as I have at least one of everything in stock 
3 Likes
@tube0013 I received mine this afternoon and wanted to say thank you. I was nervous at first since being a noob; but I spotted a TI device on my visualization diagram and after a few hours devices started routing efficiently. I have 4 zigbee wall plugs as routers; but this device is on another level just flat out powerful. Thank you @tube0013
2 Likes
@tube0013 any more thoughts on shipping internationally? IE: Canada? USPS should be fairly efficient.
Just saw your co-ordinator too. Being able to use an ethernet connection would be great to get the co-ordinator in a more centralized location. My conbee2 is buried in a corner of the basement which could be half of my issue right there. A central coordinator and some router’s would be great!
1 Like
I’ve been shipping international - to Canada is like $12 flat rate $14 everywhere else. Bumps up by $2 over 1/2 pound but that’s like over 3 devices (2 being coordinators)
I have his CC2652P2 and yeah, over the Conbee2, it’s fantastic. Been running it for a couple weeks now and it’s running like a champ.
Worked out to $16 shipping for the coordinator and 2 routers. Excited to try these out.
This is great news! I’ve always had some zigbee stability issues, hopefully this will get rid of most of those. I’ve avoided motion lighting simply because of all the commands my other zigbee devices miss.
1 Like
I have one coordinator and two of the routers. Haven’t had a single message drop or device drop-off since I switched over to them. Well, except for two of my craptastic Ikea drivers. But… they are getting replaced this weekend. 
2 Likes