2024.12: Scene you in 2025! šŸŽ„

Hi,
all my

command_line:
- sensor:
    name: "Teploměry 2"
    command: "python3 /config/inels/inels_json.py GETVALUE --json_file /config/inels/inels_temperatures2.json"
    unique_id: teplomery_2
    scan_interval: 10
    json_attributes:
      - Kotel-Topeni-korekce
      - Kotel-Topeni-nastaveno

stop updating values.

In changelog i didnā€™t find any info about this breaking change.

Must rollback to 2024.11.3.

Kuba

And we havenā€™t seen your logsā€¦

1 Like

Nooooo, Iā€™m so sad that Spotify removed access to the audio features :sob:

I have Frigate installed but I havenā€™t configured it yet, so its not started, nor starting on boot. I notice my problems get worse after reloading yaml, I just reached 82% a few minutes ago while reloading templates and automation yaml filesā€¦ :confused:

I like to send you some debug, but in log wasnā€™t any message. I looks like command_line sensors stop running scripts.
In /developer-tools/state was values before upgrade.

For thouse with Lidl Silvercrest Coordinator issue after update to 2024.12 Upgrade the EZSP Version to 6.7.8.0 !! This will fix the issue. Follow the upgrade procedure. ONLY UPDATE !!!.
In the original script firmware_upgrade.sh i changed something, related to ssh to work.
The modified script is:

#!/bin/bash
GATEWAY_HOST="$1"
SSH_PORT="$2"
FIRMWARE_FILE="$4"
EZSP_VERSION="$3"
CONFIGURATION_FRAME="\x00\x42\x21\xA8\x53\xDD\x4F\x7E"

if [ $EZSP_VERSION = "V8" ]; then
  CONFIGURATION_FRAME="\x00\x42\x21\xA8\x5C\x2C\xA0\x7E"
fi

cat sx | ssh -p${SSH_PORT} root@${GATEWAY_HOST} -oHostKeyAlgorithms=+ssh-rsa -oPubkeyAcceptedAlgorithms=+ssh-rsa "cat > /tmp/sx"
cat ${FIRMWARE_FILE} | ssh -p${SSH_PORT} root@${GATEWAY_HOST} -oHostKeyAlgorithms=+ssh-rsa -oPubkeyAcceptedAlgorithms=+ssh-rsa "cat > /tmp/firmware.gbl"

ssh -p${SSH_PORT} root@${GATEWAY_HOST} -oHostKeyAlgorithms=+ssh-rsa -oPubkeyAcceptedAlgorithms=+ssh-rsa "
chmod +x /tmp/sx
killall -q serialgateway
stty -F /dev/ttyS1 115200 cs8 -cstopb -parenb -ixon crtscts raw
echo -en '\x1A\xC0\x38\xBC\x7E' > /dev/ttyS1
echo -en '$CONFIGURATION_FRAME' > /dev/ttyS1
echo -en '\x81\x60\x59\x7E' > /dev/ttyS1
echo -en '\x7D\x31\x43\x21\x27\x55\x6E\x90\x7E' > /dev/ttyS1
stty -F /dev/ttyS1 115200 cs8 -cstopb -parenb -ixon -crtscts raw
echo -e '1' > /dev/ttyS1
/tmp/sx /tmp/firmware.gbl < /dev/ttyS1 > /dev/ttyS1
reboot
"

echo "Successfully flashed new EZSP firmware! The device will now reboot."

It will ask for root password of Lidl coordinator serveral times.

Heh, I know itā€™s trivial, Iā€™m a seasoned sysadmin with sufficient Docker and k8s experience. Iā€™d like to tinker and somebody has to test and run hass core, isnā€™t it? Only when the hassle becomes too much Iā€™ll switch to the hass Docker container.

Right now the only two inconveniences were Python and Rust, both of which can be easily compiled and installed in /usr/local .

Iā€™ve tried running the zwave-js-ui add-on as a systemd service, but that became too much of a burden (and a storage hog, like every other JavaScript/TypeScript project :wink: ) and thatā€™s why Iā€™m running that as a container.

did you get this to work in the end?

Here, same kind of issue on Armbian Ubuntu stable (jammy) with HA core
ffmpeg version 4.4.2
Unable to install package av==13.1.0: Ɨ Failed to download and build av==13.1.0

1 Like

Any known issues with the Tado integration? Since upgrading, my scripts nor manual moving of thermostat etc are actioning anything in Tado.

There is a link to known issues on every integration page. Issues Ā· home-assistant/core Ā· GitHub

Hi.

Previously I was at 2024.10.3 version and upgraded to 2024.12.1 running on kubernetes.
Upgrade went fine apart some sensors that are refresh by commands in command_line.
I have one script that is executed inside docker that gets data from http://overpass-api.de/api/interpreter using curl command and when it is executed inside docker it does not work, outside docker it is ok.

I assume problem is curl command that comes with image?
I noticed this:

host:/config# nslookup overpass-api.de
Server: 192.168.0.1
Address: 192.168.0.1#53

Non-authoritative answer:
Name: overpass-api.de
Address: 162.55.144.139
Name: overpass-api.de
Address: 65.109.112.52
Name: overpass-api.de
Address: 2a01:4f8:261:3c4f::2
Name: overpass-api.de
Address: 2a01:4f9:3051:3e48::2

host:/config# curl -4 -vvv http://overpass-api.de/api/interpreter
20:51:46.769637 [0-x] == Info: [READ] client_reset, clear readers
20:51:57.937638 [0-0] == Info: Could not resolve host: overpass-api.de
20:51:57.938359 [0-x] == Info: shutting down connection #0
curl: (6) Could not resolve host: overpass-api.de

Outside docker above curl works ok.
Curl version inside docker is:
curl 8.11.0 (x86_64-alpine-linux-musl) libcurl/8.11.0 OpenSSL/3.3.2 zlib/1.3.1 brotli/1.1.0 zstd/1.5.6 c-ares/1.33.1 libidn2/2.3.7 libpsl/0.21.5 nghttp2/1.62.1

Regards.

Itā€™s a known issue. Hopefully should be patched in the core 2024.12.2 release on Friday.

Thereā€™s a manual workound in the meantime which I can confirm works

Anyone else using self-signed certs? I am now getting this error, connecting to ZoneMinder via SSL:

2024-12-08 18:45:19.929 ERROR (MainThread) [homeassistant.components.cert_expiry.coordinator] Certificate validation error: {IP redacted} [Missing Authority Key Identifier]
2024-12-08 18:45:19.965 ERROR (MainThread) [homeassistant.components.cert_expiry.coordinator] Certificate validation error: {IP redacted} [self-signed certificate in certificate chain]

I poked around but donā€™t see anything in Python 3.13 indicating AKID is now a requirement in self-signed certs. Curious if anyone else has self-signed certs working on the latest version, before I fire up my CA machine and generate new certificates.

Yeah, It must have just been a once off. Even my test automation using the old syntax still works.

Well, believe it or not.
Yesterday i was creating a couple of sensors.
Then, off course, i restarted HA.
It took HA more then 5 minutes to restart.
Suddenly, all camerastreams worked perfect !
The reason ? I think i will never know but thatā€™s ok. Everything is working now how it should be :wink:

2024.12.1 seems to have broken the Lennox iComfort thermostat integration. HA is unable to connect to the iComfort server.
Commented on issue#52 on the integrationā€™s Github page.
MyiComfort will not load Ā· Issue #52 Ā· thevoltagesource/LennoxiComfort

Posting on that GitHub issue is the way to deal with it.

2024.12.2 has been released and it fixes the Tado integration issue. :slight_smile:

1 Like

Hi.

Can someone that is on 2024.12.1 version try command inside docker:

curl -4 -vvv http://overpass-api.de/api/interpreter

Want to see is this working fine or it is something else.

Regards