Home Assistant Core 2022.9.0 → 2022.10.0

Bayesian

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:

1. Providing additional observations that evaluate to True when the other evaluates to False, effectively mirroring it. This forced Bayesian to take into account a negative observation.
2. Tweaking prior, threshold, and even sometimes prob_given_true and prob_given_false to 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

(@HarvsG - #67631) (documentation)

Bluesound

When the player is grouped and isn't master, the state no longer reports as "grouped" but instead reports as "idle".

(@epenet - #78096) (documentation)

Elexa Guardian

The previously deprecated guardian.reboot and guardian.reset_valve_diagnostics services have been removed and replaced by button entities on the guardian valve controller device.

(@bachya - #78663) (documentation)

Frontier Silicon

When the player is loading, the state no longer reports as "opening", but instead reports as "buffering".

(@epenet - #78101) (documentation)

HERE Travel Time

The previously deprecated YAML configuration of the HERE Travel Time integration has been removed.

HERE Travel Time is now configured via the UI, any existing YAML configuration has been imported in previous releases and can now be safely removed from your YAML configuration files

(@eifinger - #77959) (documentation)

HomeKit Controller

When the player is not active, the state no longer reports as "problem", but instead reports as "off".

When the player is active, but the state doesn't match known states, the state no longer reports as "ok" but instead reports as "on".

(@epenet - #78105) (documentation)

Radarr

Some backward-incompatible changes have been made in disabling the Movies count sensor out of caution. This sensor can cause problems with massive databases. If you still wish to use it, you may do so.

Movie names are no longer included as attributes in the movies sensor. Upcoming has been removed. It is being modernized as calendar items should be. Diskspace is now split into different sensors, one for each folder. Status and commands have been removed as they don't appear to have real value for automations.

(@tkdrob - #78965) (documentation)

Supervisor

In Home Assistant 2022.4, the binary sensors for showing an update from the Supervisor integration were deprecated in favor of update entities.

These binary sensors for showing an update have now been removed.

(@ludeeus - #60677) (documentation)

Synology DSM

In Home Assistant 2022.4 the binary sensor of Synology DSM for showing an update was deprecated in favor of the newer update entity.

This binary sensor for showing an update has now been removed.

(@mib1185 - #79509) (documentation)

Workday

Due to changes in the upstream library, the following is no longer supported by the Workday integration:

• UK subdivisions (Wales, Scotland, England...) can no longer be provided as values to the country configuration key. They are still available for use as values to the province setting.
• IsleOfMan is no longer a recognized province of the UK, use the IM code for the country instead.
• The extended Portuguese holiday set (PortugalExt) is no longer available as a separate country; instead you should use the country code PT and the province Ext.

(@TomBrien - #78832) (documentation)

Z-Wave

You must use zwave-js-server 1.24.0 or greater (schema 24).

With this release, you will need to update your zwave-js-server instance.

• If you use the Z-Wave JS addon, you need to have at least version 0.1.74.
• If you use the Z-Wave JS UI addon, you need to have at least version 1.1.0.
• If you use the Z-Wave JS UI Docker container, you need to have at least version 8.1.0.
• If you run your own Docker container, or some other installation method, you will need to update your zwave-js-server instance to at least 1.24.0.

(@raman325 - #79342) (documentation)

---

The fan speed levels of Leviton ZW4SF fan controllers are now mapped correctly to corresponding percentage levels in Home Assistant.

This may change which fan speed is selected at certain percentages. You should adjust any automations and scripts that target these devices as needed.

(@mkowalchuk - #60677) (documentation)

Farewell to the following

The following integrations are also no longer available as of this release:

• Ambee as it became impossible to get API keys for private use.
• Climacell has been replaced by Tomorrow.io.
• Flu Near You the resource is no longer available, causing the integration no longer to work.
• U.S. Citizenship and Immigration Services (USCIS) the integration relied on webscraping, which is no longer allowed.