diff --git a/.textlintrc.json b/.textlintrc.json index d196f13a944..1ab82cc45c2 100644 --- a/.textlintrc.json +++ b/.textlintrc.json @@ -308,6 +308,7 @@ ["grey", "gray"], ["hass", "Home Assistant"], ["Hass\\.?io", "Home Assistant"], + ["hassio.local", "homeassistant.local"], ["HassOS", "Home Assistant Operating System"], ["he or she", "they"], ["he/she", "they"], diff --git a/source/_docs/authentication/multi-factor-auth.markdown b/source/_docs/authentication/multi-factor-auth.markdown index a026cd0ed1d..d38b7f215b4 100644 --- a/source/_docs/authentication/multi-factor-auth.markdown +++ b/source/_docs/authentication/multi-factor-auth.markdown @@ -63,7 +63,7 @@ TOTP is _time based_ so it relies on your Home Assistant clock being accurate. I The Notify MFA module uses the [notify component](/integrations/notify/) to send you an [HMAC-based One-Time Password](https://en.wikipedia.org/wiki/HMAC-based_One-time_Password_algorithm). It is typically sent to your phone, but can be sent to any destination supported by a `notify` service. You use this password to log in. -#### Setting up TOTP +#### Setting up MFA notify Add Notify MFA to your `configuration.yaml` file like this: diff --git a/source/_integrations/automatic.markdown b/source/_integrations/automatic.markdown index 9cb9cfc2576..10cf7958d4a 100644 --- a/source/_integrations/automatic.markdown +++ b/source/_integrations/automatic.markdown @@ -14,7 +14,7 @@ The `automatic` device tracker platform offers presence detection by retrieving ## Setup -To use Automatic with Home Assistant, first you must [create a free development account](https://developer.automatic.com/). Automatic will generate a Client ID and Secret for you to use in your Home Assistant configuration. You will need to update your Event Delivery preferences to ensure Home Assistant can receive updates. On the developer page, under App Settings / Event Delivery, select "Websocket" for Event Delivery Preference. Next, specify the OAuth Redirect URL in the developer page. This should be configured to `/api/automatic/callback`. (Example: `http://hassio.local:8123/api/automatic/callback`) Note that this URL only needs to be accessible from the browser you use to perform the authentication. +To use Automatic with Home Assistant, first you must [create a free development account](https://developer.automatic.com/). Automatic will generate a Client ID and Secret for you to use in your Home Assistant configuration. You will need to update your Event Delivery preferences to ensure Home Assistant can receive updates. On the developer page, under App Settings / Event Delivery, select "Websocket" for Event Delivery Preference. Next, specify the OAuth Redirect URL in the developer page. This should be configured to `/api/automatic/callback`. (Example: `http://homeassistant.local:8123/api/automatic/callback`) Note that this URL only needs to be accessible from the browser you use to perform the authentication. Home Assistant can also take advantage of `scope:current_location` if available. This will allow Home Assistant to receive periodic location updates during a trip. In order to use this functionality, you must request the scope for your application from Automatic. Once `scope:current_location` is available, change `current_location` to `true` in your `configuration.yaml`. diff --git a/source/_integrations/climate.modbus.markdown b/source/_integrations/climate.modbus.markdown index a5cf70b4354..827160891c4 100644 --- a/source/_integrations/climate.modbus.markdown +++ b/source/_integrations/climate.modbus.markdown @@ -23,7 +23,7 @@ climate: hub: hub1 slave: 1 data_type: uint - count: 1 + data_count: 1 scale: 0.1 offset: 0 precision: 1 @@ -56,6 +56,11 @@ current_temp_register: description: Register number for current temperature (Process value). required: true type: integer +current_temp_register_type: + description: Modbus register type (holding, input) for current temperature, default holding. + required: false + type: string + default: holding data_type: description: Response representation (int, uint, float, custom). If float selected, value will converted to IEEE 754 floating point format. required: false diff --git a/source/_integrations/default_config.markdown b/source/_integrations/default_config.markdown index 96ccf20c966..546cb615c14 100644 --- a/source/_integrations/default_config.markdown +++ b/source/_integrations/default_config.markdown @@ -24,6 +24,7 @@ This integration is a meta-component and configures a default set of integration - [System Health](/integrations/system_health/) - [Updater](/integrations/updater/) - [Zero-configuration networking (zeroconf)](/integrations/zeroconf/) +- [Zone](/integrations/zone) ## Configuration diff --git a/source/_integrations/jewish_calendar.markdown b/source/_integrations/jewish_calendar.markdown index 95ed43b637b..07a689fac81 100644 --- a/source/_integrations/jewish_calendar.markdown +++ b/source/_integrations/jewish_calendar.markdown @@ -60,6 +60,7 @@ havdalah_minutes_after_sunset: - weekly_portion: Shows the weekly portion (parshat hashavu'a). - holiday: If it is a holiday, shows the name of the holiday _(see below for more info)_. - omer_count: An integer sensor indicating the day of the Omer (1-49) or 0 if it is not currently the Omer. +- daf_yomi: Shows the date's daf yomi page. ### Time sensors diff --git a/source/_integrations/konnected.markdown b/source/_integrations/konnected.markdown index e6529b4bf47..65084bad9fb 100644 --- a/source/_integrations/konnected.markdown +++ b/source/_integrations/konnected.markdown @@ -12,7 +12,7 @@ ha_codeowners: - '@heythisisnate' --- -The `konnected` integration lets you connect wired sensors and switches to a NodeMCU ESP8226 based device running the [open source Konnected software](https://github.com/konnected-io/konnected-security). Reuse the wired sensors and siren from an old or pre-wired alarm system installation and integrate them directly into Home Assistant. +The `konnected` integration lets you connect wired sensors and switches to a Konnected Alarm Panel, or NodeMCU ESP8226 based device running the [open source Konnected software](https://github.com/konnected-io/konnected-security). Reuse the wired sensors and siren from an old or pre-wired alarm system installation and integrate them directly into Home Assistant. Visit the [Konnected.io website](https://konnected.io) for more information about the Konnected Alarm Panel board and compatible hardware. @@ -22,7 +22,7 @@ The integration currently supports the following device types in Home Assistant: - Switch: Actuate a siren, strobe, buzzer or relay module. - Sensor: Periodic measurements from DHT temperature/humidity sensors and DS18B20 temperature sensors. -This integration uses the [`discovery`](/integrations/discovery) component, which must be enabled for device discovery to work. If you don't want to use discovery, set the _host_ and _port_ for each device in the description. +This integration uses the [SSDP](/integrations/ssdp) integration, which must be enabled for device discovery to work. If you don't want to use discovery, set the _host_ and _port_ for each device in the description.
@@ -32,7 +32,13 @@ Konnected devices communicate with Home Assistant over your local LAN -- there i ## Configuration -A `konnected` section must be present in the `configuration.yaml` file that specifies the Konnected devices on the network and the sensors or actuators attached to them: +Home Assistant offers Konnected integration through **Configuration** -> **Integrations** -> **Konnected.io**. + +The configuration flow will guide you through a setup process that lets you connect to the panel and generate a configuration entry. You can then utilize the options flow to configure or modify the behavior of each zone. + +If you prefer you can also utilize a `konnected` section in the `configuration.yaml` file that specifies the Konnected devices on the network and the sensors or actuators attached to them. If using `configuration.yaml` the configuration will automatically be imported and used to start a configuration flow. **Note that you must still complete the configuration/options flow before the configuration entry will be finalized.** + +Details of the configuration fields and values can be found below - these apply to both the configuration flow and the YAML. ```yaml # Example configuration.yaml entry @@ -69,7 +75,7 @@ devices: type: list keys: id: - description: The MAC address of the NodeMCU Wi-Fi module with colons/punctuation removed, for example `68c63a8bcd53`. You can usually find the mac address in your router's client list. Or, check the home-assistant.log for log messages from automatically discovered devices. + description: The MAC address of the Konnected device with colons/punctuation removed, for example, `68c63a8bcd53`. You can usually find the mac address in your router's client list. Or, check the `home-assistant.log` for log messages from automatically discovered devices. required: true type: string binary_sensors: @@ -78,10 +84,10 @@ devices: type: list keys: pin: - description: The number corresponding to the _IO index_ of the labeled pin on the NodeMCU dev board. See the [NodeMCU GPIO documentation](https://nodemcu.readthedocs.io/en/master/en/modules/gpio/) for more details. Valid values are `1`, `2`, `5`, `6`, `7` and `9`. + description: See [Configuration Notes](#configuration-notes). required: exclusive zone: - description: The number corresponding to the labeled zone on the [Konnected Alarm Panel](https://konnected.io) board. Valid values are `1`, `2`, `3`, `4`, `5` and `6`. + description: See [Configuration Notes](#configuration-notes). required: exclusive type: description: Any [binary sensor](/integrations/binary_sensor/) class, typically `door`, `window`, `motion` or `smoke`. @@ -101,10 +107,10 @@ devices: type: list keys: pin: - description: The number corresponding to the _IO index_ of the labeled pin on the NodeMCU dev board. See the [NodeMCU GPIO documentation](https://nodemcu.readthedocs.io/en/master/en/modules/gpio/) for more details. Valid values for sensors are `1`, `2`, `5`, `6`, `7` and `9`. + description: See [Configuration Notes](#configuration-notes). required: exclusive zone: - description: The number corresponding to the labeled zone on the [Konnected Alarm Panel](https://konnected.io) board. Valid values for sensors are `1`, `2`, `3`, `4`, `5` and `6`. + description: See [Configuration Notes](#configuration-notes). required: exclusive name: description: The name of the device used in the front end. @@ -124,10 +130,10 @@ devices: type: list keys: pin: - description: The number corresponding to the _IO index_ of the labeled pin on the NodeMCU dev board. See the [NodeMCU GPIO documentation](https://nodemcu.readthedocs.io/en/master/en/modules/gpio/) for more details. Valid values are 1, 2, 5, 6, 7 and 8. + description: See [Configuration Notes](#configuration-notes). required: exclusive zone: - description: The number corresponding to the labeled zone on the [Konnected Alarm Panel](https://konnected.io) board or the word `out` to specify the dedicated ALARM/OUT terminal on the Konnected board. Valid values are `1`, `2`, `3`, `4`, `5` and `out`. + description: See [Configuration Notes](#configuration-notes). required: exclusive name: description: The name of the device used in the front end. @@ -169,8 +175,11 @@ devices: ### Configuration Notes -- Either **pin** or **zone** is required for each actuator or sensor. Do not use both in the same definition. +- Either `pin` or `zone` is required for each actuator or sensor. Do not use both in the same definition. +- `pin` represents the number corresponding to the _IO index_ of the labeled pin on the NodeMCU dev board. See the [NodeMCU GPIO documentation](https://nodemcu.readthedocs.io/en/master/en/modules/gpio/) for more details. Valid values are `1`, `2`, `5`, `6`, `7`, `8`, and `9`. Pin based configuration is only allowed with ESP8266 based devices. - Pin `D8` or the `out` zone will only work when activation is set to high (the default). +- `zone` represents the value corresponding to the labeled zone on the [Konnected Alarm Panel](https://konnected.io) boards. Valid zone values are `1`, `2`, `3`, `4`, `5`, `6`, and `out` for the Konnected Alarm Panel (`out` represents the dedicated ALARM/OUT terminal) and `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9`, `10`, `11`, `12`, `out1`, `alarm1`, and `alarm2_out2` for the Konnected Alarm Panel Pro. +- **The Konnected Alarm Panel Pro does not support configuration via `pin`.** ## Extended Configuration diff --git a/source/_integrations/rpi_gpio_pwm.markdown b/source/_integrations/rpi_gpio_pwm.markdown index fcc13105bef..bd0ad3aa114 100644 --- a/source/_integrations/rpi_gpio_pwm.markdown +++ b/source/_integrations/rpi_gpio_pwm.markdown @@ -8,7 +8,7 @@ ha_release: 0.43 logo: raspberry-pi.png --- -The `rpi_gpio_pwm` platform allows to control multiple lights using pulse-width modulation, for example LED strips. It supports one-color, RGB and RGBW LEDs driven by GPIOs of a Raspberry Pi or a PCA9685 controller. +The `rpi_gpio_pwm` platform allows to control multiple lights using pulse-width modulation, for example LED strips. It supports one-color, RGB and RGBW LEDs driven by GPIOs of a Raspberry Pi (same host or remote) or a PCA9685 controller. For controlling the GPIOs, the platform connects to the [pigpio-daemon](http://abyz.me.uk/rpi/pigpio/pigpiod.html), which must be running. On Raspbian Jessie 2016-05-10 or newer the `pigpio` library is already included. On other operating systems it needs to be installed first (see [installation instructions](https://github.com/soldag/python-pwmled#installation)). @@ -59,6 +59,10 @@ leds: required: false default: 0x40 type: string + host: + description: The remote host address for the GPIO driver. + required: false + type: string {% endconfiguration %} ## Examples @@ -94,3 +98,17 @@ light: pins: [3, 4, 5, 6] # [R, G, B, W] type: rgbw ``` + +### RGB LED connected to the GPIO pins of an remote Raspberry Pi. + +On the Raspberry Pi the pigpio daemon is running on the default port 6666. + +```yaml +# Example configuration.yaml entry +light: + - platform: rpi_gpio_pwm + leds: + - name: Lightstrip Sideboard + driver: gpio + host: 192.168.0.66 +``` diff --git a/source/_integrations/simplisafe.markdown b/source/_integrations/simplisafe.markdown index f7b5cec6a10..715cc2b57f4 100644 --- a/source/_integrations/simplisafe.markdown +++ b/source/_integrations/simplisafe.markdown @@ -95,8 +95,11 @@ For any property denoting a volume, the following values should be used: ## Events -Automations can listen for `SIMPLISAFE_EVENT` events. Anytime one of these events is -received, it will come with event data that contains the following keys: +### `SIMPLISAFE_EVENT` + +`SIMPLISAFE_EVENT` events represent events that appear on the timeline of the SimpliSafe +web and mobile apps. When received, they come with event data that contains the +following keys: * `changed_by`: the PIN that triggered the event (if appropriate) * `event_type`: the type of event @@ -130,3 +133,14 @@ following values: * `doorbell_detected` * `entry_detected` * `motion_detected` + +### `SIMPLISAFE_NOTIFICATION` + +`SIMPLISAFE_NOTIFICATION` events represent system notifications that would appear in the +messages section of the SimpliSafe web and mobile apps. When received, they come with +event data that contains the following keys: + +* `category`: The notification category (e.g., `error`) +* `code`: The SimpliSafe code for the notification +* `message`: The actual text of the notification +* `timestamp`: The UTC timestamp of the notification diff --git a/source/_integrations/twitch.markdown b/source/_integrations/twitch.markdown index 4ba79e52fd7..38fab3d6634 100644 --- a/source/_integrations/twitch.markdown +++ b/source/_integrations/twitch.markdown @@ -10,9 +10,22 @@ ha_iot_class: Cloud Polling The `twitch` platform will allow you to monitor [Twitch](https://www.twitch.tv/) channel status from within Home Assistant and setup automation based on the information. -## Setup +## Setup Client ID -Create a new app at "Register Your Application" in the [Twitch developer portal](https://glass.twitch.tv/console/apps). Then get the **Client ID** for the new app. +Create a new app at "Register Your Application" in the [Twitch developer portal](https://glass.twitch.tv/console/apps). Then get the __Client ID__ for the new application. + +## Setup OAuth Token + +To enable the follow and subscription attributes, the OAuth token is needed to get the right permissions on the Twitch API. +If you don't need those, ignore the configuration setting: `token`. + +To get the OAuth token, visit the [OAuth Token Generator](https://twitchapps.com/tokengen/#), insert your __Client ID__ and `user_read user_subscriptions` inside __scopes__. + +Before clicking Summit (the broken image below the form), visit the [Twitch dev console](https://dev.twitch.tv/console) and add a new application. + +As __OAuth Redirect URLs__ add `https://twitchapps.com/tokengen/` and click __Create__ +. +Back at the Token Generator, click the __Summit__ button, accept the consent screen and get your __OAuth Token__. ## Configuration @@ -33,6 +46,10 @@ client_id: description: Your Twitch client ID. required: true type: string +token: + description: Your Twitch OAuth Token. + required: false + type: string channels: description: List of channels names required: true diff --git a/source/_lovelace/button.markdown b/source/_lovelace/button.markdown index 68db61aaf7a..2c06e57d49f 100644 --- a/source/_lovelace/button.markdown +++ b/source/_lovelace/button.markdown @@ -50,6 +50,11 @@ icon_height: description: Set the height for the icon. This is in pixels which is handled by the configuration UI. (Advanced users can use other CSS values if they like) type: string default: auto +state_color: + required: false + description: Set to `true` to have icons colored when entity is active + type: boolean + default: true tap_action: required: false description: Action to take on tap diff --git a/source/_lovelace/glance.markdown b/source/_lovelace/glance.markdown index fb9b54191ac..90d731e8278 100644 --- a/source/_lovelace/glance.markdown +++ b/source/_lovelace/glance.markdown @@ -47,6 +47,11 @@ columns: required: false description: Number of columns to show. If not specified the number will be set automatically. type: integer +state_color: + required: false + description: Set to `true` to have icons colored when entity is active + type: boolean + default: true {% endconfiguration %} ## Options For Entities diff --git a/source/_lovelace/picture-elements.markdown b/source/_lovelace/picture-elements.markdown index 98196750fa0..4cb8999ead2 100644 --- a/source/_lovelace/picture-elements.markdown +++ b/source/_lovelace/picture-elements.markdown @@ -188,6 +188,11 @@ title: required: false description: Icon tooltip. Set to null to hide. type: string +state_color: + required: false + description: Set to `true` to have icons colored when entity is active + type: boolean + default: true tap_action: required: false description: Action to take on tap diff --git a/source/_posts/2017-08-26-release-0-52.markdown b/source/_posts/2017-08-26-release-0-52.markdown index 7ff53669dc5..b678fea3dec 100644 --- a/source/_posts/2017-08-26-release-0-52.markdown +++ b/source/_posts/2017-08-26-release-0-52.markdown @@ -92,7 +92,7 @@ usps: - eliqonline: The optional channel_id configuration variable of the Eliqonline sensor needs to be a positive integer. ([@molobrakos] - [#9072]) ([sensor.eliqonline docs]) (breaking change) - MySensors: Not a breaking change per se but users that have not been following the mysensors [serial API](https://www.mysensors.org/download/serial_api_20) could face dropped messages after this change. Messages are now validated according to the API before being passed along from/to devices. See [0.11 release notes](https://github.com/theolind/pymysensors/releases/tag/0.11) for more info. ([@MartinHjelmare] - [#9069]) ([mysensors docs]) ([binary_sensor.mysensors docs]) ([climate.mysensors docs]) ([cover.mysensors docs]) ([device_tracker.mysensors docs]) ([light.mysensors docs]) ([notify.mysensors docs]) ([sensor.mysensors docs]) ([switch.mysensors docs]) (breaking change) - Automatic has disabled password authentication on their API. Home Assistant will now use OAuth2 to authenticate accounts. The following steps must be taken to transition your setup: - 1) Log in to your Automatic developer account. In the Automatic Developer Apps Manager, specify the OAuth Redirect URL in the developer page. This should be configured to `/api/automatic/callback`. (Example: `http://hassio.local:8123/api/automatic/callback`) Note that this URL only needs to be accessible from the browser you use to perform the authentication. + 1) Log in to your Automatic developer account. In the Automatic Developer Apps Manager, specify the OAuth Redirect URL in the developer page. This should be configured to `/api/automatic/callback`. (Example: `http://homeassistant.local:8123/api/automatic/callback`) Note that this URL only needs to be accessible from the browser you use to perform the authentication. 2) Remove username/password from your automatic device tracker configuration in configuration.yaml. 3) If you have authorized your account for `scope:current_location`, add `current_location: true` to your automatic device tracker configuration in configuration.yaml. 4) When you restart Home Assistant, click on the Automatic Configure link in the Configurator card, and follow the instructions to authorize Home Assistant.

NOTE: Automatic's API is currently not correctly authorizing with refresh tokens, so Step 4 currently needs to be performed after every restart. ([@armills] - [#8962] [#9002]) ([configurator docs]) ([device_tracker.automatic docs]) (breaking change) diff --git a/source/_posts/2020-02-05-release-105.markdown b/source/_posts/2020-02-05-release-105.markdown index fa70420e893..50a9221093e 100644 --- a/source/_posts/2020-02-05-release-105.markdown +++ b/source/_posts/2020-02-05-release-105.markdown @@ -628,6 +628,22 @@ Hats over your heart for these shuttered integrations. Pour one out for: [spotify docs]: /integrations/spotify/ [vizio docs]: /integrations/vizio/ +## Release 0.105.5 - February 17 + +- Upgrade bimmer_connected to 0.7.0 ([@gerard33] - [#31894]) ([bmw_connected_drive docs]) +- Report which data causes JSON serialization error ([@balloob] - [#31901]) + +[#31489]: https://github.com/home-assistant/home-assistant/pull/31489 +[#31894]: https://github.com/home-assistant/home-assistant/pull/31894 +[#31901]: https://github.com/home-assistant/home-assistant/pull/31901 +[@balloob]: https://github.com/balloob +[@frenck]: https://github.com/frenck +[@gerard33]: https://github.com/gerard33 +[abode docs]: /integrations/abode/ +[adguard docs]: /integrations/adguard/ +[airly docs]: /integrations/airly/ +[bmw_connected_drive docs]: /integrations/bmw_connected_drive/ + ## Beta Fixes - ZHA dependencies bump ([@Adminiuga] - [#31295]) ([zha docs]) (beta fix) diff --git a/source/getting-started/index.markdown b/source/getting-started/index.markdown index ab059dc7850..9957699f59a 100644 --- a/source/getting-started/index.markdown +++ b/source/getting-started/index.markdown @@ -62,7 +62,7 @@ We will need a few things to get started with installing Home Assistant. The Ras 5. Insert the SD card into your Raspberry Pi. If you are going to use an Ethernet cable, connect that too. 6. Connect your power supply to the Raspberry Pi. 7. The Raspberry Pi will now boot up, connect to the Internet and download the latest version of Home Assistant. This will take about 20 minutes. -8. Home Assistant will be available at `http://hassio.local:8123`. If you are running an older Windows version or have a stricter network configuration, you might need to access Home Assistant at `http://hassio:8123` or `http://X.X.X.X:8123` (replace `X.X.X.X` with your Pi's IP address). +8. Home Assistant will be available at `http://homeassistant.local:8123`. If you are running an older Windows version or have a stricter network configuration, you might need to access Home Assistant at `http://homeassistant:8123` or `http://X.X.X.X:8123` (replace `X.X.X.X` with your Pi's IP address). 9. If you used a USB stick for configuring the network, you can now remove it. [the examples]: https://github.com/home-assistant/hassos/blob/dev/Documentation/network.md diff --git a/source/hassio/installation.markdown b/source/hassio/installation.markdown index d36d8a696b3..604dfd3ba82 100644 --- a/source/hassio/installation.markdown +++ b/source/hassio/installation.markdown @@ -49,13 +49,19 @@ The following will take you through the steps required to install Home Assistant -6. You will be able to reach your installation at `http://hassio.local:8123` (if your router supports mDNS, otherwise see below). +6. You will be able to reach your installation at `http://homeassistant.local:8123` (if your router supports mDNS, otherwise see below). 7. It is important to provide yourself proper access, including the Home Assistant CLI tools. Both the [Samba add-on][samba] and the [SSH add-on][ssh] should be the first add-ons you should install, before making changes to the configuration in the `/config/` folder. From the UI choose **Supervisor**, which is located in the sidebar and then the add-on store. +
+ +We used `hassio.local` in the past, if you have a system that is installed before this naming change, you might need to use `hassio.local` instead of `homeassistant.local`. + +
+
-If your router doesn't support mDNS, then you'll have to use the IP address of your Pi instead of `hassio.local`. For example, `http://192.168.0.9:8123`. You should be able to find the IP address of your Pi from the admin interface of your router. +If your router doesn't support mDNS, then you'll have to use the IP address of your Pi instead of `homeassistant.local`. For example, `http://192.168.0.9:8123`. You should be able to find the IP address of your Pi from the admin interface of your router.
@@ -211,23 +217,23 @@ A detailed guide about running Home Assistant as a virtual machine is available [balenaEtcher]: https://www.balena.io/etcher [Virtual Appliance]: https://github.com/home-assistant/operating-system/blob/dev/Documentation/boards/ova.md [hassos-network]: https://github.com/home-assistant/operating-system/blob/dev/Documentation/network.md -[pi0-w]: https://github.com/home-assistant/operating-system/releases/download/3.10/hassos_rpi0-w-3.10.img.gz -[pi1]: https://github.com/home-assistant/operating-system/releases/download/3.10/hassos_rpi-3.10.img.gz -[pi2]: https://github.com/home-assistant/operating-system/releases/download/3.10/hassos_rpi2-3.10.img.gz -[pi3-32]: https://github.com/home-assistant/operating-system/releases/download/3.10/hassos_rpi3-3.10.img.gz -[pi3-64]: https://github.com/home-assistant/operating-system/releases/download/3.10/hassos_rpi3-64-3.10.img.gz -[pi4-32]: https://github.com/home-assistant/operating-system/releases/download/3.10/hassos_rpi4-3.10.img.gz -[pi4-64]: https://github.com/home-assistant/operating-system/releases/download/3.10/hassos_rpi4-64-3.10.img.gz -[tinker]: https://github.com/home-assistant/operating-system/releases/download/3.10/hassos_tinker-3.10.img.gz -[odroid-c2]: https://github.com/home-assistant/operating-system/releases/download/3.10/hassos_odroid-c2-3.10.img.gz -[odroid-n2]: https://github.com/home-assistant/operating-system/releases/download/4.2/hassos_odroid-n2-4.2.img.gz -[odroid-xu4]: https://github.com/home-assistant/operating-system/releases/download/3.10/hassos_odroid-xu4-3.10.img.gz -[intel-nuc]: https://github.com/home-assistant/operating-system/releases/download/3.10/hassos_intel-nuc-3.10.img.gz -[vmdk]: https://github.com/home-assistant/operating-system/releases/download/3.10/hassos_ova-3.10.vmdk.gz -[vhdx]: https://github.com/home-assistant/operating-system/releases/download/3.10/hassos_ova-3.10.vhdx.gz -[vdi]: https://github.com/home-assistant/operating-system/releases/download/3.10/hassos_ova-3.10.vdi.gz +[pi0-w]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_rpi0-w-3.11.img.gz +[pi1]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_rpi-3.11.img.gz +[pi2]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_rpi2-3.11.img.gz +[pi3-32]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_rpi3-3.11.img.gz +[pi3-64]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_rpi3-64-3.11.img.gz +[pi4-32]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_rpi4-3.11.img.gz +[pi4-64]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_rpi4-64-3.11.img.gz +[tinker]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_tinker-3.11.img.gz +[odroid-c2]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_odroid-c2-3.11.img.gz +[odroid-n2]: https://github.com/home-assistant/operating-system/releases/download/4.3/hassos_odroid-n2-4.3.img.gz +[odroid-xu4]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_odroid-xu4-3.11.img.gz +[intel-nuc]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_intel-nuc-3.11.img.gz +[vmdk]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_ova-3.11.vmdk.gz +[vhdx]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_ova-3.11.vhdx.gz +[vdi]: https://github.com/home-assistant/operating-system/releases/download/3.11/hassos_ova-3.11.vdi.gz [linux]: https://github.com/home-assistant/hassio-installer -[local]: http://hassio.local:8123 +[local]: http://homeassistant.local:8123 [samba]: /addons/samba/ [ssh]: /addons/ssh/ [pi-power]: https://www.raspberrypi.org/help/faqs/#powerReqs