Version History - MiWiFi XiaoHack Edition

📝 Changelog — MiWiFi Integration

📦 Version v3.5.0 – 2026-01-03

✅ Fixes & Stability

• 🧠 Stable per-device metrics exposure: device traffic/usage metrics are now exposed through dedicated sensor entities (instead of relying only on device_tracker attributes), improving compatibility across dashboards and automations.
• 🔄 Reliable dynamic updates: new device sensors are created automatically when a new client is detected, without requiring a Home Assistant restart (hooked to the same internal update/signaling flow).
• 🧹 Cleaner entity lifecycle: device sensors follow the same cleanup logic as tracked devices, avoiding orphan entities after purges.

⚙️ Improvements

• 📡 New per-device sensors (one set per client entity), built from the same authoritative source (updater.devices) used by the tracker:
• sensor.<entity>_down_speed
• sensor.<entity>_up_speed
• sensor.<entity>_total_usage
• sensor.<entity>_signal_quality
• sensor.<entity>_signal
• sensor.<entity>_ip
• sensor.<entity>_connection
• sensor.<entity>_online
• sensor.<entity>_last_activity
• sensor.<entity>_first_seen
• sensor.<entity>_internet_blocked

• 📏 Human-readable units (recommended HA approach):
• Device speeds are exposed as DATA_RATE with native units in Bytes/s, allowing Home Assistant to automatically display kB/s / MB/s when appropriate.
• Total usage is exposed as DATA_SIZE with native units in Bytes, allowing Home Assistant to automatically display MB / GB based on the value.

• 🔗 Device registry consistency: sensors are linked to the same client device entry (per MAC), improving the device page experience and entity grouping.

✅ Compatibility

• ✅ Fully compatible with existing device_tracker.miwifi_* entities.
• ✅ No breaking changes in tracker attributes; sensors are additive.
• ✅ Uses Home Assistant best practices (device_class, state_class) to preserve statistics, history and UI formatting.

📘 How to Update

1. Update the integration files to v3.5.0.
2. Restart Home Assistant.
3. Optional (recommended if you previously tested earlier versions):

• If you notice old units still displayed, check the entity settings (custom unit overrides) or remove the affected entities from the Entity Registry and restart again.

ℹ️ Información adicional

Example: new per-device entities

• Before: traffic/usage only available inside device_tracker attributes.
• Now: you can build dashboards/automations directly using sensors like:
• sensor.servidor_down_speed
• sensor.servidor_total_usage

Notes

• Speeds and usage are exposed with stable native units; Home Assistant takes care of the readable scaling (MB/s, GB, etc.) in the UI.

💖 Support & Donations

If you find this integration useful and want to support continued development:

• 💸 Wise
• 💸 PayPal

🧾 Summary of changes

📝 Changelog — MiWiFi Integration

📦 Version v3.4.9 – 2026-01-01

✅ Fixes & Stability

• 🧩 Unsupported registry migrated to Home Assistant Storage

Replaced the legacy unsupported_user.py workflow with __HTML_PLACEHOLDER_1__ (Store-based persistence). This prevents write-permission issues inside custom_components and makes the behavior consistent across HA installs.

• 🔁 No more repeated “unsupported” suggestions after restart

Compatibility checks now treat predefined unsupported features as N/A (None) instead of failures, so diagnostics will not re-trigger the same warning on every reboot.

• 🛡️ Guest Wi-Fi compatibility noise removed

The previous Guest Wi-Fi compatibility probe could report false negatives due to mismatched client methods/endpoints. The check was removed/neutralized to avoid incorrect “unsupported” recommendations.

⚙️ Improvements

• ➕ “Add to unsupported” is now functional from diagnostics

The diagnostics action now uses a dedicated endpoint (/api/miwifi/add_unsupported) that performs an authenticated service call to miwifi.add_unsupported.

• 🧠 Automatic merge of base + user unsupported models

The integration now merges:

• Base UNSUPPORTED registry (shipped with the integration)
• User-defined entries stored in .storage/miwifi/unsupported_user.json

• 🧼 Improved UX for the diagnostics action

The confirmation page auto-returns to Home Assistant after the service call, so users don’t need to manually close extra pages.

✅ Compatibility

• ✅ Compatible with Home Assistant 2025.5.0+
• ✅ No breaking changes to existing configurations

(Legacy unsupported_user.py remains supported via migration/merge logic if present.)

📘 How to Update

1. Replace all files inside custom_components/miwifi/ with the contents of this release.
2. Restart Home Assistant.
3. (Optional) If you previously used unsupported_user.py, confirm that new entries are now stored in:

.storage/miwifi/unsupported_user.json

1. If diagnostics suggest adding a feature to unsupported, click the action link and verify the model appears in the Storage JSON.

ℹ️ Información adicional

• The supported “Add unsupported” workflow is now Storage-first (recommended for all users).
• If you see entries like "new" in the Storage file, ensure the feature key matches the CompatibilityChecker feature name (e.g., wifi_config, mac_filter, etc.), otherwise it will be stored but not applied.

💖 Support & Donations

If you find this integration useful and want to support continued development:

• 💸 Wise
• 💸 PayPal

📌 Summary of changes (v3.4.8 → v3.4.9)

📝 Changelog — MiWiFi XiaoHack Edition (Home Assistant Integration)

📦 Version v3.4.7 — 2025-12-28

✅ Fixes & Stability

• 🐞 Fixed wrong mode detection in CompatibilityChecker: routers reporting numeric modes (e.g. mode=2) no longer fall back incorrectly to DEFAULT.
• 🧩 Proper “SKIP” behavior for non-applicable checks: returning None from compatibility checks (e.g. AP / Repeater / Mesh) is now treated as *intentional skip* instead of triggering retries and false “unsupported” warnings.
• 🛡️ Reduced false positives in logs such as:
• Feature 'device_list' failed after 5 attempts...
• Feature 'topo_graph' failed after 5 attempts...

when the router is running in Access Point / Repeater / Mesh modes where those endpoints can be unreliable or not applicable.

⚙️ Improvements

• 🧠 Unified mode parsing using the existing Mode(IntEnum) as the single source of truth:
• Numeric parsing first (Mode(int(...)))
• Phrase/alias fallback ("ap", "router", etc.)
• 🔍 More consistent debug output for Compatibility mode parsing and feature evaluation.

✅ Compatibility

• ✅ Improved compatibility for RA82 and similar models reporting mode=2 (Access Point), avoiding incorrect mode classification and noisy “unsupported” suggestions.
• ✅ Compatibility checks now behave correctly across:
• DEFAULT (0) router mode
• REPEATER (1)
• ACCESS_POINT (2)
• MESH_NODE (3)
• MESH_LEAF (8)
• MESH (9)

📘 How to Update

1. Download v3.4.8 from the GitHub Releases page.
2. Replace the integration folder:

• custom_components/miwifi/

1. Restart Home Assistant.
2. (Optional) Clear browser cache if you are also using the MiWiFi Panel.

ℹ️ Additional Information

• This release focuses on CompatibilityChecker reliability and does not change router control logic.
• No breaking changes expected.

💖 Support & Donations

If this project is useful to you and you want to support future development:

• ⭐ Star the repository on GitHub.
• 🐛 Report issues and share logs/topology captures to improve compatibility with more routers.
• 💬 Share screenshots and feedback from your setup so we can keep polishing the experience.
• 💸 Wise
• 💸 PayPal

Every bit of feedback helps to keep MiWiFi XiaoHack Edition healthy and evolving. 🙌

📊 Summary of changes

📝 Changelog — MiWiFi Integration

📦 Version v3.4.7 — 2025-12-19

🆕 Compatibility Model

• ✅ Added support for new router model RC02 #194

📘 How to Update

1. HACS: Open HACS → *Integrations* → MiWiFi → Update → Restart Home Assistant.
2. Manual: Replace the folder custom_components/miwifi/ with the new release → Restart Home Assistant.
3. After restarting, verify:

• NAT rules list correctly under your main router.
• Adding/removing rules works as expected.
• (Optional) Check logs for the selected NAT path (default or fallback).

ℹ️ Additional Information

• If you previously patched endpoints per model, the new centralized map will take precedence.
• For diagnostics, enable debug logging for custom_components.miwifi and look for messages about autodiscovered NAT paths.

💖 Support & Donations

If this project is useful to you and you want to support future development:

• ⭐ Star the repository on GitHub.
• 🐛 Report issues and share logs/topology captures to improve compatibility with more routers.
• 💬 Share screenshots and feedback from your setup so we can keep polishing the experience.
• 💸 Wise
• 💸 PayPal

Every bit of feedback helps to keep MiWiFi XiaoHack Edition healthy and evolving. 🙌

📝 Changelog — MiWiFi Integration

📦 Version v3.4.6 — 2025-12-06

🆕 Compatibility Model

• ✅ Added support for new router model R4ACv2 #183

✅ Fixes & Stability

-

⚙️ Improvements

-

🧩 Compatibility

-

📘 How to Update

1. HACS: Open HACS → *Integrations* → MiWiFi → Update → Restart Home Assistant.
2. Manual: Replace the folder custom_components/miwifi/ with the new release → Restart Home Assistant.
3. After restarting, verify:

• NAT rules list correctly under your main router.
• Adding/removing rules works as expected.
• (Optional) Check logs for the selected NAT path (default or fallback).

ℹ️ Additional Information

• If you previously patched endpoints per model, the new centralized map will take precedence.
• For diagnostics, enable debug logging for custom_components.miwifi and look for messages about autodiscovered NAT paths.

💖 Support & Donations

If this project is useful to you and you want to support future development:

• ⭐ Star the repository on GitHub.
• 🐛 Report issues and share logs/topology captures to improve compatibility with more routers.
• 💬 Share screenshots and feedback from your setup so we can keep polishing the experience.
• 💸 Wise
• 💸 PayPal

Every bit of feedback helps to keep MiWiFi XiaoHack Edition healthy and evolving. 🙌