2024.12: Scene you in 2025! 🎄

Blog
190

I tried both.

191

I suggest you create a support thread for this issue. It will get lost here.

192

I did that a while ago but didn’t get any response.

193

i tried to upgrade again but zha fails. gonna go back 2024.11

2024-12-08 14:41:34.894 DEBUG (MainThread) [homeassistant.components.zha] Failed to set up ZHA
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/zha/init.py”, line 151, in async_setup_entry
await zha_gateway.async_initialize()
File “/usr/local/lib/python3.13/site-packages/zha/application/gateway.py”, line 275, in async_initialize
await self._async_initialize()
File “/usr/local/lib/python3.13/site-packages/zha/application/gateway.py”, line 258, in _async_initialize
await self.application_controller.startup(auto_form=True)
File “/usr/local/lib/python3.13/site-packages/zigpy/application.py”, line 220, in startup
await self.connect()
File “/usr/local/lib/python3.13/site-packages/bellows/zigbee/application.py”, line 155, in connect
await self._ezsp.connect(use_thread=self.config[CONF_USE_THREAD])
File “/usr/local/lib/python3.13/site-packages/bellows/ezsp/init.py”, line 138, in connect
await self.startup_reset()
File “/usr/local/lib/python3.13/site-packages/bellows/ezsp/init.py”, line 130, in startup_reset
await self.get_xncp_features()
File “/usr/local/lib/python3.13/site-packages/bellows/ezsp/init.py”, line 184, in get_xncp_features
self._xncp_features = await self.xncp_get_supported_firmware_features()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.13/site-packages/bellows/ezsp/init.py”, line 679, in xncp_get_supported_firmware_features
rsp = await self.send_xncp_frame(xncp.GetSupportedFeaturesReq())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.13/site-packages/bellows/ezsp/init.py”, line 663, in send_xncp_frame
rsp_frame = xncp.XncpCommand.from_bytes(data)
File “/usr/local/lib/python3.13/site-packages/bellows/ezsp/xncp.py”, line 70, in from_bytes
payload, rest = COMMANDS[command_id].deserialize(data)
~~~~~~~~^^^^^^^^^^^^

194

Bump the topic then, flooding the blog will not get you support (as you’ve seen so far)

195

I ment on Github

196

Ok, but if you want support, create a topic on the forums and people will help you solve your issue.

Posting exceptions here typically doesn’t generate developer response. That’s what GitHub is for. So right now, you already have the proper thing in place to get developer eyes on your problem.

2 Likes
197

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

198

And we haven’t seen your logs…

1 Like
199

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

200

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:

202

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.

203

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.

204

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.

206

did you get this to work in the end?

207

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
208

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

209

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

210

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.

211

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