getChildAndRouteInfo signs of trouble or not?

tjward · December 10, 2020, 9:14pm

I’m coming off of ST and on my third fresh install on my new HE, and I have learned quite a bit on how to mess up a mesh. I now have 50 devices, 16 are repeaters, and it is running smoothly. Today, though, I see an oddity in the getChildAndRouteInfo list.

I see a newly installed motion sensor in the Child Data section. Why is it there? None of my other motions are. Is something wrong with it? It seems to work... Should I kill it with fire and replace it?

Also I have about 100 more devices to add... it's a big house. should I go for a second HE?

thanks folks

bobbles · December 10, 2020, 9:24pm

I have 12 child devices which are all sensors.
All work and don't drop off the mesh.
They just like talking directly to the hub and don't route via a repeater.

Also my motto is. If it ain't broke...........

If you have a good mesh, the devices will sort themselves out in my experience.

bertabcd1234 · December 10, 2020, 9:26pm

I wouldn't consider that an oddity. As mentioned above, it just means that the device has a direct communication path to the hub instead of via a router (repeater). If you have more than 32 of those and no repeaters for them to use instead (that's Hubitat's maximum "end device" limit, and if you came from v2 ST hub, it was the same--I think v3 doubled that), you'll run into trouble, but just one seems more than normal to me--especially if it's close enough to the hub that this would be a logical path for it.