v1.5.3 Breaking change to default MQTT namespace
Lightwand v1.5.3 – Release Notes
Released – 2025‑09‑07
Lightwand is now available with a handful of new features, a few important improvements, and a small but helpful change in the default MQTT namespace. These changes make the app easier to use, safer to configure, and more flexible for future integrations.
What’s New
🎯 false_alarm mode
- Purpose – Reset the light back to its normal state after the “fire” mode was activated.
- How it works – Triggering the
false_alarmservice will return the light to the previous mode without requiring a full restart of the app.
🔧 keep_on_conditions
- Feature – Keep the light on if a user‑defined condition (e.g. a sensor threshold, time of day, or Home Assistant state) is satisfied.
- Usage – Add a list of python if statements to the
keep_on_conditionskey in your YAML configuration.
🌤️ Ad‑Weather integration
- Benefit – Reuse the weather sensors you already have from the
ad-Weatherapp. - Setup – Simply enable the
use_ad_weatherflag in the Lightwand config; the app will subscribe to the same sensor updates.
🛠️ Safety check on input_select updates
- The app now verifies that an option actually exists in an
input_selectbefore attempting to update it, preventing unnecessary errors when a new option is added or removed.
🔄 MQTT namespace consistency
- The default MQTT namespace has been switched to
mqttto align with AppDaemon documentation and to keep the naming consistent across all of my apps.
Improvements
| Area | Change |
|---|---|
| Configuration | Default MQTT namespace updated to mqtt. |
| Code quality | Minor refactoring for readability and maintainability. |
| Safety | Added existence checks for input_select options. |
Compatibility
- Custom MQTT namespace – If you are using MQTT make sure to update the
mqtt_namespacekey in your Lightwand config or simply remove it if your namespace is called 'mqtt'.
Changelog
For a line‑by‑line diff, view the full changelog on GitHub:
Credits
- Developer – @Pythm (first contribution via PR #20)
- Thanks to the community for continuously testing and providing feedback.
Enjoy the new features, and feel free to open issues or PRs on the repo if you spot anything or want to contribute!