The longer term prospects for the Met Office integration are uncertain. Even if the Python incompatibility is fixed (and an upstream PR has been submitted, so awaiting the code owner to accept it), the current API it uses is I believe shutting down before the end of April 2024, and a new integration will need to be coded more or less from scratch. There’s more information in the GitHub discussion here.
I’ve moved to OpenWeatherMap in the mean time, and signed up to use its One Call API, which is free up to a limit which I’ve comfortably yet to exceed. Seems an adequate replacement.
Ever since the update, my Switchbot Blind tilts using the Switchbot integration has this problem where I can’t see the current status. They still work fine, but every time I control them I’ll get a message that the service call failed. And when I check the status, instead of telling me that it’s opened to a certain percentage or closed, it only says “Unknown”.
I have other devices using the Switchbot integration like the curtain and button pusher, but only the Blinds tilts are affected. I did ask around and one other person told me that they have this issue too. Is the team aware that this might be widespread yet.
time triggers only fire on the second, they don’t account for microseconds. So it is throwing the calc off. This is the most accurate I can get it scheduling the update ahead of time
- trigger:
- platform: homeassistant
event: start
- platform: time
at: sensor.next_swatch_time
sensor:
- name: Next SwatchTime
unique_id: 8a98c032-e92b-4295-8b79-4fde63865e94
device_class: timestamp
state: >
{% set rdt = utcnow() %}
{% set inc = timedelta(seconds=86.4) %}
{% set dt = rdt + timedelta(hours=1) %}
{% set d = timedelta(hours=dt.hour, minutes=dt.minute, seconds=dt.second, microseconds=dt.microsecond) %}
{% set c = d % inc %}
{% set next = (rdt - c + inc).replace(microsecond=0) + timedelta(seconds=1) %}
{% if next < rdt %}
{{ (next + inc) | as_local }}
{% else %}
{{ next | as_local }}
{% endif %}
- name: Internet Time
unique_id: f7e3e6b6-24c2-4ea3-9603-d466a1808b89
state: >
{% set time_bmt = utcnow() + timedelta(hours = 1) %}
{%
set delta = timedelta(hours = time_bmt.hour,
minutes = time_bmt.minute,
seconds = time_bmt.second,
microseconds = time_bmt.microsecond)
%}
{% set beat = (delta.total_seconds() * 10) | int // 864 %}
{{ "@{0:03d}".format(beat) }}
If you just use the next template, it’ll have slightly more accuracy every 5th beat. All the other beats in between will have the same accuracy.
- trigger:
- platform: time_pattern
seconds: /1
sensor:
- name: Internet Time
unique_id: f7e3e6b6-24c2-4ea3-9603-d466a1808b89
state: >
{% set time_bmt = utcnow() + timedelta(hours = 1) %}
{%
set delta = timedelta(hours = time_bmt.hour,
minutes = time_bmt.minute,
seconds = time_bmt.second,
microseconds = time_bmt.microsecond)
%}
{% set beat = (delta.total_seconds() * 10) | int // 864 %}
{{ "@{0:03d}".format(beat) }}
Both versions will be at update at most 1 second off from the actual beat time update frequency.
I’m unsure if caused by HA 2024.2.0/1 and/or by the accompanying updates to OTBR/Matter addons, but my thread network is terribly unstable and less than one or two hours after a system reboot at least one (if not two or three) of my 25 HomeKit devices drop off the network, simply become “unavailable” until I reboot HA. This has been going on for the past few days.
I’m considering reverting to 2024.1, but am reluctant, as I haven’t yes reinstalled an older HA version from a full backup before and am fearing other issues.
I appreciate the advice.
I solely had the first sentence originally. Then added the last three sentences to test/debug why it stopped working with just the “office to 75” but still worked with “office to 75 degrees” and posted them to show here, in this post, what I tried.
Not a big issue, I just have to add something after the “75”/{temp_degrees}
As a follow-up: I just checked (using only the first sentence as suggested) it again after today’s HA Core Update and Assist’s response is:
“Brightness Set” even though I don’t have “brightness” anywhere in my -intents:- nor my -intent_script:- code.
Warning: with words: true, don’t go with large ranges… HA’s assistant still can’t do large math (in any reasonable timeframe, or without crashing), nor negative numbers
Thanks. I found a partial backup from which I restored Matter Server addon 5.0.4 and my thread network seems to be a bit more stable, currently only 1/25 thread devices are unavailable. I’ll wait another day or two before doing a complete restore.
The last Release Party introduced me to the -Developer Tools/Assist" feature. It seems there is a built in feature that overrides my custom sentences. Here is the output of that feature when I type “office to 73”:
