Error doing job: Task exception was never retrieved after update to v1.18.0 #682
Comments
bouwew
changed the title
|
It seems like your adapt_color switch is not properly initialized for some reason. Are you sure there were no more errors messages at the start of the logs? |
|
No, no other errors, just these two. Sorry, I'm looking at the HA LOG once more, the error is present in HA 2023.7.3 too: |
|
I will downgrade to v1.17.5 to see if that make a difference. Update: after the downgrade I see a similar error in the HA LOG. Update 2: hmm, I'm still seeing v1.18.0 in the manifest.json file. I'll try to downgrade once more. Update 3: Now the downgrade succeeded. Checking the logfile... Update 4: with v1.17.5 installed the error is gone. And my lights I'm testing with are working normally again. |
|
Hi, I can also confirm this in the logs after updating to 1.18.0: This happens when I flash lights in control of Adaptive Lighting (using device type in automation or the light.turn_on service with flash option). Usually the light flashes for 1 to 3 seconds and is not even turned on. Since AL 1.18.0 the lights stay on until their dedicated automation (switches on by motion triggers) turns them off after time. Interestingly, when running the flash service manually I sometimes get additionally to AL log entry I see all of this for the very first time since AL 1.18.0 update. I used an older version before, I think it was 1.14.0. Also checked former HA log prior to the restart (2023-07-01 until 2023-07-29) and beginning of effective usage of 1.18.0 - yes, 100 % been introduced with AL 1.18.0, former HA log only contained other AL entries which had no practical impact afaict. |
|
@bouwew could you share your script.turn_up_k_lights script? |
|
@bcutter I’ll check what happens with the flash. Is the expected behavior that the lights turn off after flashing? |
|
Same here. Lights turn on, but stay at 1% brightness after upgrade to v1.18.0. |
|
@giannoug, do you know what you did to trigger error? |
|
@basnijholt I updated yesterday at around midnight. I believe lights were working correctly before I went to bed. Today afternoon it seems that they do not work (I use the Sensor Light automation). BTW I have an issue where lights controlled by this automation turn on at 1% brightness and then take either a second or a couple more to turn to the correct color. I haven't found time to fix that yet. Here's the weird part. Lights controlled by the automation above have the issue reported here and lag when turning on. Lights controlled by switches do not seem to be affected by these bugs 🤔 My first guess when I was trying to debug the 1% brightness issue I have was transitions, but I'm a bit new to HA and all these stuff so I hit a wall fast. |
After flashing the light should turn back to its previous state. So yes, if it is off and it flashes, it should turn off again. I am not sure and can't test it currently, but it might be the light's entity state might even not been |
|
@bouwew, your issue is solved in #686. This is a strange race condition which happens when initializing the AdaptiveSwitch is done before initializing the other switches (e.g., This condition has been present in all previous versions, however, for some reason it is more likely to occur now. |
|
I'm not seeing the errors in log, but my automatic lights still seem to be stuck at 1% 🤔 Lights controlled by switches seem fine though. Anyway this should be the other issue I'm having |
|
If you can enable debugging logging and share them I can help you better |
|
Didn't think of that. It has some interesting info there. It shouldn't be marking them as manually controlled. Maybe because I'm using the Hue group and the Hue integration is doing something weird under the hood? If you feel this is out of scope, we can move discussion in another issue. |
|
I see, this means that you are turning on the lights outside of Home Assistant, and Home Assistant is only picking up the state change. Whenever You need to enable |
|
I'm not turning on the lights outside of Home Assistant though. The lights should be turned on by the automation (through HA). I see I've mixed groups in Adaptive Lighting and the automation. For example, I had set Checking with debugging logging to see if anything interesting comes up |
|
Ok good to know! Thanks for your patience. Would you be able to share how you configured that automation? Maybe it’s turning on devices instead of entities. |
|
Here are some logs. The Adaptive Lighting integration I'm debugging is "Lounge automatic lights" which includes two entities,
|
|
@giannoug, when I read your logs it seems like AL is adapting the lights you mentioned. Here you turn on the lights (with your automation?) This might indeed be due to a transition in your Unfortunately, it is Home Assistant that reports these state changes and this cannot be sped up. |
|
BTW currently, AL can only do instantaneous adaptation with single lights. After #679 is merged you likely will see instantaneous changes for the |
|
@basnijholt I've upgraded to v1.18.2. I can confirm that the errors in HA LOG are gone 👍 But, unfortunately, this script does not give the correct result, the group of light doesn't turn off: The group of lights turns on OK based on movement detection, but the group does not turn off when the related timer ends. |
Lights that worked yesterday with switches, stay at 1% today 🥴 How does AL know a switch is a group or a single light? From what I undestand, grouped lights are on the Hue level and exposed to HA as a single one |
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.
In HA Core v2023.8.0b1 (I don't see the errors when I roll back to v2023.7.3) I see these errors in the LOG:
I also see this Error:
devices.yamlgroups.yamlconfiguration.yamlserver:user:password:pan_id:network_key:log_syslogif you use thisDescribe the bug and how to reproduce it:
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: