2021.4: For our advanced users ❤️

It gives you the full template you can search for. That last one has issues with quotes. Use double quotes outside your template and single quotes inside.

I am sorry to look stupid. How do I search for the full template ? I have many files and right now I use the FIle editor addon. Maybe I should use another one?

Don’t know about the file editor addon but the editor I use (VSCode) you press ctrl+f to find then paste what you are searching for into the find field.

1 Like

And this work among all the files and all the folders that you have? Meaning I do not need to open each file containing code and do ctrl+f each time?
Because with File editor, the search is limited to the current file displayed on the screen.

See this post, about 10 posts up

2 Likes

Thank you @petro, thank you @tom_l

1 Like

I am still doing something wrong I guess…

Is there a reason the “latest” version is a lower release date than what I have installed for both CORE and Supervisor?

Did you set the files to include?

Also exclude the home-assistant.log file.

Yes there is. Read up a few posts.

It doesn’t seem to do this if you are on the Beta channel? Not doing it on mine anyway…

I’m not in the beta at the moment and I’ve never seen the issue (HA OS NUC). :man_shrugging:

I am not in the beta and I have supervised on debian, I have never seen it either.

I’m having the same here, I’m on 2021.4.6 and it’s saying the newest version is 2021.4.4

ignore it

You use zigbee2mqtt right? Those first 4 templates match the pattern of ones created by Z2M. This issue is tracking that and this pr has been merged to fix it. Next release of Z2M is expected may 1st so you can either wait until then or switch to the edge/dev version to see the changes sooner.

However few additional notes

  • koenkk says here that click is deprecated as an attribute. So that value_json.click one won’t be fixed, you should look into getting rid of that
  • The long running_state one is still being looked at i believe. There’s some conversation with koenkk on that here. You can follow along and add your input if you want

The last mapping_proxy one is something else, it’s not Z2M. You’ll have to track that one down separately

1 Like

I saw your post about this in the other thread too but I don’t see what you are seeing.

I have an automation that runs a couple of times a day at most. The last time it ran was at 0835 this morning (1147 riught now as I type this) and my automation trace is still there. Along with the one that ran last night and the one that ran yesterday morning.

I believe restarting HA will remove the trace history tho because there have been times I expected to see a trace and it wasn’t there and I believe it was caused by a HA restart.

I assume you aren’t restarting HA in between the time the automation should have run and the time you check the trace?

Also I’m not sure if the trace gets created if the automation trigger fails to start the automation? Maybe that’s a place to start looking.

I love this update and the whole project. Everytime I install an update, there are such great additions to this project, thank you all for the great work!

1 Like

I haven’t restarted HA no, I just get to looking at the trace 2-3 minutes after its run, and its missing.

Basically, the automation is not failing, its just doing an action I’m trying to block in certain scenarios. I have push notifications that tell me if someone is detected in the front yard by my camera. I want to block it when certain things happen, e.g. I leave home by opening the front door, don’t send one, or I am arriving home, as my distance is less than 200m from my house, but I’m not yet tagged as ‘at_home’ (GPS update delay). I still have the odd break through case that’s happening (e.g. notification when I dont want it) and I want to find out why, unfortunately with the trace missing, I am unable to.

1 Like

Any advanced user idea why my update from 2021.3.4 to 2021.4.6, on RPi4, HassOS 5.13, 32b, fresh db file approx 50Mb, is lasting 4 hrs so far? Core CPU usage 0.7%, Core RAM usage 5.6%.
Last 14 says I am trying to update, but no way, does not matter if I try RPi3 or RPi4, 32b or 64b version, everytime it ends in the same way, core log is spammed by the similar warnings (repeating in cycles)

2021-04-25 13:03:24 ERROR (MainThread) [custom_components.hacs] <Plugin iantrich/restriction-card> 
2021-04-25 13:03:24 ERROR (MainThread) [custom_components.hacs] iantrich/restriction-card - 
2021-04-25 13:03:25 ERROR (MainThread) [custom_components.hacs] <Integration thomasloven/hass-browser_mod> 
2021-04-25 13:03:25 ERROR (MainThread) [custom_components.hacs] thomasloven/hass-browser_mod - 
2021-04-25 13:03:30 ERROR (MainThread) [custom_components.hacs] <Theme JuanMTech/google_light_theme> 
2021-04-25 13:03:30 ERROR (MainThread) [custom_components.hacs] JuanMTech/google_light_theme - 
2021-04-25 13:03:31 ERROR (MainThread) [custom_components.hacs] <Plugin thomasloven/lovelace-hui-element> 
2021-04-25 13:03:31 ERROR (MainThread) [custom_components.hacs] thomasloven/lovelace-hui-element - 
2021-04-25 13:03:33 WARNING (MainThread) [homeassistant.components.media_player] Updating braviatv media_player took longer than the scheduled update interval 0:00:10
2021-04-25 13:03:43 WARNING (MainThread) [homeassistant.components.media_player] Updating braviatv media_player took longer than the scheduled update interval 0:00:10
2021-04-25 13:03:49 WARNING (MainThread) [homeassistant.components.weather] Updating darksky weather took longer than the scheduled update interval 0:00:30
2021-04-25 13:03:50 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating rpi_power binary_sensor took longer than the scheduled update interval 0:00:30
2021-04-25 13:03:50 WARNING (MainThread) [homeassistant.components.switch] Updating wake_on_lan switch took longer than the scheduled update interval 0:00:30
2021-04-25 13:03:51 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:01:00
2021-04-25 13:03:53 WARNING (MainThread) [homeassistant.components.media_player] Updating braviatv media_player took longer than the scheduled update interval 0:00:10
2021-04-25 13:03:54 WARNING (MainThread) [homeassistant.components.sensor] Updating sql sensor took longer than the scheduled update interval 0:00:30
2021-04-25 13:03:54 WARNING (MainThread) [homeassistant.components.sensor] Updating history_stats sensor took longer than the scheduled update interval 0:00:30
2021-04-25 13:03:54 WARNING (MainThread) [homeassistant.components.sensor] Updating filesize sensor took longer than the scheduled update interval 0:00:30
2021-04-25 13:03:54 WARNING (MainThread) [homeassistant.components.sensor] Updating systemmonitor sensor took longer than the scheduled update interval 0:00:30
2021-04-25 13:03:56 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:01:00
2021-04-25 13:04:03 WARNING (MainThread) [homeassistant.components.media_player] Updating braviatv media_player took longer than the scheduled update interval 0:00:10
2021-04-25 13:04:11 WARNING (MainThread) [homeassistant.components.calendar] Updating google calendar took longer than the scheduled update interval 0:01:00
2021-04-25 13:04:13 WARNING (MainThread) [homeassistant.components.media_player] Updating braviatv media_player took longer than the scheduled update interval 0:00:10
2021-04-25 13:04:19 WARNING (MainThread) [homeassistant.components.weather] Updating darksky weather took longer than the scheduled update interval 0:00:30
2021-04-25 13:04:20 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating rpi_power binary_sensor took longer than the scheduled update interval 0:00:30
2021-04-25 13:04:20 WARNING (MainThread) [homeassistant.components.switch] Updating wake_on_lan switch took longer than the scheduled update interval 0:00:30
2021-04-25 13:04:23 WARNING (MainThread) [homeassistant.components.media_player] Updating braviatv media_player took longer than the scheduled update interval 0:00:10
2021-04-25 13:04:24 WARNING (MainThread) [homeassistant.components.sensor] Updating sql sensor took longer than the scheduled update interval 0:00:30
2021-04-25 13:04:24 WARNING (MainThread) [homeassistant.components.sensor] Updating history_stats sensor took longer than the scheduled update interval 0:00:30
2021-04-25 13:04:24 WARNING (MainThread) [homeassistant.components.sensor] Updating filesize sensor took longer than the scheduled update interval 0:00:30
2021-04-25 13:04:24 WARNING (MainThread) [homeassistant.components.sensor] Updating systemmonitor sensor took longer than the scheduled update interval 0:00:30
2021-04-25 13:04:33 WARNING (MainThread) [homeassistant.components.media_player] Updating braviatv media_player took longer than the scheduled update interval 0:00:10
2021-04-25 13:04:43 WARNING (MainThread) [homeassistant.components.media_player] Updating braviatv media_player took longer than the scheduled update interval 0:00:10
2021-04-25 13:04:49 WARNING (MainThread) [homeassistant.components.weather] Updating darksky weather took longer than the scheduled update interval 0:00:30
2021-04-25 13:04:50 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating rpi_power binary_sensor took longer than the scheduled update interval 0:00:30
2021-04-25 13:04:50 WARNING (MainThread) [homeassistant.components.switch] Updating wake_on_lan switch took longer than the scheduled update interval 0:00:30
2021-04-25 13:04:51 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:01:00

The only solution is to go back to 2021-3-4 which works w/o errors.
I´ve tried fresh flash and snapshot recovery to 2021-3-4 and update to 2021-4-6, fresh flash to 2021-4-6, snapshot recovery of add ons - everything working, copying of config files, modifying them iaw breaking changes, deleting db file => everything with the same result :frowning:
I guess that waiting more than 12 hrs as I did several times for the database file of less than 1Gb, during last attempt it was 485Mb, is not normal.
It seems that i am doing something in the wrong way, but not able to identify what.