2023.4: Custom template macros, and many more new entity dialogs!

with File Editor i find /usr/src but no folder inside.
i search this /usr/src/homeassistant/homeassistant/components/renault/manifest.json
can you explain me how please ?

1 Like

What install method did you use?

Normal. No docker.

Hello, I upgraded to 2023.4.5 and OS10. This night at 4h30 in the morning, HA state was in trouble, seems not responding (no data collected till power off/on).
There are some scheduled task during the night ?
I’m trying to found the root cause but nothing in logs and again this morning, same things happened.
Strange :wink:

The database is purged at 4:12am.

1 Like

OS release 10 does seem to have serious troubles: Home Assistant OS 10: Better memory management and new board support - #75 by 11125

Personally I held back updating, also because of raised issues in the repo.

1 Like

I updated to 2023.4.5 (and HAOS 10.0) and after that I have noticed that my smart lights seem to go on randomly. But that’s only on frontend, the actual light does not go on (and I can control them via HA interface without problems). It’s just odd to see 4-5 lights that according to frontend are on without any reason…

my renault integration broke too, but so did the renault app, so I’m contacting renault to see whether its an issue on their end.

+1
The whole Home Assistant is in german, but the enitiy states are in english.

Yes…same issue here after upgrading from 2023.3.6 to 2023.4.5. I have like 10 devices that got affected. Not sure if you or anyone found a solution other than redoing it?

After updating from 2023.4.4. to 2023.4.5 I m unable to restart Home Assistant due to this warning: Platform error sensor.solaredge_local - Exception importing homeassistant.components.solaredge_local.sensor.
Do not know what to do with this, the only thing is a backup back to 2023.4.4. Anyone else the same problem and how to fix it?

Hello, after ESPhome update to 2023.4.0 unusually high CPU LOAD started on HA host and stays above 1.2 all the time(even after host restart). Before the update load was 0.2 on average.
image

In ESPhome I’m using 1 ESP32 BLE tracker device(upgraded to 2023.4.0) and 2 BLE iBeacon devices.
Home Assistant 2023.4.5 Supervisor 2023.04.0 Operating System 10.0

I can see connection errors in the log:

 Logger: aioesphomeapi.connection
Source: runner.py:179
m5stack-atom-lite @ 192.168.1.84: Connection error occurred: [Errno 104] Connection reset by peer
Logger: aioesphomeapi.reconnect_logic
Source: runner.py:179
Can't connect to ESPHome API for m5stack-atom-lite @ 192.168.1.84: Error connecting to ('192.168.1.84', 6053): [Errno 113] Connect call failed ('192.168.1.84', 6053)

Also ping to the ESPhome device is unusually high:
image

Tried to change framework type from arduino to esp-idf in ESPhome but no change :frowning:

There are four methods; core, OS, supervised, and container. Pick one.

Please open a GitHub issue and post a callgrind file from the profiler.start service as well as a py-spy

https://community.home-assistant.io/t/instructions-to-install-py-spy-on-haos/480473 but use 0.3.14

Ive updated that community guide some time ago with the 0.3.14 version, so that people can simply c&p.

also re-ordered the pid to the end of the line, allowing easier c&p there :wink:

finally, I added a command to output the files with a templated name, so they are always visible.

1 Like

@MT0321
Probably need to open an issue on this

I received a 2023.4.6 update notification, but there’s no release notes for it on the main blog entry after 2023.4.5. Someone miss part of some process?

There is, I was just reading them. 2023.4: Custom template macros, and many more new entity dialogs! - Home Assistant

After py-spy installation to HassOS OdroidC4 it seems not to work.
py-spy commands end with error:

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: ParseIntError { kind: PosOverflow }', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/proc-maps-0.2.1/src/linux_maps.rs:81:65
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: receiving on a closed channel

Looks like it’s a bug in py spy. They could probably use another trace

In the mean time start with just the callgrind