Blissful October! October is at all times a particular month for the challenge. It’s the
month all people begins engaged on their dwelling automations once more, the month that
Hacktoberfest brings in a lot of new contributions and contributors to the
challenge (👋 welcome!), and in addition this 12 months: the Month of “What the Heck?!”.
The Month of WTH already looks very promising,
and plenty of good and fascinating points, concepts, and strategies to streamline
have been proposed. Preserve these subjects and votes going ❤️.
Oh! And House Assistant Core 2022.10! 🎉
Final month’s launch was an enormous one; this month’s launch principally continues to
bettering on that. I suppose it’s no shock that the largest enchancment can
be discovered (as soon as once more) in Bluetooth! There may be much more, although this launch
is a bit “all over”, which is definitely kinda good.
Benefit from the launch!
../Frenck
PS: I seen the House Assistant SkyConnect is now accessible for pre-order 🥳
Don’t overlook to join our release party live stream on YouTube at present at 12:00 PDT / 21:00 CET!
Table of Contents
Marcel van der Veldt joins Nabu Casa
We are excited to announce that Marcel van der Veldt
has joined Nabu Casa!
Marcel is thought for his contributions to the Z-Wave integration,
the rewrite of the Hue integration, the
Music Assistant custom integration,
and plenty of extra!
Marcel goes to be engaged on Matter
help in House Assistant. Simply in case you missed it, Matter is now officially
available/released 🎉.
Welcome aboard Marcel!
Lively Bluetooth in all places
Two releases again, we introduced the Bluetooth integration.
The previous release we brought Bluetooth everywhere in your home by adding
support for Bluetooth Proxies.
Let’s not stop there!
In this release, those proxies now support active Bluetooth connections! 🤯
To explain this quickly: Previously, we could listen for Bluetooth devices
and only receive data via the proxies (passive connection); now, we can actively
set up a conversation with those devices and send data (active connection). This
adds the capability to extend the range of Bluetooth devices that can be
controlled đź’™.
For this occasion, ESPHome will have an additional release, which adds this
functionality. We have also updated our Bluetooth proxy installer website
to put in with help for energetic connections.
So, you need to management that SwitchBot Bluetooth system on the opposite finish of your
dwelling that appears out of attain? Now you’ll be able to by putting in a proxy on
a easy ESP32 system.
Oh! Bonus: the Bluetooth efficiency has been improved too! Particularly native
Bluetooth adapters must be fairly a bit sooner. 🚀
Help for iBeacons
This launch additionally provides help for iBeacons. These are Bluetooth-enabled units
that ship out identifiers to announce their location. House Assistant can
now decide these up and present an approximate distance to such an iBeacon.
iBeacons can open up loads of superior use instances for automations. For instance,
you possibly can connect an iBeacon to your automotive, so that you’ll know the automotive is at dwelling. Or,
on the trash can and use it to find out if the rubbish remains to be sitting within the
storage on pick-up day and ship out a notification.
Read more about iBeacons in our documentation.
Finding the right integration
For some brands of devices, we have multiple integrations available.
For example, we have a lot of “Google” integrations. Some brands provide devices
that can work via Zigbee or their matching hub, meaning you’d have a choice
of integrating their hub or using the devices directly via Zigbee
(e.g., using ZHA).
To make it more clear on the choices available, you can now categorize
integrations by brand. Home Assistant will show the options available
for that specific brand. For example, the “Google” brand:
This way, you no longer have to “find out” how your device could be integrated.
We now show if an integration uses “the cloud” or not, so you are aware upfront.
We often get questions about YAML-only integrations that cannot be found in the
user interface. While we love them to be available via the UI, we can
understand not finding them at all can be confusing.
To help with that, we now show all integrations when adding a new
integration, including those only available via YAML. While they cannot be
set up via the user interface, we now do provide links to the documentation
with the instructions on how to set it up.
Subviews for dashboards
This might be one of the coolest and most impactful features that has been
added to our Dashboards lately: Subviews!
Each view on a dashboard can now be marked as being a “Subview”:
Subviews won’t show up in the navigation bar of your dashboard, meaning
you can only navigate to them by using, for example, a navigation action on
a button.
When you navigate to a subview, the subview itself will not show the Dashboard
navigation bar. Instead, it will show a back button to the previous view
you came from.
Screen recording showing a Kitchen subview in action.
This allows for creating cool navigation concepts that are particularly helpful
on a mobile or tablet device.
All dialogs restyled
All dialogs that are shown in the Home Assistant have been slightly updated.
Most notably: The dialogs are now rounder on the edges, and the action buttons
have been styled and named more consistently. It brings Home Assistant closer
to version 3 of the Material Design that Home Assistant follows.
Viewing YAML automations in the automation editor
In the last release, we revamped our automation editor, and we are very
happy to read how many of you loved these changes ❤️
However, if you manage your automations manually in YAML, you’d always be
served an error message when trying to open an automation in the UI. Not very
helpful, right?
This has been improved! You can now open any automation (or script) in the
UI. This lets you view your automation, providing a quick glance at its
workings.
Besides, as a bonus, if you have considered moving your automation to the UI,
you can now view and experience how it would look/work for those automations
and import them into the UI with the click of a button in the top right.
Handling version numbers in templates
A new version() template function/filter has been added, allowing you to do
awesome things with version numbers in templates.
It allows for getting information about a version number, comparing version
numbers, and even checking the difference between two versions.
-
version("2022.10.0") > "2022.9.7"
Returns true, as2022.10.0is newer. -
(version("2022.10.1") - "2022.10.0").patch
Returns true, as the patch number of the version changed. -
(version("2022.10.1") - "2022.10.0").minor
Returns false, as there is just a patch difference. -
version("2022.10.0b0").beta
Return true, as this is a beta version.
version() can be helpful when building automations or Blueprints for
update entities. You could, for example, easier
decide to automatically upgrade or send more detailed notification messages
in case a patch version is available.
Google Sheets
This release introduces a new way to export data from Home Assistant:
Google Sheets.
With this integration, you can add new rows to a Google Sheet document
from a service call, allowing you to export data from automations for
further processing, visualization, or insights.
Export anything you like to a sheet in Google Sheets, like your energy usage.
Maybe you like to export your daily energy usage or keep track of the number
of diapers you have used in your baby feeding diary spreadsheet.
The possibilities with this are endless.
Other noteworthy changes
There is much more juice in this release; here are some of the other
noteworthy changes this release:
- The long-term statics card now uses the unit you have selected a sensor to
be in. So, if you’ve changed the sensor, it will now match! Also, more sensors
are now able to change/convert units. Thanks, @emontnemery and @epenet! - When eradicating integrations that use utility credentials, we’ll now ask
if you wish to clear up these credentials. Good contact, @allenporter! - The Netatmo integration bought a lot of love! It now helps the Netatmo
Doorbell, modulating thermostats and now additionally helps units from Legrand,
Bubendorff, BTicino and Smarther! Thanks @cgtobi! - When you’ve got a Prusa printer, now you can use the PrusaLink integration
to regulate your print job utilizing the brand new job management buttons accessible!
Thanks, @balloob! - BTHome now helps binary sensors! Thanks, @Ernst79!
- The HomeKit Controller now helps Thread transport. Thanks, @roysjosh
and @Jc2k! -
forked-daapd (OwnTone) now helps the media browser and might leverage
the Spotify integration. Thanks, @uvjustin! - The Min/Max helper now helps calculating the statistical vary. For
instance, useful if you wish to present the distinction between the best and
warmest rooms. Thanks, @jsherman256! -
@holysoles added distinctive ID help to the Common Media Participant,
@magic7s added help for it to OhmConnect. Thanks! -
NETGEAR now has a bunch of switches to regulate issues like parental
controls, Wi-Fi availability, and entry. Thanks, @starkillerOG!
New Integrations
We welcome the next new integrations on this launch:
Integrations now available to set up from the UI
The following integrations are now available via the Home Assistant UI:
Release 2022.10.1 – October 6
Release 2022.10.2 – October 9
Release 2022.10.3 – October 10
Release 2022.10.4 – October 14
Release 2022.10.5 – October 20
Need help? Join the community!
Home Assistant has a great community of users who are all more than willing
to help each other out. So, join us!
Our very active Discord chat server is an excellent place to be
at, and don’t forget to join our amazing forums.
Discovered a bug or situation? 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 e-mail? Signal-up for our Constructing the Open House E-newsletter
to get the newest information about options, issues taking place in our group and
different information about constructing an Open House; straight into your inbox.
Breaking Changes
Below is a listing of the breaking change for this release, per subject or
integration. Click on one of those to read more about the breaking change
for that specific item.
prob_given_false is now a required configuration variable. Previously it had a default value of 1 - prob_given_true; this didn’t really have any mathematical basis and so has been removed. You can use this documentation to calculate what it should be, or to restore your previous functionality, set it to 1 - prob_given_true.
The logic of Bayesian sensors has been significantly corrected. Previously the configs given in the examples above would not have worked as expected. For example, if the device device_tracker.paulus was home, this would not have updated the probability that Paulus Home was on. This is because Bayesian ignored observations that were false, even though that should update our probabilities.
Because of this, many users will have had to use either of two workarounds:
- Providing additional observations that evaluate to
Truewhen the other evaluates toFalse, effectively mirroring it. This forced Bayesian to take into account a negative observation. - Tweaking
prior,threshold, and even sometimesprob_given_trueandprob_given_falseto get the desired functionality, often with the help of a community-provided spreadsheet for iterative testing.
To solve (1), all you need do is delete the mirrored entry as shown below:
# Example of a mirrored entry used a workaround
binary_sensor:
- name: "Heat On"
platform: bayesian
prior: 0.2
probability_threshold: 0.9
observations:
- platform: numeric_state
entity_id: sensor.outside_air_temperature_fahrenheit
prob_given_true: 0.95
prob_given_false: 0.05
below: 50
- platform: numeric_state # line no longer needed - delete
entity_id: sensor.outside_air_temperature_fahrenheit # line no longer needed - delete
prob_given_true: 0.05 # line no longer needed - delete
prob_given_false: 0.95 # line no longer needed - delete
above: 50 # no longer needed - delete
- platform: state
entity_id: binary_sensor.house_occupied
prob_given_true: 0.3
prob_given_false: 0.05
to_state: "on"
- platform: state # line no longer needed - delete
entity_id: binary_sensor.house_occupied # line no longer needed - delete
prob_given_true: 0.7 # line no longer needed - delete
prob_given_false: 0.95 # line no longer needed - delete
to_state: "off" # line no longer needed - delete
To solve (2), you need to re-estimate your probabilities using this documentation – this will likely result in better performance in the long term.
A hacky and not recommended workaround to restore your previous functionality would be to put in a mirrored entry for each observation where prob_given_false is equal to prob_given_true. This will induce the same behavior as before – the negative, counterfactual observation is essentially ignored. Be warned – this may break or cause errors in future versions and will not work for template or numeric_state observations. For templates, instead, make them return None where they would have returned False to induce Bayesian to ignore them.
binary_sensor:
- name: "Heat On"
platform: bayesian
prior: 0.2
probability_threshold: 0.9
observations:
- platform: state
entity_id: binary_sensor.house_occupied
prob_given_true: 0.3
prob_given_false: 0.05
to_state: "on"
- platform: state # not
entity_id: binary_sensor.house_occupied # not recommended
prob_given_true: 0.5 # not recommended
prob_given_false: 0.5 # not recommended
to_state: "off" # not recommended
The beforehand deprecated YAML configuration of the HERE Journey Time
integration has been eliminated.
HERE Journey Time is now configured through the UI, any present YAML
configuration has been imported in earlier releases and might now be safely
eliminated out of your YAML configuration information
When the participant shouldn’t be energetic, the state not studies as “downside”,
however as a substitute studies as “off”.
When the participant is energetic, however the state doesn’t match identified states,
the state not studies as “okay” however as a substitute studies as “on”.
Some breaking adjustments have been made in disabling the Motion pictures rely sensor out
of warning. This sensor may cause issues with large databases.
For those who nonetheless want to use it, it’s possible you’ll achieve this.
Film names are not included as attributes within the films sensor. Upcoming
has been eliminated. It’s being modernized as calendar gadgets must be.
Diskspace is now break up into completely different sensors, one for every folder.
Standing and instructions have been eliminated as they don’t seem to have actual
worth for automations.
Attributable to adjustments within the upstream library, the next is not supported by
the Workday integration:
- UK subdivisions (Wales, Scotland, England…) can not be supplied as
values to thenationconfiguration key. They’re nonetheless accessible to be used as
values to theprovincesetting. -
IsleOfManis not a acknowledged province of the UK,
use theIMcode for thenationas a substitute. - The prolonged Portuguese vacation set (
PortugalExt) is not accessible
as a separate nation; as a substitute it’s best to use the nation codePTand
the provinceExt.
You could use zwave-js-server 1.24.0 or higher (schema 24).
With this launch, you will have to replace your zwave-js-server occasion.
- For those who use the
Z-Wave JSaddon, it is advisable to have at the least model 0.1.74. - For those who use the
Z-Wave JS UIaddon, it is advisable to have at the least model 1.1.0. - For those who use the
Z-Wave JS UIDocker container, it is advisable to have at the least model 8.1.0. - For those who run your personal Docker container, or another set up methodology, you will have to replace your
zwave-js-serveroccasion to at the least 1.24.0.
(@raman325 – #79342) (documentation)
The fan velocity ranges of Leviton ZW4SF fan controllers at the moment are mapped appropriately
to corresponding share ranges in House Assistant.
This may occasionally change which fan velocity is chosen at sure percentages.
You need to modify any automations and scripts that focus on these units
as wanted.
(@mkowalchuk – #60677) (documentation)
If you’re a customized integration developer and need to study breaking
adjustments and new options accessible in your integration: Remember to observe our
developer blog. The next are essentially the most notable for this launch:
Farewell to the next
The next integrations are additionally not accessible as of this launch:
- Ambee because it grew to become not possible to get API keys for personal use.
- Climacell has been changed by Tomorrow.io.
-
Flu Close to You the useful resource is not accessible, inflicting the combination
not to work. -
U.S. Citizenship and Immigration Providers (USCIS) the combination relied
on webscraping, which is not allowed.
All adjustments
After all, there may be much more on this launch. You’ll find an inventory of
all adjustments made right here: Full changelog for House Assistant Core 2022.10