v2.0.0
Lightwand 2.0 – Release Notes
Release date: 2025‑12‑22
Lightwand has been refactored from the ground up. The new architecture brings a cleaner code base and better performance.
Backward compatible except 'exclude_from_custom' can no longer be defined in light level option. Toggle Lights does not support motion any more.
1. What’s new
| Feature | What it means |
|---|---|
| Singleton translation manager | translation.json is now a singleton. It is imported by all integration files, so you only need to define the JSON file path and the language once. |
| Open/Closed state for motion sensors | You can now define sensors that reports open and closed states as motion_sensors. This allows you to trigger scenes based on the actual status of the door. |
| Performance‑friendly persistence | The plugin now writes only the current mode name on shutdown. The JSON file lives in <ad-config>/persistent/lightwand/. This reduces disk I/O and speeds up startup. |
| Automatic input selector population | The input_selector is automatically updated on startup with valid mode names, except for the reserved modes fire and false‑alarm. |
| Defining exclude_from_custom mode | The exclude_from_custom flag can now only be set at the room level options. |
| Motion no longer part of Toggle lights | The legacy “Toggle lights” mode no longer supports motion. Use a dedicated Lights mode with a single on/off setting for motion‑triggered lights. |
| Per‑sensor timers | When a room contains multiple motion sensors, each sensor now gets its own timer, preventing false‑positive deactivation. |
| Adaptive Lighting + Motion | The brightness comparison logic now uses the last known brightness when deciding between motion and mode priorities, yielding more predictable results. |
Please open an issue on GitHub if you run into any problems during the upgrade. Happy lighting! 🚀
Full Changelog: v1.5.4...v2.0.0