Merge branch 'current' into next

Gemfile.lock

@@ -70,7 +70,7 @@ GEM
       nokogiri (~> 1.12)
     jekyll-watch (2.2.1)
       listen (~> 3.0)
-    json (2.13.1)
+    json (2.13.2)
     kramdown (2.5.1)
       rexml (>= 3.3.9)
     kramdown-parser-gfm (1.1.0)
@@ -142,10 +142,9 @@ GEM
     ruby2_keywords (0.0.5)
     safe_yaml (1.0.5)
     sass (3.4.25)
-    sass-embedded (1.89.2-arm64-darwin)
-      google-protobuf (~> 4.31)
-    sass-embedded (1.89.2-x86_64-linux-gnu)
+    sass-embedded (1.89.2)
       google-protobuf (~> 4.31)
+      rake (>= 13)
     sass-globbing (1.1.5)
       sass (>= 3.1)
     sassc (2.1.0)
@@ -199,4 +198,4 @@ RUBY VERSION
    ruby 2.6.2p47
 
 BUNDLED WITH
-   2.5.3
+   2.5.3

sass/homeassistant/base/_post.scss

@@ -119,5 +119,9 @@ article {
     .meta {
       margin-bottom: 3em;
     }
+
+    > header + img + p{
+      margin-top: 24px;
+    }
   }
 }

source/_dashboards/history-graph.markdown

@@ -95,9 +95,9 @@ name:
 
 ### Long term statistics
 
-Home Assistant saves long-term statistics for a sensor if the entity has a state_class of measurement, total, or total_increasing. For short-term statistics, a snapshot is taken every 5 minutes. For long-term statistics, an hourly aggregate is stored of the short-term statistics. Short-term statistics are automatically purged after a predefined period (default is 10 days). Long-term statistics are never purged.
+Home Assistant saves long-term statistics for a sensor if the entity has a state_class of measurement, total, or total_increasing. For long-term statistics, an hourly aggregate is stored from the sensor history. Long-term statistics are never purged.
 
-In the history graph card, if the hours to show variable is set to a figure higher than the purge_keep period, long-term statistics will be used, with short term statistics shown in bold.
+In the history graph card, if the hours to show variable is set to a figure higher than the recorder retention period, long-term statistics will backfill the older parts of the history graph, with more recent actual sensor values from the recorder shown in bold.
 
 ### Examples
 

source/_integrations/alexa_devices.markdown

@@ -98,6 +98,10 @@ The **Alexa Devices** {% term integration %} provides the following entities:
 - Sensor - temperature and illuminance sensors
 - Switch - Do not disturb
 
+## Known limitations
+
+This integration requires multifactor authentication using an authentication app (such as Microsoft Authenticator). To enable MFA, in your Amazon account settings, select **Login & Security** > **2-step verification** > **Backup methods** > **Add new app**. See [Amazon's documentation](https://www.amazon.com/gp/help/customer/display.html?nodeId=G9MX9LXNWXFKMJYU) for more information.
+
 ## Troubleshooting
 
 ### Can’t set up the integration

source/_integrations/binary_sensor.mqtt.markdown

@@ -145,7 +145,7 @@ entity_picture:
   required: false
   type: string
 expire_after:
-  description: If set, it defines the number of seconds after the sensor's state expires, if it's not updated. After expiry, the sensor's state becomes `unavailable`. Default the sensors state never expires.
+  description: If set, it defines the number of seconds after the sensor's state expires if it's not updated. After expiry, the sensor's state becomes `unavailable`. By default, the sensor's state never expires. Note that when a sensor's value was sent retained to the MQTT broker, the last value sent will be replayed by the MQTT broker when Home Assistant restarts or is reloaded. As this could cause the sensor to become available with an expired state, it is not recommended to retain the sensor's state payload at the MQTT broker. Home Assistant will store and restore the sensor's state for you and calculate the remaining time to retain the sensor's state before it becomes unavailable.
   required: false
   type: integer
 force_update:

source/_integrations/reolink.markdown

@@ -369,6 +369,8 @@ The following models have been tested and confirmed to work with a direct link t
 - [E1 Outdoor PoE](https://reolink.com/product/e1-outdoor-poe/)
 - [E1 Outdoor Pro](https://reolink.com/product/e1-outdoor-pro/)
 - [Elite Floodlight WiFi](https://reolink.com/product/elite-floodlight-wifi/)
+- [FE-P](https://reolink.com/product/fe-p/) (only "fisheye" or "5-in-1" view for the streams, not "dual panoramic", "quad", "cylindrical", "defished", or "hemispheric" view)
+- [FE-W](https://reolink.com/product/fe-w/) (only "fisheye" or "5-in-1" view for the streams, not "dual panoramic", "quad", "cylindrical", "defished", or "hemispheric" view)
 - [Lumus Pro](https://reolink.com/product/lumus-pro/)
 - RLC-410*
 - [RLC-410W](https://reolink.com/product/rlc-410w/)

source/_integrations/saj.markdown

@@ -19,7 +19,8 @@ ha_quality_scale: legacy
 
 The `saj` {% term integration %} will poll a [SAJ](https://www.saj-electric.com/) solar inverter and present the values as sensors in Home Assistant.
 
-This sensor uses the web interface and to use it, you have to be able to connect to the solar inverter from your favorite web browser.
+This sensor uses the web interface and to use it, you have to be able to connect to the solar inverter from your favorite web browser. 
+Not all inverters appear to support the local interface.
 
 There is a difference between inverters that are connected via an ethernet module and those connected via a Wi-Fi module.
 The Wi-Fi module requires a username and password for authentication where the ethernet module does not.

source/_integrations/sensor.mqtt.markdown

@@ -139,7 +139,7 @@ entity_picture:
   required: false
   type: string
 expire_after:
-  description: If set, it defines the number of seconds after the sensor's state expires, if it's not updated. After expiry, the sensor's state becomes `unavailable`. Default the sensors state never expires.
+  description: If set, it defines the number of seconds after the sensor's state expires if it's not updated. After expiry, the sensor's state becomes `unavailable`. Default the sensors state never expires. By default, the sensor's state never expires. Note that when a sensor's value was sent retained to the MQTT broker, the last value sent will be replayed by the MQTT broker when Home Assistant restarts or is reloaded. As this could cause the sensor to become available with an expired state, it is not recommended to retain the sensor's state payload at the MQTT broker. Home Assistant will store and restore the sensor's state for you and calculate the remaining time to retain the sensor's state before it becomes unavailable.
   required: false
   type: integer
   default: 0

source/_integrations/shelly_zwave.markdown

@@ -13,6 +13,8 @@ ha_platforms:
   - binary_sensor
   - sensor
   - switch
+works_with:
+  - zwave
 ha_iot_standard: zwave
 ha_brand: true
 ---
@@ -25,6 +27,8 @@ ha_brand: true
 
 ## Supported devices
 
-- [Shelly Wave 1PM Mini](https://www.shelly.com/products/shelly-qubino-wave-1pm-mini)
 - [Shelly Wave PM Mini](https://www.shelly.com/products/shelly-qubino-wave-pm-mini)
 - [Shelly Wave i4](https://www.shelly.com/products/shelly-qubino-wave-i4)
+- [Shelly Wave 1PM Mini](https://www.shelly.com/products/shelly-qubino-wave-1pm-mini)
+- [Shelly Wave 2PM](https://www.shelly.com/products/shelly-qubino-wave-2pm)
+- [Shelly Wave Pro 1PM](https://www.shelly.com/products/shelly-wave-pro-1-pm)

source/_integrations/zwave_js.markdown

@@ -1007,32 +1007,48 @@ You can switch between the official Z-Wave JS add-on and the Z-Wave JS UI add-on
 
 ### How to switch from Z-Wave JS to the Z-Wave JS UI add-on?
 
-You can switch from the official **Z-Wave JS** add-on to the **Z-Wave JS UI** add-on. However, you cannot run them both at the same time. Only one of the add-ons can be active at the same time.
+You can switch from the official **Z-Wave JS** add-on to the community **Z-Wave JS UI** add-on. However, you cannot run them both at the same time. Only one of the add-ons can be active at the same time.
 
-Switching does not require renaming your devices.
+Both add-ons communicate with Home Assistant via the same **Z-Wave** {% term integration %}.
 
 1. Note your network security keys from the official add-on.
+   - In your browser, open {% my supervisor_addon addon="core_zwave_js" title="**Settings** > **Add-ons** > **Z-Wave JS**" %}.  
+   - From the three dots {% icon "mdi:dots-vertical" %} menu, select **Edit in YAML**.
+   - You should see about 12 lines of YAML, including items like `device: xxx` and `s2_access_control_key: xxx`.  Select all and copy them somewhere safe.  You will need them later.
 
-2. Install and start the **Z-Wave JS UI** add-on.
+2. Install and start the community **Z-Wave JS UI** add-on.
+   - In your browser, open {% my supervisor_store title="**Settings** > **Add-ons** > **Add-on Store**" %}.
+   - Select **Install**, then **Start**.
    - It may take a while for the add-on to start up.
 
-3. Open the **Documentation** tab and copy the URL listed in the section **Setting up the Home Assistant Z-Wave JS integration**. You will need it later.
-4. Start reconfiguring the adapter.
-   - In your browser, open Home Assistant in a new tab.
-   - Select the **Z-Wave** integration and select the three-dot {% icon "mdi:dots-vertical" %} menu.
+3. Note the WebSocket URL that the integration will use to communicate with Z-Wave JS.
+    - Within the same **Z-Wave JS UI** add-on from step 2, open the **Documentation** tab.
+    - Search (Ctrl-F) for a link that begins with "ws://".  For example, `ws://a0d7b954-zwavejs2mqtt:3000`.
+    - Copy that URL somewhere safe.  You will need it later.
+
+4. Start reconfiguring the integration.
+   - Open a new browser tab.
+   - Go to {% my integrations title="**Settings** > **Devices & services**" %} and select the **Z-Wave** integration.  
+   - Select the three-dot {% icon "mdi:dots-vertical" %} menu next to the **Z-Wave JS** top row.
    - From the menu, select **Reconfigure**, then **Reconfigure current adapter**.
-   - Uncheck the **Use the Z-Wave JS Supervisor add-on**.
-   - Keep that tab open.
-5. Switch to the other tab to configure the **Z-Wave JS UI** add-on with the added control panel, including setting the location of your Z-Wave device and the network security keys.
-   - Open the **Z-Wave JS UI** web UI and go to **Settings** > **UI** > **Z-Wave**.
-   - Enter the security keys and region.
+   - Uncheck **Use the Z-Wave JS Supervisor add-on**.
+   - Keep this tab open.
+
+5. Configure the new add-on using the information saved in step 1.
+   - Switch back to your initial browser tab.
+   - Within the **Z-Wave JS UI** add-on, switch back to the **Info tab** and select **Open Web UI**.
+   - Open the **Settings** {% icon "mdi:cog" %} page and expand the **Z-Wave** section.
+   - Fill out the subsections for **Serial Port**, **Security Keys**, and **RF Region**.
    - Save your changes.
 
-6. Switch back to the tab where you started the reconfiguration of the integration.
-   - Under **WebSocket URL**, enter the URL you copied before.
+6. Finish reconfiguring the integration.
+   - Switch back to the tab from step 4.
+   - Under **WebSocket URL**, enter the URL you saved in step 3.
 
-7. Uninstall the official **Z-Wave JS** add-on.
-   - You are asked if you want to delete the related data. Keep it if you think you might switch back to the **Z-Wave JS** add-on later.
+7. Uninstall the official add-on.
+   - Go to {% my supervisor_addon addon="core_zwave_js" title="**Settings** > **Add-ons** > **Z-Wave JS**" %} and select **Uninstall**.
+   - You are asked if you want to delete the related data. 
+   - Keep it if you think you might switch back to the **Z-Wave JS** add-on later.
 
 ### How to migrate from one adapter to a new adapter using Z-Wave JS UI?
 

source/_posts/2025-07-28-shelly-joins-works-with-home-assistant.markdown

@@ -0,0 +1,84 @@
+---
+layout: post
+title: "Shelly joins Works with Home Assistant"
+description: "With a great selection of switches and relays built for Z-Wave."
+date: 2025-07-29 00:00:01
+date_formatted: "July 29, 2025"
+author: Miranda Bishop
+comments: true
+categories: Works-with-Home-Assistant
+og_image: /images/blog/2025-07-shelly/art.jpg
+---
+
+<img src='/images/blog/2025-07-shelly/art.jpg' style='border: 0;box-shadow: none;' alt="Shelly joins Works with Home Assistant">
+
+We’re excited to welcome [Shelly](https://www.shelly.com/) to the [Works with Home Assistant](https://works-with.home-assistant.io/) program! Shelly is very well-established in both our ecosystem and the smart home world, so it’s great to formally certify a selection of their Z-Wave devices.
+
+Their retrofit smart switches and relays are amazing for turning all sorts of _dumb_ devices, like light fixtures or ceiling fans, into devices you can easily control in _smart_ new ways. Also, being Works with certified means they have been thoroughly tested, ensuring they give the best possible experience with Home Assistant.
+
+The variety of complex settings and functionality, like energy monitoring, makes them popular with our community doing advanced smart retrofits, like connecting an old garage door or motorized shutters. These are perfect for keeping non-smart devices out of the landfill and working for years to come.
+<!--more-->
+
+## From A to Z-Wave
+
+Shelly, originally launched in Bulgaria in 2017, has been a mainstay in our community for some years. They became known initially for their WiFi smart switches and relays that could be easily used locally, but now offer a wide range of smart devices and ways to connect them. For this first round of Works with Home Assistant certified products, the focus is firmly on the [Z-Wave](/integrations/zwave_js/) lines.
+
+ If you’re not familiar with Z-Wave, it’s a well-established low-powered wireless technology designed with the smart home in mind. It uses an entirely different bit of radio spectrum than WiFi, meaning it has less chance of experiencing interference. This spectrum makes it better at getting through thick walls and communicating over longer distances — with the recent [Long Range](https://z-wavealliance.org/what-is-z-wave-long-range-how-does-it-differ-from-z-wave/) iteration of the standard, they can [communicate even further](/blog/2024/05/08/zwave-is-not-dead/#range-testing-our-z-wave-stick-prototype).
+
+Given our focus on local control, items that work on Z-Wave are ideal if you want to avoid the cloud. Home Assistant will act as your Z-Wave controller using the [Z-Wave JS add-on](https://github.com/hassio-addons/addon-zwave-js-ui) (another awesome Open Home Foundation project). So, all you need is a Z-Wave adapter to use alongside these devices. _If you haven’t purchased one yet, you might want to wait before hitting that buy button_ 😉.
+
+Shelly shares our focus on interoperability, with items using a variety of protocols, while being available worldwide. These items are also super helpful for the energy-conscious. They have low power consumption, power metering, and can easily blend in with your current home decor, as they sit in the wall behind your existing switches.
+
+<p class='img'><img src='/images/blog/2025-07-shelly/pm-mini.webp' style='border: 0;box-shadow: none;' alt="Shelly Wave PM Mini in hand showing small size">Mini? This thing is microscopic!</p>
+
+## Getting Involved
+
+We’ve been lucky enough to meet the Shelly team on several occasions, and they were kind enough to showcase [how the Las Vegas Mob Museum uses Shelly and Home Assistant](https://www.youtube.com/live/o4Vctz1_KYE?t=6897s) during our annual ‘State of the Open Home’ event. In May, they went one step further and hosted one of our [Community Days](/blog/2025/06/24/community-day-2025-wrap-up/) in South Florida. It’s really exciting to see that partners who join the ‘Works with’ program don’t just see it as a badge to stick on a box, but a real chance to engage with, and contribute to, this amazing community.
+
+<div class="alert">
+    <p>"Many of our users already rely on Home Assistant to power their smart homes, and we’ve seen firsthand how important local control, privacy, and flexibility are to them. By joining the <i>Works with Home Assistant</i> program, we’re reinforcing our commitment to open, reliable smart home solutions. With the upcoming launch of our <strong>Shelly Wave Long Range</strong> devices—offering wireless coverage of up to <strong>1 kilometer</strong> — we’re pushing the boundaries of what smart home technology can do. Combined with Home Assistant’s powerful platform, this will be a <strong>market-leading solution</strong>, capable of covering <strong>use cases no other ecosystem today can reach</strong>. Together, we’re building the future of smart homes: open, powerful, and ready for real-world demands."</p>
+<em style="text-align: right; display: block;">- Leon Kralj, CTO at Shelly</em>
+</div>
+
+
+## Devices
+
+In case you didn’t know, Works with Home Assistant differs from other certification programs as products are rigorously tested in-house to ensure they work seamlessly out of the box. Any company joining also commits to providing long-term support and firmware updates while being a positive force in the Home Assistant community. Works with Home Assistant is operated by the [Open Home Foundation](https://www.openhomefoundation.org/), and the support of [Home Assistant Cloud](/cloud/) subscribers funds this work.
+
+**What devices have been certified?**
+
+- [Shelly Wave PM Mini](https://www.shelly.com/products/shelly-qubino-wave-pm-mini)
+
+- [Shelly Wave i4](https://www.shelly.com/products/shelly-qubino-wave-i4)
+
+- [Shelly Wave 1PM Mini](https://www.shelly.com/products/shelly-qubino-wave-1pm-mini)
+
+- [Shelly Wave 2PM](https://www.shelly.com/products/shelly-qubino-wave-2pm)
+
+- [Shelly Wave Pro 1PM](https://www.shelly.com/products/shelly-wave-pro-1-pm)
+
+Whilst the Shelly Wave Pro 1PM sits in an electrical box, the remaining devices sit behind a standard plug, switch or device. This means they are a super cost-effective way to retrofit devices, which in turn reduces e-waste. The Minis are very small (duh), and so should fit in most tight places around the home, even with low-profile installations. The Shelly Wave 1PM Mini is the world’s smallest Z-Wave smart switch. In some areas of the world, you may need professional installation by a qualified electrician, so be sure to check your region's regulations. If you’re a confident DIYer, Shelly has a lot of [helpful guides](https://kb.shelly.cloud/knowledge-base/installation-guides) on their site to walk you through installing it yourself.
+
+## The first of many waves
+
+These devices are the first from Shelly to join the program, but certainly won’t be the last, as we look forward to many exciting developments with Z-Wave Long Range. Keep your eyes peeled for our upcoming hardware announcement that will work perfectly with our Z-Wave partners.
+
+Thanks again for your support (by subscribing to [Home Assistant Cloud](/cloud/) and [buying official hardware](https://www.nabucasa.com/#:~:text=the%20first%20boot.-,Official%20Home%20Assistant%20hardware,-Get%20the%20best)), which allows the Open Home Foundation to build these partnerships and certify new devices to join Works with Home Assistant.
+
+### FAQs
+
+**Q: If I have a device that is not listed under ‘Works with Home Assistant does this mean it’s not supported?**
+
+A: No! It just means that it hasn’t gone through a testing schedule with our team yet or doesn’t fit the requirements of the program. It might function well but be added to the testing schedule later down the road, or it might work under a different connectivity type that we don’t currently test under the program. It may also have a feature missing in Home Assistant that we’re working to add.
+
+**Q: Ok, so what’s the point of the Works with program?**
+
+A: It highlights the devices we know work well with Home Assistant and the brands that make a long-term commitment to keeping support for these devices going. The certification agreement specifies that the devices must work well within Home Assistant, operate locally without the need for cloud and will continue to do so long-term.
+
+**Q: How were these devices tested?**
+
+A: All devices in this list were tested using a standard HA Green Hub, a Z-Wave adapter and with our [Z Wave integration](/integrations/zwave_js/). If you have another hub / adapter / integration that’s not a problem but we test against these as they are the most effective way for our team to certify within our ecosystem.
+
+**Q: Will you be adding more Shelly devices to the program?**
+
+A: Absolutely. Shelly has a huge number of product lines and will be expanding their Z-Wave Long Range list. We’re sure they’ll keep our testers busy with a steady stream of devices to add.