eWeLink Privacy: What Data Does the App Actually Collect?
A plain-English breakdown of what eWeLink's own privacy policy discloses about device data, permissions, third-party SDKs, and where the data goes.
~/archive $ ls -la
Archive
no-cloud
-
-
Zigbee2MQTT database.db Corrupted or Wiped: What to Do
Zigbee2MQTT lost every device after a restart, or database.db is 0 bytes? What the file stores, why it happens, and how to recover before re-pairing.
-
Do Aqara/Xiaomi Devices Stop Working When Discontinued?
Aqara or Xiaomi drops a model. Here's what actually happens to the unit already running on your Zigbee2MQTT or ZHA network, and what really can break it.
-
Sonoff DIY Mode: Local Control Without eWeLink Cloud
Sonoff's DIY Mode swaps eWeLink cloud control for a local HTTP API, no reflash needed. Which devices support it, and how to bring it into Home Assistant.
-
Zigbee2MQTT Debounce vs Throttle: Fixing Duplicate Updates
Zigbee2MQTT has five per-device options for noisy state updates. What debounce, throttle, and the filter options each do, and which one fits your device.
-
LocalTuya vs Tuya-Local: Which HA Integration to Use?
LocalTuya, tuya-local, and Home Assistant's official Tuya integration are three different things. Which to install in 2026, and which fork to pick.
-
Zigbee2MQTT last_seen Not Updating? What It Actually Tracks
Zigbee2MQTT's last_seen goes frozen, N/A, or oddly fresh on dead devices. What it tracks, why it misleads, and how to build a stale check that works.
-
tinytuya: Tuya Local Control Without Home Assistant
tinytuya lets you script and verify local control of Tuya Wi-Fi devices directly, without Home Assistant, LocalTuya, or tuya-local in the loop.
-
Aqara/Xiaomi Zigbee Firmware Updates Without the App
Aqara/Xiaomi Zigbee on Zigbee2MQTT: which firmware you can update locally without the app, which needs a one-time app step, and the FP300 exception.
-
Zigbee2MQTT \”Failed to Interview\”: Why Pairing Gets Stuck
A Zigbee2MQTT pairing that stalls on \"failed to interview\" usually means the join worked and the discovery queries timed out — not a config mistake.