2021.5: Stability, performance, triggers, color modes!

[petro]

Known_devices was deprecated years ago. You have to do everything through the UI now.

[bdraco (J. Nick Koston)]

@123

The only Log warnings were for some Helpers that took longer than 10 seconds to load. I’ve seen it reported in previous releases and have ignored it; maybe it’s normal to take >10 seconds to load a few dozen Helpers on an RPI3.

That’s pretty normal on an RPi3 where everything is competing for disk I/O at startup. We did do some work to reduce the amount of writes in this version. There is a bit more next month, however it’s always going to be bound by the performance of the device and the underlying storage so I wouldn’t expect more than a few ms improvement.

[MandM78 (Greg)]

Getting the HACS “Failed to set up” warning in “Integrations”. It’s not really affecting my setup right now, so that’s less of a bother.

However, my IQVIA integration had the same error, so I deleted it and tried to re-add it and now it fails to add. Says that something went wrong during setup and then the integration “failed to load”. A reboot of HA gets rid of it. Any ideas?

[thermseekr (Tales Maschio)]

After the update I have a failure in Denon integration generating a log entry every 20 seconds:

2021-05-05 22:49:33 ERROR (MainThread) [homeassistant.components.denonavr.media_player] Error Not all attributes updated, those are left: {AppCommandCmd(cmd_id='1', cmd_text='GetToneControl', name=None, param_list=None, set_command=None, response_pattern=(AppCommandResponsePattern(update_attribute='_tone_control_status', add_zone=False, suffix='/status', get_xml_attribute=None), AppCommandResponsePattern(update_attribute='_tone_control_adjust', add_zone=False, suffix='/adjust', get_xml_attribute=None), AppCommandResponsePattern(update_attribute='_bass_level', add_zone=False, suffix='/basslevel', get_xml_attribute=None), AppCommandResponsePattern(update_attribute='_bass', add_zone=False, suffix='/bassvalue', get_xml_attribute=None), AppCommandResponsePattern(update_attribute='_treble_level', add_zone=False, suffix='/treblelevel', get_xml_attribute=None), AppCommandResponsePattern(update_attribute='_treble', add_zone=False, suffix='/treblevalue', get_xml_attribute=None))): None} occurred in method async_update for Denon AVR receiver
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/denonavr/media_player.py", line 173, in wrapper
    return await func(self, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/components/denonavr/media_player.py", line 224, in async_update
    await self._receiver.async_update()
  File "/usr/local/lib/python3.8/site-packages/denonavr/denonavr.py", line 173, in async_update
    await self.tonecontrol.async_update(
  File "/usr/local/lib/python3.8/site-packages/denonavr/tonecontrol.py", line 72, in async_update
    await self.async_update_tone_control(
  File "/usr/local/lib/python3.8/site-packages/denonavr/tonecontrol.py", line 81, in async_update_tone_control
    await self.async_update_attrs_appcommand(
  File "/usr/local/lib/python3.8/site-packages/denonavr/foundation.py", line 550, in async_update_attrs_appcommand
    raise AvrProcessingError(
denonavr.exceptions.AvrProcessingError: Not all attributes updated, those are left: {AppCommandCmd(cmd_id='1', cmd_text='GetToneControl', name=None, param_list=None, set_command=None, response_pattern=(AppCommandResponsePattern(update_attribute='_tone_control_status', add_zone=False, suffix='/status', get_xml_attribute=None), AppCommandResponsePattern(update_attribute='_tone_control_adjust', add_zone=False, suffix='/adjust', get_xml_attribute=None), AppCommandResponsePattern(update_attribute='_bass_level', add_zone=False, suffix='/basslevel', get_xml_attribute=None), AppCommandResponsePattern(update_attribute='_bass', add_zone=False, suffix='/bassvalue', get_xml_attribute=None), AppCommandResponsePattern(update_attribute='_treble_level', add_zone=False, suffix='/treblelevel', get_xml_attribute=None), AppCommandResponsePattern(update_attribute='_treble', add_zone=False, suffix='/treblevalue', get_xml_attribute=None))): None}

Has anyone else seen this? Any hints?

Thanks
Tales

[richieframe (Richie)]

The dev changelog has additional breaking changes for custom integrations, and the sun component is one of them, so the integration needs to be modified

[matze338]

I also have this issues.

[nickrout]

Painless upgrade, as always

[pergola.fabio]

Have you reported the denon avr issue on GitHub? Then i can subscribe before info the update… What model do you have?

[wlaarhov (Wim)]

Same issue and log messages here.

[Hellis81]

@system

There is a database upgrade in this release, but worry not as database upgrades now happen in the background and no longer prevent Home Assistant from starting. During migration, Home Assistant will prevent being restarted or stopped until the migration has been completed.

What if you are on the older version?
I’m still in March version, what happens if I upgrade to this version. Will I get the above upgrade type or the April with hours of downtime?

[T1ppes]

I am seeing the same behaviour, although I did not have the FRITZ!Box Tools installed via HACS, I did have the Fritz Box Device Tracker configured via YAML. With the new integration, that popped up, I do now have a lot of duplicate known devices. Is there any way to clean these up again? E.g. I have automations connected to device_tracker.device1, which is now not tracked anymore, and have a duplicate device_tracker.device1_2, which is tracked, but not used in the automations.

Also, if known_devices.yaml is depricated. How to I enable/disable tracking of devices? Previously I had a lot of devices set to track: false within the known_devices.yaml. I do not see a similar action in the UI.
Can the known_devices.yaml be deleted?

[seanomat]

I remove the Fritzbox-Tools again, removed the fritzbox-integration from .yaml, renamed the known_device.yaml, restarted HA and added the fritzbox-tools again.

The newly discovered devices now get their name from the fritzbox, without a suffix.

No idea how to disable tracking, but I don’t mind devices being tacked. I just don’t use the ones I’m not interested in.

[Hellis81]

CTRL + F5?
That usually works or reboot then CTRL + F5

[T1ppes]

Thanks. Is there any way to change the consider_home option?

[carsten_h (Carsten Friehe)]

@Hellis81

CTRL + F5?

Will not work as I am on a Mac.
But you are correct. I used a Webapp on the Mac and after restarting it it worked.

[carsten_h (Carsten Friehe)]

I have a problem with all my Tasmota lights:

I can click on one of the colors, the light is shortly switching to this color and then back to white.

This is not happening with ZigBee lights!

[DarrenHill]

OK, so I guess it’s time to bite the bullet and rebuild my devices list.

There’s a lot in there that are either duplicates or aren’t recognised properly (just list as IP address or Android MAC address) so it’s going to be a pain…

I think I’m going to roll back with the snapshot, then remove the configuration.yaml device tracking entry and known_devices.yaml and update again so hopefully I won’t get all the duplicates again and can make it a bit more clean.

[deluxestyle]

I can see there is a new blueprint under

config\blueprints\script\homeassistant\confirmable_notification.yaml

It seems to be a script. But I do not find how to use this blueprint

[DigitalFeonix]

I have the adaptive lighting custom integration from HACS installed and I found that half my lights that I had set up with them work (the cheap ecosmart zigbee bulbs from Homedepot, brought in via ZHA) and half don’t (some Shelly duos with latest firmware, brought in via built in integration).

[ben1410 (Ben)]

Hi,
I updated my dev box and when i restart i get this message
2021-05-06 06:43:42 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: ‘None’ has no attribute ‘name’ when rendering ‘{{ states.switch.lounge_tv_unit.name}} Current’

2021-05-06 06:43:42 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: ‘None’ has no attribute ‘name’ when rendering ‘{{ states.switch.lounge_tv_unit.name}} Current Consumption’

2021-05-06 06:43:42 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: ‘None’ has no attribute ‘name’ when rendering ‘{{ states.switch.lounge_tv_unit.name}} Total Consumption’

2021-05-06 06:43:42 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: ‘None’ has no attribute ‘name’ when rendering ‘{{ states.switch.lounge_tv_unit.name}} Voltage’

2021-05-06 06:43:42 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: ‘None’ has no attribute ‘name’ when rendering ‘{{ states.switch.lounge_tv_unit.name}} Today’s Consumption’

i have this setup in my config yaml for use with the TP-Link HS110

      driveway_light_amps:
          friendly_name_template: "{{ states.switch.driveway_light.name}} Current"
          value_template: '{{ states.switch.driveway_light.attributes["current_a"] | float }}'
          unit_of_measurement: 'A'
      driveway_light_watts:
          friendly_name_template: "{{ states.switch.driveway_light.name}} Current Consumption"
          value_template: '{{ states.switch.driveway_light.attributes["current_power_w"] | float }}'
          unit_of_measurement: 'W'
      driveway_light_total_kwh:
          friendly_name_template: "{{ states.switch.driveway_light.name}} Total Consumption"
          value_template: '{{ states.switch.driveway_light.attributes["total_energy_kwh"] | float }}'
          unit_of_measurement: 'kWh'
      driveway_light_volts:
          friendly_name_template: "{{ states.switch.driveway_light.name}} Voltage"
          value_template: '{{ states.switch.driveway_light.attributes["voltage"] | float }}'
          unit_of_measurement: 'V'
      driveway_light_today_kwh:
          friendly_name_template: "{{ states.switch.driveway_light.name}} Today's Consumption"
          value_template: '{{ states.switch.driveway_light.attributes["today_energy_kwh"] | float }}'
          unit_of_measurement: 'kWh'

Only started appearing on reboot after the latest update , all the entities appear to be fine …
Thanks
Ben