v0.5.0 — Fleet-Map device overlay

First stable release of the device-swap overlay. A read-only layer that connects your Shelly Cloud devices to their local Home Assistant twins.

✨ Fleet-Map

A new action Shelly Cloud DIY: Fleet map (read-only by default) that, for every device in your Shelly account:

• Matches it to its local HA twin by MAC — both Wi-Fi Shellys (native shelly integration) and Bluetooth/BLU sensors (e.g. bthome). BLU devices are matched by decoding the cloud's XB id back to the BLE MAC.
• Includes offline devices and marks them [OFFLINE] — important, since a device you want to replace is usually offline.
• Suggests names (cloud alias → local device) you can optionally apply. The apply touches only the device's technical name, never name_by_user, never entity IDs — so automations and Node-RED are unaffected.
• Flags control-path risks — devices controllable only via the cloud, or where an automation drives the cloud entity despite a local twin existing.
• Plus machine-readable diagnostics (MACs fingerprinted, names redacted).

🔧 Replace device (opt-in, preview first)

Shelly Cloud DIY: Replace device transplants a dead Shelly's Home Assistant identity (entity IDs, device, name, area, history, automation references) onto a new unit of the same model, so you don't reconfigure HA after a hardware swap. Cloud devices supported now; native local Shelly + an upstream HA Core contribution are planned. Run it with Dry run on first.

🧭 Local-first

The cloud is never in the control path — this is an overlay over your fast, offline-resilient native shelly integration. Validated on a live 60+ device fleet.

See the README for details and the roadmap (Milestone 2: OAuth + WebSocket realtime).

🤖 Generated with Claude Code