@gopher.ny I run 2 production hubs and every time I add a new component device to my radios hub and share it with my coordinator hub via hub mesh, the child components come over as disabled:
Clicking the disable toggle temporarily enables them and then they disable again.
Today's new device was a Zooz Zen16 and I don't add component devices that often but this has been happening for many releases, I just don't add these types of devices that often. My work around is to use Postman to update the enabled flag on my target mesh hub.
I am happy to leave things alone if you want to look at my hub.
@gopher.ny Sorry misspoke even though hub mesh is enabled on the parent Zen16 on my radios hub (source hub):
It is NOT enabled on the child component devices:
Because of this my target mesh Coordinator hub has these devices disabled. As mentioned I can perform a Post request to "/device/update" on each of the child component devices setting meshEnabled to true on the source Radios hub to fix it but obviously this shouldn't be happening.
@gopher.ny I updated to the latest build and this still isn't working. I had to exclude my Zooz Zen16 because I made a change to one of the input settings which requires exclusion and re-inclusion and again the child component devices are still disabled for hub mesh even though the parent device is enabled.
@gopher.ny I have also encountered this bug where children of hub meshed parents go offline on the remote hubs. This happens across all different kinds of devices. For me the quick fix has always been to restart the source hub (also see this thread from 2024 about the same thing https://community.hubitat.com/t/2-3-7-145-hub-mesh-c-7-to-c-8-some-child-devices-offline ). I have experienced this issue since at least ver 2.3.4. Once the restart has been done, the child devices come back online and stay online.
On a related note, I have just recently run into a very similar issue. I’m in the middle of migrating from a set of hubs to another set of hubs and that involves a lot of removals of hub meshed devices. The issue is that when I disable Hub Mesh on the parent device, none of the children follow. The parent device is successfully removed from Hub Mesh but all child devices are still in use by Hub Mesh. Other than trying to use the Postman approach that @ritchierich mentioned above, I have no idea how to cleanly disable Hub Mesh for the child devices.
@gopher.ny I have sorted my issue by manually sending a POST command to the hub to set 'meshEnabled' and 'meshFullSync' to false for each child device of a parent device that has had Hub Mesh turned off. Thanks to @ritchierich for providing the steps on how to do this.
