Enhance Starling bank integration with new options via updated starlingbankapi package

Gemfile.lock

@@ -27,8 +27,8 @@ GEM
       eventmachine (>= 0.12.9)
       http_parser.rb (~> 0)
     eventmachine (1.2.7)
-    ffi (1.17.2-arm64-darwin)
-    ffi (1.17.2-x86_64-linux-gnu)
+    ffi (1.17.3-arm64-darwin)
+    ffi (1.17.3-x86_64-linux-gnu)
     forwardable-extended (2.6.0)
     google-protobuf (4.33.2-arm64-darwin)
       bigdecimal
@@ -118,7 +118,7 @@ GEM
       logger
     regexp_parser (2.11.3)
     rexml (3.4.4)
-    rouge (4.6.1)
+    rouge (4.7.0)
     rubocop (1.82.1)
       json (~> 2.3)
       language_server-protocol (~> 3.17.0.2)

README.md

@@ -7,6 +7,16 @@
 
 This is the source for the [Home-Assistant.io website](https://home-assistant.io).
 
+## Access
+
+You can access the site at the following URLs, depending on the target branch:
+
+- **Production** (`current` branch): https://www.home-assistant.io
+- **Beta** (`rc` branch): https://rc.home-assistant.io
+- **Development** (`next` branch): https://next.home-assistant.io
+
+Additionally, Netlify provides a preview deployment for every pull request, linked in the first PR comment.
+
 ## Setup
 
 Setting up to contribute to documentation and the process for submitting pull requests is explained in the [developer documentation](https://developers.home-assistant.io/docs/documenting/).

source/_docs/scripts.markdown

@@ -982,7 +982,7 @@ assistant. The conversation response can be templated.
 # Example of a templated conversation response resulting in "Testing 123"
 - variables:
     my_var: "123"
-- set_conversation_response: "{{ 'Testing ' + my_var }}"
+- set_conversation_response: "{{ 'Testing ' ~ my_var }}"
 ```
 
 {% endraw %}

source/_docs/scripts/conditions.markdown

@@ -554,8 +554,11 @@ conditions:
 Valid values for `weekday` are `mon`, `tue`, `wed`, `thu`, `fri`, `sat`, `sun`.
 Note that if only `before` key is used, the condition will be `true` *from midnight* until the specified time.
 If only `after` key is used, the condition will be `true` from the specified time *until midnight*.
+
 Time condition windows can span across the midnight threshold if **both** `after` and `before` keys are used. In the example above, the condition window is from 3pm to 2am.
 
+The after times are inclusive while before are exclusive. In the example above, if the time was at 3pm (15:00:00) then it meets the after time condition. If the time was at 2am (2:00:00), it would fail the condition because it will only be valid up to 1:59:59.
+
 {% tip %}
 A better weekday condition could be by using the [Workday Binary Sensor](/integrations/workday/).
 {% endtip %}

source/_integrations/hue_ble.markdown

@@ -33,9 +33,10 @@ Before trying to connect your light(s) to Home Assistant, you must put the light
 
 This {% term integration %} is tested to work with the following models:
 
-| Model number | Product name                                     |
-|--------------|--------------------------------------------------|
-| LCA006       | Hue White and Color 1100                         |
+| Model number | Product name                                           |
+|--------------|--------------------------------------------------------|
+| LCA006       | Hue White and Color 1100                               |
+| Unknown      | Hue White and Color Ambiance Go portable accent light  |
 
 The **Philips Hue BLE** integration has been designed to work with other models as well. If you have a different model and it is working, please let us know.
 

source/_integrations/seventeentrack.markdown

@@ -53,26 +53,52 @@ Each package entry (for example, within a status sensor) contains the following
 
 ### Dashboard summary card
 
-Use the following templated Markdown card to list all packages in transit along with their status:
+To display package information on your dashboard, first create a trigger-based template sensor that calls the `seventeentrack.get_packages` action:
+
+```yaml
+template:
+  - trigger:
+      - trigger: time_pattern
+        hours: /1
+      - trigger: homeassistant
+        event: start
+    action:
+      - action: seventeentrack.get_packages
+        data:
+          config_entry_id: YOUR_CONFIG_ENTRY_ID
+          package_state:
+            - in_transit
+        response_variable: result
+    sensor:
+      - name: "Packages in transit"
+        unique_id: packages_in_transit
+        state: "{{ result.packages | count }}"
+        attributes:
+          packages: "{{ result.packages }}"
+```
+
+Then use a templated Markdown card to list all packages in transit along with their status:
 
 {% raw %}
 
 ```yaml
 type: markdown
 title: Packages in transit
 content: >
-  {% for package in
-  states.sensor['17track_in_transit'].attributes.packages %}
+  {% for package in state_attr('sensor.packages_in_transit', 'packages') %}
 
-  >- **{{ package.friendly_name }} ({{ package.tracking_number }}):** {{
+  - **{{ package.friendly_name }} ({{ package.tracking_number }}):** {{
   package.info_text }}
 
   {% endfor %}
-
 ```
 
 {% endraw %}
 
+{% tip %}
+To find your `config_entry_id`, go to {% my integrations title="**Settings** > **Devices & services**" %}, select the 17Track integration, click the three-dot menu, and select **Copy entry ID**.
+{% endtip %}
+
 ## Actions
 
 ### Action `seventeentrack.get_packages`

source/_integrations/starlingbank.markdown

@@ -47,10 +47,14 @@ To add Starling account balance sensors to your installation, add the following
 {% include integrations/restart_ha_after_config_inclusion.md %}
 ```yaml
 # Example configuration.yaml entry
+
 sensor:
   - platform: starlingbank
     accounts:
-      - access_token: YOUR_PERSONAL_ACCESS_TOKEN
+    - access_token: YOUR_PERSONAL_ACCESS_TOKEN
+      balance_types: "[effective_balance or cleared_balance]"
+      name: "[the name of the account you want to create the sensor to monitor]"
+      space_name: "[optional - the Starling Space to monitor]"
 ```
 
 {% configuration %}
@@ -63,6 +67,11 @@ name:
   required: false
   type: string
   default: Starling
+space_name:
+  description: The name of the Space you'd like to monitor - if you leave it blank, the sensor will show the account balance, and if given, only the balance of the given Space
+  required: false
+  type: string
+  default: none
 sandbox:
   description: For test purposes. Set to true if you are using an access token for a sandbox Starling account.
   required: false

source/_integrations/transport_nsw.markdown

@@ -16,7 +16,7 @@ The **Transport NSW** {% term integration %} will give you the time until the ne
 
 ## Setup
 
-Prerequisite is a free API key from [Transport NSW](https://opendata.transport.nsw.gov.au/). You will need to register an account and then create a new application. You will need to add the 'Trip Planner APIs' to your application. 
+Prerequisite is a free API key from [Transport NSW](https://opendata.transport.nsw.gov.au/). You will need to register an account and then create a new application. You will need to add the 'Trip Planner APIs' to your application. Transport NSW has [instructions for doing so](https://opendata.transport.nsw.gov.au/developers/userguide).
 
 In order to find your stop id, use the [Transport NSW stop finder](https://transportnsw.info/stop#/) and search for your stop. The URL will contain the stop id as a number.
 

source/_integrations/vera.markdown

@@ -50,6 +50,10 @@ and will be automatically added when HA connects to your Vera controller.
 
 {% include integrations/config_flow.md %}
 
+{% important %}
+Ensure the protocol and port are added to the **Controller URL**. For example `http://192.168.1.1:3480`.
+{% endimportant %}
+
 {% tip %}
 It is recommended to assign a static IP address to your Vera Controller. This ensures that it won't change IP addresses, so you won't have to change the `vera_controller_url` if it reboots and comes up with a different IP address. See your router's manual for details on how to set this up. If you need the MAC address of your Vera, check the label on the bottom.
 {% endtip %}