3. Select the `Develop` tab at the top of the page, then in the upper right hand corner select the `Test` button to generate the draft version Test App. If you don't see this option, go to the `Test` tab instead, click on the `Settings` button in the top right below the header, and ensure `On device testing` is enabled (if it isn't, enable it).
-4. Add the `google_assistant` integration configuration to your `configuration.yaml` file and restart Home Assistant following the [configuration guide](#configuration) below.
+4. Add the `google_assistant` integration configuration to your `configuration.yaml` file and restart Home Assistant following the [configuration guide](#yaml-configuration) below.
5. Add services in the Google Home App (Note that app versions may be slightly different.)
1. Open the Google Home app.
2. Click the `+` button on the top left corner, click `Set up device`, in the "Set up a device" screen click "Works with Google". You should have `[test]
- 
-
+You must have multi-factor authentication set up in your SimpliSafe account to install the integration.
+
+
+
+You must use a "standard" operating system (Windows, macOS, Linux) to perform the below instructions. Indications are that non-standard OS's, like Chrome OS, will not work.
+
+
Because of a technical limitation, the below instructions will not work for iOS users as-is. It is recommended that you set up the SimpliSafe integration from a desktop browser. If you must use an iOS device, please ensure that the SimpliSafe app is not installed before beginning; the app can be re-installed after the integration is set up.
@@ -47,10 +55,16 @@ Starting in 2021, SimpliSafe has moved to a new authentication mechanism via its
1. Initiate adding the integration via the instructions above.
2. When prompted, click the link that opens the SimpliSafe web app.
3. Input your SimpliSafe credentials. You will see "Verification Pending" – leave this browser tab open.
-4. Check your email for a message from SimpliSafe. When you have received that email, click "Verify Device" – note that this will open a second browser tab/window.
-5. After the verification is successful, return to the first browser tab/window. The browser will show an error about not being able to navigate to the page; ignore it.
+4. You will receive a multi-factor authentication prompt, either via SMS or email. Regardless of the type, use this message to verify the access request.
+5. After the verification is successful, return to the first browser tab/window.
-At this stage, take a look at the address bar and note the `code` parameter at the very end of the URL:
+Retrieving the access code is different depending on which browser you are using:
+
+* Chrome: Navigate to `Developer -> Developer Tools -> Console Tab` and look for a `Failed to launch` error.
+* Edge: Navigate to `Developer -> Developer Tools -> Console Tab` and look for a `Failed to launch` error.
+* Safari: Navigate to `Develop -> Show Web Inspector -> Network Tab` and look for a reference to `ErrorPage.html`.
+
+Look for a reference to a URL that starts with `com.simplisafe.mobile://` and note the code at the end:
```txt
com.simplisafe.mobile://auth.simplisafe.com/ios/com.simplisafe.mobile/callback?code=
diff --git a/source/_integrations/solarlog.markdown b/source/_integrations/solarlog.markdown
index bdc46f08f62..c523630f14e 100644
--- a/source/_integrations/solarlog.markdown
+++ b/source/_integrations/solarlog.markdown
@@ -35,11 +35,10 @@ In case you would like to convert the values, for example, to Wh instead of the
```yaml
# Example configuration.yaml entry for sensor template platform
-sensor:
- - platform: template
- sensors:
- solarlog_yield_day_template:
- value_template: "{{ (states('sensor.solarlog_yield_day') | float * 1000) | round(0) }}"
+template:
+ - sensor:
+ - name: "Solarlog yield day"
+ state: "{{ (states('sensor.solarlog_yield_day') | float(default=0) * 1000) | round(0,default=0) }}"
```
{% endraw %}
diff --git a/source/_integrations/switchbot.markdown b/source/_integrations/switchbot.markdown
index 80a82ba2bb3..de424c44a55 100644
--- a/source/_integrations/switchbot.markdown
+++ b/source/_integrations/switchbot.markdown
@@ -43,6 +43,15 @@ There are three attributes available on the SwitchBot entity to give you more in
- `Switch mode`: Specifies the mode of the SwitchBot. If `true` the the SwitchBot is in Pull/Retract mode for toggle switches otherwise the bot is in momentary switch mode.
- `MAC address`: The BTLE MAC for the device.
+## SwitchBot Options
+
+There are four options that can be configured for the SwitchBot entities. Setting any of these options will apply to all of your SwitchBot devices.
+
+- `Time between updates (seconds)`: Increase/Decrease the update interval for the device. (Could impact battery life)
+- `Retry count`: How many times to retry sending commands and retry polling your SwitchBot devices.
+- `Timeout between retries`: How long to wait before retries.
+- `How long to scan for advertisement data`: Bluetooth LE uses advertisement data for device statuses and/or attributes. This setting spesifies how long the scan should run.
+
### Error codes and troubleshooting
{% configuration_basic %}
diff --git a/source/_integrations/tasmota.markdown b/source/_integrations/tasmota.markdown
index 7b6e70a0a4e..d13e79c0933 100644
--- a/source/_integrations/tasmota.markdown
+++ b/source/_integrations/tasmota.markdown
@@ -37,15 +37,15 @@ This integration allows you to control [Tasmota](https://tasmota.github.io/docs/
Tasmota Buttons, Fans, Lights, relays, Sensors, Shutters and Switches are supported.
-- Tasmota Buttons will be added as Home Assistant `automation triggers` when `SetOption73` is enabled.
+- Tasmota Buttons will be added as Home Assistant `automation triggers` when `SetOption73` is enabled. No `binary_sensor` entity will be created. You can find the available `automation triggers` on the device screen. 
- Tasmota Lights will be added as Home Assistant `light` entities. Single channel Dimmers, RGB lights, RGB lights with Color Temperature control and RGB lights with White control are supported.
- Tasmota Relays will be added as Home Assistant `switch` entities, if `SetOption30 0`. If `SetOption30 1`, relays will be added as `light` entities.
- Tasmota Sensors will be added as Home Assistant `sensor` entities.
- Tasmota Shutters will be added as Home Assistant `cover` entities. Currently only Shutter modes 1 to 4 are supported. Shutter mode 5 and Tuya shutters are not supported.
-- Tasmota Switches will be added as Home Assistant `binary_sensor` entities or `automation triggers` depending by the `switchmode` used when `SetOption114` is enabled.
+- Tasmota Switches will be added as either Home Assistant `binary_sensor` entities or `automation triggers` depending on the `switchmode` used when `SetOption114` is enabled.
- The fan functionality in Tasmota devices with module configured as iFan02 or iFan03 will be added as Home Assistant `fan` entities. Tuya fans are not supported.
- The integration will also create up to eight Status Sensors, each one with a different information. Please note all the Status Sensors are disabled by default.
- 
+ 
{% include integrations/config_flow.md %}
diff --git a/source/_integrations/template.markdown b/source/_integrations/template.markdown
index c1d0d2e14ee..51c45afa5fb 100644
--- a/source/_integrations/template.markdown
+++ b/source/_integrations/template.markdown
@@ -117,7 +117,7 @@ sensor:
type: string
default: None
state_class:
- description: "Defines the state class of the sensor, if any. Only possible value currently is `measurement`. Set this if your template sensor represents a measurement of the current value (so not a daily aggregate etc)."
+ description: The [state_class](https://developers.home-assistant.io/docs/core/entity/sensor#available-state-classes) of the sensor.
required: false
type: string
default: None
@@ -236,7 +236,7 @@ select:
required: false
type: template
availability:
- description: Defines a template to get the `available` state of the entity. If the template either fails to render or returns either of `True`, `"1"`, `"true"`, `"yes"`, `"on"`, `"enable"` or a non-zero number, the entity is `available`. If the template returns any other value, the device will be `unavailable`. If not configured, the entity will always be `available`. Note that the string comparison not case sensitive; `"TrUe"` and `"yEs"` are allowed.
+ description: Defines a template to get the `available` state of the entity. If the template either fails to render or returns `True`, `"1"`, `"true"`, `"yes"`, `"on"`, `"enable"`, or a non-zero number, the entity will be `available`. If the template returns any other value, the entity will be `unavailable`. If not configured, the entity will always be `available`. Note that the string comparison not case sensitive; `"TrUe"` and `"yEs"` are allowed.
required: false
type: template
default: true
@@ -599,7 +599,7 @@ sensors:
required: true
type: template
availability_template:
- description: Defines a template to get the `available` state of the entity. If the template either fails to render or returns either of `True`, `"1"`, `"true"`, `"yes"`, `"on"`, `"enable"` or a non-zero number, the entity is `available`. If the template returns any other value, the device will be `unavailable`. If not configured, the entity will always be `available`. Note that the string comparison not case sensitive; `"TrUe"` and `"yEs"` are allowed.
+ description: Defines a template to get the `available` state of the entity. If the template either fails to render or returns `True`, `"1"`, `"true"`, `"yes"`, `"on"`, `"enable"`, or a non-zero number, the entity will be `available`. If the template returns any other value, the entity will be `unavailable`. If not configured, the entity will always be `available`. Note that the string comparison not case sensitive; `"TrUe"` and `"yEs"` are allowed.
required: false
type: template
default: true
diff --git a/source/_integrations/tplink.markdown b/source/_integrations/tplink.markdown
index e2a4ce487e2..80b011b483f 100644
--- a/source/_integrations/tplink.markdown
+++ b/source/_integrations/tplink.markdown
@@ -71,5 +71,7 @@ There is currently support for the following device types within Home Assistant:
- KL125
- KL130
- KB130
+- KL400
+- KL430
Other bulbs may also work, but with limited color temperature range (2700-5000). If you find a bulb isn't reaching the full-color temperature boundaries, submit a bug report to [python-kasa](https://github.com/python-kasa/python-kasa).
diff --git a/source/_integrations/xiaomi_miio.markdown b/source/_integrations/xiaomi_miio.markdown
index 0efaddfed17..beb4ec35197 100644
--- a/source/_integrations/xiaomi_miio.markdown
+++ b/source/_integrations/xiaomi_miio.markdown
@@ -500,7 +500,6 @@ Carbon Dioxide | The current carbon dioxide measured in ppm
Filter Life Remaining | The remaining life of the filter | True
Filter Use | Filter usage time in hours | True
Humidity | The current humidity measured | True
-Illuminance | The current illuminance measured | True
PM2.5 | The current particulate matter 2.5 measured | True
Temperature | The current temperature measured | True
Use Time | The accumulative number of seconds the device has been in use | False
@@ -893,7 +892,6 @@ Switch | Description
Buzzer | Turn on/off the Buzzer
Child Lock | Turn on/off the Child Lock
Ionizer | Turn on/off the Ionizer
-LED | Turn on/off the LED
### Platform Services
diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown
index 54a726a6ea0..401b168d810 100644
--- a/source/_integrations/zwave_js.markdown
+++ b/source/_integrations/zwave_js.markdown
@@ -515,6 +515,12 @@ There is no automatic migration wizard for the `ozw` integration. Please follow
2) Remove the Z-Wave integration from Home Assistant: Configuration --> Integrations --> Z-Wave (or OpenZWave) --> Press the three dots and click Delete.
+
+
+ If you have configured Z-Wave manually, make sure to also remove the `zwave:` section from your `configuration.yaml`.
+
+
+
3) If you were running the OpenZWave beta, make sure to stop (or even remove) the OpenZWave add-on, also make sure it doesn't start automatically at startup.
4) Restart your Home Assistant host. This step is important to make sure that your Z-Wave stick is released by the operating system.
diff --git a/source/_posts/2021-09-15-home-assistant-amber.markdown b/source/_posts/2021-09-15-home-assistant-yellow.markdown
similarity index 50%
rename from source/_posts/2021-09-15-home-assistant-amber.markdown
rename to source/_posts/2021-09-15-home-assistant-yellow.markdown
index febd594d31b..3df7daff9c6 100644
--- a/source/_posts/2021-09-15-home-assistant-amber.markdown
+++ b/source/_posts/2021-09-15-home-assistant-yellow.markdown
@@ -1,6 +1,6 @@
---
layout: post
-title: "Home Assistant Amber"
+title: "Home Assistant Yellow"
description: "Join our crowdfunding campaign for the easiest way to run Home Assistant."
date: 2021-09-13 00:00:00
date_formatted: "September 15, 2021"
@@ -9,18 +9,20 @@ author_twitter: balloob
comments: true
categories:
- Announcements
-og_image: /images/blog/2021-09-home-assistant-amber/social.png
+og_image: /images/blog/2021-09-home-assistant-yellow/social.png
---
-
+
-To celebrate our 8th birthday we're launching a crowdfunding campaign for Home Assistant Amber. We designed Home Assistant Amber from scratch for both beginners and home automation enthusiasts
+_This project was originally published under the name Home Assistant Amber._
+
+To celebrate our 8th birthday we're launching a crowdfunding campaign for Home Assistant Yellow. We designed Home Assistant Yellow from scratch for both beginners and home automation enthusiasts
to be the easiest way to run Home Assistant.
-### [Go to campaign on CrowdSupply »](https://www.crowdsupply.com/nabu-casa/home-assistant-amber)
+### [Go to campaign on CrowdSupply »](https://www.crowdsupply.com/nabu-casa/home-assistant-yellow)
-We will be hosting a Home Assistant Amber live stream today at 12.00 PDT / 21.00 CEST. We will talk about how Home Assistant Amber came to be and answer any questions you might have!
+We will be hosting a Home Assistant Yellow live stream today at 12.00 PDT / 21.00 CEST. We will talk about how Home Assistant Yellow came to be and answer any questions you might have!
diff --git a/source/_posts/2021-10-06-release-202110.markdown b/source/_posts/2021-10-06-release-202110.markdown
index f1b8e7a3a7d..deb00b39e14 100644
--- a/source/_posts/2021-10-06-release-202110.markdown
+++ b/source/_posts/2021-10-06-release-202110.markdown
@@ -47,7 +47,7 @@ Enjoy the release!
[hacktoberfest]: https://hacktoberfest.digitalocean.com/
-- [Home Assistant Amber](#home-assistant-amber)
+- [Home Assistant Yellow](#home-assistant-yellow)
- [Z-Wave JS updates!](#z-wave-js-updates)
- [S2 is now supported](#s2-is-now-supported)
- [Migration wizard from the old Z-Wave integration](#migration-wizard-from-the-old-z-wave-integration)
@@ -69,20 +69,20 @@ Enjoy the release!
- [Farewell to the following](#farewell-to-the-following)
- [All changes](#all-changes)
-## Home Assistant Amber
+## Home Assistant Yellow
In case you've missed it: Home Assistant turned 8 years old! 🥳
-And to celebrate that, we've revealed the **Home Assistant Amber**!
+And to celebrate that, we've revealed the **Home Assistant Yellow**!
-Home Assistant Amber was launched using a crowdfunding campaign, which already
+Home Assistant Yellow was launched using a crowdfunding campaign, which already
reached its funding goal! This is absolutely fantastic!
-And... You can still back the campaign to get your own Home Assistant Amber!
+And... You can still back the campaign to get your own Home Assistant Yellow!
-### [Go to campaign on CrowdSupply »](https://www.crowdsupply.com/nabu-casa/home-assistant-amber)
+### [Go to campaign on CrowdSupply »](https://www.crowdsupply.com/nabu-casa/home-assistant-yellow)
-
+
## Z-Wave JS updates!
diff --git a/source/_posts/2021-11-03-release-202111.markdown b/source/_posts/2021-11-03-release-202111.markdown
index 841bcc63b66..92786e90658 100644
--- a/source/_posts/2021-11-03-release-202111.markdown
+++ b/source/_posts/2021-11-03-release-202111.markdown
@@ -63,6 +63,9 @@ Enjoy the release!
- [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui)
- [Release 2021.11.1 - November 5](#release-2021111---november-5)
- [Release 2021.11.2 - November 9](#release-2021112---november-9)
+- [Release 2021.11.3 - November 11](#release-2021113---november-11)
+- [Release 2021.11.4 - November 15](#release-2021114---november-15)
+- [Release 2021.11.5 - November 19](#release-2021115---november-19)
- [If you need help...](#if-you-need-help)
- [Breaking Changes](#breaking-changes)
- [Farewell to the following](#farewell-to-the-following)
@@ -473,6 +476,135 @@ The following integrations are now available via the Home Assistant UI:
[xiaomi_miio docs]: /integrations/xiaomi_miio/
[zha docs]: /integrations/zha/
+## Release 2021.11.3 - November 11
+
+- Fix rpi_camera setup hanging on initialization ([@enegaard] - [#59316]) ([rpi_camera docs])
+- Fix state of sense net_production sensor ([@kbickar] - [#59391]) ([sense docs]) ([emulated_kasa docs])
+- Update frontend to 20211109.0 ([@bramkragten] - [#59451]) ([frontend docs])
+- Fix zeroconf with sonos v1 firmware ([@bdraco] - [#59460]) ([sonos docs])
+- Ignore None state in state_change_event ([@dgomes] - [#59485]) ([integration docs])
+- Fix wirelesstag switch arm/disarm ([@sergeymaysak] - [#59515]) ([wirelesstag docs])
+- Remove incomplete segment on stream restart ([@uvjustin] - [#59532]) ([stream docs])
+
+[#59316]: https://github.com/home-assistant/core/pull/59316
+[#59391]: https://github.com/home-assistant/core/pull/59391
+[#59451]: https://github.com/home-assistant/core/pull/59451
+[#59460]: https://github.com/home-assistant/core/pull/59460
+[#59485]: https://github.com/home-assistant/core/pull/59485
+[#59515]: https://github.com/home-assistant/core/pull/59515
+[#59532]: https://github.com/home-assistant/core/pull/59532
+[@bdraco]: https://github.com/bdraco
+[@bramkragten]: https://github.com/bramkragten
+[@dgomes]: https://github.com/dgomes
+[@enegaard]: https://github.com/enegaard
+[@kbickar]: https://github.com/kbickar
+[@sergeymaysak]: https://github.com/sergeymaysak
+[@uvjustin]: https://github.com/uvjustin
+[emulated_kasa docs]: /integrations/emulated_kasa/
+[frontend docs]: /integrations/frontend/
+[integration docs]: /integrations/integration/
+[rpi_camera docs]: /integrations/rpi_camera/
+[sense docs]: /integrations/sense/
+[sonos docs]: /integrations/sonos/
+[stream docs]: /integrations/stream/
+[wirelesstag docs]: /integrations/wirelesstag/
+
+## Release 2021.11.4 - November 15
+
+- Air visual : robustness at startup when evaluate time interval ([@jugla] - [#59544]) ([airvisual docs])
+- Override api url in norway_air ([@ludeeus] - [#59573]) ([norway_air docs]) ([met docs])
+- Fix firmware status check for Fritz ([@chemelli74] - [#59578]) ([fritz docs])
+- Always use a step size of 1 for z-wave js fans ([@mkowalchuk] - [#59622]) ([zwave_js docs])
+- Fix favorite RPM max value in Xiaomi Miio ([@bieniu] - [#59631]) ([xiaomi_miio docs])
+- Bump zeroconf to 0.36.12 ([@bdraco] - [#59133]) ([zeroconf docs])
+- Bump zeroconf to 0.36.13 ([@bdraco] - [#59644]) ([zeroconf docs])
+- Bump greecliamate to 0.12.4 ([@cmroche] - [#59645]) ([gree docs])
+- Ensure flux_led bulbs turn on even if brightness is 0 ([@bdraco] - [#59661])
+- Update aiolookin to 0.0.4 version ([@ANMalko] - [#59684]) ([lookin docs])
+- Fix bug in AirVisual re-auth ([@bachya] - [#59685]) ([airvisual docs])
+- Bump greeclimate to 0.12.5 ([@cmroche] - [#59730]) ([gree docs])
+- Bump flux_led to 0.24.21 ([@bdraco] - [#59662]) ([flux_led docs])
+- Bump flux_led to 0.24.24 ([@bdraco] - [#59740]) ([flux_led docs])
+- Fix invalid string syntax in French OwnTracks config flow ([@spacegaier] - [#59752]) ([owntracks docs])
+
+[#59133]: https://github.com/home-assistant/core/pull/59133
+[#59544]: https://github.com/home-assistant/core/pull/59544
+[#59573]: https://github.com/home-assistant/core/pull/59573
+[#59578]: https://github.com/home-assistant/core/pull/59578
+[#59622]: https://github.com/home-assistant/core/pull/59622
+[#59631]: https://github.com/home-assistant/core/pull/59631
+[#59644]: https://github.com/home-assistant/core/pull/59644
+[#59645]: https://github.com/home-assistant/core/pull/59645
+[#59661]: https://github.com/home-assistant/core/pull/59661
+[#59662]: https://github.com/home-assistant/core/pull/59662
+[#59684]: https://github.com/home-assistant/core/pull/59684
+[#59685]: https://github.com/home-assistant/core/pull/59685
+[#59730]: https://github.com/home-assistant/core/pull/59730
+[#59740]: https://github.com/home-assistant/core/pull/59740
+[#59752]: https://github.com/home-assistant/core/pull/59752
+[@ANMalko]: https://github.com/ANMalko
+[@bachya]: https://github.com/bachya
+[@bdraco]: https://github.com/bdraco
+[@bieniu]: https://github.com/bieniu
+[@chemelli74]: https://github.com/chemelli74
+[@cmroche]: https://github.com/cmroche
+[@jugla]: https://github.com/jugla
+[@ludeeus]: https://github.com/ludeeus
+[@mkowalchuk]: https://github.com/mkowalchuk
+[@spacegaier]: https://github.com/spacegaier
+[airvisual docs]: /integrations/airvisual/
+[flux_led docs]: /integrations/flux_led/
+[fritz docs]: /integrations/fritz/
+[gree docs]: /integrations/gree/
+[lookin docs]: /integrations/lookin/
+[met docs]: /integrations/met/
+[norway_air docs]: /integrations/norway_air/
+[owntracks docs]: /integrations/owntracks/
+[xiaomi_miio docs]: /integrations/xiaomi_miio/
+[zeroconf docs]: /integrations/zeroconf/
+[zwave_js docs]: /integrations/zwave_js/
+
+## Release 2021.11.5 - November 19
+
+- Use source list property instead of the attribute in Denon AVR integration ([@bieniu] - [#59768]) ([denonavr docs])
+- Fix typo in attribute for Fritz ([@chemelli74] - [#59791]) ([fritz docs])
+- Fix Netgear init error on orbi models ([@starkillerOG] - [#59799]) ([netgear docs])
+- Bump velbusaio to 2021.11.7 ([@Cereal2nd] - [#59817]) ([velbus docs])
+- Fix invalid string syntax in OwnTracks config flow translations ([@spacegaier] - [#59838]) ([owntracks docs])
+- Strip out deleted entities when configuring homekit ([@bdraco] - [#59844]) ([homekit docs])
+- Bugfix in Tuya Number value scaling ([@PlusPlus-ua] - [#59903]) ([tuya docs])
+- Fix Tuya back scaling in Climate and Humidifer entities ([@frenck] - [#59909]) ([tuya docs])
+- Store: copy pending data ([@balloob] - [#59934])
+- Remove test_check_package_version_does_not_match ([@emontnemery] - [#59785])
+
+[#59768]: https://github.com/home-assistant/core/pull/59768
+[#59785]: https://github.com/home-assistant/core/pull/59785
+[#59791]: https://github.com/home-assistant/core/pull/59791
+[#59799]: https://github.com/home-assistant/core/pull/59799
+[#59817]: https://github.com/home-assistant/core/pull/59817
+[#59838]: https://github.com/home-assistant/core/pull/59838
+[#59844]: https://github.com/home-assistant/core/pull/59844
+[#59903]: https://github.com/home-assistant/core/pull/59903
+[#59909]: https://github.com/home-assistant/core/pull/59909
+[#59934]: https://github.com/home-assistant/core/pull/59934
+[@Cereal2nd]: https://github.com/Cereal2nd
+[@PlusPlus-ua]: https://github.com/PlusPlus-ua
+[@balloob]: https://github.com/balloob
+[@bdraco]: https://github.com/bdraco
+[@bieniu]: https://github.com/bieniu
+[@chemelli74]: https://github.com/chemelli74
+[@emontnemery]: https://github.com/emontnemery
+[@frenck]: https://github.com/frenck
+[@spacegaier]: https://github.com/spacegaier
+[@starkillerOG]: https://github.com/starkillerOG
+[denonavr docs]: /integrations/denonavr/
+[fritz docs]: /integrations/fritz/
+[homekit docs]: /integrations/homekit/
+[netgear docs]: /integrations/netgear/
+[owntracks docs]: /integrations/owntracks/
+[tuya docs]: /integrations/tuya/
+[velbus docs]: /integrations/velbus/
+
## If you need help...
...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e).
diff --git a/source/_posts/2021-11-12-100k-analytics.markdown b/source/_posts/2021-11-12-100k-analytics.markdown
new file mode 100644
index 00000000000..56d4218dc29
--- /dev/null
+++ b/source/_posts/2021-11-12-100k-analytics.markdown
@@ -0,0 +1,122 @@
+---
+layout: post
+title: "100,000 installations in analytics!"
+description: "Our opt-in analytics have reached their first milestone: 100k users."
+date: 2021-11-12 00:00:00
+date_formatted: "November 12, 2021"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories:
+- Announcement
+og_image: /images/blog/2021-11-analytics/social.png
+---
+
+
+
+Today we have reached a major milestone for [Home Assistant Analytics][analytics]: 100,000 users have opted in to be included!
+
+This is a big deal because it's not enabled by default, users have to opt-in, and we only launched Home Assistant Analytics last April. We promoted it in the release blog post and during live streams, but have never nagged existing users in the interface. New users did get asked to opt-in as part of onboarding.
+
+The 100,000 installations are not the total number of Home Assistant users. The truth here is that we don't know the total number of installations because Home Assistant is private by design. Our estimate is that there are 4-5x more installations than people that opt-in to analytics.
+
+_For the latest version of the graphs in this post, visit [Home Assistant Analytics][analytics]_
+
+
+
+
+
+## Why we collect data
+
+It's good to start off with why we allow users to opt-in to share some data with us.
+
+Manufacturers of IoT products live in their own world in which we have little presence. We don't have stands at CES or other trade shows. Instead, manufacturers see we're open source and assume it's a small user base. They assume the ability to integrate with Home Assistant and other platforms is not profitable enough to allocate resources to add the necessary APIs to integrate.
+
+With the data collected by Home Assistant Analytics, we can show that providing an API can expand their market around the globe.
+
+
+
+Screenshot of analytics during Home Assistant onboarding
+
+
+## How people run Home Assistant
+
+The collected data is also used to give us, the Home Assistant developers, insight into how Home Assistant is installed and what we should improve. As you can see in our installation breakdown, the operating system installation type is by far the most popular. This makes sense because it is our recommended installation type and the easiest to use. It gives the full Home Assistant experience and can be fully managed via the user interface. No text editors, Linux experience, or computer science degree necessary.
+
+
+
+The board breakdown below only applies to the operating system installation type. The Raspberry Pi family of devices is by far the most popular way of running Home Assistant, followed by running it in a virtual machine. Running Home Assistant in a virtual machine is popular because it is our recommended approach for people that already have a server at home.
+
+
+
+## Tracking updates
+
+We have spent a lot of time making sure that it is easy to update both Home Assistant Core and Home Assistant Operating System. Ease of updates is important because when critical bugs or security issues arise, users should feel confident to hit the update button.
+
+Home Assistant can be updated using a single click in the interface and will automatically roll back if the update fails or the system fails to come online afterward. This gives our users the confidence to update and we see this reflected in the speed at which our users update when a new monthly release drops:
+
+
+
+
+
+## Home Assistant around the world
+
+It's our goal to make the privacy focused smart home a viable option for everyone, everywhere. That's why Home Assistant is free and open source, translated into 60 different languages and why we integrate with products from around the world, not just the ones that are big enough to come to America or Europe.
+
+As you can see on our map we have a global reach. Some countries only see a few users, like the country of Nepal having 13 installations. However, with open source all we need is 1 contributor to help translate our user interface into their native language and make it more accessible for speakers of that language. To learn more about helping translating Home Assistant, [check the documentation](https://developers.home-assistant.io/docs/translations).
+
+
+
+## Integrations
+
+There are multiple levels of analytics that users can opt-in to. The basic level is how you run Home Assistant but you can also share what integrations you use.
+
+This data is integrated into the Home Assistant website when users navigate the various integrations. It sometimes highlights certain integrations that serve their purpose but don't have a big audience, like the integration for the [Dublin bus schedule](/integrations/dublin_bus_transport/):
+
+
+
+However, more interesting is of course the most popular integrations. I'm always surprised how high MQTT is on this list and very happy to see ESPHome doing so well.
+
+| Rank | Integration | Installations
+| - | - | -
+| 1 | 
[FFmpeg](/integrations/ffmpeg/) | 35151 (43.5 %)
+| 2 | 
[Google Cast](/integrations/cast/) | 33252 (41.2 %)
+| 3 | 
[MQTT](/integrations/mqtt/) | 30338 (37.5 %)
+| 4 | 
[UPnP/IGD](/integrations/upnp/) | 22771 (28.2 %)
+| 5 | 
[Google Assistant](/integrations/google_assistant/) | 16422 (20.3 %)
+| 6 | 
[ESPHome](/integrations/esphome/) | 14315 (17.7 %)
+| 7 | 
[HomeKit](/integrations/homekit/) | 13705 (17.0 %)
+| 8 | 
[Philips Hue](/integrations/hue/) | 12592 (15.6 %)
+| 9 | 
[System Monitor](/integrations/system_monitor/) | 12110 (15.0 %)
+| 10 | 
[Spotify](/integrations/spotify/) | 11533 (14.3 %)
+
+_For the full list, see [Home Assistant Analytics][analytics-integrations]._
+
+We see that integrations that offer automated discovery do very well. This makes sense because once discovered we'll prompt the user to set them up:
+
+
+
+Screenshot of setting up integrations during Home Assistant onboarding
+
+
+## Statistics
+
+It is also possible to share some basic statistics about your installation like how many states and users you have.
+
+- Average number of automations: 24
+- Average number of integrations: 74
+- Average number of installed add-ons: 7.01
+- Average number of entities: 204
+- Average number of users: 1.87
+
+It's impressive to see the high number of integrations and entities that are being used in Home Assistant. Our users sure love automating their homes!
+
+## Opt-in to analytics!
+
+If you haven't yet, please opt-in to Home Assistant Analytics by clicking the button below to help us and manufacturers better understand our impact.
+
+{% my general badge %}
+
+[analytics]: https://analytics.home-assistant.io
+[analytics-integrations]: https://analytics.home-assistant.io/#integrations
+[analytics-source]: https://github.com/home-assistant/analytics.home-assistant.io/
diff --git a/source/_posts/2021-11-27-netdaemon-release.markdown b/source/_posts/2021-11-27-netdaemon-release.markdown
new file mode 100644
index 00000000000..23f512327e8
--- /dev/null
+++ b/source/_posts/2021-11-27-netdaemon-release.markdown
@@ -0,0 +1,22 @@
+---
+layout: post
+title: "New NetDaemon Release: Use C# to automate Home Assistant"
+description: "NetDaemon just released a new version of their .Net platform for Home Assistant"
+date: 2021-11-27 00:00:00
+date_formatted: "November 27, 2021"
+author: Frank Bakker
+comments: true
+categories:
+- Announcement
+og_image: /images/blog/2021-11-NetDaemon/NetDaemonLogo.png
+---
+
+
+
+Great news for Home Assistant users who's preferred way of coding is C#: [NetDaemon](https://netdaemon.xyz/) has just released a new version of their open source platform that allows you to use C# 10 for .Net 6 to write your applications or automations for Home Assistant.
+
+This release includes a new API called [`HassModel`](https://netdaemon.xyz/docs/hass_model/hass_model) which makes it easier than ever to interact with Home Assistant from .Net. It generates strong typed interfaces based on the entities in your own Home Assistant instance, their attributes and all available services and their parameters. Intellisense can be used to discover all your entities and available services directly from your IDE.
+
+[Check out the documentation and how to get started with NetDaemon](https://netdaemon.xyz/)
+
+_This project is not affiliated with Home Assistant, but leverages our [open API](https://developers.home-assistant.io/docs/api/websocket)._
diff --git a/source/_redirects b/source/_redirects
index 6eec93367d4..2ca0cb706f9 100644
--- a/source/_redirects
+++ b/source/_redirects
@@ -11,7 +11,9 @@
/energy /home-energy-management
/integrations/energy /docs/energy 301!
-/amber https://www.crowdsupply.com/nabu-casa/home-assistant-amber
+/amber https://www.crowdsupply.com/nabu-casa/home-assistant-yellow
+/yellow https://www.crowdsupply.com/nabu-casa/home-assistant-yellow
+/blog/2021/09/13/home-assistant-amber/ /blog/2021/09/13/home-assistant-yellow/
# Older development pages
/developers https://developers.home-assistant.io
diff --git a/source/blue/index.html b/source/blue/index.html
index 8a741f05aee..b228e100fc2 100644
--- a/source/blue/index.html
+++ b/source/blue/index.html
@@ -585,11 +585,11 @@ All other parts of the bundle will remain available for purchase.
{% enddetails %}
-{% details "What is the difference with Home Assistant Amber?" %}
+{% details "What is the difference with Home Assistant Yellow?" %}
We partnered with a single-board computer (SBC) manufacturer to introduce Home Assistant Blue, our first foray into creating hardware that runs Home Assistant. Home Assistant Blue was always meant to be a limited edition and its production has been discontinued.
-Though Blue has been limited, we will continue to support it and, just like Amber, it is able to run the latest version of Home Assistant.
+Though Home Assistant Blue has been limited, we will continue to support it and, just like Home Assistant Yellow, it is able to run the latest version of Home Assistant.
{% enddetails %}
diff --git a/source/examples/index.markdown b/source/examples/index.markdown
index c45af3e8d26..8190d71582d 100644
--- a/source/examples/index.markdown
+++ b/source/examples/index.markdown
@@ -21,7 +21,7 @@ A great place to find popular configurations is on this
## Popular Blueprints
-This is a list of the most popular [blueprints](/integrations/blueprint) in the [Blueprint Exchange category on the forums](https://community.home-assistant.io/c/blueprints-exchange/53/l/top/all).
+This is a list of the most popular [blueprints](/integrations/blueprint) in the [Blueprint Exchange category on the forums](https://www.home-assistant.io/get-blueprints).
{% for post in site.data.blueprint_exchange_data limit:25 %}
diff --git a/source/images/blog/2021-09-home-assistant-amber/overview.png b/source/images/blog/2021-09-home-assistant-amber/overview.png
deleted file mode 100644
index 8fec5ddba7c..00000000000
Binary files a/source/images/blog/2021-09-home-assistant-amber/overview.png and /dev/null differ
diff --git a/source/images/blog/2021-09-home-assistant-amber/social.png b/source/images/blog/2021-09-home-assistant-amber/social.png
deleted file mode 100644
index 8fcef7dfb19..00000000000
Binary files a/source/images/blog/2021-09-home-assistant-amber/social.png and /dev/null differ
diff --git a/source/images/blog/2021-09-home-assistant-yellow/overview.png b/source/images/blog/2021-09-home-assistant-yellow/overview.png
new file mode 100644
index 00000000000..8edf7d7d95d
Binary files /dev/null and b/source/images/blog/2021-09-home-assistant-yellow/overview.png differ
diff --git a/source/images/blog/2021-09-home-assistant-yellow/social.png b/source/images/blog/2021-09-home-assistant-yellow/social.png
new file mode 100644
index 00000000000..253fa607c30
Binary files /dev/null and b/source/images/blog/2021-09-home-assistant-yellow/social.png differ
diff --git a/source/images/blog/2021-11-NetDaemon/NetDaemonLogo.png b/source/images/blog/2021-11-NetDaemon/NetDaemonLogo.png
new file mode 100644
index 00000000000..9116ba0b6e6
Binary files /dev/null and b/source/images/blog/2021-11-NetDaemon/NetDaemonLogo.png differ
diff --git a/source/images/blog/2021-11-analytics/active-installations.png b/source/images/blog/2021-11-analytics/active-installations.png
new file mode 100644
index 00000000000..ee68a0ee5de
Binary files /dev/null and b/source/images/blog/2021-11-analytics/active-installations.png differ
diff --git a/source/images/blog/2021-11-analytics/board-breakdown.png b/source/images/blog/2021-11-analytics/board-breakdown.png
new file mode 100644
index 00000000000..cebae9da1ee
Binary files /dev/null and b/source/images/blog/2021-11-analytics/board-breakdown.png differ
diff --git a/source/images/blog/2021-11-analytics/discovery.png b/source/images/blog/2021-11-analytics/discovery.png
new file mode 100644
index 00000000000..b450b8106f8
Binary files /dev/null and b/source/images/blog/2021-11-analytics/discovery.png differ
diff --git a/source/images/blog/2021-11-analytics/dublin-bus-stats.png b/source/images/blog/2021-11-analytics/dublin-bus-stats.png
new file mode 100644
index 00000000000..bbcaaeb4f87
Binary files /dev/null and b/source/images/blog/2021-11-analytics/dublin-bus-stats.png differ
diff --git a/source/images/blog/2021-11-analytics/installation-types.png b/source/images/blog/2021-11-analytics/installation-types.png
new file mode 100644
index 00000000000..daac3599292
Binary files /dev/null and b/source/images/blog/2021-11-analytics/installation-types.png differ
diff --git a/source/images/blog/2021-11-analytics/map.png b/source/images/blog/2021-11-analytics/map.png
new file mode 100644
index 00000000000..d0129cdf541
Binary files /dev/null and b/source/images/blog/2021-11-analytics/map.png differ
diff --git a/source/images/blog/2021-11-analytics/onboarding-analytics.png b/source/images/blog/2021-11-analytics/onboarding-analytics.png
new file mode 100644
index 00000000000..38ad018a513
Binary files /dev/null and b/source/images/blog/2021-11-analytics/onboarding-analytics.png differ
diff --git a/source/images/blog/2021-11-analytics/onboarding-discovery.png b/source/images/blog/2021-11-analytics/onboarding-discovery.png
new file mode 100644
index 00000000000..12f722e48fd
Binary files /dev/null and b/source/images/blog/2021-11-analytics/onboarding-discovery.png differ
diff --git a/source/images/blog/2021-11-analytics/os-breakdown.png b/source/images/blog/2021-11-analytics/os-breakdown.png
new file mode 100644
index 00000000000..14342552cb4
Binary files /dev/null and b/source/images/blog/2021-11-analytics/os-breakdown.png differ
diff --git a/source/images/blog/2021-11-analytics/release-breakdown.png b/source/images/blog/2021-11-analytics/release-breakdown.png
new file mode 100644
index 00000000000..9e1e8236e88
Binary files /dev/null and b/source/images/blog/2021-11-analytics/release-breakdown.png differ
diff --git a/source/images/blog/2021-11-analytics/social.png b/source/images/blog/2021-11-analytics/social.png
new file mode 100644
index 00000000000..81b8b399ad5
Binary files /dev/null and b/source/images/blog/2021-11-analytics/social.png differ
diff --git a/source/images/blog/2021-11-analytics/statistics.png b/source/images/blog/2021-11-analytics/statistics.png
new file mode 100644
index 00000000000..f075032bed6
Binary files /dev/null and b/source/images/blog/2021-11-analytics/statistics.png differ
diff --git a/source/images/blog/2021-11-analytics/version-history.png b/source/images/blog/2021-11-analytics/version-history.png
new file mode 100644
index 00000000000..905a1290d70
Binary files /dev/null and b/source/images/blog/2021-11-analytics/version-history.png differ
diff --git a/source/images/frontpage/amber-frontpage.jpg b/source/images/frontpage/amber-frontpage.jpg
deleted file mode 100644
index 48def1b7cee..00000000000
Binary files a/source/images/frontpage/amber-frontpage.jpg and /dev/null differ
diff --git a/source/images/frontpage/yellow-frontpage.jpg b/source/images/frontpage/yellow-frontpage.jpg
new file mode 100644
index 00000000000..a2520c94789
Binary files /dev/null and b/source/images/frontpage/yellow-frontpage.jpg differ
diff --git a/source/images/integrations/iammeter/demo.jpg b/source/images/integrations/iammeter/demo.jpg
deleted file mode 100644
index 57eede1761a..00000000000
Binary files a/source/images/integrations/iammeter/demo.jpg and /dev/null differ
diff --git a/source/images/integrations/tasmota/tasmota_button_automations.png b/source/images/integrations/tasmota/tasmota_button_automations.png
new file mode 100644
index 00000000000..9ff3fcbb263
Binary files /dev/null and b/source/images/integrations/tasmota/tasmota_button_automations.png differ
diff --git a/source/images/integrations/tasmota/tasmota_status_sensors.png b/source/images/integrations/tasmota/tasmota_status_sensors.png
new file mode 100644
index 00000000000..e890363d569
Binary files /dev/null and b/source/images/integrations/tasmota/tasmota_status_sensors.png differ
diff --git a/source/images/state-of-the-open-home/promo.png b/source/images/state-of-the-open-home/promo.png
new file mode 100644
index 00000000000..fdb48defbc5
Binary files /dev/null and b/source/images/state-of-the-open-home/promo.png differ
diff --git a/source/images/state-of-the-open-home/social.png b/source/images/state-of-the-open-home/social.png
new file mode 100644
index 00000000000..816cf78c1d6
Binary files /dev/null and b/source/images/state-of-the-open-home/social.png differ
diff --git a/source/index.html b/source/index.html
index c61a38e866a..29483e0c658 100644
--- a/source/index.html
+++ b/source/index.html
@@ -90,18 +90,28 @@ feedback: false
+
+
+
- Home Assistant Amber
+ Home Assistant Yellow
- Join our crowdfunding campaign for the easiest way to run Home Assistant
+ The easiest way to run Home Assistant. Now available for pre-order.
diff --git a/source/more-info/local-media/setup-media.markdown b/source/more-info/local-media/setup-media.markdown
index cc6d1618ae9..3dc217bfd72 100644
--- a/source/more-info/local-media/setup-media.markdown
+++ b/source/more-info/local-media/setup-media.markdown
@@ -4,7 +4,7 @@ description: "More information on how to set up local media sources in Home Assi
---
In order to use the media browser with Home Assistant, it needs to know where to
-find you local media.
+find your local media.
## Home Assistant OS and Supervised
diff --git a/source/state-of-the-open-home/index.markdown b/source/state-of-the-open-home/index.markdown
new file mode 100644
index 00000000000..b836abc581f
--- /dev/null
+++ b/source/state-of-the-open-home/index.markdown
@@ -0,0 +1,22 @@
+---
+title: State of the Open Home 2021
+show_title: false
+feedback: false
+description: December 11, 2021 we will host the State of the Open Home.
+og_image: /images/state-of-the-open-home/social.png
+---
+
+
+
+Where: YouTube
+When: Saturday, December 11, at 11am PST / 8pm CET
+
+For over 8 years we've been working on the open home. We envision the open home as one where you are in control of the technology, your data and who can access it. At the State of the Open Home 2021 we will present on the progress we made this year in making the open home a viable choice for everyone.
+
+The event is hosted by Nabu Casa, Home Assistant & ESPHome and we'll be joined by our friends from WLED and Z-Wave JS to talk about our work on making this vision a reality.
+
+To be notified when the live stream is online, [visit YouTube](https://www.youtube.com/watch?v=6ZMXE5PXPqU) and click “Set Reminder”.
+
+
+
+