Merge branch 'current' into rc

Gemfile.lock

@@ -29,10 +29,10 @@ GEM
     ffi (1.17.0-arm64-darwin)
     ffi (1.17.0-x86_64-linux-gnu)
     forwardable-extended (2.6.0)
-    google-protobuf (4.28.3-arm64-darwin)
+    google-protobuf (4.29.0-arm64-darwin)
       bigdecimal
       rake (>= 13)
-    google-protobuf (4.28.3-x86_64-linux)
+    google-protobuf (4.29.0-x86_64-linux)
       bigdecimal
       rake (>= 13)
     http_parser.rb (0.8.0)
@@ -123,7 +123,7 @@ GEM
       rubocop-ast (>= 1.36.1, < 2.0)
       ruby-progressbar (~> 1.7)
       unicode-display_width (>= 2.4.0, < 4.0)
-    rubocop-ast (1.36.1)
+    rubocop-ast (1.36.2)
       parser (>= 3.3.1.0)
     ruby-lsp (0.22.1)
       language_server-protocol (~> 3.17.0)
@@ -151,7 +151,7 @@ GEM
       rack-protection (= 4.1.1)
       rack-session (>= 2.0.0, < 3)
       tilt (~> 2.0)
-    sorbet-runtime (0.5.11668)
+    sorbet-runtime (0.5.11670)
     stringex (2.8.6)
     terminal-table (3.0.2)
       unicode-display_width (>= 1.1.1, < 3)

plugins/icon.rb

@@ -5,7 +5,8 @@ module Jekyll
       def initialize(tag_name, args, tokens)
         super
         if args.strip =~ SYNTAX
-          @icon = Regexp.last_match(1).downcase
+          @icon = Regexp.last_match[:icon].downcase
+          @title = Regexp.last_match[:title]
         else
           raise SyntaxError, <<~MSG
             Syntax error in tag 'icon' while parsing the following options:
@@ -13,18 +14,29 @@ module Jekyll
             #{args}
 
             Valid syntax:
-              {% icon "<icon-set>:<icon-name>" %}
+              {% icon "<icon-set>:<icon-name>" [title="<title>"] %}
           MSG
         end
       end
       
+      def default_title(icon)
+        # split away "mdi:" part
+        icon_name = icon.split(':').last
+
+        # remove dashes and capitalize e.g. "water-polo" to "Water polo"
+        parts = icon_name.split('-')
+        parts[0] = parts[0].capitalize
+        parts.join(' ')
+      end
+
       def render(_context)
-        "<iconify-icon inline icon='#{@icon}'></iconify-icon>"
+        title = @title || default_title(@icon)
+        "<iconify-icon inline icon='#{@icon}' title='#{title}'></iconify-icon>"
       end
 
       private
 
-      SYNTAX = %r!^"([a-z0-9]+(?:-[a-z0-9]+)*:[a-z0-9]+(?:-[a-z0-9]+)*)"$!.freeze
+      SYNTAX = %r!^"(?<icon>[a-z0-9]+(?:-[a-z0-9]+)*:[a-z0-9]+(?:-[a-z0-9]+)*)"(?:\s+title="(?<title>[^"]+)")?$!.freeze
     end
   end
 end

source/_integrations/google_assistant.markdown

@@ -74,7 +74,7 @@ To use Google Assistant, your Home Assistant configuration has to be [externally
         2. Select **Create and Continue**.
         3. Under **Select a role**, select **Service Accounts** > **Service Account Token Creator**.
         4. Select **Continue** and then **Done**.
-    6. Under **Service Accounts**, there should now be an account called [name from 4.1]@[projectname].iam.gserviceaccount.com.
+    6. Under **Service Accounts**, there should now be an account called [name from 5.1]@[projectname].iam.gserviceaccount.com.
     7. Select the pencil button of that service account.
     8. Go to **Keys** and **Add key**.
     9. Create a private key in JSON format.

source/_integrations/input_boolean.markdown

@@ -46,7 +46,7 @@ Input booleans can also be configured via {% term "`configuration.yaml`" %} file
         description: Initial value when Home Assistant starts.
         required: false
         type: boolean
-        default: false
+        default: a previous value is restored if available
       icon:
         description: Icon to display in front of the input element in the frontend.
         required: false
@@ -78,7 +78,7 @@ Home Assistant itself.
 
 If you set a valid value for `initial` this integration will start with the state
 set to that value. Otherwise, it will restore the state it had prior to
-Home Assistant stopping.
+Home Assistant stopping; if there is no state to restore - an `off` value is set. 
 
 ## Automation examples
 

source/_integrations/schlage.markdown

@@ -23,7 +23,13 @@ ha_domain: schlage
 
 The Schlage integration provides connectivity with Schlage WiFi smart locks through Schlage's cloud API.
 
-{% include integrations/config_flow.md %}
+## Known working devices
+
+- Schlage Encode Smart WiFi Deadbolt
+- Schlage Encode Smart WiFi Lever
+- Schlage Encode Plus Smart WiFi Deadbolt
+
+Other devices not listed above have not been tested and may not function as expected.
 
 There is currently support for the following device types within Home Assistant:
 
@@ -32,6 +38,12 @@ There is currently support for the following device types within Home Assistant:
 - Sensor
 - Switch
 
+{% include integrations/config_flow.md %}
+
+## Data updates
+
+The Schlage integration fetches updated lock state data every 30 seconds.
+
 ## Binary sensor
 
 Once you have enabled the Schlage integration, you should see the following binary sensor:
@@ -56,3 +68,9 @@ Once you have enabled the Schlage integration, you should see the following swit
 
 - **1-Touch Locking** - When enabled, locks the lock with a press of the Schlage button.
 - **Keypress Beep** - Controls whether the lock will emit beeping tones on use.
+
+## Removing the integration
+
+This integration follows standard integration removal. No extra steps are required.
+
+{% include integrations/remove_device_service.md %}

source/_posts/2024-10-02-connect-zbt1-issue-and-replacement.markdown

@@ -11,12 +11,17 @@ og_image: /images/blog/2024-10-zbt1-issue/art.jpg
 ---
 <img src='/images/blog/2024-10-zbt1-issue/art.jpg' alt="Home Assistant Connect ZBT-1 issue and replacement">
 
-We've found an issue in Home Assistant Connect ZBT-1 that has affected a small number of customers, which appears to be the result of a faulty part incorporated in the first production run of ZBT-1 devices. We want to make sure everyone can get a replacement ZBT-1 and ensure they are covered far into the future.
+{% note %}
+The replacement program is now operational, please contact the retailer where you purchased your device to request a replacement. The replacement program only covers ZBT-1 branded devices purchased prior to October 2024, and not SkyConnect-branded devices (identify which device you have [with this graphic](#do-i-have-a-zbt-1)).
+{% endnote %}
 
-Though Home Assistant SkyConnect is identical to the ZBT-1 under the hood, it is not affected. The design is not what's at fault, but instead, a defective voltage regulator that was used in this specific production run that is causing the issue. When a ZBT-1 is inserted into certain USB-A ports, the voltage regulator can fail, fully bricking the device. We used high-quality manufacturing and quality control in this and previous production runs. We are undertaking an investigation to find out how this could happen and most importantly, to avoid a repeat of anything remotely similar in the future.
+We've found an issue in Home Assistant Connect ZBT-1 that has affected a small number of customers, which appears to be the result of a faulty part incorporated in the first production run of ZBT-1 devices, causing the device to fail and become completely unresponsive. We want to make sure everyone can get a replacement ZBT-1 and ensure they are covered far into the future.
+
+Though Home Assistant SkyConnect is identical to the ZBT-1 under the hood, **it is not affected**. The design is not what's at fault, but instead, a defective voltage regulator that was used in this specific production run that is causing the issue. When a ZBT-1 is inserted into certain USB-A ports, the voltage regulator can fail, fully bricking the device. We used high-quality manufacturing and quality control in this and previous production runs. We are undertaking an investigation to find out how this could happen and most importantly, to avoid a repeat of anything remotely similar in the future.
 
 We're sorry for any inconvenience this may cause you. Below are details on our investigation, how devices are affected, and the replacement program.
 - [Background](#background)
+- [Do I have a ZBT-1?](#do-i-have-a-zbt-1)
 - [Pausing sales](#pausing-sales)
 - [Replacement Program](#replacement-program)
 - [Conclusion](#conclusion)
@@ -25,19 +30,21 @@ We're sorry for any inconvenience this may cause you. Below are details on our i
 
 ## Background
 
-Around a month ago, we were contacted about one of our latest (and [recently rebranded](/blog/2024/06/13/zbt1-annoucement/)) Home Assistant Connect ZBT-1s not being detected and showing a small mark on the housing. A couple more similar issues were reported, and we began a dialogue with the small number of people who were affected, having them send us the devices to test.
+Around a month ago, we were contacted about one of our latest (and [recently rebranded](/blog/2024/06/13/zbt1-annoucement/)) Home Assistant Connect ZBT-1s not being detected and showing a deformation on the housing. A couple more similar issues were reported, and we began a dialogue with the small number of people who were affected, having them send us the devices to test.
 
 <p class='img'><img src='/images/blog/2024-10-zbt1-issue/zbt1-issue.jpg' style='border: 0;box-shadow: none;' alt="ZBT-1 case deformation and faulty voltage regulator">Circled in red the deformation on the case and the board showing the failed chip</p>
 
-When we opened them, we found a dead voltage regulator. The mark in the outer casing is a sign that it overheated and failed. All of our devices are certified by CE and ROHS, and the plastic shell has been designed not to combust. This is a real-life demonstration of just how important this certification is and why we take that step.
+Indeed, the device no longer worked at all, not being detected by any device it was connected to. When we opened them, we found a dead voltage regulator. Though SkyConnect devices can also develop a small discoloration on the outside casing after long-term use, and this is not a sign of failure, the deeper deformation in the outer casing pictured above is a sign that the ZBT-1 has overheated and failed. All of our devices are certified by CE and ROHS, and the plastic shell has been designed not to combust. This is a real-life demonstration of just how important this certification is and why we take that step.
 
 We replaced the voltage regulator on the devices we tested, and the devices sprang back to life. We found our culprit, but why was it failing? As mentioned, the SkyConnect internal design and the manufacturing were effectively identical to the ZBT-1, and we received no reports of any such failures in the literally tens of thousands of them in the wild. In manufacturing runs there is always a little variance, and in this run, something went wrong with the voltage regulator that was sourced - again, we're looking into this.
 
+It took us a couple of weeks to replicate the problem with our own units. We went down some wrong paths, but eventually found it was triggered only by certain devices, specifically certain desktop PCs (internally, we have only found one desktop that causes this failure). We have not observed the failure occur when the device has only been connected to a Home Assistant Green, Raspberry Pi, or even a Mac. If you have plugged your ZBT-1 into a different device, specifically a desktop PC, and it is not recognized by that system, inspect it for this deformation pictured above. Obviously, we want you to be able to use the device with any hardware, and even if only a small number of devices from this production run have reported issues, it is still unacceptable to us.
+
+## Do I have a ZBT-1?
+
 <img src='/images/blog/2024-10-zbt1-issue/skyconnect-zbt1.png' style='border: 0;box-shadow: none;' alt="SkyConnect (left) and ZBT-1 (right)">
 <p style="text-align: center; font-size: 0.9rem;">SkyConnect (left) and ZBT-1 (right) branded devices, SkyConnect are unaffected by this issue.</p>
 
-It took us a couple of weeks to replicate the problem with our own units. We went down some wrong paths, but eventually found it was triggered only by certain devices, specifically certain desktop PCs (internally, we have only found one desktop that causes this failure). We have not observed the failure occur when the device has only been connected to a Home Assistant Green, Raspberry Pi, or even a Mac. If you have plugged your ZBT-1 into a different device, specifically a desktop PC, and it is not recognized by that system, inspect it for this deformation pictured above. Obviously, we want you to be able to use the device with any hardware, and even if only a small number of devices from this production run have reported issues, it is still unacceptable to us.
-
 ## Pausing sales
 
 We have asked our distributors to pause sales and return all stock. For the next month, you will see "Out of Stock" banners, and if you are attempting to get a replacement device for a failed unit, this will not be possible until production is resumed.
@@ -51,7 +58,7 @@ If you have purchased Home Assistant Connect ZBT-1, we are working on a replacem
 It is a core value of ours to do things as sustainably as possible, and that's why we've provided such a long coverage period. We want to give owners with working ZBT-1s, who do not expect to use the device in a different system for the foreseeable future, the ability to keep it operating with peace of mind.
 
 {% note %}
-All ZBT-1 branded devices produced, as of October 2024, are believed to have this fault. You can tell if your device is a ZBT-1 by checking the white label on the back for “ZBT-1”. There is no need to test if your device is affected by this fault.
+All ZBT-1 branded devices produced, as of October 2024, are believed to have this fault. You can tell if your device is a ZBT-1 by checking the white label on the back for “ZBT-1” (identify which device you have [with this graphic](#do-i-have-a-zbt-1)). There is no need to test if your device is affected by this fault.
 {% endnote %}
 
 If it's working, keep it plugged into the device it's working with, and don't worry about a replacement until you need it. If you need or want a replacement, please contact the seller where you purchased your device, and they will arrange the return process and replacement. Replacement devices are expected by early November, and we will be prioritizing people with non-functioning devices.