The light card is broken and will be fixed in the 2023.3.1 patch.
2 Likes
Thats all in the frontend supervisor log. No newer entries after the last row…
Heres the host log:
Mar 02 19:08:46 homeassistant systemd[1]: Unmounted /run/docker/netns/31e3ff444e1b.
Mar 02 19:08:46 homeassistant systemd[1]: var-lib-docker-overlay2-3283d6ec41e82fd5c86e28bbeed59adc54a72387efb2157d79d2381fe59959a0-merged.mount: Deactivated successfully.
Mar 02 19:08:46 homeassistant systemd[1]: Unmounted /var/lib/docker/overlay2/3283d6ec41e82fd5c86e28bbeed59adc54a72387efb2157d79d2381fe59959a0/merged.
Mar 02 19:08:46 homeassistant systemd[1]: mnt-data-docker-overlay2-3283d6ec41e82fd5c86e28bbeed59adc54a72387efb2157d79d2381fe59959a0-merged.mount: Deactivated successfully.
Mar 02 19:08:46 homeassistant systemd[1]: Unmounted /mnt/data/docker/overlay2/3283d6ec41e82fd5c86e28bbeed59adc54a72387efb2157d79d2381fe59959a0/merged.
Mar 02 19:08:47 homeassistant dockerd[477]: time="2023-03-02T19:08:47.132550184Z" level=info msg="stopping event stream following graceful shutdown" error="<nil>" module=libcontainerd namespace=moby
Mar 02 19:08:47 homeassistant dockerd[477]: time="2023-03-02T19:08:47.134407407Z" level=info msg="Daemon shutdown complete"
Mar 02 19:08:47 homeassistant dockerd[477]: time="2023-03-02T19:08:47.134458240Z" level=info msg="stopping healthcheck following graceful shutdown" module=libcontainerd
Mar 02 19:08:47 homeassistant dockerd[477]: time="2023-03-02T19:08:47.134532387Z" level=info msg="stopping event stream following graceful shutdown" error="context canceled" module=libcontainerd namespace=plugins.moby
Mar 02 19:08:48 homeassistant systemd[1]: docker.service: Deactivated successfully.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped Docker Application Container Engine.
Mar 02 19:08:48 homeassistant systemd[1]: docker.service: Consumed 1min 41.451s CPU time.
Mar 02 19:08:48 homeassistant systemd[1]: hassos-apparmor.service: Deactivated successfully.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped HassOS AppArmor.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped target System Time Synchronized.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped target System Time Set.
Mar 02 19:08:48 homeassistant systemd[1]: systemd-time-wait-sync.service: Deactivated successfully.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped Wait Until Kernel Time Synchronized.
Mar 02 19:08:48 homeassistant systemd[1]: Stopping Network Time Synchronization...
Mar 02 19:08:48 homeassistant systemd[1]: systemd-timesyncd.service: Deactivated successfully.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped Network Time Synchronization.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped target Network is Online.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped target Network.
Mar 02 19:08:48 homeassistant systemd[1]: NetworkManager-wait-online.service: Deactivated successfully.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped Network Manager Wait Online.
Mar 02 19:08:48 homeassistant systemd[1]: Stopping Network Manager...
Mar 02 19:08:48 homeassistant NetworkManager[385]: <info> [1677784128.2149] caught SIGTERM, shutting down normally.
Mar 02 19:08:48 homeassistant systemd[1]: Stopping Network Name Resolution...
Mar 02 19:08:48 homeassistant wpa_supplicant[407]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 02 19:08:48 homeassistant systemd[1]: Stopping WPA supplicant...
Mar 02 19:08:48 homeassistant NetworkManager[385]: <info> [1677784128.2332] dhcp4 (eth0): canceled DHCP transaction
Mar 02 19:08:48 homeassistant NetworkManager[385]: <info> [1677784128.2333] dhcp4 (eth0): state changed bound -> terminated
Mar 02 19:08:48 homeassistant NetworkManager[385]: <info> [1677784128.2335] dhcp6 (eth0): canceled DHCP transaction
Mar 02 19:08:48 homeassistant NetworkManager[385]: <info> [1677784128.2335] dhcp6 (eth0): state changed bound -> terminated
Mar 02 19:08:48 homeassistant NetworkManager[385]: <info> [1677784128.2345] manager: NetworkManager state is now CONNECTED_SITE
Mar 02 19:08:48 homeassistant kernel: kauditd_printk_skb: 11 callbacks suppressed
Mar 02 19:08:48 homeassistant kernel: audit: type=1334 audit(1677784128.232:505): prog-id=0 op=UNLOAD
Mar 02 19:08:48 homeassistant NetworkManager[385]: <info> [1677784128.2356] device (wlan0): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'managed')
Mar 02 19:08:48 homeassistant systemd[1]: systemd-resolved.service: Deactivated successfully.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped Network Name Resolution.
Mar 02 19:08:48 homeassistant systemd[1]: systemd-resolved.service: Consumed 2.029s CPU time.
Mar 02 19:08:48 homeassistant systemd[1]: Requested transaction contradicts existing jobs: Transaction for NetworkManager-dispatcher.service/start is destructive (var.mount has 'stop' job queued, but 'start' is included in transaction).
Mar 02 19:08:48 homeassistant wpa_supplicant[407]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Mar 02 19:08:48 homeassistant wpa_supplicant[407]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Mar 02 19:08:48 homeassistant kernel: audit: type=1334 audit(1677784128.304:506): prog-id=0 op=UNLOAD
Mar 02 19:08:48 homeassistant wpa_supplicant[407]: wlan0: CTRL-EVENT-TERMINATING
Mar 02 19:08:48 homeassistant systemd[1]: wpa_supplicant.service: Deactivated successfully.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped WPA supplicant.
Mar 02 19:08:48 homeassistant systemd[1]: Requested transaction contradicts existing jobs: Transaction for NetworkManager-dispatcher.service/start is destructive (etc-modules\x2dload.d.mount has 'stop' job queued, but 'start' is included in transaction).
Mar 02 19:08:48 homeassistant NetworkManager[385]: <info> [1677784128.7970] exiting (success)
Mar 02 19:08:48 homeassistant systemd[1]: NetworkManager.service: Deactivated successfully.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped Network Manager.
Mar 02 19:08:48 homeassistant systemd[1]: NetworkManager.service: Consumed 2.611s CPU time.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped target Basic System.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped target Preparation for Network.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped target Path Units.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped target Slice Units.
Mar 02 19:08:48 homeassistant systemd[1]: Removed slice User and Session Slice.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped target Socket Units.
Mar 02 19:08:48 homeassistant systemd[1]: docker.socket: Deactivated successfully.
Mar 02 19:08:48 homeassistant systemd[1]: Closed Docker Socket for the API.
Mar 02 19:08:48 homeassistant systemd[1]: systemd-journal-gatewayd.socket: Deactivated successfully.
Mar 02 19:08:48 homeassistant systemd[1]: Closed Journal Gateway Service Socket.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped target System Initialization.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped target Local Encrypted Volumes.
Mar 02 19:08:48 homeassistant systemd[1]: systemd-ask-password-console.path: Deactivated successfully.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
Mar 02 19:08:48 homeassistant systemd[1]: systemd-ask-password-wall.path: Deactivated successfully.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped target HassOS overlay targets.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped target Local Integrity Protected Volumes.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped target Local Verity Protected Volumes.
Mar 02 19:08:48 homeassistant dbus-broker[180]: Dispatched 20275 messages @ 26(±19)μs / message.
Mar 02 19:08:48 homeassistant systemd[1]: Stopping D-Bus System Message Bus...
Mar 02 19:08:48 homeassistant systemd[1]: systemd-sysctl.service: Deactivated successfully.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped Apply Kernel Variables.
Mar 02 19:08:48 homeassistant systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped Create Volatile Files and Directories.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped target Local File Systems.
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting NetworkManager persistent system connections...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting Dropbear persistent keys...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting Hostname persistent configuration...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting Hosts persistent configuration...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting /etc/machine-id...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting Kernel persistent modprobe.d...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting Kernel persistent modules-load.d...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting Timesyncd persistent configuration...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting Udev persistent rules.d...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting HassOS boot partition...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting Docker persistent user...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting Dropbear persistent user...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting /run/docker/netns/default...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting Temporary Directory /tmp...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting NetworkManager persistent data...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting Bluetooth persistent state...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting Docker persistent data...
Mar 02 19:08:48 homeassistant systemd[1]: Unmounting Systemd persistent state...
Mar 02 19:08:48 homeassistant systemd[1]: [email protected]: Deactivated successfully.
Mar 02 19:08:48 homeassistant systemd[1]: Stopped Grow File System on /mnt/data.
Mar 02 19:08:48 homeassistant systemd[1]: Removed slice Slice /system/systemd-growfs.
Mar 02 19:08:48 homeassistant systemd[1]: Stopping Flush Journal to Persistent Storage...
Users see now in the more-info dialog the settings and all others info which was only visalbe to Admins up to now. Is this intentionally? I don’t like this… would like to be ablte to enalbe/disalbe what can be seen on the more-info dialog.
1 Like
You right, it should be hidden. It’s not intentional. I will look at this.
2 Likes
The Raspberry pi doesn’t have onboard battery. Something else is the problem.
Once again about more-info for lights.
IMHO there are 2 cases:
— client device with a large screen (like a PC);
— client device with a small screen (like a phone).
For small screens it is better to have a compact view - and it could be a view with “mostly needed controls”, and all other controls may be hidden in subviews. But here a survey must be done to define which controls are “mostly needed”. Hope this is already done - then would be nice to get a feedback from users who actively use lamps. Currently only brightness is selected as “most needed” - but many people change colors, temperature - probably even more often than a brightness.
For large screens it is better to have a more detailed view with more controls. Currently in 4K screen a view with lonely slider does not look great.
15 Likes
Was wondering the same thing - would like to align my HA thread network with my Homekit network
I had a lot of problems after the installation. I couldn’t even go back with a backup. Looks like I missed a few python libs that were used by various integrations (Alexa, Goove, etc).
Looking in the logs I found that it tried to install them but it gave an SSL error '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (against the web https://files.pythonhosted.org/). Caused by self signed certificate in that website.
So tried many things:
- connected by bash to the core docker and install it by hand. pip install… Nothing.
- I downloaded the package (wget) and install it by hand (pip install). The whl package gave an error.
- Finally after several hours I managed to do it as follows:
- Update pip :
pip3 install --upgrade pip
- Install the packages manually:
python -m pip install --trusted-host pypi.python.org --trusted-host files.pythonhosted.org --trusted-host pypi.org --trusted-host files.pythonhosted.org pip <packet>
Reboot everything and you’re done. Running
I am an “older” user of HA for the past few years.
Every time I try to update to a new core, my Amcrest camera stuff is either unusable or sporatic.
As a retired Software Engineer, my only guess is that there is so much time spent on all the new “applications”, that some just get missed (interrupts).
It’s great that you are supporting the new stuff, but ignoring the older “stuff” is just wrong.
Just my .02
2 Likes
OMG.
Just noticed new design for more-info for switches.
These are “changes for changes”, not for work.
Same as for lights: this approach may only be nice for tiny screens of mobile phones.
Here what we get:
- Let’s replace precise history-graphs with approximated statistics graphs.
- Let’s hide history-graphs for some domains (let a user make more steps to get these graphs).
Yes, these vertical sliders are nice - but this fact should not force users to see them only when they open more-info.
17 Likes
Oh, and to add to this, I am currently running 2022.5.3 to have an even REMOTELY stable version of the core running.
Damn it 
I am also having the same issue AND for the second time in a row 
Last two DB updates corrupted my database. First I lost 160GB of states table, now about 2 years of statistics.
Thank you very much for your answer, activating the advanced mode solves the problem. Very kind. Best regards
The new decimal precision doesnt seem to work on widgets on android. I have a widget showing me thr current price for electricity. It is set to only show 2 decimals in HA. But the widget seem to ignore this.
1 Like
Well at least I no longer have to restart my VM twice a day due to the 5 minute statistics job causing all state history to stop.
Icing on top of that is that all of those historical statistics jobs were stating in their debug logs “compiling statistics for 00:00:00-00:05:00” (or whatever 5 minute time span) - but the query was actually unconstrained in time according to MariaDB’s active queries view~
In other words, HA would start, the queue for backlogged statistics jobs would start, state history would all stop coming in. And the queries, being unconstrained in time, would continually start to run longer and longer and longer (aka, more than 5 minutes), resulting in an ever growing backlog of blocking queries to compile statistics and no other state history coming in, meaning I would have to restart the VM again to get HA and the DB unstuck.
Horary for the excellent work here 
1 Like
I’m mixed regarding this - on the one hand, it looks gorgeous. On the other, there are so many clicks to restart HA now. If I update some components via HACS, and click ‘navigate’, I now have to navigate, click restart, then click restart again - where only a few releases ago it was a ‘restart’ button directly instead of a ‘navigate’ one. Yes, cool, it’s pretty, and explains a lot more - but it’s added more for seemingly no reason other than ‘pretty’.
I added a button to one of my panels that just restarts it directly. Simple solution, but one brought into necessity through decisions I don’t fully comprehend.
1 Like
There are a few of us who have had issues with custom quirks in ZHA after the upgrade.
Seem to all be TUYA zigbee devices and it stops ZHA starting.
Perhaps list as a breaking change?
Discussions here with the solution which is to modify the custom quirk to “remove all references to TuyaDPType” :
2 Likes
Possibly a topic for it’s own thread, but since it was mentioned in the main post… I have an old Hue bridge (v2) that sits in a drawer since I changed everything to ZHA on a Sonoff dongle. Is there any benefit to be gained by setting up the hue bridge again now it can be used as a matter bridge?
Did you wait until the database upgrade was completed? I had the same issue, but simply let it run for the night and in the morning it was all migrated.
Hi,
The solution I found there works for me : Requirements for uptime_kuma not found: ['pyuptimekuma==0.0.6']. · Issue #37 · meichthys/uptime_kuma · GitHub
You just need to type “pip3 install pyuptimekuma==0.0.6” in the command shell of your HA container and Uptime Kuma will be fix after reboot.