#httpswww toptal

1 messages ยท Page 1 of 1 (latest)

junior valley
#

how are you filtering this? would you be willing to share an unfiltered log?

kindred lily
#

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?

junior valley
#

nah i want the entire HA log

#

from that time period pls

kindred lily
#

like just copy and paste from /config/logs, yeah?

#

unless theres some other way to do it that im missing

junior valley
#

the log makes no sense

#

what type of bulb is it?

kindred lily
#

E11-N13 is the model

junior valley
#

so it's a sengled bulb

kindred lily
#

Yeah

junior valley
#

this is getting weirder

kindred lily
#

Double checked the actual log file in ha too and that same section is still 212 lines

junior valley
#

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

kindred lily
#

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..

shut finch
#

Could your coordinator be positioned in such a way that it is not receiving group messages destined for the bulb?

junior valley
#

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?

kindred lily
#

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

shut finch
#

Do you have any automations that change the bulb brightness but with a long transition time, longer than 40s?

junior valley
#

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
kindred lily
#

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

junior valley
#

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

kindred lily
#

thats the light

junior valley
#

if you have a transition i'd expect to see move_to_level_with_on_off on cluster 8

#

not off on cluster 6

kindred lily
#

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

junior valley
#

huh

#

are you setting the level when the bulb is off?

#

where is the automation again?

#

I need to look closer at that now

kindred lily
#

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

junior valley
#

sure

#

i'd expect to see calls to the bulb to do that though

#

unless the log is incomplete

kindred lily
#

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 ๐Ÿ˜…

junior valley
#

so

#

lets do this

#

can you give us the full HA log

#

not just this short time period

junior valley
#

something else is obviously happening

kindred lily
#

(automation mentioned above)

#

yeah i can do that

junior valley
#

ty

#

also is this something that is happening regularly?

shut finch
#

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: ?

kindred lily
#

yeah thats what i mentioned above

#

it should be that

#

that should equate to 1% per second, i believe

shut finch
#

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

kindred lily
junior valley
#

that's what we are thinking

#

so

#

here is a thought

kindred lily
#

im trying to post the full log, but it's not saving on the site ๐Ÿ˜…

junior valley
#

turn off the transition automation

#

so it doesn't happen tonight

#

then see what happens when the other runs

#

easy test

shut finch
#

DM the log file to one of us if it's too big to upload

kindred lily
#

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

shut finch
#

Try zipping it first

kindred lily
# junior valley turn off the transition automation

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

junior valley
#

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)

shut finch
#

Yep, you're sending these every 30s, with a 75s transition duration

junior valley
#

it's in the log 714 times

#

not sure that is doin what you want ๐Ÿ˜„

kindred lily
#

every 30s? is it 75s every time?

junior valley
#

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>)

kindred lily
#

wdym

junior valley
#

sorry that wasn't for you

kindred lily
#

oh lol

junior valley
#

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

kindred lily
#

lol yeah. just the automation should be off at that point

junior valley
#

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)

kindred lily
#

i dont understand how the lux sensor is triggering it every 30 seconds when the sensor hardly changes after the sun goes down

junior valley
#

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

kindred lily
#

see, until recently i had it linked to smartthings which only reported whole number values

junior valley
#

so you have a 75s transition

#

the illuminance values in the room are changing for the 75s

#

the sensor is reporting

kindred lily
#

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

junior valley
#

the cycle continues

kindred lily
#

so that should fix the transition times part

#

and yeah i see what you mean, i didnt realize this sensor was so sensitive ๐Ÿ˜