I wanted local client visibility and presence tracking from Movistar’s current Askey router in Home Assistant, without depending on a Movistar cloud service.
The existing movistar_rft8115vw integration provided the original parser and idea, but it still used Home Assistant’s deprecated legacy YAML device tracker. I have forked and modernized it as Movistar Askey Router.
Repository: GitHub - jardenberg/ha-movistar-askey: Modern local Home Assistant integration for Movistar Askey RTF8316VW and RTF8115VW routers · GitHub
Latest prerelease: Releases · jardenberg/ha-movistar-askey · GitHub
What it provides
- UI setup and reauthentication through Settings → Devices & services
- Local polling directly against the router’s web interface
- A Home Assistant device representing the router
- A Connected devices sensor
- A current client inventory in the sensor attributes
- Optional device trackers for clients seen by the router
- Configurable polling and presence-grace intervals
- Privacy-preserving diagnostics
- English and Spanish setup text
Trackers are created disabled by default, so the integration does not immediately fill Home Assistant with dozens of presence entities. You can enable only the clients you actually want to track.
Compatibility
- Askey RTF8316VW / Movistar WiFi 7 Router: tested live on hardware revision 4
- Askey RTF8115VW: expected to work because it is the original integration target and uses the same local network-map protocol
- Other Movistar routers: currently unknown
The integration uses the router’s web-administration password, not the Wi-Fi password. Communication remains on the local network over HTTP.
Installation through HACS
Version 2 is currently a prerelease, so add it as a custom repository:
- Open HACS → Integrations
- Choose Custom repositories
- Add
https://github.com/jardenberg/ha-movistar-askeyas an Integration - Install the latest prerelease and restart Home Assistant
- Open Settings → Devices & services → Add integration
- Search for Movistar Askey Router
- Enter the router IP address (normally
192.168.1.1) and its web-admin password
Please keep a recent Home Assistant backup while testing the prerelease.
Why the rewrite?
The new version replaces the deprecated legacy YAML tracker with config entries, coordinated polling, current entity APIs, reauthentication, options, diagnostics, and dynamic device registration. It has been tested with Home Assistant 2026.7.3 and an RTF8316VW.
I would particularly appreciate reports from people using an RTF8115VW, other RTF8316VW firmware or hardware revisions, or another Movistar Askey model. Please include the exact router model and Home Assistant version, but never post passwords or an unredacted client inventory.
Issues and contributions are welcome on GitHub. And full credit to Luis Garza’s original integration, which made this modernization possible.
