Skip to content

⚠️⚠️⚠️ POSSIBLE BREAKING CHANGE ⚠️⚠️⚠️

Choose a tag to compare

View all tags
@cataseven cataseven released this 11 Apr 19:34
· 8 commits to main since this release
v1.2.4
152d1cd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

⚠️⚠️⚠️ Breaking changes possible — this release reorganizes how WAN connections are represented. Some existing entities may disappear or be replaced with new ones. We strongly recommend removing the integration and setting it up from scratch after updating to avoid stale or duplicate entities. Your automations referencing old WAN entities may need to be updated.

What's New

🌐 Multi-WAN Support

Your Keenetic router can handle multiple internet connections with automatic failover — now Home Assistant knows about all of them, not just the active one.

Each WAN (main ISP, backup WireGuard tunnels, LTE sticks, etc.) now shows up as its own device in Home Assistant, with a full set of sensors:

  • Connected — is the internet actually reachable through this WAN?
  • Enabled — matches the on/off toggle in the router UI
  • Provider — the name you gave it in the router ("Telekom", "Zurich", etc.)
  • Role — "Default connection", "Backup connection 1", "Backup connection 2", ...
  • Public IP — the real public address assigned to this WAN
  • Interface — which physical port or tunnel it's running on
  • Uptime — how long this connection has been up
  • RX / TX Bytes — cumulative traffic counters
  • RX / TX Throughput — live download/upload speed

🚨 Real Internet Outage Detection

Home Assistant can now tell the difference between two very different problems:

  1. The cable fell out — link down, obvious
  2. The link is up but the internet is actually broken — ISP peering issue, upstream routing problem, dead captive portal

Previously, only the first case was detected. Now, if you enable Ping check in your router's web UI for a WAN connection, Home Assistant will use the router's own ping-check result as the source of truth — the same signal that triggers the red "NO INTERNET ACCESS" badge in the Keenetic web UI and fails over to a backup connection.

The Connected sensor exposes useful details as attributes:

  • Which hosts the router is pinging
  • Success and failure counts
  • A human-readable failure reason when the check is failing
  • The check profile name and mode

This means you can now build automations like:

"When my main ISP actually stops working (not just when the cable is unplugged), send me a notification and switch my smart home into offline mode."

If you haven't enabled ping check in your router, the sensor still works using a sensible fallback — it just won't catch the trickier upstream-outage cases until you turn the feature on.

🐛 Bug Fix: Settings Dialog Error

Fixed an error message that appeared when opening the integration's settings dialog to change tracked devices or the ping interval. The dialog now displays correctly in all languages (Russian, English, Turkish).

Upgrade Notes

⚠️⚠️⚠️ Because this release reorganizes WAN entities, some sensors from previous versions may disappear or become unavailable after updating. The cleanest way to upgrade is:

  1. Remove the Keenetic integration from Home Assistant
  2. Update to this version
  3. Add the integration again from scratch

You'll then see new devices appear in Home Assistant — one per WAN connection on your router.

To get the most out of the real internet outage detection, turn on Ping check for your main WAN in the Keenetic web UI (Internet → your connection → Ping check).

Assets 3
Loading