Hi all
This morning I saw the log entry below. I updated to 2026.6.1 yesterday.
Logger: py.warnings
Source: components/image/init .py:15
First occurred: 7 June 2026 at 10:21:42 (1 occurrence)
Last logged: 7 June 2026 at 10:21:42
/usr/local/lib/python3.14/site-packages/rich/segment.py:547: SyntaxWarning: 'return' in a 'finally' block return
I tried to trace this but on my HA Green the path /usr/local/lib has no such python directory.
Finally I used the find command and saw that the source only resides in custom integrations, but I got stuck again in tracing the culprit:
[core-ssh /]$ find / -name "__init__.py"
/homeassistant/custom_components/sems/__init__.py
/homeassistant/custom_components/hacs/__init__.py
/homeassistant/custom_components/hacs/utils/__init__.py
/homeassistant/custom_components/hacs/repositories/__init__.py
/homeassistant/custom_components/hacs/hacs_frontend/__init__.py
/homeassistant/custom_components/hacs/validate/__init__.py
/homeassistant/custom_components/hacs/websocket/__init__.py
[core-ssh /]$
Is it worth hunting down this message?
tom_l
June 8, 2026, 12:22pm
2
There has been an issue open for this for a few months:
opened 10:32PM - 04 Mar 26 UTC
### The problem
I just upgraded my homeassistant container running on podman an… d i'm seeing this warning
```
2026-03-04 23:25:53.911 WARNING (ImportExecutor_0) [py.warnings] /usr/local/lib/python3.14/site-packages/rich/segment.py:547: SyntaxWarning: 'return' in a 'finally' block
return
```
### What version of Home Assistant Core has the issue?
core-2026.3.0
### What was the last working version of Home Assistant Core?
core-2026.2.3
### What type of installation are you running?
Home Assistant Container
### Integration causing the issue
_No response_
### Link to integration documentation on our website
_No response_
### Diagnostics information
_No response_
### Example YAML snippet
```yaml
```
### Anything in the logs that might be useful for us?
```txt
```
### Additional information
I attach the full log
```
[rXXX@XXXX ~]# podman logs --follow homeassistant-server
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
2026-03-04 23:25:50.610 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-03-04 23:25:50.610 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration edata which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-03-04 23:25:50.610 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration dreame_vacuum which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-03-04 23:25:51.404 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=622 from 2026-03-04 22:19:15.305886)
2026-03-04 23:25:53.911 WARNING (ImportExecutor_0) [py.warnings] /usr/local/lib/python3.14/site-packages/rich/segment.py:547: SyntaxWarning: 'return' in a 'finally' block
return
```
Thanks. I guess python hit the pi limit.
tom_l
June 8, 2026, 12:34pm
4
This is one of the things wrong with Home Assistant's Integration model. I don't use the Integration causing this (Sure Petcare) yet I still see the errors.
Same thing happens with add-ons / apps. Does not matter if you have an add-on installed or not - if there's something wrong with it you get the errors/warnings.