Hubit network spoofing to enable greater fault tolerance, hardware upgrades, and more HE sales

Feature request: Hubitat should use virtual (software-generated) network addresses (ie., spoofed MAC address) for all network communication. Those MAC addresses, being independent of the physical hardware but unique to the LAN, could be saved as an independent backup, distinct from rules, apps, etc.

Implementation: For existing hubs, "changing" the current Zigbee & ZWave network identification will probably require network rediscovery ('repair'), but mapping of end-devices to Hubitat device IDs can be preserved, enabling a (slow) transition with little user effort. For new Hub installs after this feature is enabled, the user experience would be the same as it is now -- network communication would simply reference the software-generated MAC addresses at all times and there would be no need for the user to be aware of the spoofing.

Use Cases:

  • virtualized network addresses would improve fault tolerance, in the case that one Hub fails, another Hub could be loaded with the virtualized MAC addresses from a backup, enabling the 2nd hub to assume the network role of the failed device without requiring device exclusion/inclusion and network repair. Similarly, assuming the MAC address of the failed hub would ensure that DHCP and routing configurations would not require intervention.

  • Similarly, virtualized network devices would enable a simple hardware upgrade path from one generation of HE device to another.

These use cases encourage existing owners to purchase additional HE devices.