LOOP & on_empty_queue does'nt get's triggered in night mode when "clock" screen expires about esphomatrixv2 HOT 9 CLOSED

thx for looking into it.
As state i am using a workaround now, so take your time :-)

from esphomatrixv2.

@andrewjswan @lubeda Tested your new PR (tag: 2024.4.1) and it's working as expected.
closing this now thx

from esphomatrixv2.

Wait a minute until the lifetime is over and "on_empty_queue" is not triggered.

Night mode simply skips this screen and does not take it into account and does not count its lifetime, but since it is there, then the queue is not empty. According to the log, it looks like this screen is not allowed for night mode, so it just quickly spins into emptiness.

from esphomatrixv2.

Got you.
So a new trigger like "on_empty_queue_night_mode" would be a solution?

If i do not take this into account my screen will be empty in night mode.

With such a new trigger, i can react an fill thje queue again.

from esphomatrixv2.

So a new trigger like "on_empty_queue_night_mode" would be a solution?

It seems to me that it is superfluous, we need to find where to view the queue and assess whether it is over or not. I'll try, but I don't promise.

from esphomatrixv2.

It looks like I found the reason, but I'm not sure.

from esphomatrixv2.

The night mode loop and missing "on_empty_queue" trigger is sadly not working with your fix.

But please set the initial brightness not to 255 (= full blast)!
You have set both to 255, so it will dim down from full blast rather than dim up (which i think is better, especially when you have the clock in your sleeping room :-)

So please set it to

    uint8_t brightness_ = 0;
    uint8_t target_brightness_;

PS.: target_brightness_ will be initialized from the pathon CONF variable, so no need to set.
But when you want to be sure they are initialized also when there is an python CONF parsing change,
please set it to:

    uint8_t brightness_ = 0;
    uint8_t target_brightness_ = 0;

thx

from esphomatrixv2.

The night mode loop and missing "on_empty_queue" trigger is sadly not working with your fix.

Any log?

from esphomatrixv2.

PR updated ...

from esphomatrixv2.