I have a c4, c5 and c7. Hub mesh is enabled between all 3. Is there a way in rule machine to determine the mesh is broken? Usually requires reboot of my Asus router if it is.
Can't say I do this myself, but I'm guessing If you run a hub info device on each hub and share that between hubs you could use one of the attributes from that device to detect if no changes have been sync'd.
Probably a bit of overkill in terms of the chatter you may get for every piece of info, so you could probably setup a hub variable to record a date/time and share that instead.
You could then look for a lag in the date/time, either from a hub info attribute or the hub variable, to indicate a loss of comm's.
The hub in my shop is on a wireless outdoor CPE. It's about 200' to my shop so I use the RM ping function to ping the hub in the house every 15 minutes. Not really the same I guess, but the only reason the mesh goes down is the wireless device losses connection.
1 Like
You’d have to parse the JSON or maybe just test for “offline”:”true” but the data is available in the driver:
I was thinking more of having other hub's hub info devices shared via hub mesh with the local hub and if they have not updated after an expected period of time they could be offline or something else is wrong. The more I thought about it, it probably isn't the way to go about it, at least the way I was suggesting. Using the hub's assessment of the mesh status is probably a better approach.
If hubinfo reports hubmeshcount changed as trigger
If hubmeshcount <>8 then
Do some things
Else
Do something
Endif
1 Like
HubInfoV3 will poll the endpoint http://<HubIPaddress>:8080/hub2/hubMeshJson on a frequency you determine and brings back what the current hub believes is the status of every other hub that is participating with it.
You could ping the other hubs to see if they are responding, but that doesn't guarantee that the mesh is communicating.
Another way to do this would be to create a virtual device that updates a date/time attribute every x minutes and share that across the mesh. Testing the attribute on the local shared copy every y minutes would allow you to determine the freshness of the connection. A value in excess of ≥ 2x would be an indication that there may be an issue.
Yeah, that was where I ended up in my train of thought as well.
Just updated my C7 and C8 hubs to the latest build.
As you can see a very simple rule is probably all you need.
All great suggestions and thoughts. I'll get started soon on trying them. Thanks to all.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
