Is there an existing issue for this?
Is your feature request related to a problem? Please describe
At the moment, if I customize a device (e.g. logo and type) on a node (device that was already synced on the hub in a previous sync routine), on the next sync these cosmetic changes are not ported to the hub.
Describe the solution you'd like
I would like a way to force the hub to apply all changes coming from the nodes for existing devices, still following the LOCKED/USER rule. If there are conflicts among the nodes, perhaps use the latest update value (if available) to determine which node to retrieve the information from.
In this way, I can stop updating values on the hub for the synced-up devices (except obviously for the IP range it manages, devices that only exist on the hub itself) and just update their information directly on the nodes.
Describe alternatives you've considered
For the moment, I manually update changes on hub and all relevant nodes.
Another “quick” method I’ve discovered is simply to remove the device from the hub: the next time it syncs, the device will be added back by the corresponding node with all the properties already applied. But, deleting devices on the hub loses their history if they ever appeared on the IP range managed by the hub, so not a great workaround.
The thing is, it’s very easy to overlook changes I’ve made to the nodes but forgot to apply to the hub as well, so the hub’s overall view might show outdated properties - or not show them at all.
Anything else?
No :)
Am I willing to test this? 🧪
Can I help implement this? 👩💻👨💻
Is there an existing issue for this?
Is your feature request related to a problem? Please describe
At the moment, if I customize a device (e.g. logo and type) on a node (device that was already synced on the hub in a previous sync routine), on the next sync these cosmetic changes are not ported to the hub.
Describe the solution you'd like
I would like a way to force the hub to apply all changes coming from the nodes for existing devices, still following the LOCKED/USER rule. If there are conflicts among the nodes, perhaps use the latest update value (if available) to determine which node to retrieve the information from.
In this way, I can stop updating values on the hub for the synced-up devices (except obviously for the IP range it manages, devices that only exist on the hub itself) and just update their information directly on the nodes.
Describe alternatives you've considered
For the moment, I manually update changes on hub and all relevant nodes.
Another “quick” method I’ve discovered is simply to remove the device from the hub: the next time it syncs, the device will be added back by the corresponding node with all the properties already applied. But, deleting devices on the hub loses their history if they ever appeared on the IP range managed by the hub, so not a great workaround.
The thing is, it’s very easy to overlook changes I’ve made to the nodes but forgot to apply to the hub as well, so the hub’s overall view might show outdated properties - or not show them at all.
Anything else?
No :)
Am I willing to test this? 🧪
netlertx-devimage when requested within 48h and report bugs to help deliver a great user experience for everyone and not to break existing installations.Can I help implement this? 👩💻👨💻