Hub Meshed Linked Device - Preferences Not Locked Down?

🛎️ Get Help
1

I just noticed that the preferences of my devices that are shared between hubs with hub mesh are not locked down as the documentation says. I have four hubs running with hub mesh enabled on all of them. I can confirm that preference changes on the source hub are updating on the destination hubs. But I can also adjust the preferences on the destination hubs and it does nothing. It also appears that the correct setting on the source hub does not overwrite the destination hub when I do this.

Example:

Device shared between Hub A to Hub B (happen to be C8Pros running 2.4.3.133)

Hub A device - update preferences - change reflected in Hub B
Hub B device - update preferences - which I should not be able to do? It accepts change but does not change on Hub A. Further the preferences are now out of sync and after waiting a while the correct setting from Hub A does not overwrite Hub B.

Is this a bug? Something I am doing wrong? Thanks.

2

I do recall them being locked down in upstream hubs in last releases. @gopher.ny

3

I would hope that you can change some settings to be different between hubs. For example, you may not want info logging turned on for ALL your hubs, so it makes sense that you should be able to disable that per-hub..

4

I quess it is an issue of what it should be doing, not what we might want it to do? My understanding was that all preferences should be greyed out in the downstream hub. In fact I recall seeing that in the past. What I am seeing now is that the preferences in the downstream hub are not greyed out, can be changed, and in fact don't have any impact on the upstream hub device preferences. So I don't think this is desired?

5

I dunno... To me this behavior sounds desirable, because I would definitely prefer to turn off device logging on all downstream hubs while still keeping it enabled on the upstream hub. The only way to do that is if the preferences can be changed independently of the upstream hub.

6

Sorry I wasn't clear. I mean't it is more of an issue of what Hubitat intended it to be doing currently vs what might be desired in the future. In my case it appears to be not doing what I think they intend it to be doing. Hopefully that didn't make it more confusing!