IMHO Add-on (including HACS) usage statistics also very interesting/valuable.
HACS is not an add-on.
Isn’t that a pedantic comment?
I believe the post was about being able to see HACS add-ons in the Analytic data which would be good.
But I may be wrong about Masterzz post, either way (even though you are correct) I don’t perceive your comment as positive.
1 Like
1 Like
It’s really important to call things by their real names though! Add-ons and integrations are/do completely different things.
There are no HACS add-ons either, these are (custom) integrations.
Have a look at the open feature request ;-).
Add statistics for custom integrations on Home Assistant Analytics - Feature Requests - Home Assistant Community (home-assistant.io)
1 Like
Fair comment
Thanks
New messages - it is fine, BUT…
- there is no pointer to - which input_boolean, which template…
How do I guess template names ?
HELP.
2021-04-13 18:18:54 WARNING (MainThread) [homeassistant.setup] Setup of input_boolean is taking over 10 seconds.
2021-04-13 18:19:34 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'linkquality' when rendering '{{ value_json.linkquality }}'
2021-04-13 18:19:34 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'linkquality' when rendering '{{ value_json.linkquality }}'
2021-04-13 18:19:34 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'linkquality' when rendering '{{ value_json.linkquality }}'
2021-04-13 18:19:34 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'battery_low' when rendering '{{ value_json.battery_low }}'
2021-04-13 18:19:34 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'tamper' when rendering '{{ value_json.tamper }}'
Search your config for the template that’s listed…
I mean, custom-components (may be wrongly named 'add-on’s by me), installed by HACS.
Searched for ‘value_json.tamper’ & ‘value_json.linkquality’ in ‘config’ directory & subdirs …
ONLY matches in
- home-assistant.log;
- various zigbee2mqtt log files.
Anyway IMHO would be nice to have warning/error message name of parent object (let say so) - quite useful information.
P.S.
Pls point me - how to find input_boolean, which set up is too long ?
2021-04-13 18:18:54 WARNING (MainThread) [homeassistant.setup] Setup of input_boolean is taking over 10 seconds.
Then that’s where your template is, inside MQTT. So adjust the discovery template coming from zigbee2mqtt or write up an issue against zigbee2mqtt.
That’s all input_booleans. I.e. the input_boolean section.
1 Like
Got it. Is any way to find out - which exactly input_boolean(s) taking most a time ?
The whole section is, not sure how else to explain it to you. I’ts not 1 input boolean that’s causing the problem. Anyways, it’s a wrning, you can ignore it.
just experienced the new trigger based templates can not be configured in a package, hasn’t anyone else here noticed this? I can only validate the config when these are in the configuration.yaml.
Hey! For people who have problems with Xiaomi Air Purifiers after this upgrade, I have noticed two things:
- After importing into the UI on upgrade, fans had a different name, with suffix _2. I needed to rename (or remove) old ones and change names to original ones.
- It seems there is a problem with the AQI attribute (it’s null), so any automation that uses it will not work properly.
That seems to be what the docs say.
Well, I must ask you where you read that, because I don’t see any mentioning the trigger based template sensors can not be configured in a package. Frankly, it would be very surprising if it were the case, because anything else can be…
forgot to mention I filed an issue in this in the Core repo
There’s a section at the bottom that mentions this is only available at the root level and reloading doesn’t work
1 Like