2022.3: Select and play media

tom_l · March 4, 2022, 1:50pm

This was mentioned further up:

Personally I’m not seeing the issue. Which is odd.

arganto · March 4, 2022, 2:15pm

You should set the other disabled colors, esp.

  input-disabled-fill-color: var(--ha-card-background)

as well. Otherwise, you have still white fields, e.g. date picker in Log and History until completely loaded.

arganto · March 4, 2022, 2:16pm

Did you open an issue or do you, @robi?

The changes must be a mistake, because you have now only two times the friendly name, but 0 entity id anymore.

Ildar_Gabdullin · March 4, 2022, 2:19pm

I did not, a bit busy for dreaming about HA now(((
Will be grateful if someone do it!

petro · March 4, 2022, 2:22pm

The entity_id’s show up in the field under the friendly name when searching. The field was replaced with the same search field you see elsewhere in the UI which only shows the friendlyname after selection. It was not a mistake. You can still view the entity_id below in the entity/state/attributes grid and you can still use that grid to see everything.

Regardless of that information, it still may be worth creating an issue about this to ensure we can see the entity_id. Possibly by updating the control to show the friendly name and below it, the entity_id. Like it does when searching that list.

adorobis · March 4, 2022, 2:28pm

@jbouwh
A question about the MQTT Breaking change " The MQTT climate hold and away mode configuration settings are now deprecated":
I’m receiving warning messages in the log:

2022-03-04 15:14:28 WARNING (MainThread) [homeassistant.components.mqtt.climate] The 'send_if_off' option is deprecated, please remove it from your configuration
2022-03-04 15:14:28 WARNING (MainThread) [homeassistant.components.mqtt.climate] The 'hold_modes' option is deprecated, please remove it from your configuration

But neither of those options are defined for my device. I’m using HA autodiscovery and the config message looks like below:

name: CA350 Climate
availability_topic: comfoair/status
payload_available: online
payload_not_available: offline
unique_id: ca350-ca350_climate
device:
  identifiers:
    - ca350
  name: CA350
  manufacturer: Zehnder
  model: ComfoAir 350
temperature_command_topic: comfoair/comforttemp/set
temperature_state_topic: comfoair/comforttemp
current_temperature_topic: comfoair/supplytemp
min_temp: '15'
max_temp: '27'
temp_step: '1'
modes:
  - 'off'
  - fan_only
mode_state_topic: comfoair/ha_climate_mode
mode_command_topic: comfoair/ha_climate_mode/set
fan_modes:
  - 'off'
  - low
  - medium
  - high
fan_mode_state_topic: comfoair/ha_climate_mode/fan
fan_mode_command_topic: comfoair/ha_climate_mode/fan/set
temperature_unit: C
platform: mqtt

Is that warning message logged regardless of whether those deprecated options are configured or not? If not where can I find it if it is not defined in my HA auto discovery messages?

Ildar_Gabdullin · March 4, 2022, 2:30pm

The “grid below” and “state above” are independent UI elements.
This “let’s remove entity_id” change is harmful and meaningless.

Of course yes. This info should be displayed.

arganto · March 4, 2022, 2:33pm

Of course it is not against you, but to be honest: Then it is a very bad decision for the developer tools page. This is still developer tools. Last release this part got the hide/dropdown for whatever reasons and now the entity_id is hidden. What is the plan with this section, to make it even more useless and remove it? I liked to use it in the past, much faster than the table below, directly possible to change values. And now I have to unhide it, set values, search again in the table below to copy or at least see id, etc.

petro · March 4, 2022, 2:35pm

The plan was simply to give users the ability to search in that ui field, which was not possible before. It wasn’t done with ill intent, so stop treating it like it was. Just simply say “Hey I don’t like this”. We don’t need to hear a dissertation with every small UI change about how stupid it may have been.

arganto · March 4, 2022, 2:38pm

There was an auto-complete before as well.

petro · March 4, 2022, 2:38pm

Alright, I’m not here to argue. Please make your request. Thanks.

jbouwh · March 4, 2022, 2:46pm

Have a look at the documentation. It is likely you are using deprecated configuration options. Preset modes have replaced the old hold modes.

adorobis · March 4, 2022, 3:00pm

The full config is here:

name: CA350 Climate
availability_topic: comfoair/status
payload_available: online
payload_not_available: offline
unique_id: ca350-ca350_climate
device:
  identifiers:
    - ca350
  name: CA350
  manufacturer: Zehnder
  model: ComfoAir 350
temperature_command_topic: comfoair/comforttemp/set
temperature_state_topic: comfoair/comforttemp
current_temperature_topic: comfoair/supplytemp
min_temp: '15'
max_temp: '27'
temp_step: '1'
modes:
  - 'off'
  - fan_only
mode_state_topic: comfoair/ha_climate_mode
mode_command_topic: comfoair/ha_climate_mode/set
fan_modes:
  - 'off'
  - low
  - medium
  - high
fan_mode_state_topic: comfoair/ha_climate_mode/fan
fan_mode_command_topic: comfoair/ha_climate_mode/fan/set
temperature_unit: C
platform: mqtt

I’ve double checked and all options are in line with the documentation. I’m not using either of the two options mentioned in the warning messages.

calisro · March 4, 2022, 3:11pm

New amcrest binary sensor to monitor doorbell button (@PanicRide - #66302) (amcrest docs)

This is in the detailed log but was pulled, correct?

tom_l · March 4, 2022, 3:24pm

I don’t actually use either of them but just had a look and yeah they briefly flash white. Thanks for the tip.

jbouwh · March 4, 2022, 3:29pm

I’ll have a look at your config later.

prates · March 4, 2022, 4:05pm

The Samsung integration can detect my TV, but no device or entity is created after I complete the setup. It’s just me?

jbouwh · March 4, 2022, 4:29pm

In your config there are modes, mode_command_topic and mode_state_topic.
Replace them with the new config values preset_modes, preset_mode_command_topic and preset_mode_state_topic, and the warnings will disappear. See the documentation at MQTT HVAC - Home Assistant.

UPDATE: This is not the cause of the warnings. (my bad). modes, mode_command_topic and mode_state_topic are still valid config parameters.

Sergeantpup · March 4, 2022, 4:48pm

I’m not sure why, but these started displaying on mobile today. There was no update from the third party icon app. Whatever it was, doesn’t appear to be an issue for me in 2022.3.1

apedance · March 4, 2022, 4:58pm

SABnzbd
stopped working with 3.1

Logger: homeassistant.setup
Source: components/sabnzbd/__init__.py:170
First occurred: 17:55:12 (1 occurrences)
Last logged: 17:55:12

Error during setup of component sabnzbd
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 235, in _async_setup_component
    result = await task
  File "/usr/src/homeassistant/homeassistant/components/sabnzbd/__init__.py", line 218, in async_setup
    await async_configure_sabnzbd(hass, conf, use_ssl, name, api_key)
  File "/usr/src/homeassistant/homeassistant/components/sabnzbd/__init__.py", line 196, in async_configure_sabnzbd
    if await async_check_sabnzbd(sab_api):
  File "/usr/src/homeassistant/homeassistant/components/sabnzbd/__init__.py", line 170, in async_check_sabnzbd
    await sab_api.check_available()
  File "/usr/local/lib/python3.9/site-packages/pysabnzbd/__init__.py", line 93, in check_available
    await self._call(params)
  File "/usr/local/lib/python3.9/site-packages/pysabnzbd/__init__.py", line 41, in _call
    async with timeout(self._timeout, loop=self._session.loop):
TypeError: timeout() got an unexpected keyword argument 'loop'