Version History - MiWiFi XiaoHack Edition

MiWiFi 3.13.3 fixes client refresh on force-load AP/Mesh nodes and improves the device panel.

• Refresh clients from the node's own lists when no recent parent snapshot is available, while preserving authoritative parent data (#378).
• Publish Wi-Fi signal snapshots atomically to avoid temporary blanks during concurrent parent updates (#380).
• Back off optional client-details reads for one hour when a firmware returns a non-JSON response; transport failures retain short retries (#382).
• Rename clients directly from Cards or Table with persistent registry updates and protection for overlapping edits (#372).
• Place the edit button on the left, display complete client names and show localized last-activity dates without breaking chronological sorting.
• Add freshness-boundary, main-reload and wired-client sensor regressions. Live checks on BE10000 with a BE7000 Mesh node confirmed panel layout, persistent renaming, metric refresh, LAN field visibility and no new MiWiFi log errors.

Restart Home Assistant and refresh the panel after updating. The experimental model-specific API/IoT features remain in PR #373 and are not included in this release.

Fix the credential privacy and reauthentication issues identified in the HACS review.

• Strip query strings before retaining diagnostic request keys or logging retry paths. Sanitize older keys again during diagnostic export and omit exception messages that can embed a request URL.
• Recognize explicit login rejection and raise ConfigEntryAuthFailed so Home Assistant stops scheduled polling and offers reauthentication. Session expiry keeps its single login retry; network failures are not classified as invalid credentials.
• Add a translated reauthentication form in all eight languages. Validate the new administrator password, update the existing entry and any password override in options, preserve its identity/settings, and reload it.
• Add regression coverage for diagnostics downloads, Wi-Fi requests, setup/polling authentication failures and recovery with or without an options override.

Restart Home Assistant and refresh the panel after updating. Experimental router API and IoT changes remain in the trial branch.

Fix blocking filesystem operations reported during the HACS review. Manual main-router MAC overrides, legacy override loading and private-download file checks now run in Home Assistant's executor. File logging uses a queue so initialization, writes, rotation, reset and shutdown do not perform disk I/O on the event loop.

Regression tests cover thread ownership, concurrent setup, rotation, partial initialization failures and shutdown. The bundled frontend version is updated to 3.13.1. Restart Home Assistant and refresh the panel after updating.

Experimental router API and IoT Wi-Fi changes remain on the trial branch and are not included in this stable release.

MiWiFi v3.13.0

Mesh recovery, persistent purge scheduling, translated client diagnostics and optional real Wi-Fi signal/link metrics.

• Fix leaf counters when the last parent-reported client leaves (#364).
• Keep auto-purge deadlines across restarts, record failures and prevent duplicate

scheduled timers (#366 and maintainer follow-up).

• Restore force-load node clients and saved tracker states, and identify wired

mesh nodes from their topology on the first refresh (#368 and #370 together).

• Recover optional NAT reads after transport failures without aborting polling.
• Use consistent 60/30/20-second presence/scan/request defaults, validate timing

changes and explain them in all eight supported languages. Saved settings stay.

• Translate client diagnostics and add optional Wi-Fi protocol and TX/RX link-rate

sensors. Use real negative RSSI when available; hide Wi-Fi-only fields on LAN. Support depends on the router's firmware. Link rates are not Internet throughput.

• Add a standalone SSH API inventory tool; it does not run in normal HA polling

and never calls discovered API handlers automatically.

• Remove internal notes and obsolete workflow copies from repository tracking.

Thanks to @brembygit for the four mesh/scheduler contributions.

Update

Update through HACS, restart Home Assistant and refresh the panel cache. The integration and frontend both use 3.13.0. The minimum remains HA 2025.8.0. New diagnostic sensors can be enabled from the device's disabled entities. Review purge candidates in simulation before enabling automatic deletion.

Automation migration: the client connection sensor now uses lan, wifi_2_4, wifi_5, guest, wifi_5_game and iot; the Internet-block sensor uses lowercase true/false. Update comparisons of those sensor states. Device-tracker attributes, entity IDs and signal-quality states stay unchanged. See the translation migration guide.

The maintainer verified stable presence, return/departure, RSSI against the app, mesh client metrics, LAN field hiding, reloads and a selective deletion on RC01/RC06, without reported errors. Scheduler deadlines, empty-leaf and force-load startup edge cases retain automated coverage; not every case was reproduced on hardware. The existing unknown client total-usage reading is not claimed fixed.

Español

Esta versión reúne las correcciones de malla y autopurga, las traducciones de diagnóstico y las nuevas métricas Wi-Fi disponibles en firmwares compatibles. Mantiene los ajustes guardados y propone 60/30/20 segundos por defecto. Actualiza desde HACS, reinicia Home Assistant y refresca el panel. Los tres sensores nuevos son opcionales; las velocidades de enlace no equivalen al tráfico de Internet. Revisa una simulación antes de activar la autopurga. Si comparas el estado de los sensores de conexión o bloqueo en automatizaciones, adapta sus valores según la guía de migración.

Mesh settings and node cleanup

• Separate shared mesh settings from per-router options. Keep existing configuration until explicitly saving global settings, and reload only the affected entry unless the shared client-sensor setting changes.
• Add an optional manual AP role for devices behind another gateway. Preserve clients/counters and status-provided speeds while avoiding unsupported gateway queries.
• Stop tracking/restoring known mesh nodes as clients. Clean old client entities only after positive node identification; preserve router entities and other integrations. Retry freed backhaul aliases across loaded nodes.

Fresh diagnostics and translations

• Add an optional fresh read-only API capture for the main router and loaded nodes, with responses, errors, explicit skips and bounded partial results.
• Keep ZIP downloads private and administrator-only. Always redact credentials; optionally replace identifying addresses/names with consistent aliases, including hardware serial and room fields.
• Translate private-download/MAC/purge notices and the optional purge MAC filter in all eight languages. Keep simulation as the purge default.
• Add discreet optional support links without restricting any feature.

Validation and updating

• Tested on the maintainer's RC01/RC06 wired mesh with HA 2026.10.1, including reload/restart, global/device settings, AP on/off, counters and diagnostic exports. The contributor also confirmed the combined changes on a four-node RD28/RA82 wired mesh.
• Final PR CI: 206 legacy tests passed (HA 2026.10.0); 513 maintained tests passed (HA 2026.10.0); 512 passed + 1 existing version-specific skip (HA 2026.9.3). Regression/frontend/packaging, HACS, hassfest and CodeQL Python/JavaScript checks all passed. HA results, validation, CodeQL. The merged release tree is identical to the validated PR tree.
• Update through HACS, restart Home Assistant and refresh the panel to load the new frontend/translations. The declared minimum remains HA 2025.8.0.
• Keep a backup before changing client-sensor settings: disabling them removes client sensors across the mesh. Old client trackers removed for a positively identified node are not automatically migrated in automations.
• Wired testing does not confirm the intermittent duplicate-router-sensor race or the wireless-backhaul report. If either appears on this version, open a new issue with steps, versions and anonymized diagnostics. WPA3 security-mode display is deferred; a CCMP label alone does not identify the WPA authentication mode.

Thanks to @brembygit for #331, #326 and #359, the detailed regressions and hardware testing. Their original commits and authorship are preserved in #362.

Documentation: mesh settings, ajustes de la malla (ES), fresh diagnostics, diagnóstico ampliado (ES).