Merge branch 'current' into rc

Gemfile

@@ -4,7 +4,7 @@ ruby '> 2.5.0'
 
 group :development do
   gem 'rake', '13.0.6'
-  gem 'jekyll', '4.3.0'
+  gem 'jekyll', '4.3.1'
   gem 'compass', '1.0.3'
   gem 'sass-globbing', '1.1.5'
   gem 'stringex', '2.8.5'

Gemfile.lock

@@ -30,7 +30,7 @@ GEM
     http_parser.rb (0.8.0)
     i18n (1.12.0)
       concurrent-ruby (~> 1.0)
-    jekyll (4.3.0)
+    jekyll (4.3.1)
       addressable (~> 2.4)
       colorator (~> 1.0)
       em-websocket (~> 0.5)
@@ -107,7 +107,7 @@ GEM
     tilt (2.0.11)
     tzinfo (2.0.5)
       concurrent-ruby (~> 1.0)
-    tzinfo-data (1.2022.5)
+    tzinfo-data (1.2022.6)
       tzinfo (>= 1.0.0)
     unicode-display_width (2.3.0)
     webrick (1.7.0)
@@ -118,7 +118,7 @@ PLATFORMS
 
 DEPENDENCIES
   compass (= 1.0.3)
-  jekyll (= 4.3.0)
+  jekyll (= 4.3.1)
   jekyll-commonmark (= 1.4.0)
   jekyll-paginate (= 1.1.0)
   jekyll-sitemap (= 1.4.0)

source/_integrations/ezviz.markdown

@@ -79,13 +79,13 @@ If you have "sleep" mode enabled on your camera, you can use this service to wak
 
 To enable/disable motion detection, use the Home Assistant built in services. 
 
-### Service `camera.enable_motion_detection'
+### Service `camera.enable_motion_detection`
 
 | Service data attribute | Description |
 | -----------------------| ----------- |
 | `entity_id` | String or list of strings that point at `entity_id`s of cameras. Use `entity_id: all` to target all. |
 
-### Service `camera.disable_motion_detection'
+### Service `camera.disable_motion_detection`
 
 | Service data attribute | Description |
 | -----------------------| ----------- |

source/_integrations/forecast_solar.markdown

@@ -23,7 +23,7 @@ with weather forecasting.
 
 This integration provides an estimated forecast on how much energy your solar
 panels are going to produce, allowing you to plan ahead on how you spend your
-produced energy in most efficiently.
+produced energy most efficiently.
 
 As an example automation idea, you could determine if:
 
@@ -63,6 +63,8 @@ value.
 
 {% include integrations/config_flow.md %}
 
+If you have more than one plane of solar modules with different properties (e.g. several sides of the roof on different strings or on different buildings, with different directions or declinations) you can add the integration multiple times setting parameters accordingly. You can then use [template sensors](/integrations/template/) to combine the data, e.g. adding up production on different planes into one value to base your planning on.
+
 ## Sensors
 
 The Forecast.Solar integration mainly provides sensors that you can use in your
@@ -89,7 +91,7 @@ default. Enable those entities in the user interface if you like to use these:
 
 ## Using your Solar.Forecast account
 
-The [Forecast.Solar](https://forecast.solar/) can be used for free, but
+The [Forecast.Solar](https://forecast.solar/) public plan can be used for free, but
 the resolution of the data used is more limited and thus, there are less
 details for this integration to work with.
 
@@ -97,18 +99,18 @@ If you like the Forecast.Solar service, or are interested in more frequent data
 updates (based on a higher data resolution), you could [sign up for one
 of their plans](https://doc.forecast.solar/doku.php?id=account_models#compare_plans).
 
-To enable the use of the API key with this integration, to {% my integrations %}
+To enable the use of the API key with this integration, go to {% my integrations %}, 
-and click "Configure" on the Forecast.Solar integration instance and enter the
+click "Configure" on the Forecast.Solar integration instance and enter the
 API key for your account.
 
 ## Tweaking the estimations
 
 The estimation can be tweaked and tuned to match your solar setup better.
-Many factors that can cause the estimations to be slightly off
+There are many factors that can cause the estimations to be slightly off
 (but don't forget, it will always remain a forecast based on, e.g., weather
-and historical data).
+and historical data - not actual power produced).
 
-Luckily there are controls to make them more accurate for your situation,
+Luckily, there are controls to make them more accurate for your situation,
 for example, by slightly adjusting the azimuth or declination. If your panels
 catch a bit of shadow in the morning/evening, you could consider damping
 the results a bit.

source/_integrations/geniushub.markdown

@@ -207,7 +207,7 @@ This option is recommended only if Option 1 does not work. The MAC address shoul
 # Example configuration.yaml entry, using a Hub Token
 geniushub:
   token: GENIUS_HUB_TOKEN
-  mac : GENIUS_HUB_MAC
+  mac: GENIUS_HUB_MAC
 ```
 
 ```yaml

source/_integrations/ibeacon.markdown

@@ -69,10 +69,12 @@ To get the Estimated distance sensor to work, in most cases, it has to be calibr
 - [Blue Charm Beacons BC08-MultiBeacon](https://bluecharmbeacons.com/product/blue-charm-beacons-bluetooth-ble-ibeacon-bc08-multibeacon-w-motion-sensor-and-button-trigger-ble-5-0/)
 - Blue Charm Beacons BC037G-GeoPattern-iBeacon (discontinued)
 - Blue Charm Beacons BC037S-SmoothPattern-iBeacon (discontinued)
+- [Chipolo ONE](https://chipolo.net/products/chipolo-one)
 - [Feasycom FSC-BP103B](https://www.feasycom.com/bluetooth-ibeacon-da14531)
 - [Feasycom FSC-BP104D](https://www.feasycom.com/dialog-da14531-bluetooth-low-energy-beacon)
 - [Feasycom FSC-BP108](https://www.feasycom.com/bluetooth-5-1-waterproof-bluetooth-beacon)
 - [NRF51822 iBeacon](https://www.aliexpress.com/item/32826502025.html)
+- [NRF52810 iBeacon](https://www.aliexpress.com/item/1005003211033416.html)
 - [Pawscout Tag](https://pawscout.com/shop/pawscout-tag/)
 
 ## Example automation

source/_integrations/yeelightsunflower.markdown

@@ -38,7 +38,3 @@ host:
 <div class='note'>
 When the hub is loaded, your lights will appear as devices with their Zigbee IDs as part of the entity name.
 </div>
-
-<div class='note warning'>
-The Yeelight Sunflower hub supports SSDP discovery, but that has not been built into the platform. Let the developer know if that would be helpful to you.
-</div>

source/_posts/2022-10-27-jasco-partner.markdown

@@ -0,0 +1,29 @@
+---
+layout: post
+title: "Jasco joins Works with Home Assistant"
+description: "Jasco join the Works with Home Assistant partner program as a Z-Wave partner."
+date: 2022-10-26 00:00:00
+date_formatted: "October 26, 2022"
+author: Paulus Schoutsen
+author_twitter: balloob
+comments: true
+categories:
+- Announcements
+og_image: /images/blog/2022-10-27-jasco-partner/social.png
+---
+
+<img src='/images/blog/2022-10-27-jasco-partner/jasco-top.png' alt="Jasco and Works with Home Assistant logos" class='no-shadow'>
+<br><br>
+
+Today we are excited to announce that [Jasco](https://byjasco.com) has joined the Works with Home Assistant program as a Z-Wave partner.
+
+Jasco is well known in the US for their Z-Wave switches and plugs. As a partner, Jasco and Nabu Casa will be working together to ensure the best experience for connecting Jasco Z-Wave devices to Home Assistant.
+
+Jasco devices connect and integrate into Home Assistant using the Z-Wave integration (Z-Wave stick required). This means that connected Jasco devices work completely local and updates coming from the device are instantaneously reflected in Home Assistant. This allows for the best user experience when building your smart home.
+
+<img src='/images/blog/2022-10-27-jasco-partner/devices.jpg' alt="Jasco Enbrighten devices" class='no-shadow'>
+<br><br>
+
+One of Jasco’s claim to fame in the Home Assistant community is being the first company to [provide firmware files](https://building.open-home.io/open-home-birthday-special/#automatic-updates-for-z-wave-devices) (for 77 devices!) to the Z-Wave JS firmware update server. This service is used by Home Assistant to keep your devices secure. It is used to automatically detect if any of your Z-Wave devices have an updated firmware available and offer users to upgrade it.
+
+_[Learn more about the Works with Home Assistant partner program.](/blog/2022/07/12/partner-program/)_

source/_redirects

@@ -526,3 +526,6 @@
 
 # Lovelace images
 /images/dashboards/lovelace_* /images/dashboards/:splat
+
+# Unsupported reasons that are also unhealthy
+/more-info/unsupported/privileged /more-info/unhealthy/privileged

source/getting-started/presence-detection.markdown

@@ -3,7 +3,7 @@ title: "Setting up presence detection"
 description: "Instructions on how to setup presence detection within Home Assistant."
 ---
 
-Presence detection detects if people are home, which is the most valuable input for automation. Knowing who is home or where they are, will open a whole range of other automation options:
+Presence detection detects if people are home, which can be valuable input for automation. Knowing who is home or where they are, will open a whole range of other automation options:
 
 - Send me a notification when my child arrives at school
 - Turn on the AC when I leave work

source/more-info/unhealthy/privileged.markdown

@@ -1,6 +1,6 @@
 ---
 title: "Privileged"
-description: "More information on why not running with privileged marks the installation as unsupported."
+description: "More information on why not running with privileged marks the installation as unhealthy."
 ---
 
 ## The issue