2022.3: Select and play media

Blog
84

Not killed - itā€™s still worked outside HA of course :rofl:

No specific error message - it just was unavailable. Tried to reinstall integration, but was not able to do that either.

Back in previous release, it works.

85

There is an error when deleting a file

Sans titre
Sans titre963Ɨ599 22.9 KB

It will be fine to add the possibility do delete a directory.

86

Following the update to core 2022.3, the UniFi integration fails to start on my instance. Iā€™m running HAOS on x64 generic build.
The logs shows the following:

Logger: homeassistant.config_entries
Source: components/unifi/controller.py:311
First occurred: 09:10:45 (1 occurrences)
Last logged: 09:10:45

Error setting up entry Default for unifi
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 335, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/usr/src/homeassistant/homeassistant/components/unifi/__init__.py", line 40, in async_setup_entry
    if not await controller.async_setup():
  File "/usr/src/homeassistant/homeassistant/components/unifi/controller.py", line 311, in async_setup
    await self.api.initialize()
  File "/usr/local/lib/python3.9/site-packages/aiounifi/controller.py", line 152, in initialize
    await self.clients.update()
  File "/usr/local/lib/python3.9/site-packages/aiounifi/api.py", line 114, in update
    raw = await self._request("get", self._path)
  File "/usr/local/lib/python3.9/site-packages/aiounifi/controller.py", line 272, in request
    return await self._request(method, path, json, url)
  File "/usr/local/lib/python3.9/site-packages/aiounifi/controller.py", line 321, in _request
    raise ResponseError(f"Call {url} received 404 Not Found")
aiounifi.errors.ResponseError: Call https://192.168.130.1:443/proxy/network/api/s/default/stat/sta received 404 Not Found
87

Thanks for the links, Marius.

It wouldā€™ve helped, I agree. Perhaps a diff between the last 2022.2 release and this one on those files would help.

I was planning on making a list for myself anyway. Iā€™ll share if/when I have something.

88

Mine is still working.

One shelly device became unavailable, I reloaded the integration and all was fine.

89

After upgrade to 2022.3.0 my shelly integration gives an config error. Whatā€™s wrong? nothing breaking mentioned in the release notes. Reloading did not work for me

90

Logs logs logs.

91

Nothing mentioned in the logfiles. Only a message in the notification area

93

How is it achievable? Docs still mention only 2 sources: TV and HDMI

2 Likes
94

Logger: homeassistant.setup
Source: setup.py:155
First occurred: 10:46:58 (1 occurrences)
Last logged: 10:46:58

Setup failed for shelly: Requirements for shelly not found: [ā€˜paho-mqtt==1.5.1ā€™].

And when i try to add Shelly as an Integration this Message is displayed:

ā€œConfig flow could not be loaded: 500 Internal Server Error Server got itself in troubleā€

95

I did it yesterday. It was quite straight forward actually! :slight_smile: Remember to comment out your yaml config of the old integration once youā€™re done or it will be imported again on a restart. That was my only issue.

1 Like
96

anyone else experiencing issues with Kiosk mode custom card?

Especially the mobile settings seem to be a bit flakey

edit

nvm, fixed that, was a user error. trying ti avoid the ever present Kiosk mode error in inspector, I tried to load it like we need to load card-mod nowadays, via:

frontend:
  extra_module_url:
    - /local/lovelace/resources/card-mod/card-mod.js
#    - /local/lovelace/resources/kiosk-mode/kiosk-mode.js

Iā€™ve reset that to the regular (manual config) in resources.yaml, and now see the mobile settings being applied once again.

97

Are you using the native shelly or some external mqtt integration? Paho-mqtt is not a requirement for native shelly

98

I am using ShellyForHassā€¦ i try switching to the native integration. Thought i was using it :-/

99

Iirc shelly4hass predated the native integration. The native is very good imho.

100

It fixed mine as well! Thank you very much!

101

Is this really new or only new on additional places, because I have this

  mdc-select-fill-color: 'var(--ha-card-background)'
  mdc-select-label-ink-color: 'var(--secondary-text-color)'
  mdc-select-ink-color: 'var(--primary-text-color)'
  mdc-select-idle-line-color: 'var(--secondary-text-color)'
  mdc-select-dropdown-icon-color: 'var(--secondary-text-color)'
  mdc-select-hover-line-color: 'var(--secondary-text-color)'

in my theme after changes in 2021.11, where the dropdown-boxes in automations, etc. looked ā€œwhiteā€ and/or were changed already.

102

:man_shrugging: My selects only changed to white with this update and these fixed it.

103

yes, thats what Ive been using in the betaā€™s/dev updates too:

# 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)

and found in inspectorā€¦

talking about that quick-bar: it doesnā€™t reload properly anymore and often keeps swirling while not doing anything. Have to resort to the server tools again for reloading the various options

104

Arh, ā€˜Play Mediaā€™ function does not support Android TV (ie. tvā€™s with Android, not the Google TV dongle).
As we only have this, and a few OLD tvā€™s with chromecast, itā€™s not of much use.
Here Iā€™ve tested a few items.
It works on

  • Chromecast
  • Nest Hub

It does NOT work on

  • Android TV (which has cast built in???)
  • Lenovo Smart Clock (which was to be expected).

I was so happy, and thenā€¦