NUT Driver's Child device showing up as Hub Mesh but shouldn't be

ronv42 · May 22, 2022, 5:39pm

Not a big issue but I am working on some Hub Mesh designs this morning and noticed that when I turn on Hub Mesh on my primary hub and shared my first device which was the Office-Lamp my UPS child device now also shows being shared. Checked on my destination hub and the only device being published is the office lamp. I also checked the devices on the originating hub and it has no option to share.

So my question is what in the code triggers the condition that makes it shared?

bertabcd1234 · May 22, 2022, 5:48pm

What is "NUT Child UPS" a (presumably) child device of? If the parent device is shared, the child devices come along, and child devices do not have their own toggle or any other ability to be shared separately from the parent.

ronv42 · May 22, 2022, 6:09pm

Here is the parent device you can see that the slider is off.

ronv42 · May 23, 2022, 1:11am

OH well I tired everything, Toggled the mesh for the parent device on and off, removed and reinstalled the device, and still it shows up as a shared device from the parent hub. On the other hub all that shows up is the office lamp. I'll just let this one stew in the land of limbo.

bertabcd1234 · May 23, 2022, 2:26am

Not sure what could be going on, but perhaps @gopher.ny might be able to take a closer look.

gopher.ny · May 23, 2022, 4:52pm

You can force share/unshare a device using a direct endpoint:

/hubMesh/setDeviceShared/123/false

Here 123 is the device id (it appears in device details URL) and false can be true/false to share/unshare the device. It works even if there is no hub mesh toggle on the device page.

This endpoint was specifically added to clean up the child devices like the one described above. I don't recommend using it for any other purpose.

ronv42 · May 23, 2022, 5:45pm

Thanks that fixed it!