Releases: Pythm/ad-Lightwand
Improvements and bug fixes
Morning routines
What's Changed
Morning Routines:
It's flu season upon us so I added more options to keep lights off in bedrooms during the morning.
Use option 'prevent_night_to_morning' to keep lights in night mode if the room is set to night and automation switches from morning/normal. This is useful if you don't have working bed sensors. Use reset mode or an input selector to switch back to normal settings.
Mode Changes:
Enhancement: Automatically updates your 'selector_input' with the current mode for the room, ensuring seamless transitions and accurate mode tracking.
Updated readme on the input selector.
More flexibility on mode
What's Changed
Mode Changes
-
Enhanced
_appnamesupport:- Now, modes can be assigned specific applications. This means a mode will only activate within its designated room, using the format
_<appname>. Note: Existing modes with underscores may be affected—check logs for warnings.
- Now, modes can be assigned specific applications. This means a mode will only activate within its designated room, using the format
-
Customized Mode Names and Language Support:
- Default mode names have been updated to accommodate user language preferences stored in
translations.json. To maintain custom changes across updates, consider copying the file elsewhere. Configure your apps withlightwand_language,
- Default mode names have been updated to accommodate user language preferences stored in
-
Modify "MODE_CHANGE" Event Text:
- The text for the "MODE_CHANGE" event can now be customized using
translations.json, useful if similar events are already configured.
- The text for the "MODE_CHANGE" event can now be customized using
Light Control Enhancements
- HA Selector Integration:
- Define lighting options within a room using the HA selector. Configure this feature with
selector_inputunder options.
- Define lighting options within a room using the HA selector. Configure this feature with
Bed Sensors and Morning Routines
-
Added
out_of_bed_delayto bed sensors:- I tried to address issues with the Aqara FP2 losing detection when my kid is sleeping, and added an
out_of_bed_delayfor rooms you have bed sensors. This feature did not solve my problem.
- I tried to address issues with the Aqara FP2 losing detection when my kid is sleeping, and added an
-
Introduced
prevent_off_to_normaloption:- Useful for maintaining lights off when a room's mode is set to "off," preventing automatic transitions from morning to normal settings (e.g., when kids are home sick or teenagers sleep in). To revert to standard operation, use the reset mode function.
Full Changelog: v1.4.3...v1.5.0
Media player modes checks lux constraint and condition
What's Changed
- Media player modes now check for lux constrains and conditions as they are considered part of the normal day to day automation.
Due to lack of sun during winter here in Norway I missed this one in testing the bigger rewrite. Now it is finally re-implemented.
Added a pass state
What's Changed
- Added state
pass: Lights that runs a program, like the 'sunrise' effect in Philips Hue restarts the program every time it receives an command. With this state Lightwand will set light_data with the turn on command, but Lightwand will not send a new command if the light is on. - If motionlight is configured with automation it updates lights with light_data on given times if motion is active. With this update that automation will not run if mode is night* or off*.
- Minor fixes.
This fixes motionlights when using Adaptive Lighting
What's Changed
- Fixes a bug that was introduced late in development in 1.4.0 to motionlight when using Adaptive Lighting.
Lightwand Update: Zigbee2MQTT v2.0.0 Support, Enhanced Logic, and Adaptive Lighting Improvements
Release Notes for Lightwand
-
Compatibility Update:
FixedOutLuxMQTT_2andRoomLuxMQTTto ensure compatibility with Zigbee2MQTT v2.0.0. -
Improved Logic:
- Rewritten underlying logic for better configurability and ease of use when setting up lights.
- The default state for all automations and modes is now
none, which activates if conditions are met. Theturn_onstate is no longer required to turn lights on.
-
Simplified Configuration:
- No need to define a state when:
- Using
offset. - Turning lights on.
- Using
- Adjusting light modes on motion detection now dims the brightness if the new mode specifies a lower brightness level.
- No need to define a state when:
-
New Feature: Adaptive Motion Control:
- Added support for
noMotion: Truein modes to prevent motion events from activating motion lighting. This is particularly useful when integrating with Adaptive Lighting. - Adaptive light brightness comparisons now convert max brightness percentages to better align with 0-255 brightness scales.
- Added support for
Updates and bugfix on Adaptive Lighting
Added option to use 'noMotion: True' in mode to prevent motion to activate when that mode is active.
Improvements to the changes between mode and motion when using Adaptive Lighting to set brightness and color temp.
v.1.3.7 introduced a Breaking Change when configuring max and min setting to be configured with 'max_brightness_pct' and 'min_brightness_pct' to better differentiate that they are in percent.
A wiki page has been added with documentation for configuring the use of Adaptive Lighting with Lightwand.
https://github.com/Pythm/ad-Lightwand/wiki/Combining-Lightwand-with-Adaptive-Lighting-Custom-Component
Breaking change in configuration of Adaptive Lighting
What's Changed
- Adaptive lighting max and min setting is now 'max_brightness_pct' and 'min_brightness_pct' to better differentiate that they are in percent as suggested by @pointlevel
- Setting mode with higher brightness than motion should now work
Contributors
Assets 2
Workaround for issue #16
A workaround for issue #16
Check issue for documentation on how to avoid brightness turning down when motion.