Setting up a traffic route is the easy part. Keeping its destination networks current is the less enjoyable work, especially when cloud services and games change their infrastructure.
Service Route Sync is a Home Assistant integration that updates the destination IP prefixes of selected services in existing UniFi routes. There is no need for an additional external scheduler.
Selected services. Existing routes.
The integration supports Microsoft 365, selected Azure service tags, AWS regions and services, and known networks used by several game providers. You can also supply your own public IPv4 and IPv6 networks.
The destination-sync feature updates only IP destinations on explicitly bound routes. It does not create or delete those routes. WAN selection, source devices, VLANs and the enabled state are preserved.
Preview first. Apply second.
Changes start in preview mode. The idea is simple: make the proposed change visible before enabling automatic writes. Controller access uses a separately configured local UniFi API key.
This is an early community release. Automated tests and one live installation are documented; a broad controller and firmware compatibility matrix is still needed.
Choose the scope deliberately.
A cloud provider is not a single service. Routing all of its networks may also affect unrelated applications. Azure tags and AWS regions and services are selected explicitly for that reason. Microsoft 365 defaults to the Optimize category.
Games may also use additional cloud, CDN and third-party networks. The included operator networks therefore do not necessarily cover every server a game uses. Overlapping services need deliberate route priorities and appropriate device scope in UniFi.
Built in the open.
Installation, permissions, architecture and validation are documented in the repository. UniFi is the implemented router backend; equivalent FRITZ!Box support is not currently available.