The entity dialogs for local weather, humidifier, and water heater entities acquired 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 simple 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 a good way to deliver extra functionalities immediately into your dashboard, while not having to open the extra information dialog.

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

Screenshot of tile playing cards with the brand new options.

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

Now you can combine your garden mower into House Assistant!
By no means fear concerning 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 an eye fixed out for different integrations!

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

When establishing a helper, typically 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 once you create or change a bunch helper.

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

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

Screenshot of making a sensor group.

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

From the UI you should use a template to set the state of the sensor.
You possibly can decide a unit of measurement, set the gadget class, and choose a state class.
Each sensors and binary sensors are supported.

This can make many of the use instances for template sensors obtainable by means of the UI and one much less want for YAML!

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

With the preview, you see a stay 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 can enable customers to fetch issues like calendar occasions and climate forecasts utilizing companies with responses and use them of their template entities. You possibly can even use OpenAI to set the worth of your entities now!

All variables from the motion block will probably be obtainable 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
        knowledge:
          start_date_time: "{{ today_at() + timedelta(days=1) }}"
          length:
            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 finished by calling a brand new service, climate.get_forecast, that may reply with the forecast.
You may as well specify what sort 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 sort, however it will possibly all be finished in 1 entity.

All climate integrations are up to date to help 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 may as well now decide what sort of climate forecast you wish to present in that card.

Screenshot of the climate extra information dialog.

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

This can make it attainable to have on-demand forecasts, that replace once you need them to, as a substitute of them being up to date on a regular basis.
It is going to additionally make the system sooner; all state knowledge will get despatched to your browser or cell app each time it’s opened so the frontend has the newest states of your entities. The forecast attribute makes the state of climate entities very large, inflicting the whole lot to be loaded slower.

Whereas the best way to entry this knowledge has modified and will affect your automations, you’ll not expertise any loss in performance. Even with this variation, relaxation assured that the forecast playing cards in your dashboard will nonetheless work, they’ll now simply use the service to retrieve the forecast knowledge asynchronously as a substitute of studying it from the state attribute. The top result’s that your dashboards will load sooner, and the frontend will probably 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
        knowledge:
          sort: 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 device when you perceive the way it works, one half that was usually neglected is its related studying curve.
We are actually actively working to flatten that curve with the intention to get extra from your property sooner and easier.
This launch reveals the primary results of that effort, a brand new onboarding movement.

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

Screenshot of the onboarding display screen.

There are lots of extra enhancements on this launch; listed here are among 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 can be dealt with by different (present) 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 a part of us!