Open Dualdriven opened 7 months ago
Not sure if it's the same problem, but I had the same problem with service actions, but once I switched to device actions, it worked.
I have the same issue, I think it's since the last update. My scenes are controlled through node red with a "light-turn on" command combined with brightness/color data.
After updating HA yesterday I've also been having a similar issue with 1 bulb (Tradfri LED2003G10) that refuses to adapt either via automation or from a light.turn_on
service call.
Home Assistant Adaptive Lighting Issue Template
Please confirm that you have completed the following steps:
Required information for bug reports:
Please include the following information in your issue.
devices.yaml
n.a.groups.yaml
n.a.configuration.yaml
Load frontend themes from the themes folder
frontend: themes: !include_dir_merge_named themes extra_module_url: /config/www/community/lovelace-card-mod/card-mod.js
automation: !include automations.yaml script: !include scripts.yaml scene: !include scenes.yaml sensor: !include sensors.yaml light: !include lights.yaml template: !include templates.yaml input_boolean: !include input_boolean.yaml group: !include groups.yaml notify: !include notify.yaml
homeassistant: name: Thuis latitude: !secret latitude longitude: !secret longitude elevation: !secret elevation unit_system: metric currency: EUR country: NL time_zone: "Europe/Amsterdam" temperature_unit: C internal_url: !secret internal_url packages: !include_dir_named packages customize: !include customize.yaml
recorder: db_url: !secret mariadb_url commit_interval: 20 purge_keep_days: 30
influxdb: host: !secret influxdb_host port: 8086 database: !secret influxdb_database username: !secret influxdb_user password: !secret influxdb_pass max_retries: 3 default_measurement: state include: #include entities domains:
http: ip_ban_enabled: true login_attempts_threshold: 3
blueprint: name: Motion-activated Light based on Sun Elevation domain: automation source_url: https://community.home-assistant.io/t/motion-activate-light-or-switch-based-on-daylight-sun-elevation/265010 input: motion_entity: name: Motion Sensor selector: entity: domain: binary_sensor device_class: motion light_target: name: Light selector: target: entity: domain: light default: "" below_elevation: name: Below sun elevation description: Solar elevation. This is the angle between the sun and the horizon. Negative values mean the sun is below the horizon. default: 3 selector: number: min: -90.0 max: 90.0 unit_of_measurement: degrees step: 1.0 mode: slider mode: restart max_exceeded: silent trigger: platform: state entity_id: !input "motion_entity" from: "off" to: "on" variables: below_elevation: !input "below_elevation" condition:
Steps to reproduce the behavior: Turn on lights with automation and turn on lights manual.
Other I have no clue why it is not working since the blueprint is still using the service light.turn_on AL should intercept it. Also I saw the log is saying that the lights are manually controlled which isn't the case (100% sure) since I waited for the lights to turn on by the automation.
A other thought I had was changing the service from light.turn_on to adaptive_lighting.apply as in:
Thanks for your time!