home-assistant · tymm · Mar 30, 2023 · Mar 30, 2023 · Mar 30, 2023 · Mar 31, 2023
diff --git a/Gemfile.lock b/Gemfile.lock
@@ -115,7 +115,7 @@ GEM
     tilt (2.1.0)
     tzinfo (2.0.6)
       concurrent-ruby (~> 1.0)
-    tzinfo-data (1.2023.2)
+    tzinfo-data (1.2023.3)
       tzinfo (>= 1.0.0)
     unicode-display_width (2.4.2)
     webrick (1.8.1)

diff --git a/source/_docs/energy/electricity-grid.markdown b/source/_docs/energy/electricity-grid.markdown
@@ -61,7 +61,7 @@ CT clamp sensors measure your energy usage by looking at the current passing thr
 
 The off-the-shelf solution that we advise is the [Shelly EM](https://shop.shelly.cloud/shelly-em-2-x-120a-clamp-wifi-smart-home-automation?tracking=A7FsiPIfUWsFpnfKHa8SRyUYLXjr2hPq). The device has a local API, updates are pushed to Home Assistant and it has a high quality integration.
 
-You can build your own using ESPHome's [CT Clamp Current sensor](https://esphome.io/components/sensor/ct_clamp.html) or energy meter sensors like the [ATM90E32](https://esphome.io/components/sensor/atm90e32.html). For the DIY route, check out [this video by digiblur](https://www.youtube.com/watch?v=n2XZzciz0s4) to get started.
+You can build your own using ESPHome's [CT Clamp Current sensor](https://esphome.io/components/sensor/ct_clamp.html) or energy meter sensors like the [ATM90E32](https://esphome.io/components/sensor/atm90e32.html) or [PZEM-004T V3](https://esphome.io/components/sensor/pzemac.html). For the DIY route, check out [this video by digiblur](https://www.youtube.com/watch?v=n2XZzciz0s4) to get started.
 
 _Attention! Installing CT clamp sensor devices requires opening your electrical cabinet. This work should be done by someone familiar with electrical wiring. Your qualified installer will know how to do this._
 

diff --git a/source/_integrations/ecobee.markdown b/source/_integrations/ecobee.markdown
@@ -58,7 +58,7 @@ Your new application will now appear on the left. Upon clicking on the applicati
 
 1. In the **Settings** -> **Devices & Services** menu, click **+** and then select "ecobee" from the pop-up menu.
 2. In the pop-up box, enter the API key you obtained from ecobee's [developer portal](https://ecobee.com/developers).
-3. In the next pop-up box, you will be presented with a unique four-character PIN code which you will need to authorize in the [ecobee consumer portal](https://www.ecobee.com/consumerportal/index.html). You can do this by logging in, selecting **My Apps** from the hamburger menu, clicking **Add Application** on the left, entering the PIN code from Home Assistant, clicking **Validate** and then **Add Application** in the bottom right.
+3. In the next pop-up box, you will be presented with a unique 8 character code separated by a dash (format: XXXX-XXXX), which you will need to authorize in the [ecobee consumer portal](https://www.ecobee.com/consumerportal/index.html). You can do this by logging in, selecting **My Apps** from the hamburger menu, clicking **Add Application** on the left, entering the PIN code from Home Assistant, clicking **Validate** and then **Add Application** in the bottom right.
 4. After authorizing the app with ecobee, return to Home Assistant and click **Submit**. If the authorization was successful, a configuration entry will be created and your thermostats, ventilators and sensors will be available in Home Assistant.
 
 ## Manual Configuration

@@ -109,8 +109,3 @@ The following models are lacking the HTTP webserver API and can therfore not wor
 - Older firmware versions do not expose the necessary information the integration needs to function. Ensure the camera is updated to the [latest firmware](https://reolink.com/download-center/) prior to setting up the integration. Note that Reolink auto update and check for update functions in the app/windows/web client often do not show the latest available firmware version. Therefore check the version in the [Reolink download center](https://reolink.com/download-center/) online.
 - Ensure at least one of the HTTP/HTTPS ports is enabled in the [windows](https://reolink.com/software-and-manual/)/web client under `Settings`->`Network`->`Advanced`->`Port Settings`, see [additional instructions](https://support.reolink.com/hc/en-us/articles/900004435763-How-to-Set-up-Reolink-Ports-Settings-via-Reolink-Client-New-Client-) on the Reolink site.
 - On some camera models, the RTMP port needs to be enabled in order for the HTTP(S) port to function properly. Make sure this port is also enabled if you get a `Cannot connect to host` error while one of the HTTP/HTTPS ports is already enabled.
-
-## Reolink firmware limitations
-
-- The Reolink NVR only sends event-notifications if motion happens on the camera connected to the first (index "0") channel, therefore the binary sensors of all channels will only be updated when the first channel sees motion. Beta NVR firmware v3.0.0.211_23011204 fixes this issue, you can request beta firmware from reolink support, release firmware is expected in a few weeks.
-- Reolink doorbell presses only generate ONVIF event notifications when the doorbell is directly connected to your network. The doorbell visitor binary sensor will not work when connecting the Reolink doorbell to an NVR. Beta NVR firmware v3.0.0.211_23011204 fixes this issue, you can request beta firmware from reolink support, release firmware is expected in a few weeks.
diff --git a/source/_integrations/simplepush.markdown b/source/_integrations/simplepush.markdown
@@ -14,17 +14,55 @@ ha_codeowners:
   - '@engrbm87'
 ---
 
-The `simplepush` platform uses [Simplepush](https://simplepush.io/) to deliver notifications from Home Assistant to your Android device. Unlike similar apps the Simplepush app requires no registration.
+The `simplepush` platform uses [Simplepush](https://simplepush.io/) to deliver notifications from Home Assistant to your Android and iOS device. Unlike similar apps the Simplepush app requires no registration and supports end-to-end encryption.
 
 {% include integrations/config_flow.md %}
 
 To test if the service works, just send a message with `curl` from the command-line.
 
 ```bash
-curl 'https://api.simplepush.io/send/device_key/title/message'
+curl 'https://simplepu.sh/YOUR_SIMPLEPUSH_KEY/message'
 ```
+
+If you enter your password and salt (as defined in the Simplepush app settings) during the configuration of this integration, all notifications sent from this integration will be end-to-end encrypted.
+
 ## Notifications
 
-Simplepush can send a notification by calling the [`notify` service](/integrations/notify/). You can specify the `event` under the `data` key. This will override the event configured in YAML when imported.
+Simplepush can send a notification by calling the [`notify` service](/integrations/notify/).
+
+You can specify the `event` under the `data` key.
+Events can be used to customize the notification behaviour.
+
+It is also possible to specify `attachments` under the `data` key.
+Attachments can be images, GIFs or video files that are accessible by an URL.
 
 To use notifications, please see the [getting started with automation page](/getting-started/automation/).
+
+## Examples 
+
+Send a notification with a title and event.
+
+```yml
+- service: notify.simplepush
+    data:
+      title: "This is the title"
+      message: "This is the message"
+      data:
+        event: "event"
+```
+
+Send a notification with four attachments defined by their URL.
+Attachments can be images, GIFs or video files.
+
+```yml
+- service: notify.simplepush
+    data:
+      message: "This is the message"
+      data:
+        attachments:
+          - image: "https://upload.wikimedia.org/wikipedia/commons/e/ee/Sample_abc.jpg"
+          - image: "https://upload.wikimedia.org/wikipedia/commons/d/d3/Newtons_cradle_animation_book_2.gif"
+          - video: "http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4"
+          - video: "http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/ElephantsDream.mp4"
+            thumbnail: "http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/images/ForBiggerEscapes.jpg"
+```
@@ -68,10 +68,11 @@ This integration requires an internet accessible incoming webhook to receive pus
 
 ## Setup instructions
 
-After completing the prerequisite steps above you are ready to setup the integration! See [troubleshooting](#troubleshooting) if you are having issues setting up the integration.
+After completing the prerequisite steps above, you are ready to setup the integration! See [troubleshooting](#troubleshooting) if you are having issues setting up the integration.
 
-1. From Home Assistant, navigate to 'Configuration' then 'Integrations'. Click the plus icon and type/select 'SmartThings'.
-1. Confirm the callback URL is correct. If using Home Assistant Cloud it will start with `https://hooks.nabuca.casa`. If the URL is not correct, update your Home Assistant configuration, restart, and try again.
+{% include integrations/config_flow.md %}
+
+1. Confirm the callback URL is correct. If using Home Assistant Cloud, it will start with `https://hooks.nabuca.casa`. If the URL is not correct, update your Home Assistant configuration, restart, and try again.
 1. Enter your Personal Access Token.
 1. Select the SmartThings Location to add to Home Assistant.
 1. On the window that opens:

diff --git a/source/_posts/2023-03-31-android-20233.markdown b/source/_posts/2023-03-31-android-20233.markdown
@@ -0,0 +1,127 @@
+---
+layout: post
+title: "Android 2023.3: Multiple servers & Windows 11 app"
+description: "It's finally here: add multiple servers to the Home Assistant Android app, install the app on Windows 11 devices and more!"
+date: 2023-03-30 00:00:00
+date_formatted: "March 30, 2023"
+author: Joris Pelgröm
+comments: true
+categories:
+ - Release-Notes
+og_image: /images/blog/2023-03-30-android/social.png
+---
+
+![Home Assistant logo with 'Android Companion 2023.3' text](/images/blog/2023-03-30-android/social.png)
+
+It's finally here, one of the most common feature requests for the Home Assistant
+Android Companion app: you can now configure multiple Home Assistant servers. The
+app can send sensor updates to all servers and easily mix and match widgets, tiles,
+and controls for different servers 🎉
+
+Plus, a preview of the Home Assistant app is now available via the Amazon Appstore
+on Windows 11, which allows you to quickly connect your computer to Home Assistant.
+
+There are also other changes that add some polish to the app and improve support
+for features in the latest Home Assistant releases, so let's dig into the update!
+
+## Configure multiple Home Assistant servers
+
+Sometimes, one Home Assistant instance is not enough. You like Home Assistant so
+much that you decide to help someone else get started, there's a second home in
+your life, or you regularly visit someplace else where they're using Home Assistant.
+
+Before this update, if you wanted to access more than one server it was a bit of a
+hassle. Switching apps, creating bookmarks, and using different profiles. Let alone
+connecting your Android device to multiple servers for features like sensors
+and notifications.
+
+This issue now belongs to the past, as there's a new option in **{% my config title="Settings" %}** >
+**Companion app** to configure a second server, and another one after that, and another...
+They will all show up in the app, and you can use all features you've come to
+expect, like lots of sensors for your device and support for push notifications.
+Each one gets individual settings, so if you don't want to share your step count
+and enable location tracking everywhere, that's OK.
+
+![Screenshots of a phone showing different dashboards in the app, one of them showing a pop-up titled 'Choose server'](/images/blog/2023-03-30-android/multiserver.png)
+
+That's not all - you can also use all servers _outside_ the app, mixing and
+matching servers when using shortcuts, notifications, widgets, tiles and controls.
+Toggling lights from three different homes side-by-side? No problem!
+
+Note: the Wear OS app does not yet support multiple servers.
+
+## Now available on Windows 11 (preview)
+
+The Home Assistant Android Companion app is now available [via the Amazon Appstore]
+on [supported Windows 11 devices]. While there are already great options to integrate your
+computer from the community out there, the Companion app makes it easy to start
+and benefits from all the work on the Android app, frequently adding new features.
+
+![Screenshot of the Home Assistant Android app on a Windows 11 device](/images/blog/2023-03-30-android/windows.png)
+
+Windows does not always provide correct information to the app and may shut down
+background work, including sensors, after several minutes, which is why we are
+releasing Windows 11 support for the app as a preview. Android support in Windows
+11 continues to get better and we intend to make adjustments to improve the
+experience in the future.
+
+[via the Amazon Appstore]: amzn://apps/android?asin=B09RP3DM5T
+[supported Windows 11 devices]: https://support.microsoft.com/windows/f8d0abb5-44ad-47d8-b9fb-ad6b1459ff6c
+
+## Refining Wear OS
+
+The Home Assistant app has been available for over a year now on Wear OS watches
+and continues to improve. Earlier this year, initial support for Assist was added,
+and in this update [@dshokouhi] made it easier to access using a watchface
+complication. Now Assist is only a tap away!
+
+Got a lot of entities and want to hide the clutter on your watch? You could already
+add favorites which would be displayed at the top of the app, but it would still load
+all entities below them. Now, there is an option to only show favorites to reduce
+what gets loaded and prevent accidental changes. Try it out and let us know if you
+prefer this more focused experience!
+
+![Screenshots of a Wear OS device, showing an Assist complication a watchface, updated launch screen, and favorites only home screen](/images/blog/2023-03-30-android/wear.png)
+
+[@SkechyWolf] and [@dshokouhi] also worked on the look and feel of the app to make it
+fit in better with other modern Wear apps.
+
+[@SkechyWolf]: https://github.com/SkechyWolf
+[@dshokouhi]: https://github.com/dshokouhi
+
+<!--more-->
+
+## Other noteworthy changes
+
+There's more in this update, here are some highlights:
+
+- Any sensor with a location attached will now show up for navigation when using Android
+  Auto. Nice one, [@dshokouhi]!
+- [@jpelgrom] added initial support for the new Thread integration in 2023.3. Thank you!
+- [@Adi146] and [@dshokouhi] worked to make the Beacon Monitor more reliable when in the
+  background and when toggling it on and off, nice to see improvements!
+- Put a lot of work in a custom dashboard, only to have it break on your phone because of
+  text that is ever so slightly too small or unwanted auto-rotation? No more, as [@dmiales]
+  tweaked settings to prevent this from happening!
+- Got a notification that should only show up on your watch? In the previous update, support
+  was added for notifications to the Wear OS app, and in this update work continues by
+  [@dshokouhi], with the app now supporting TTS notifications.
+
+Even more people worked on fixing bugs in this update, like [@Suxsem] and [@JBassett]. Thanks
+to all of those who contributed. If you have a good idea to improve the app or found a bug to
+fix, feel free to [join us on the forums] or [contribute on GitHub].
+
+[join us on the forums]: https://community.home-assistant.io/c/mobile-apps/android-companion/42
+[contribute on GitHub]: https://github.com/home-assistant/android
+[@Adi146]: https://github.com/Adi146
+[@dmiales]: https://github.com/dmiales
+[@JBassett]: https://github.com/JBassett
+[@jpelgrom]: https://github.com/jpelgrom
+[@Suxsem]: https://github.com/Suxsem
+
+## All changes
+
+You can find a complete list of all changes made for this update here:
+[Full changelog for Home Assistant Android 2023.3.0].
+
+[Full changelog for Home Assistant Android 2023.3.0]: https://github.com/home-assistant/android/releases/tag/2023.3.0
diff --git a/source/images/blog/2023-03-30-android/multiserver.png b/source/images/blog/2023-03-30-android/multiserver.png
diff --git a/source/images/blog/2023-03-30-android/social.png b/source/images/blog/2023-03-30-android/social.png
diff --git a/source/images/blog/2023-03-30-android/wear.png b/source/images/blog/2023-03-30-android/wear.png
diff --git a/source/images/blog/2023-03-30-android/windows.png b/source/images/blog/2023-03-30-android/windows.png