Updater
The updater
binary sensor will check daily for new releases. The state will be “on” when an update is available. Otherwise, the state will be “off”. The newer version, as well as the link to the release notes, are attributes of the updater.
The updater integration will also collect basic information about the running Open Peer Power instance and its environment. The information includes the current Open Peer Power version, the time zone, Python version and operating system information. No identifiable information (i.e., IP address, GPS coordinates, etc.) will ever be collected. If you are concerned about your privacy, you are welcome to scrutinize the Python source code.
Configuration
This integration is by default enabled, unless you’ve disabled or removed the default_config:
line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
updater:
For further information about the Updater’s data, please check the detailed overview. If you choose not to share any information when checking for updates, you can set reporting: false
.
It is possible to report the integrations that you are using to the Open Peer Power developers. This will help them focus on improving the popular ones. To enable this option, you have to add include_used_components: true
.
"components": [
"apcupsd",
"api",
"automation",
"binary_sensor",
"binary_sensor.zwave",
"camera",
"camera.uvc",
"config",
"config.core",
...
]
Notification
For an added bonus, an automation integration can be created to send a message with a notifier when that state of this component’s entity changes.
# Example configuration.yaml entry
automation:
alias: Update Available Notification
trigger:
- platform: state
entity_id: binary_sensor.updater
from: 'off'
to: 'on'
action:
- service: notify.notify
data_template:
message: "Open Peer Power {{ state_attr('binary_sensor.updater', 'newest_version') }} is available."