(If using Zigbee2MQTT), provide your configuration files (remove all personal information before posting):
devices.yaml
groups.yaml
configuration.yaml ⚠️; WarningREMOVE ALL of the PERSONAL INFORMATION BELOW before posting ⚠️;
mqtt: server:
mqtt: user:
mqtt: password:
advanced: pan_id:
advanced: network_key:
anything in log_syslog if you use this
Brand and model number of problematic light(s)
N/a
Describe the bug and how to reproduce it:
Cannot get AL to configure through yaml (See initial warning in logs).
After encountering on my live config on 2023.7.3, I tried some debugging on a clean 2023.8.1 HA Config with demo entities and it reproduces.
Create clean HA environment with the provided yaml in the config file and observe the logs for the warning to appear.
Steps to reproduce the behavior:
See part 4.
Workaround to get past the warning.
After commenting out the lines that cause AL to preemptively stop, the config simply procedes and actually completes. Reverting this change and restarting HA causes the warning to be bypassed somehow as the entities had already been created. All works as expected from there on out... 🤔
Home Assistant Adaptive Lighting Issue Template
Bug Reports
If you need help with using or configuring Adaptive Lighting, please open a Q&A discussion thread here instead.
Before submitting a bug report, please follow these troubleshooting steps:
Please confirm that you have completed the following steps:
Required information for bug reports:
Please include the following information in your issue.
Issues missing this information may not be addressed.
Debug logs captured while the issue occurred. See here for instructions on enabling debug logging: (Got additional data in the debug logging for my own troubleshooting)
Your Adaptive Lighting configuration: Issue reproduces on HA
2023.8.1
with a clean config withdemo
entities.(If using Zigbee2MQTT), provide your configuration files (remove all personal information before posting):
devices.yaml
groups.yaml
configuration.yaml
⚠️; Warning REMOVE ALL of the PERSONAL INFORMATION BELOW before posting ⚠️;server
:user
:password
:pan_id
:network_key
:log_syslog
if you use thisDescribe the bug and how to reproduce it: Cannot get AL to configure through yaml (See initial warning in logs). After encountering on my live config on
2023.7.3
, I tried some debugging on a clean2023.8.1
HA Config with demo entities and it reproduces.Steps to reproduce the behavior: See part 4.
Workaround to get past the warning. After commenting out the lines that cause AL to preemptively stop, the config simply procedes and actually completes. Reverting this change and restarting HA causes the warning to be bypassed somehow as the entities had already been created. All works as expected from there on out... 🤔