After restarting HA, reloading integrations, Google Nest and BMW still not working.
I had to uninstall google nest and BMW integrations.
After reinstalling the 2 integrations, it works now.
I tested my configuration and all of my issues were fixed prior to the release. Some (most)were custom issues) some were not understanding the changes. There is a big advantage in joining the beta as the “team” is monitoring the discord channel and very responsive to issues.
3 Likes
try to reinstall it again, at least for me HA allows restarting, my JQ200 never worked properly for me, so not a bill loss.
Thank you for all the hard work.
I think I found a tiny little bug. I apologize if I am letting you know in the wrong place.
It seems that integrations which have many objects listed so they can scroll are missing a three dot (hamburger) sub menu for basic controls like reload, delete etc. I am attaching a screen shot
I’ve tried in safari and firefox.
Thanks!
Edit: Thank you cyn. After clicking “>” I get get to a three dot menu.
The three dots show up on each device. Click the > sign.
1 Like
I ended up deleting one of my shelly switchs (Shelly 1L) from the core integration, and now it is not discoverable anymore by HA.
All other shelly devices are ok.
I can acess it directly by IP address or in shelly app, so its really related with the last upgrade.
Settings on shelly switch did not change (CoIoT is activated), firmware is updated, so not sure why it is ignored by HA.
EDIT: After 2-3 restarts HA recognized the switch and accepted this inclusion again. Its working!
I am experiencing the same problem. Rather than SSH to restart, is it safe to stop and restart the docker container?
I’m unable to upgrade to 2021.12.1, I ran into the same issue with 2021.12.0 and hoped that it would be resolved in 2021.12.1 but it hasn’t
Home Assistant crashes and then reverts to 2021.11.5
Any troubleshooting steps that helps me resolve this is appreciated.
21-12-13 08:37:13 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2021.12.1
21-12-13 08:37:13 INFO (SyncWorker_3) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2021.11.5 to ghcr.io/home-assistant/qemux86-64-homeassistant:2021.12.1
21-12-13 08:37:13 INFO (SyncWorker_3) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2021.12.1.
21-12-13 08:37:34 INFO (SyncWorker_3) [supervisor.docker.interface] Stopping homeassistant application
21-12-13 08:37:34 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Received message 8:1000 is not str
21-12-13 08:37:34 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed
21-12-13 08:37:52 INFO (SyncWorker_3) [supervisor.docker.interface] Cleaning homeassistant application
21-12-13 08:37:53 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
21-12-13 08:37:53 INFO (SyncWorker_4) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2021.12.1
21-12-13 08:37:53 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
21-12-13 08:38:23 ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed!
21-12-13 08:38:23 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback!
21-12-13 08:38:23 INFO (MainThread) [supervisor.homeassistant.core] A backup of the logfile is stored in /config/home-assistant-rollback.log
21-12-13 08:38:23 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2021.11.5
21-12-13 08:38:23 INFO (SyncWorker_8) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2021.12.1 to ghcr.io/home-assistant/qemux86-64-homeassistant:2021.11.5
21-12-13 08:38:23 INFO (SyncWorker_8) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2021.11.5.
21-12-13 08:38:23 INFO (SyncWorker_8) [supervisor.docker.interface] Cleaning homeassistant application
21-12-13 08:38:24 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse
21-12-13 08:38:24 INFO (SyncWorker_2) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/qemux86-64-homeassistant with version 2021.11.5
21-12-13 08:38:24 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
21-12-13 08:38:50 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
21-12-13 08:38:50 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-12-13 08:39:35 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
21-12-13 08:39:35 INFO (MainThread) [supervisor.homeassistant.core] Successfully started Home Assistant 2021.11.5
21-12-13 08:39:35 INFO (SyncWorker_0) [supervisor.docker.interface] Cleanup images: ['ghcr.io/home-assistant/qemux86-64-homeassistant:2021.12.1']
What does the rollback log say?
HOLY MOLY there are a lot of clicks needed in order to restart HA. Not sure that was the best UI decision…
1 Like
Mine worked fine before this update ((
Hello,
Some questions about change made in HUE integration.
Flash : ok I saw the issue reported.
Motion sensor: I’m using in a lot of automations attributes: dark & daylight. Via both of the value, I’m able to determine if I need to switch light ON or OFF. This is available in hue motion sensors to detect when it’s dark (value defined in hueapp).
Now with 2021.12: I don’t see them anymore. I don’t find any easy trigger value that replace those.
I don’t really want to play with lux value which will need to know for every room, what kind of value is good.
So my question is why it’s removed ?
Feature added by 2021.12
Swtich Motion : → same as the switch of the Hue App (thanks to provide this)
Switch illuminance: → What is the purpose ? (not in Hue App)
Attribute light_level_valid: true → this value is always true → What is the purpose ?
[post updated: answering myself:
- light_level_valid: required(boolean) Indication whether the value presented in light_level is valid
As mentionned, hue integration moving to API V2 which don’t have those dark and daylight :(]
Thank you for your help
You could put the restart service in a script, then put that script entity on any lovelace dashboard.
alias: Restart HA
sequence:
- service: homeassistant.restart
mode: single
icon: mdi:restart
This is just an example of a lovelace entities card I threw together:
6 Likes
➜ cat home-assistant-rollback.log
2021-12-13 08:37:55 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration alexa_media 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
2021-12-13 08:37:55 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration attributes 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
2021-12-13 08:37:55 WARNING (SyncWorker_3) [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
2021-12-13 08:37:55 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration nhl_api 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
2021-12-13 08:37:55 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration pyscript 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
2021-12-13 08:37:55 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration frigate 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
2021-12-13 08:37:55 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration meater 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
2021-12-13 08:37:55 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration reolink_dev 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
Thanks for the suggestion, @gonzotek! I think I will give that a try. Although, it does really bug me that the native restart button is now buried so deep in the UI.
No mention of anything Tuya. A lot of previously supported devices stopped working back in 2021.11.1 and no one seems to be responding to the bug reports on github. I’m stuck in 2021.10.6 until this is fixed. Any ideas?
Thanks. It’s odd that it mentions fixing support for brightness for device type dj, but that’s the device I can’t get to recognize in the first place. I guess I’ll give it a try and see.
Doesn’t work for me, if I switch this entity off, it simply switched back on a few seconds later
One click to Systems and Integrations now. Thank you so much!