2024.5: Just a little bit smaller

I think that the trigger for the template sensor would be any of the entities you use in the sensor, in this case:

Entity: sensor.pc321_power_l1
Entity: sensor.pc321_power_l2
Entity: sensor.pc321_power_l3

I have added the availability statement into the template

Hi, thank you for your patience.
I modified the configuration and after a couple of hours i can see it has no effect.
There’s something wrong in 2024.5

yes I know. I thought it was initially a network issue because I saw errors in the HA logs, but my linux box tcp monitoring never saw it fail (for months). HA just lost it for some reason. I was busy for a few days and not home so I could not troubleshoot, but it has been stable since upgrading to 2024.5.2.

1 Like

Seriously. I copied the same code of power_ac sensor in the template editor

EDIT: after some tests i can say it does not refresh all the sensor states so it do math always with new l3 value and old l1 and l2 values. On the contrary the template editor engine works correctly.
Changed trigger to

      - platform: state                                              
          - sensor.pc321_power_l1
          - sensor.pc321_power_l2                                                                                                             
          - sensor.pc321_power_l3 

and it seems to have solved the issue.
Before 2024.5 it was working with only l3.
Repeating entity_id: before each sensor does not work, i think the last one overwrites previous ones.

EDIT2: Too soon, it still have some unusual spikes, never did before 2024.5

EDIT3: Checking the history veery closely is clear the template just fires 3 times in the same second, one for each sensor in the trigger, so the first 2 times the value is wrong but it’s stored in the graph and the last is correct and it’s the one i see in the frontend. So before 2024.5 was i simply lucky to use trigger with only sensor l3 as it was the last updated?
Looks like someone added a DoEvents() in the code somewhere before finishing read the full mqtt message…

EDIT4: The last sensor to update now is l1 so the code works exactly as before 2024.5 if i trigger to l1 only, however i don’t think this is the proper way to do things…

I was previously in 2024.3.3 which seemed to work with my sonoff devices. Since the upgrade, after a while, the states stop updating. If I switch the lights on, the state goes back to off but the light remains on and vice versa.

I know you are new here, but you provide none of the information required. How to help us help you - or How to ask a good question

Has anyone else’s Lutron Pico switch button press events stopped working after upgrading to 2024.5? I moved from 4.4 to 5.3 recently and HA stopped taking action on my switch button presses. The button presses show up in the HA Log/History but the Scenes don’t work. I didn’t see any breaking changes called out.

Following on, here is what I see:

  • Automations that listen for Pico button presses - no longer work
    – Pico button press is registered in HA log
    – Manually running the automation (with lights turned on and off) works
    – Looks like the automation isn’t triggering anymore. No changes to the Lutron events or my devices as far as I can see?

  • Automations that listen for Motion sensor events - continue to work fine (motion sensor triggers HA, automation picks up the event and executes)

This is with a RadioRA2 (Lutron plug in) set up.

So what does your automation trace say?

Also the automation yaml is missing from your post.


If the actual Automation from Settings > Automation & Scenes > (my automation) > Run works fine, does Automation Trace help?

The actual yaml is pretty straightforward and I confirmed my Lutron entity names haven’t changed

- alias: Bedroom Pico Off
    - platform: event
      event_type: lutron_event
        id: bedroom_pico_off
        action: single
    - service: light.turn_off
        entity_id: light.bedroom_lamp

This will just run the ‘action’ part of your Automation, so doesn’t test the actual Triggers or Conditions (for automations that have them).

Thanks @sparkydave – so yes, I think somehow with that automation yaml, I am not getting the Trigger.

I checked Developer Tools > States > event.bedroom_pico_off does exist (as before the upgrade), but I think the same automation yaml is no longer triggering…

Yes it does (or may).

I keep getting a notification about a Core update (2024.5.4). When I try and update, however, it doesn’t actually seem to update. I get the notification again shortly after.

EDIT: I should also mention I can’t find anything in the logs at all about an attempted update.

I have HA installed on a docker on an iHost. Prior to the update to the katest version, my HA would show correct status of all lights. Since the update, the states always revert to the previous state. Is there anything I can attach here to get you the information you need?

look in your supervisor logs, not HA logs.

Installed 2024.5.4 but having issues with mqtt mosquitto broker. I didn’t have time to look, so rollback ongoing. Seems connect / disconnect directly for all client.

You’ll have to clarify what you mean. The broker is not tied to the HA version.

1 Like

Thanks! Below is the error I appear to be receiving.

2024-05-17 09:49:52.710 ERROR (MainThread) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/yellow-homeassistant:2024.5.4: 404 Client Error for http+docker://localhost/v1.44/images/ghcr.io/home-assistant/yellow-homeassistant:2024.5.4/json: Not Found ("No such image: ghcr.io/home-assistant/yellow-homeassistant:2024.5.4")
2024-05-17 09:49:52.711 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed

are you out of disk space?