2024.4: Organize all the things!

[inkblotadmirer]

Well, I started with the trigger-based template sensor linked by Taras but I got that same error. So I tried modifying it based on the quick blurb in your post to which I replied.

So I thought these were automations that created/updated a sensor but I obviously don’t have the syntax down correctly. Ideally I want the sensor instead of the weather entity but I get the same error in either case. I’m going to keep spending time on it, I usually get these things, but I’m certainly missing something from the examples I’ve seen linked.

From your reply, it appears I don’t want an automation but I create a sensor with the trigger? (I haven’t used one of these as of yet, thus my confusion). That makes sense, I saw the triggers and assumed it was an automation.

And as to Mariusthvdb question, I was (apparently incorrectly) creating an automation and it’s my default to include the initial_state in case I want to disable it by default for some reason. Yes, I know I can flip a switch in the UI, old habits die hard.

[petro]

Yeah, this stuff goes in the template section of your configuration.yaml. There’s an example in the documentation to make a sensor from a weather get_forecasts call.

[123 (Taras)]

@inkblotadmirer

started with the trigger-based template sensor linked by Taras but I got that same error

There are two links in my post:

2024.4: Organize all the things!

This might be helpful. It shows how to create a Trigger-based Template Sensor to periodically get the daily weather forecast and store it in an attribute named forecast. Then you simply point forecast_daily_template to that Template Sensor’s forecast attribute. The example also shows how to round the weather values but that’s completely optional. If you don’t need rounding, there’s a simpler version of the Trigger-based Template Sensor shown here.

Which link did you use and what was the exact error message?

[sparkydave (🇦🇺 Dave)]

Yes, but nothing else is. ie: input_booleans etc. So basically all the other stuff we have in Packages other than Automations are not saved in YAML when done through the UI.

[frenck (Franck Nijhof)]

This is not a frontend FR, the backend isn’t there.

[Mariusthvdb (Marius)]

sorry, I didnt realize that.

Ive opened a FR for it in Backend also.
hope it can be done

[Mariusthvdb (Marius)]

@inkblotadmirer

And as to Mariusthvdb question, I was (apparently incorrectly) creating an automation and it’s my default to include the initial_state in case I want to disable it by default for some reason. Yes, I know I can flip a switch in the UI, old habits die hard.

ha yes, I relate to that …

tbh, I was surprised it still is an option but after some serious searching (it isnt written in the docs of the automation integration, or clicking through to go to Basics) I found it here Automation YAML - Home Assistant

disabling an automation ‘should be done’ by toggling a conditional (boolean), so we are told, so that might be an idea to get those old habits out of the way

tbh, I wished we would finally get the initial on those booleans in the UI, as that would really be helpful, and there is a long standing FR for it…

[crashingdutchman (JD)]

For me it fixed itself after there was a message in HA for loading a new frontend.

[snaky69]

This release causes me a ton of CPU issues using native automations and integrations.

It locks up after a few hours. Reverting back to 2024.3.3 until this is fixed. They did something to the event bus that broke automations that have worked flawlessly for years here.

[snaky69]

This happens to me as well. It’s due, at least on my end, to HA pegging the CPU at 100% and locking up. Reverting back to 2024.3.3 fixes it. Check your CPU usage.

[inkblotadmirer]

Thanks to all who chimed in on this to help. Taras, you can ignore my problem with your link because I was putting sensors/weather entities in the automation (my misunderstanding based on the presence of triggers and actions).

I did get the new forecast to work and can now proceed to get all my weather-related sensors updated based on this. For the record, I have a package “climate.yaml” included from configuration.yaml, and this is the sensor:

template:
  - trigger:
      - platform: time_pattern
        minutes: /30
      - platform: homeassistant
        event: start
    action:
      - service: weather.get_forecasts
        data_template:
          type: hourly
        target:
          entity_id: weather.nws_weather
        response_variable: hourly
    sensor:
      - name: "NWS Forecast Now Trigger"
        state: "{{ hourly['weather.nws_weather'].forecast[0].condition }}"
        attributes:
          forecast: "{{ hourly['weather.nws_weather'].forecast }}"

Ref: Forecast Depreciation - #2 by 123

From day one, the logic behind HA configuration is not intuitive for me (not saying it’s wrong, it just doesn’t work the way I think). Pair that with yaml syntax and I loathe making changes. I appreciate the patience with what in hindsight are silly errors.

[Mariusthvdb (Marius)]

simply waiting here without reporting in the core repo wont solve anything for you. please check the open issues, and if required, add one with your specifics so the dev team can at least be notified.

@HK-47

[aleco]

It’s great to see the integration startup times, but it’s frustrating to see how slow homekit_controller startup time is. 25 seconds on a Raspi 4, managing 25 devices. Do others experience a similar issue? Is there any way to improve its startup speed?

[rjing001]

but the basic ability is already there, no reason they couldn’t do it.

[urbo83 (Carles)]

I found a missing change in the release notes about the Entity filter card. Now it supports the conditions variable (see `conditional` & `entity-filter`: add ability to filter through `entit… · home-assistant/home-assistant.io@87311ae · GitHub). This new configuration variable doesn’t support attributes yet.

I noticed this change because the legacy state_filter stopped working after the update (I’m on 2024.4.2). I will open a bug later today.

[JoeSydney]

I had the same issue, and found the documentation that says that zones can be added and managed through the user interface at Settings → Areas & Zones

[AlexHu (Alex)]

Yesterday, I spent an afternoon enjoying this new update.
Today, I woke up to an unresponsive UI.

Web client doesn’t do anything but show the HA logo, Nabu Casa says my instance is disconnected and I dont have any means to access the system.

All automations seem to work, though, so I doubt it is a hardware issue.

Odroid N1 running HAOS.
Any pointers are welcome.

[boheme61]

How to help us help you - or How to ask a good question.
Start reading, from point 9 (above direct link)

Check your logfiles ( No Samba or SSH Access ?, then your left with HA-Console, get familiar with it by typing -help )

I Assume you are familiar with basic troubleshooting procedures, quite similar as with PC/Phones ( I.E Restart/Reboot )

[parautenbach (Pieter Rautenbach)]

Not here.

Do you have cameras in that list and are you splitting it out to individual controllers as recommended in the docs?

[aleco]

My 25 homekit devices are mostly from Eve (the TRVs, the wall plugs, the motion sensors), plus a few Nanoleaf lights. I’m not sure if I could/should split these somehow, I just have a single thread network and one homekit_controller instance.