Merge branch 'next' into ap-condition

Author: AzonInc

content/components/select/_index.md

@@ -65,7 +65,7 @@ MQTT Options:
 ## Select Automation
 
 You can access the most recent state of the select in [lambdas](/automations/templates#config-lambda) using
-`id(select_id).state`.
+`id(select_id).current_option()`.
 For more information on using lambdas with select, see [lambda calls](#select-lambda_calls).
 
 {{< anchor "select-on_value" >}}
@@ -268,19 +268,28 @@ advanced stuff (see the full API Reference for more info).
   to select the first option or `call.select_next(true)` to select the next
   option with the cycle feature enabled.
 
-- `.state`  : Retrieve the currently selected option of the select.
+- `.current_option()`  : Retrieve the currently selected option of the select. Returns `const char*`.
 
 ```cpp
     // For example, create a custom log message when an option is selected:
-    auto state = id(my_select).state.c_str();
+    auto state = id(my_select).current_option();
     ESP_LOGI("main", "Option of my select: %s", state);
 ```
 
 ```yaml
-    # Check if a specific option is selected
+    # Check if a specific option is selected (using strcmp)
     - if:
         condition:
-          - lambda: 'return id(my_select).state == "my_option_value";'
+          - lambda: 'return strcmp(id(my_select).current_option(), "my_option_value") == 0;'
+```
+
+```yaml
+    # Or convert to std::string for comparison
+    - if:
+        condition:
+          - lambda: |-
+              std::string current = id(my_select).current_option();
+              return current == "my_option_value";
 ```
 
 - `.size()`  : Retrieve the number of options in the select.

content/components/select/template.md

@@ -50,7 +50,7 @@ select:
 - All other options from [Select](/components/select#config-select).
 
 > [!NOTE]
-> If you don't set a `lambda` and `optimistic` is `false` (default), updates to the select component state will need to be taken care of as part of your `set_action` using `id(my_select).publish_state(x);` (in a lambda). Do not use [`select.set` Action](/components/select#select-set_action) here, as this would generate a loop. Also, don't use `id(my_select).state = x` as this won't have the desired effect (e.g. HA won't update with the change).
+> If you don't set a `lambda` and `optimistic` is `false` (default), updates to the select component state will need to be taken care of as part of your `set_action` using `id(my_select).publish_state(x);` (in a lambda). Do not use [`select.set` Action](/components/select#select-set_action) here, as this would generate a loop.
 
 ## `select.set` Action
 

content/components/time/rx8130.md

@@ -77,6 +77,7 @@ time:
     # repeated synchronization is not necessary unless the external RTC
     # is much more accurate than the internal clock
     update_interval: never
+    timezone: Europe/Paris
   - platform: homeassistant
     # instead try to synchronize via network repeatedly ...
     on_time_sync: