2021.4: For our advanced users ❤️

[pedro.goncalves]

okay so it seems to be a normal process for the upgrade, thanks i am just going to leave it for a few days and see how it goes thanks again.

[sparkydave (🇦🇺 Dave)]

If you find yourself trying again, just go straight to HA version 2021.5.3 and skip 2021.4.x. The database migration has been streamlined and takes place in the background. This is what I did.

[pedro.goncalves]

Hi @sparkydave i’m currently on 2021.5.4 - i have been having this issue below since the DB upgrade and it does not matter how long i leave HA to run - i have rebuilt it like 6 times. there has to be something i’m missing as this list goes on and on and on.

 2021-05-15 17:41:14 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.561443124472cf432abf04f is taking over 10 seconds
2021-05-15 17:41:14 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.803043132dc44f2229a332d is taking over 10 seconds
2021-05-15 17:41:14 WARNING (MainThread) [homeassistant.helpers.entity] Update of calendar.phases_of_the_moon is taking over 10 seconds
2021-05-15 17:41:15 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.bom_mandurah_max_temp_c_0 is taking over 10 seconds
2021-05-15 17:41:17 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.brandon_lamp is taking over 10 seconds
2021-05-15 17:41:17 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.living_room_lamp is taking over 10 seconds
2021-05-15 17:41:17 WARNING (MainThread) [homeassistant.components.light] Updating tplink light took longer than the scheduled update interval 0:00:05
2021-05-15 17:41:22 WARNING (MainThread) [homeassistant.components.light] Updating tplink light took longer than the scheduled update interval 0:00:05
2021-05-15 17:41:25 WARNING (MainThread) [homeassistant.components.switch] Updating tuya switch took longer than the scheduled update interval 0:00:15
2021-05-15 17:41:25 WARNING (MainThread) [homeassistant.components.light] Updating tuya light took longer than the scheduled update interval 0:00:15
2021-05-15 17:41:27 WARNING (MainThread) [homeassistant.components.light] Updating tplink light took longer than the scheduled update interval 0:00:05
2021-05-15 17:41:32 WARNING (MainThread) [homeassistant.components.light] Updating tplink light took longer than the scheduled update interval 0:00:05
2021-05-15 17:41:33 WARNING (MainThread) [homeassistant.components.systemmonitor.sensor] Updating systemmonitor took longer than the scheduled update interval 0:00:15
2021-05-15 17:41:35 WARNING (MainThread) [homeassistant.components.sensor] Updating bom_forecast sensor took longer than the scheduled update interval 0:00:30
2021-05-15 17:41:37 WARNING (MainThread) [homeassistant.components.light] Updating tplink light took longer than the scheduled update interval 0:00:05
2021-05-15 17:41:40 WARNING (MainThread) [homeassistant.components.light] Updating tuya light took longer than the scheduled update interval 0:00:15
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of weather.mandurah is taking over 10 seconds
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.living_room_lamp_on is taking over 10 seconds
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.theatre_lamp_on is taking over 10 seconds
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.cassidy_lamp_on is taking over 10 seconds
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.brandon_lamp_on is taking over 10 seconds
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.patio_on is taking over 10 seconds
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.alfresco_on is taking over 10 seconds
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.activty_on is taking over 10 seconds
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.living_room_on is taking over 10 seconds
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.living_room_on_2 is taking over 10 seconds
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.dining_room_on is taking over 10 seconds
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.kitchen_back_on is taking over 10 seconds
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.kitchen_pendants_on is taking over 10 seconds
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.kids_bathroom_on is taking over 10 seconds
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.main_bathroom_on is taking over 10 seconds
2021-05-15 17:41:43 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.night_light_on is taking over 10 seconds
2021-05-15 17:41:44 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.db_size is taking over 10 seconds
2021-05-15 17:41:47 WARNING (MainThread) [homeassistant.components.light] Updating tplink light took longer than the scheduled update interval 0:00:05
2021-05-15 17:41:47 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.8023042313d3c4f22b426e73 is taking over 10 seconds
2021-05-15 17:41:47 WARNING (MainThread) [homeassistant.helpers.entity] Update of calendar.holidays_in_australia is taking over 10 seconds
2021-05-15 17:41:47 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.bom_mandurah_min_temp_c_0 is taking over 10 seconds
2021-05-15 17:41:50 WARNING (MainThread) [homeassistant.helpers.entity] Update of switch.56144431272cf432a3be94d2 is taking over 10 seconds
2021-05-15 17:41:52 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.brandon_lamp is taking over 10 seconds
2021-05-15 17:41:52 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.living_room_lamp is taking over 10 seconds
2021-05-15 17:41:52 WARNING (MainThread) [homeassistant.components.light] Updating tplink light took longer than the scheduled update interval 0:00:05
2021-05-15 17:41:55 WARNING (MainThread) [homeassistant.components.switch] Updating tuya switch took longer than the scheduled update interval 0:00:15
2021-05-15 17:41:55 WARNING (MainThread) [homeassistant.components.light] Updating tuya light took longer than the scheduled update interval 0:00:15
2021-05-15 17:41:57 WARNING (MainThread) [homeassistant.components.light] Updating tplink light took longer than the scheduled update interval 0:00:05
2021-05-15 17:42:02 WARNING (MainThread) [homeassistant.components.light] Updating tplink light took longer than the scheduled update interval 0:00:05
2021-05-15 17:42:03 WARNING (MainThread) [homeassistant.components.weather] Updating darksky weather took longer than the scheduled update interval 0:00:30
2021-05-15 17:42:03 WARNING (MainThread) [homeassistant.components.systemmonitor.sensor] Updating systemmonitor took longer than the scheduled update interval 0:00:15

[nickrout]

Does this actually have a noticeable effect on performance? Or are you just worried about the log entries?

[pedro.goncalves]

Hi @nickrout - i can not access the default lovelace interface 20sec to 30sec afer i restart home asssitant via docker. i can not restart home assistant from the normal settings area.

[pedro.goncalves]

wow something strange just happned - i rebooted Home Assistant again via docker and so far it has not locked up - it’s been almost 5min maybe rebooting HA until it finally works must have fixed something - not too sure, but happy i’m all working again.

Thanks to all for your ideas. Have a great day!!

edit… Spoke too soon, Home Assistant interface is blank again

[Mariusthvdb (Marius)]

nm, post error

[rodpayne]

The automation trace is truly amazing! I’ve already fixed a couple of things.

At first I thought that the automation had to be editable to get the trace because that is where the SHOW TRACE button is located, but then I discovered the icon. Maybe an Info Trace Edit column heading would help some of us. (I think that I tried the icon at some point but it did not do anything within my attention span.)

[nickrout]

Why did you post this here instead of wherever you found the template?

[msauto (Mike)]

Because I found the template years ago when I first installed home assistant and cant remember where I found it (and a search on the forum and google brought me here). I obviously made a mistake asking for help in this thread and apologize. I will remove my post if I can. Thanks for the assist.

[finity]

@msauto

cant remember where I found it

likely somewhere in here:

Last Alexa Sensor using Keaton Taylor Alexa Media Player custom component

I have been using the alexa python script https://blog.loetzimmer.de/2017/10/amazon-alexa-hort-auf-die-shell-echo.html?m=1 for some time now mainly for the last alexa option which returns the last echo or dot to have spoken. This script is not 100% reliable and requires the cookie to be updated every couple of weeks. I noticed when I updated https://github.com/keatontaylor/custom_components/tree/master/media_player to the latest version 1.0.2 it now has an attribute last_called. This can be u…

[msauto (Mike)]

Thanks for the helpful suggestion, i will check it out and see if i can find any info. Thanks again @finity

[GSzabados (Gábor Szabados)]

Does anybody know what category the Energy “integration” falls under on the Analytics webpage? I cannot find it as Energy.

[tom_l]

What analytics web page?

[GSzabados (Gábor Szabados)]

@system

Home Assistant Analytics

Now don’t be scared by the title!

Today we introduce: Home Assistant Analytics. Opt-in, privacy-aware, public and open source. Just as it all should be for our project.

@ludeeus did a fantastic job writing this new integration. You decide if you turn it on or not; however, we guarantee its privacy-aware. Doubt it? Review it! Everything is open source!

Not open enough for you? We are publishing the result for everybody to see:

Screenshot of the Home Assistant Analytics website.

Well, maybe you want to view the public result yourself:

https://analytics.home-assistant.io

So why do we do this? Well, it helps the project and all contributors to see things like: Most used integrations. This can significantly help with improving project priorities. It also helps to convince manufacturers to work with Home Assistant, add local control and privacy-focused features.

“But the updater did this already, right?” Yes, well, the updater has actually been broken. So while we had some data, it was barely usable (actually not useable at all). Instead of fixing the updater, we now have a better solution that better matches our project goals. The updater still exists; it now just does one single thing: showing if an update is available.

Want to help the project out? Please enable Home Assistant Analytics. We would be very grateful!

This one from the OP…

[tom_l]

Ah right. Sorry I forgot all about that and didn’t realise which release this topic was for.

The energy dashboard is not an integration so is not tracked there.

So close to 100,000 tracked users.

[GSzabados (Gábor Szabados)]

@tom_l

The energy dashboard is not an integration so is not tracked there.

Actually, according the Info page, it is…

So, why is it then not on the Analytics page?

[tom_l]

According to the integrations page it isn’t. So

[mgim]

Hey @CentralCommand ,

Thank you for your answer.
My system is up to date as of january 2022 (HA and Z2M) and I still have this Warning. Any clue how to fix it?

Logger: homeassistant.helpers.template
Source: helpers/template.py:1779
First occurred: 18:50:39 (1 occurrences)
Last logged: 18:50:39

Template variable warning: 'dict object' has no attribute 'action' when rendering '{{ value_json.action }}'<s>Text</s>

[CentralCommand (Mike)]

If you know which sensor created by Z2M is looking for action in the MQTT messages and you don’t actually use that sensor then you can disable it in HA. That will stop it from processing messages looking for action and failing to find the attribute.

If you don’t know which sensor that’s coming from or you do use it then there’s no workaround available, you have to report an issue in the Z2M repo. The template that is processing the MQTT messages is created by Z2M during discovery, you can’t change it yourself.

TBH even if you can use the workaround you should report an issue. I haven’t seen any warnings like that from Z2M for months and the issue I linked has gone silent a while ago as well. You must either be in an edge case that Koenkk would want to know about or something is misconfigured.