Hub Mesh goes offline between C-5 and C-7 after an hour or so after updating both to 2.2.9.137 from 2.2.8.156. It has been rock solid between these two hubs on this same reliable network for the last year. Resetting the Mesh Token on both ends gets it back but not for long.
About a week ago I tried 2.2.9.128 on the C-5 with 2.2.8.156 on the C-7 and that was unstable. When I rolled back the C-5 to 2.2.8.156 it returned to normal. I only have about 5 devices on the C-5. 4 of which are shared to the C-7.
I would shut down hub from the settings menu, unplug the unit at the wall (not at the hub), wait 5 mins and power back up. See if that helps. Do you have any zooz stuff in your mesh?
Yes to Zooz, actually the only reason I'm still using the C-5. I have two Zooz 4 in 1 motion sensors. I just rolled back the C-5 to 2.2.8.156 and mesh seems to be stable now. Also noticed that z-wave exclusion does not appear to initiate on the C-5 with 2.2.9.137. I'm waiting for another Hue motion sensor to arrive today and then the C-5 is likely headed to eBay if it continues to have current firmware incompatibility issues.
I normally put this disclaimer on my reports of "Works for me" but I forgot this time.... busy with screen caps I guess.
I believe your experience is accurate. Your question implies "Has this been reported or is it rare?" My contribution is to add a data point to that question
I think I see what you might be referring to.... there's no UI feedback. You click, it does the work entirely behind the scenes... no user indication, just a two-liner in the logs.
Back to Hub Mesh. These are event logs from two Zooz 4 in 1s and a Peanut plug on my C-5 as devices on the C-7. Both hubs are on 2.2.9.137. There is no activity I'm aware of that might account for hub mesh cycling between enabled and disabled. I'm going to move both of these hubs to the same network switch to see if their behavior changes.
