✨ New Features & 🐛 Bug Fix

✨ New Feature

Site-to-site IPsec tunnels as devices with status sensors and an enable/disable switch

🐛 Bug Fixes - Thanks to @ABovsh for his great contribution

Ping Check: Connection check enabled from the Web UI now works correctly
When you enable the "Check internet access (Ping Check)" option from the router's web interface, the integration now correctly reads the status of this setting. Previously, even if the ping check failed, the respective WAN connection could be reported as "has internet access" — even if the router itself said "No internet access". Now, when the ping check fails on your primary line, the sensor correctly shows "no connection," and your failover scenarios are triggered properly.

⚡ Performance Improvements - Thanks to @ABovsh for his great contribution
Coordinator now fetches data from the router in parallel

Requests made to the router in each update cycle are now sent in a controlled parallel manner instead of sequentially. As a result:

Updates are noticeably faster. The tick duration is significantly reduced, especially on mid-range router hardware.

No skipped updates. On slower routers or congested networks, some updates were silently skipped, delaying device data — this no longer happens.

A single problematic endpoint no longer breaks the entire update. If a component of the router temporarily fails to respond, other data continues to update, and the problematic call is retried in the next cycle.

Correct behavior when the router is unreachable. When the router cannot be reached, the integration now reports the status to Home Assistant and correctly marks entities as "unavailable" instead of pretending to "work with empty data".

No silent failures. Temporary fetch errors are now visible in the logs — making diagnosis easier when an issue occurs.

Your router hardware is protected: The number of concurrent requests has been limited so as not to overwhelm low-end router CPUs.