House Assistant Core 2023.9! 🎉
Frenck is having fun with a nicely earned vacation, so I’m taking good care of the discharge this month.
This month, on the seventeenth, it has been 10 years since House Assistant began. We’ll be making ready a particular occasion on the Home Assistant YouTube channel to have a good time, mirror and look forward. We may have some cool bulletins too! We hope you’ll be able to be part of us on the seventeenth @ 12:00 PDT / 21:00 CET!
This launch is fairly packed! With some very good updates to the UI with new entity dialogs for local weather entities, and many tile card options. Template sensors will be created from the UI now, and for the extra superior template sensors, the flexibility to get information from providers!
A brand new service to get the climate forecast, and higher choices to show completely different forecasts.
And one thing you’ll in all probability not see if you find yourself already utilizing House Assistant: the onboarding move is totally redesigned!
I completely adore it!
Benefit from the launch!
Don’t overlook to join our release party live stream on YouTube
6 September 2023, at 12:00 PDT / 21:00 CEST!
New local weather, humidifier, and water heater entity dialogs
The entity dialogs for local weather, humidifier, and water heater entities received an replace, and in the event you ask me, it seems completely gorgeous!
It now has a newly designed round slider exhibiting the present and goal temperatures and permits you to 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 indicate 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 gets many new features this release.
The features of a tile card are a great way to bring more functionalities directly into your dashboard, without needing to open the more info dialog.
- HVAC mode
- Water heater mode
- Temperature control
- Cover position
- Cover tilt
- Lawn mower commands
- Color temperature
Screenshot of tile cards with the new features.
A new entity type was added this release: the lawn mower!
You can now integrate your lawn mower into Home Assistant!
Never worry about the lawn mower when it starts raining, you can now automate the lawn mower to stop and go back when it rains.
For now, just MQTT is supported, but keep an eye out for other integrations!
Screenshot of the more info dialog of a lawn mower entity.
When setting up a helper, sometimes it can be useful to see how the entity that you are creating looks while you are setting it up. That’s why we added a preview when you create or change a group helper.
It will show exactly what the entity will look like with the current settings.
And talking about groups, we also got a new group, the
Screenshot of creating a sensor group.
We also added preview support to another helper that finally made its way into the UI, the template sensor.
From the UI you can use a template to set the state of the sensor.
You can pick a unit of measurement, set the device class, and select a state class.
Both sensors and binary sensors are supported.
This will make most of the use cases for template sensors available through the UI and one less need for YAML!
Other more advanced fields, like attributes, are unavailable from the UI. You will still have to set those up in YAML.
With the preview, you see a live update of the sensor value while writing the template.
Screenshot of creating a template sensor.
Trigger template entities can now have an action block that is executed after the trigger but before the entities are rendered.
This will allow users to fetch things like calendar events and weather forecasts using services with responses and use them in their template entities. You can even use OpenAI to set the value of your entities now!
All variables from the action block will be available in the template.
An example that checks at midnight if you have something on your calendar tomorrow and sets a binary sensor:
template: - trigger: - platform: time at: "00:00:00" action: - service: calendar.list_events target: entity_id: calendar.calendar data: start_date_time: " today_at() + timedelta(days=1) " duration: hours: 24 response_variable: events binary_sensor: - name: Calendar events tomorrow state: " count > 0 "
We added a new service for weather entities,
weather.get_forecast, that responds with the weather forecast.
Previously you would have to look at the
forecast attribute of a weather entity to get the forecast, now this can be done by calling a new service,
weather.get_forecast, that will respond with the forecast.
You can also specify what type of forecast you want. Do you want to see the forecast by day or do you want to know it for every hour? This means you no longer need separate entities for every forecast type, but it can all be done in 1 entity.
All weather integrations are updated to support this new service.
Screenshot of service developer tools showing the weather forecast service.
If an entity supports multiple forecasts, you can choose which forecast you want to see in the more info dialog.
In the weather card in your dashboard, you can also now pick what kind of weather forecast you want to show in that card.
Screenshot of the weather more info dialog.
With this change, the
forecast attribute of the weather entity is deprecated, and will be removed in Home Assistant Core 2024.3.
This will make it possible to have on-demand forecasts, that update when you want them to, instead of them being updated all the time.
It will also make the system faster; all state data gets sent to your browser or mobile app every time it is opened so the frontend has the latest states of your entities. The forecast attribute makes the state of weather entities very big, causing everything to be loaded slower.
While the way to access this data has changed and may impact your automations, you will not experience any loss in functionality. Even with this change, rest assured that the forecast cards in your dashboard will still work, they will now just use the service to retrieve the forecast data asynchronously instead of reading it from the state attribute. The end result is that your dashboards will load faster, and the frontend will be leaner.
You can use the newly added
action part of a template entity to fetch the forecast and use it in your template:
template: - trigger: - platform: time at: "00:00:00" action: - service: weather.get_forecast target: entity_id: weather.home data: type: daily response_variable: forecast binary_sensor: - name: Is it going to rain? state: " forecast.forecast.precipitation > 0 "
While it is certain that Home Assistant is a great tool once you understand how it works, one part that was often overlooked is its associated learning curve.
We are now actively working to flatten that curve so that you can get more from your home faster and simpler.
This release shows the first result of that effort, a new onboarding flow.
Something you probably have not seen for a while, but we gave our onboarding a fresh new look! It is shortened to get users in Home Assistant as fast as possible, so they can enjoy tinkering with their home faster!
Screenshot of the onboarding screen.
There are many more improvements in this release; here are some of the other
noteworthy changes this release:
Enphase Envoy has gotten a lot of love this release, ensure it works
perfectly with the latest firmware available. Thanks @bdraco and @cgarwood!
- The Shelly integration now helps the Shelly Fuel Valve addon. Thanks @bieniu!
@starkillerOG added zoom buttons and AI detection delay time controls to
the Reolink integration. Good!
- Now you can set separate damping elements for morning and night within the
Forecast Photo voltaic integration. Thanks @joostlek!
- @Kane610 added a restart gadget button to the UniFi integration. Thanks!
- The Tomorrow.io integration now stories humidity and dew level in its climate
forecasts. Thanks @lymanepp!
- Assist for soil moisture sensors was added to the Gardena integration.
- @timmo001 added an influence service to the System Bridge integration. Thanks!
- If you happen to change your password, you’ll be requested if you wish to logout in all places.
- The file and picture add components have been revamped.
- Now you can kind the choices of an enter choose entity. Thanks @karwosts!
- Native Bluetooth has been optimized and is now sooner, thanks @bdraco!
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:
Home Assistant has a great community of users who are all more than willing
to help each other out. So, join us!
Discovered a bug or problem? Please report it in our issue tracker,
to get it fastened! Or, examine our assist web page for steering for extra
locations you’ll be able to go.
Are you extra into electronic mail? Signal-up for our Constructing the Open House E-newsletter
to get the newest information about options, issues occurring in our group and
different information about constructing an Open House; straight into your inbox.
You would possibly get false positives for leak detected and excessive move sensors in the event you
have previous unread notifications within the Flume app.
Earlier than, the leak detected and excessive move sensors would solely set off till you
learn the notification within the Flume app which was too late for House Assistant
to take any automated motion.
Now, they set off regardless when you have learn or not the notification. They’ll
stay lively till you delete the notification within the Flume app,
just like the previous habits documented.
The Météo-France climate entities have been up to date:
forecaststate attribute is deprecated and shall be eliminated in
House Assistant Core 2024.3, it’s best to as an alternative use the
- The config entry choice to pick hourly or each day forecast can now not be
adjusted, however any current configuration of the forecast interval shall be
revered till House Assistant Core 2024.3.
- Météo-France now gives a single climate entity which helps each
hourly and each day forecast.
maximum_boiler_temperature sensor entity has been changed by a quantity
entity, permitting management as nicely.
The extra schema state attributes of the local weather entity have been eliminated.
They’ve beeen beforehand changed by a choose entity.
The entity naming logic has been up to date to be much less brittle. In consequence,
zwave_js entities that you just haven’t given a customized identify to could also be renamed.
Since they’re registered within the entity registry, the entity IDs won’t change
and your automations ought to subsequently not be impacted by the change.
With this launch, you’ll need to replace your zwave-js-server occasion. You need to use zwave-js-server 1.31.0 or larger (schema 31).
If you happen to use the Z-Wave JS add-on, you want a minimum of model 0.1.88.
If you happen to use the Z-Wave JS UI add-on, you want a minimum of model 1.15.9.
If you happen to use the Z-Wave JS UI Docker container, you want a minimum of model 8.23.2.
If you happen to run your individual Docker container or another set up methodology, you’ll need to replace your zwave-js-server occasion to a minimum of 1.31.0.
In case you are a customized integration developer and wish to find out about breaking
adjustments and new options out there to your integration: You’ll want to comply with our
developer blog. The next are essentially the most notable for this launch:
In fact, there’s much more on this launch. You will discover a listing of
all adjustments made right here: Full changelog for House Assistant Core 2023.9