#httpswww toptal
1 messages ยท Page 1 of 1 (latest)
that should be the whole unfiltered log, just for that period of time
i searched for '00:' just to make it easire to scroll through, but that should still include everything, right?
like just copy and paste from /config/logs, yeah?
yeah that still looks like everything https://www.toptal.com/developers/hastebin/abeqefuhoj.php-template
unless theres some other way to do it that im missing
E11-N13 is the model
so it's a sengled bulb
Yeah
this is getting weirder
Double checked the actual log file in ha too and that same section is still 212 lines
are these on switches someone could be flipping?
is there any remote chance someone is physically turning them back on
sorry to ask... but the log makes no sense
Nah, i live alone. Only way I could see it turning back on is if the power goes, since the default state after a power failure is on, but that doesn't seem like it would be happening..
Could your coordinator be positioned in such a way that it is not receiving group messages destined for the bulb?
change the setting and try again?
what is odd
in the log... I see "executing off" with empty args
then we see an off attr report for cluster 6
and the HA state change
BUT
then we get several brightness reports with the brightness creeping up
followed by a report from the light telling us it is on again
and then the HA state change
can I have the diagnostic file from the light?
I've got an automation that changes the brightness based on a lux sensor, but that should turn off in the automation before the lights turn off, plus it doesn't say that it was triggered by that automation, plus it was a solid 30 seconds after the automation to turn both things off was executed
I'll grab the diagnostic
My coordinator is pretty central, it's not more than 10 ft away from the light
Do you have any automations that change the bulb brightness but with a long transition time, longer than 40s?
you do have state compare errors and template errors in the logs
not sure what they correlate to but I did see them
2022-07-07 00:49:27 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=automation.new_automation_4, old_state=<state automation.new_automation_4=on; last_triggered=2022-07-06T22:23:32.432125-04:00, mode=single, current=0, id=1650944951007, friendly_name=Persistent notification test @ 2022-07-06T22:37:34.458278-04:00>, new_state=<state automation.new_automation_4=on; last_triggered=2022-07-07T00:49:27.172448-04:00, mode=single, current=1, id=1650944951007, friendly_name=Persistent notification test @ 2022-07-06T22:37:34.458278-04:00>>
2022-07-07 00:49:27 INFO (MainThread) [homeassistant.components.automation.new_automation_4] Persistent notification test: Running automation actions
2022-07-07 00:49:27 INFO (MainThread) [homeassistant.components.automation.new_automation_4] Persistent notification test: Skipped disabled step call_service
2022-07-07 00:49:27 INFO (MainThread) [homeassistant.components.automation.new_automation_4] Persistent notification test: Skipped disabled step condition
2022-07-07 00:49:27 INFO (MainThread) [homeassistant.components.automation.new_automation_4] Persistent notification test: Executing step call service
2022-07-07 00:49:27 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: 'dict object' has no attribute 'state' when rendering '{{trigger.to_state.attributes.method~"and"~trigger.state.domain}}'
2022-07-07 00:49:27 ERROR (MainThread) [homeassistant.components.automation.new_automation_4] Persistent notification test: Error executing script. Error for call_service at pos 3: Error rendering data template: UndefinedE
yeah im pretty sure those errors are from unrelated automations.
i do have some longer transitions in that are in that same automation that turns off, not sure how long so let me go see
on the same bulb?
2022-07-07 00:49:21 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x407D:1:0x0006]: executed 'off' command with args: '()' kwargs: '{}' result: Default_Response(command_id=0, status=<Status.SUCCESS: 0>)
this is the light right?
0x407D
thats the light
if you have a transition i'd expect to see move_to_level_with_on_off on cluster 8
not off on cluster 6
it should just be off, the only transition i have going on is specifically in this automation, between brightness levels, not from on to off
huh
are you setting the level when the bulb is off?
where is the automation again?
I need to look closer at that now
i suppose it actually could be possible that the automation is still running right when it turns off, so after the light turns off, it sees a change in lux and tells it to transition up to the desired brightness
sure
i'd expect to see calls to the bulb to do that though
unless the log is incomplete
this is the automation that actually triggers the lights shutting off, ill grab that one that is generally controlling the lights too, that ones kinda messy though
https://www.toptal.com/developers/hastebin/julitipefe.yaml
it shouldnt be incomplete, it was just a straight copy-paste
this is also the specific section that changes the transition, its the only one in the whole automation (the one i still need to link). iirc this equates to 1% per second
state_attr('sun.sun', 'elevation') > minelevation else 0 %}
{%set elevationinteger =
maxelevation-(maxelevation-hallwayoffset)-minelevation %}
{%set sensor = sensordarkvalue if
states('sensor.light_sensor_illuminance')|int < sensordarkvalue else
states('sensor.light_sensor_illuminance') %}
{%set brightness =
(maxbrightness-sqrt(((sensor|int-2)/350))*maxbrightness)|round%}
{% if brightness | int > maxbrightness %}
{{maxbrightness-(sqrt(elevation/elevationinteger)*maxbrightness)|round}}
{%else%}
{{brightness-(sqrt(elevation/elevationinteger)*brightness)|round}}
{%endif%}```
thats like
well, ill just link the whole automation rather than try to explain it ๐
so
lets do this
can you give us the full HA log
not just this short time period
something else is obviously happening
There is an automation that sets the transition dynamically:
transition: >
{%set elevation = state_attr('sun.sun', 'elevation') -
minelevation if
state_attr('sun.sun', 'elevation') > minelevation else 0 %}
{%set elevationinteger =
maxelevation-(maxelevation-hallwayoffset)-minelevation %}
{%set sensor = sensordarkvalue if
states('sensor.light_sensor_illuminance')|int < sensordarkvalue else
states('sensor.light_sensor_illuminance') %}
{%set brightness =
(maxbrightness-sqrt(((sensor|int-2)/350))*maxbrightness)|round%}
{% if brightness | int > maxbrightness %}
{{maxbrightness-(sqrt(elevation/elevationinteger)*maxbrightness)|round}}
{%else%}
{{brightness-(sqrt(elevation/elevationinteger)*brightness)|round}}
{%endif%}
You sure this should be transition: and not brightness: ?
yeah thats what i mentioned above
it should be that
that should equate to 1% per second, i believe
1% per second would mean a 0-100% transition would take longer than 40s and thus the original move_to_level command would not show up in your 40s log snippet
only happens at night. (well the only time this light is on is after sunset). im thinking maybe light turns off, but the automation hasnt turned off yet and so it tries to transition up from 0 to 75
im trying to post the full log, but it's not saving on the site ๐
turn off the transition automation
so it doesn't happen tonight
then see what happens when the other runs
easy test
DM the log file to one of us if it's too big to upload
the log is 34 mb and i dont have nitro, so i'm just gonna grab a snippet from that whole hour instead. think whats going on is probably in there
Try zipping it first
i might just end up leaving it on and checking tonight to see what actually happens. usually im in another room but if its actually fading up i can see that happen, otherwise ill turn it off and try again
2022-07-06 22:24:25 DEBUG (MainThread) [zigpy.zcl] [0x407D:1:0x0008] Sending request: move_to_level_with_on_off(level=191, transition_time=750)
Yep, you're sending these every 30s, with a 75s transition duration
every 30s? is it 75s every time?
2022-07-07 00:48:51 DEBUG (MainThread) [homeassistant.components.zha.core.channels.base] [0x407D:1:0x0008]: executed 'move_to_level_with_on_off' command with args: '(191, 750.0)' kwargs: '{}' result: Default_Response(command_id=4, status=<Status.SUCCESS: 0>)
wdym
sorry that wasn't for you
oh lol
you are using a 75s transition
BUT here is the deal
your light level is changing in the room
so the illum sensor is changing
and guess what happens
lol yeah. just the automation should be off at that point
search automation_triggered[L]: name=Living room Lights (Variables)
in the log
542 times
yeah for every attr report w/ light that automation fires
followed by calls like this
move_to_level_with_on_off(level=181, transition_time=710)
i dont understand how the lux sensor is triggering it every 30 seconds when the sensor hardly changes after the sun goes down
that sensor has 1375 reports in the log
[0x64E8:1:0x0400] Attribute report received: measured_value=
search that
they are hyper sensitive
the aqara illuminance sensors are VERY good
see, until recently i had it linked to smartthings which only reported whole number values
so you have a 75s transition
the illuminance values in the room are changing for the 75s
the sensor is reporting
i realized though that transition times are so long, because it should be new brightness-current brightness but i have it as just new brightness
the cycle continues