2023.11 To-do: Add release title

NaduK · November 2, 2023, 11:10pm

Hi all, I added Local To-do to see what it is but now I want to remove it. Even after I delete the list I still see it in the side bar. How can I remove it? Thanks

Gary_BKK · November 3, 2023, 12:18am

Yes, I see Supervisor in the dropdown list of logs. All entries in there are green.

stamandr · November 3, 2023, 1:24am

Anyone else having issues with automations ? I have many that no longer work after the update to 2023.11

tom_l · November 3, 2023, 2:10am

Check your logs for errors.

dicekillsyou161 · November 3, 2023, 2:16am

check for automations using a device ID and correct the device IDs in your automations, but it is best to use entity IDs so that this doesn’t happen.

nickrout · November 3, 2023, 2:16am

Please comment on the feature request relevant to this, rather than polluting this thread.

Gary_BKK · November 3, 2023, 2:30am

I tried the update again and now I DO see an error in the Supervisor log (not sure why I didn’t see it with previous attempts). Here is the error(s):

23-11-03 07:22:31 ERROR (MainThread) [supervisor.docker.interface] Can’t install ghcr.io/home-assistant/yellow-homeassistant:2023.11.0: 404 Client Error for http+docker://localhost/v1.43/images/ghcr.io/home-assistant/yellow-homeassistant:2023.11.0/json: Not Found (“No such image: ghcr.io/home-assistant/yellow-homeassistant:2023.11.0”)
23-11-03 07:22:31 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed
23-11-03 07:23:18 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token

Any help on how to resolve this?

allenporter · November 3, 2023, 2:55am

Technically possibly, definitely something to consider for the future! You are welcome to make a post in the feature requests forum.

allenporter · November 3, 2023, 2:57am

You can go to Settings > Devices & services then click on the Local Todo then ... and Delete.

peterd2 · November 3, 2023, 3:45am

My Flo did not have an issue with the update

mclever · November 3, 2023, 5:17am

2023.11.0 made my HA extremely slow. Going to revert to 10.5 or whatever the latest 10 release was.

Mini pc a handful of years old 8 core 32gb ram with ssd hardly being used.

NaduK · November 3, 2023, 5:48am

I did but I still have the icon on the sidebar. Can click that and add a list again (which again adds an entry in “Devices & services”)

starob · November 3, 2023, 9:19am

Thanks for your reply. Same behavior on my system now. Still a little strange though.

elmurato · November 3, 2023, 9:57am

To everyone who knows what a creeper or a zombie pigman is: 2023.11 also added support for Bedrock Edition servers

pcwii · November 3, 2023, 10:00am

I do now.

Deadpool · November 3, 2023, 10:22am

I’ve noticed this as well. Quite a few blueprints are broken after this update.

petro · November 3, 2023, 10:35am

Processor spikes are normal on complex operations. What’s noticeable between last version and this version is less processor use. I skipped the beta this release, updated on Wednesday.

The 2 large spikes are restarts. The periodic spikes are my 4am nightly backup.

artismiezitis · November 3, 2023, 10:38am

There is strange behavior with Shelly Wall Display.

It update values every 5minutes, but values hands on. If wall display shows - 28*C that in home assistant value is from last restart or when i reload the devices. Only then it updates values with the same which is on wall display.
If i wont restart the wall display or don`t press the Reload Device in HA, the values are stuck and wont change…

petro · November 3, 2023, 10:38am

You can already do that. That’s how and conditions work. If you have 4 anded conditions, the first is checked, if that passes it looks at the second and so on. Any time it fails, it does not check beyond that and fails the overall condition. This is how and works in all software languages too.

petro · November 3, 2023, 10:41am

@SgtBatten We’ve already looked into this. This stems from blueprints using incorrect defaults on selectors. It’s not a bug, but a bad blueprint. Please let the author of the blueprint know.

See this issue for details

github.com/home-assistant/core

Selector device/integration (mobile_app) issue in Blueprint after upgrade to 2023.11

opened 03:05PM - 02 Nov 23 UTC

closed 09:51AM - 03 Nov 23 UTC

hamid-elaosta

### The problem The Frigate Notification blueprint ([here](https://github.com/S…gtBatten/HA_blueprints/blob/main/Frigate%20Camera%20Notifications/Stable)) doesn't allow a value not to be set for the `notify_device` selector. Previously this worked with the default which is set to "false", by leaving the field empty in the UI, however, since upgrading to 2023.11 that is no longer accepted and unless a device is selected, the automation using this blueprint cannot be saved. Switching to YAML and setting it to empty, removing the selector or using empty double quotes also does not work, sayinf the value is invalid. ### What version of Home Assistant Core has the issue? core-2023.11.0 ### What was the last working version of Home Assistant Core? core-2023.10.5 ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Automation ### Link to integration documentation on our website https://www.home-assistant.io/docs/blueprint/selectors/#device-selector ### Diagnostics information _No response_ ### Example YAML snippet ```yaml notify_device: name: Mobile Device description: Select a device that runs the official Home Assistant app to receive notifications. If you wish to notify a group of devices or and Android/Fire TV use the field below to override this selection. This can be left blank in that case default: false selector: device: integration: mobile_app ``` ### Anything in the logs that might be useful for us? ```txt ERROR:homeassistant.components.automation:Blueprint 'Frigate Notification (0.11.0.13) - SgtB' generated invalid automation with inputs {'tv_transparency': '0%', 'camera': 'doorbell', 'base_url': 'https://<redacted>', 'critical': 'true', 'update_thumbnail': False, 'title': 'Doorbell', 'color': 'teal', 'icon': 'mdi:cctv', 'tv_size': 'large', 'tv_position': 'center', 'notify_group': 'ALL_DEVICES'}: Unknown device 'False' ERROR:homeassistant.components.automation:Blueprint 'Frigate Notification (0.11.0.13) - SgtB' generated invalid automation with inputs {'tv_transparency': '0%', 'base_url': 'https://<redacted>', 'critical': 'true', 'update_thumbnail': False, 'title': 'Other Camera', 'color': 'red', 'icon': 'mdi:cctv', 'tv_size': 'large', 'tv_position': 'center', 'notify_group': 'ALL_DEVICES', 'camera': 'camera.other'}: Unknown device 'False' ``` ### Additional information _No response_

In the case of the issue above, the default should be '' or [] for a device selector because it will output a list or string depending on the number of devices that are selected.