2023.9: New local weather entity dialogs, a number of tile options, and template sensors from the UI!

The entity dialogs for local weather, humidifier, and water heater entities bought an replace, and in the event you ask me, it appears to be like completely gorgeous!
It now has a newly designed round slider exhibiting the present and goal temperatures and means that you can simply swipe to the specified goal temperature.
There are additionally devoted buttons to vary the goal, so it’s straightforward to make use of if you’re not utilizing a touchscreen.
It is going to glow within the center to point out its present motion, for instance when it’s heating or cooling.

Screenshot of the extra information dialog of a local weather entity.

The tile card will get many new options this launch.

The options of a tile card are an effective way to deliver extra functionalities immediately into your dashboard, without having to open the extra information dialog.

• HVAC mode
• Water heater mode
• Temperature management
• Cowl place
• Cowl tilt
• Garden mower instructions
• Colour temperature

Screenshot of tile playing cards with the brand new options.

A brand new entity kind was added this launch: the garden mower!

Now you can combine your garden mower into House Assistant!
By no means fear in regards to the garden mower when it begins raining, now you can automate the garden mower to cease and return when it rains.
For now, simply MQTT is supported, however maintain a watch out for different integrations!

Screenshot of the extra information dialog of a garden mower entity.

When organising a helper, generally it may be helpful to see how the entity that you’re creating appears to be like while you’re setting it up. That’s why we added a preview whenever you create or change a gaggle helper.

It is going to present precisely what the entity will appear to be with the present settings.

And speaking about teams, we additionally bought a brand new group, the occasion group!

Screenshot of making a sensor group.

We additionally added preview assist to a different helper that lastly made its method into the UI, the template sensor.

From the UI you need to use a template to set the state of the sensor.
You’ll be able to decide a unit of measurement, set the machine class, and choose a state class.
Each sensors and binary sensors are supported.

This may make a lot of the use instances for template sensors accessible by way of the UI and one much less want for YAML!

Different extra superior fields, like attributes, are unavailable from the UI. You’ll nonetheless should set these up in YAML.

With the preview, you see a dwell replace of the sensor worth whereas writing the template.

Screenshot of making a template sensor.

Set off template entities can now have an motion block that’s executed after the set off however earlier than the entities are rendered.

This may permit customers to fetch issues like calendar occasions and climate forecasts utilizing providers with responses and use them of their template entities. You’ll be able to even use OpenAI to set the worth of your entities now!

All variables from the motion block will likely be accessible within the template.

An instance that checks at midnight in case you have one thing in your calendar tomorrow and units a binary sensor:

template:
  - set off:
      - platform: time
        at: "00:00:00"
    motion:
      - service: calendar.list_events
        goal:
          entity_id: calendar.calendar
        information:
          start_date_time: "{{ today_at() + timedelta(days=1) }}"
          period:
            hours: 24
        response_variable: occasions
    binary_sensor:
      - identify: Calendar occasions tomorrow
        state: "{ rely > 0 }"

We added a brand new service for climate entities, climate.get_forecast, that responds with the climate forecast.

Beforehand you would need to take a look at the forecast attribute of a climate entity to get the forecast, now this may be achieved by calling a brand new service, climate.get_forecast, that can reply with the forecast.
You may also specify what kind of forecast you need. Do you wish to see the forecast by day or do you wish to comprehend it for each hour? This implies you now not want separate entities for each forecast kind, however it will probably all be achieved in 1 entity.

All climate integrations are up to date to assist this new service.

Screenshot of service developer instruments exhibiting the climate forecast service.

If an entity helps a number of forecasts, you’ll be able to select which forecast you wish to see within the extra information dialog.
Within the climate card in your dashboard, you can too now decide what sort of climate forecast you wish to present in that card.

Screenshot of the climate extra information dialog.

With this transformation, the forecast attribute of the climate entity is deprecated, and will likely be eliminated in House Assistant Core 2024.3.

This may make it attainable to have on-demand forecasts, that replace whenever you need them to, as an alternative of them being up to date on a regular basis.
It is going to additionally make the system quicker; all state information will get despatched to your browser or cellular app each time it’s opened so the frontend has the most recent states of your entities. The forecast attribute makes the state of climate entities very massive, inflicting every little thing to be loaded slower.

Whereas the way in which to entry this information has modified and should affect your automations, you’ll not expertise any loss in performance. Even with this transformation, relaxation assured that the forecast playing cards in your dashboard will nonetheless work, they are going to now simply use the service to retrieve the forecast information asynchronously as an alternative of studying it from the state attribute. The top result’s that your dashboards will load quicker, and the frontend will likely be leaner.

You should utilize the newly added motion a part of a template entity to fetch the forecast and use it in your template:

template:
  - set off:
      - platform: time
        at: "00:00:00"
    motion:
      - service: climate.get_forecast
        goal:
          entity_id: climate.residence
        information:
          kind: day by day
        response_variable: forecast
    binary_sensor:
      - identify: Is it going to rain?
        state: "{{ forecast.forecast[0].precipitation > 0 }}"

Whereas it’s sure that House Assistant is a good instrument when you perceive the way it works, one half that was typically missed is its related studying curve.
We at the moment are actively working to flatten that curve with the intention to get extra from your private home quicker and less complicated.
This launch exhibits the primary results of that effort, a brand new onboarding move.

One thing you in all probability haven’t seen for some time, however we gave our onboarding a contemporary new look! It’s shortened to get customers in House Assistant as quick as attainable, to allow them to take pleasure in tinkering with their residence quicker!

Screenshot of the onboarding display screen.

There are a lot of extra enhancements on this launch; listed below are a few of the different
noteworthy modifications this launch:

We welcome the next new integrations on this launch:

This launch additionally has a brand new digital integration. Digital integrations are stubs which might be dealt with by different (current) integrations to assist with findability. These are new:

House Assistant has an awesome group of customers who’re all greater than prepared
to assist one another out. So, be part of us!