mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-19 15:26:59 +00:00
Update default name (#3756)
This commit is contained in:
parent
e7d99e5b16
commit
978a3f2867
@ -14,7 +14,7 @@ ha_release: 0.53
|
||||
---
|
||||
|
||||
|
||||
The `bayesian` binary sensor platform observes the state from multiple sensors and uses Bayes' rule to estimate the probability that an event has occurred given the state of the observed sensors. If the estimated posterior probability is above the `probability_threshold`, the sensor is `on` otherwise it is `off`.
|
||||
The `bayesian` binary sensor platform observes the state from multiple sensors and uses [Bayes' rule](https://en.wikipedia.org/wiki/Bayes%27_theorem) to estimate the probability that an event has occurred given the state of the observed sensors. If the estimated posterior probability is above the `probability_threshold`, the sensor is `on` otherwise it is `off`.
|
||||
|
||||
This allows for the detection of complex events that may not be readily observable, e.g., cooking, showering, in bed, the start of a morning routine, etc. It can also be used to gain greater confidence about events that _are_ directly observable, but for which the sensors can be unreliable, e.g., presence.
|
||||
|
||||
@ -23,7 +23,7 @@ To enable the Bayesian sensor, add the following lines to your `configuration.ya
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
binary_sensor:
|
||||
- platform: 'bayesian'
|
||||
- platform: bayesian
|
||||
prior: 0.1
|
||||
observations:
|
||||
- entity_id: 'switch.kitchen_lights'
|
||||
@ -36,14 +36,14 @@ binary_sensor:
|
||||
Configuration variables:
|
||||
|
||||
- **prior** (*Required*): The prior probability of the event. At any point in time (ignoring all external influences) how likely is this event to occur?
|
||||
- **probability_threshold** (*Optional*): The probability at which the sensor should trigger to `on`.
|
||||
- **name** (*Optional*): Name of the sensor to use in the frontend. Defaults to `Bayesian Binary sensor`.
|
||||
- **observations** array (*Required*): The observations which should influence the likelihood that the given event has occurred.
|
||||
- **entity_id** (*Required*): Name of the entity to monitor.
|
||||
- **prob_given_true** (*Required*): The probability of the observation occurring, given the event is `true`.
|
||||
- **prob_given_false** (*Optional*): The probability of the observation occurring, given the event is `false` can be set as well. If `prob_given_false` is not set, it will default to `1 - prob_given_true`.
|
||||
- **platform** (*Required*): The only supported observation platforms are `state` and `numeric_state`, which are modeled after their corresponding triggers for automations, requiring `before` and/or `after` instead of `to_state`.
|
||||
- **to_state** (*Required*): The target state.
|
||||
- **probability_threshold** (*Optional*): The probability at which the sensor should trigger to `on`.
|
||||
- **name** (*Optional*): Name of the sensor to use in the frontend. Defaults to `Bayesian Binary`.
|
||||
|
||||
## {% linkable_title Full examples %}
|
||||
|
||||
@ -74,6 +74,8 @@ binary_sensor:
|
||||
platform: 'state'
|
||||
to_state: 'below_horizon'
|
||||
```
|
||||
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
binary_sensor:
|
||||
|
Loading…
x
Reference in New Issue
Block a user