I have a C5 connected with a C7.
I have a few virtual drives on my C7 I'm sharing back with my C5, and they are full of these messages where I only see them on the mirror image (in this case in the C5 event logs) not in the main host (C7 in this case): "hubMeshDisabled" False/True togging back and forth.
It's making the rules I have on my C5 very very unreliable. There are very frequent (feels like the majority of the time) times where I'll open up the device on the C5 and none of the Device Commands will work, only if I pull up the original real device on the C7.
Something about HubMesh isn't working reliably.
My two hubs are next to eachother, hardwired into the same router.
I am forcing syncing both at 5min.
Since it seems to happen with every sync, have you tried changing the full sync interval to never? I have had mine set to never on my hubs for quite a while and haven't had any issues.
It’s a great question. Yes. Started at 1 hour, tried never, but same unreliable command issue. Hence why I changed it to every 5min to see if that would help.
So I did the router reboot to just check. No changes. Also reverted to 'hourly' sync and the hubMeshDisabled now is only doing that toggle hourly.
The issue I have though is that while the status is correctly showing/syncing from the Primary Hub where the virtual device is attached to the secondary hub. Any commands on the Secondary hub don't do anything. As in I can't actually control the device from the meshed hub, only the original/primary.
@gopher.ny - are there any tips for troubleshooting? Couldn't find any in the documentation. FWIW it's not all of my devices that suffer from this, just a few with one notable virtual custom driver.
Update. Still not working for this specific device. States are syncing great, but commands from the meshed hub to the hub where the device is originally connected isn't working.
My work-around right now is to create a new virtual button, mesh that button, then use that in Rules on my secondary device.
So: My rule pushes the button, and HubMesh syncs that state/trigger for a local Rule that then toggles the TV that is on that same hub.
100% reliable. So bizarre.
Could there be something about how this virtual device is connected? Should I kill it and re-mesh it?
edit :removed the device from HubMesh and readded (and did device swap with a temp virtual switch). Same results. Commands from the meshed device not working. Wondering if there is something unique to this virtual device code (Samsung device driver) where commands are being sent differently than expected?)
