2022.3: Select and play media

[nickrout]

Nice pic and welcome aboard, but neither 2.7 nor 2.9 are versions. Please see here, and follow the advice there.

How to help us help you - or How to ask a good question

Before we begin… This forum is not a helpdesk The people here don’t work for Home Assistant, that’s an open source project. We are volunteering our free time to help others. Not all topics may get an answer, never mind one that helps you solve your problem. [image] This also isn’t a general home automation forum, this is a forum for Home Assistant and things related to it. Any question about Home Assistant, and about using things with Home Assistant, is welcome here. We can’t help you with e…

[koldogut]

I have it already enabled under configuration.yaml but no luck, any other idea?

[tonicb]

Just upgraded to 2022.3.3 and my system does not reports the correct versions and wants to upgrade to 2022.3.2. Interesting…

[Geeforce]

The update is for supervisor

[tonicb]

Thanks for your help! didn’t notice it was only the supervisor

[Mariusthvdb (Marius)]

just noticed the top corners of the input_selects (border-top-left-radius/border-top-right-radius) in eg logbook use a 4px border -radius, while the bottom ones (border-bottom-left-radius/border-bottom-right-radius …) use 0px.

the 4px looks odd in my 0px frontend, so just letting you know that setting:

mdc-shape-small: 0px

in the theme fixes that.

with

# set colors on quickbar
    mdc-text-field-fill-color: var(--card-background-color) # quickbar header
    mdc-text-field-ink-color: var(--primary-text-color) #var(--mdc-theme-primary)
# set colors on input_select
    mdc-select-ink-color: var(--primary-text-color)
    mdc-select-fill-color: var(--card-background-color)
# set top corners of input_selects in logbook
    mdc-shape-small: 0px

I have my themes corrected (…) though I admit not using all other theme options that might be off in the new frontend.

[yuri-vashchenko]

in my case stream component is enabled

[schmitter]

I was able to get music to play on roku, but not a video from a camera stream. This is a great feature, let me know if I can help.

[jumon]

Getting a failure on the upgrade from core-2022.3.2 to core-2022.3.3:

22-03-09 20:25:22 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2022.3.3
22-03-09 20:25:22 INFO (SyncWorker_2) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2022.3.2 to ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2022.3.3
22-03-09 20:25:22 INFO (SyncWorker_2) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/raspberrypi4-64-homeassistant with tag 2022.3.3.
22-03-09 20:25:42 ERROR (MainThread) [supervisor.jobs] Unhandled exception: 
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 106, in wrapper
    return await self._method(*args, **kwargs)
  File "/usr/src/supervisor/supervisor/homeassistant/core.py", line 229, in update
    await _update(version)
  File "/usr/src/supervisor/supervisor/homeassistant/core.py", line 207, in _update
    await self.instance.update(
  File "/usr/src/supervisor/supervisor/utils/__init__.py", line 33, in wrap_api
    return await method(api, *args, **kwargs)
asyncio.exceptions.TimeoutError
22-03-09 20:25:42 WARNING (MainThread) [supervisor.utils.codenotary] rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 35.168.17.115:443: i/o timeout"

[nickrout]

That appears to be one of amazon’s hosts. Possibly a momentary glitch.

[guedeaux]

Same here. I was having some other issues simultaneously, so thought it was a “me” issue.

There are some additional errors in the supervisor:

22-03-09 19:46:59 WARNING (MainThread) [supervisor.utils.codenotary] rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 35.168.17.115:443: i/o timeout"
22-03-09 19:47:19 ERROR (MainThread) [supervisor.resolution.check] Error during processing IssueType.TRUST: 
22-03-09 19:47:19 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
22-03-09 19:47:19 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
22-03-09 19:47:19 INFO (MainThread) [supervisor.resolution.check] System checks complete
22-03-09 19:47:19 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
22-03-09 19:47:29 ERROR (MainThread) [supervisor.utils.codenotary] Timeout while processing CodeNotary
22-03-09 19:47:39 WARNING (MainThread) [supervisor.utils.codenotary] rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 35.168.17.115:443: i/o timeout"

[Friedi]

The same here from 2022.02.09 to 2022.03.03.
It seems the supervisor-2022.03.2 has a problem. Before updated to supervisor-2022.03.2 it was possible for me to update to 2022.03.03 but I had to restore 2022.02.09 due to a issue with the Netatmo integration which doesn’t work for me with 2022.03.03.
Unfortunately I updated the supervisor meanwhile and since that I am not able to update

Anyway, there is a issue opened: Cann't update from 2022.3.1 to 2022.3.3 · Issue #67930 · home-assistant/core · GitHub

[dbrunt (Daniel)]

Is it just me or has the UI link to config/energy/dashboard gone AWOL?

[makai]

It’s here now: config/dashboards/energy

[dbrunt (Daniel)]

Ah, thanks. I was trying to find it under Configuration, not Dashboards.

I managed to get to it for my post via…

[Jtarche]

The new “Media Selector” has Text-to-Speech feature from Nabucasa.

If I setup Google Cloud TTS manually (no Nabucasa), will TTS be available thru Media Selector?

[Obelixxx (Rein Graat)]

In 2022.03.03 it is not possible anymore to insert energy costs in Dashboard.

Logger: frontend.js.latest.202203011
Source: components/system_log/init.py:190
First occurred: 09:54:05 (23 occurrences)
Last logged: 11:53:02

• https://192.168.2.2:8123/frontend_latest/ff1cd660.js:194:393 Uncaught TypeError: Cannot read properties of undefined (reading ‘value’)
• https://192.168.2.2:8123/lovelace-dashboard/home:0:0 Uncaught
• https://xxx.duckdns.org/lovelace/default_view:0:0 Uncaught
• https://xxx.duckdns.org/frontend_latest/ff1cd660.js:194:393 Uncaught TypeError: Cannot read properties of undefined (reading ‘value’)
• https://192.168.2.2:8123/lovelace/default_view:0:0 Uncaught

[jumon]

The following commands fixed this for me (have to SSH into the OS):
ha su repair
ha core rebuild
ha host reboot

Did a backup after running these commands and it may have also fixed my oppressively huge backup issue. Notice the file size of the full backup now vs before:

[Geeforce]

Sorry, but what will be fixed by this?

[jumon]

This is a reply to Friedi which is a reply to my earlier post. You can follow the chain in the upper right of the messages. In short, a supervisor upgrade issue was causing all of this and this fix corrected that and must have cleaned out some other stuff causing my backups to get smaller/faster.