Go to Settings > System > Repairs, click the overflow menu (three vertical dots) and select āIntegration startup timeā.
The list shows all of the integrations that have been loaded (and how long it took to load them). Youāll notice that the list contains far more entries than in Settings > Devices & Services > Integrations.
For example, Automation is an integration, so is Template, Group, Input Boolean, etc. Each has a corresponding web page (like the URL you posted).
My guess is that there was a design decision made to only show integrations (in the Integrations page) where the user has control over their configuration (unlike, for example, the Automation and Template integrations which have no user-configurable options).
Itās not a problem in our systems or in 2023.9, I think itās some weird random network issue somewhere. After recent HA restart the error is gone. But if I restart again, it probably will appear againā¦
IMO if some communication issue happens (as CRC error timeout etc), HA stops querying modbus registers. Itās needed to to call service modbus restart. My previous version was 2023.8.2; it worked well.
Looks like an awesome update. Nothing that couldnāt have been done before but now with a lower barrier. Thatās great. HA is very powerful and increasingly usable but still has a steep learning curve. Making it available to more people is a good thing.
Does the new weather.forecast service poll the underlying provider, or a local cache that is updated on its own provider specific frequency? Iām limited to a maximum number of calls per day to openweathermap.
The entities you create via the Template integration are configurable. The Template integration itself is not configurable (nor is Automation, Input Boolean, etc and the others that arenāt displayed in the Integrations page).
Theyāve been āmissingā ever since the Integrations page was created (i.e. a long time ago); it has the earmarks of being by design rather than oversight.
If you feel strongly about it, post a Feature Request to have all of the loaded integrations listed in the Integrations page.
Check DNSBL (and dnsbl logs) in pfsense - It has a whitelisting capability also. I had enabled it and took awhile to discover what was blocking some updates - /pfblockerng/pfblockerng_dnsbl.php in your pfsense instance.
New climate stuff in the Overview is cool and I can see it on my mini-split. But unfortunately this update no longer sees my Ecobee. Simply āunavailable.ā
The question was not about the template syntax (yours is not correct btw) but where to put it in the helper. The answer is that the helper is a simple version of the sensor template integration and does not support templating the icon.
In the example you posted above, one (or both) of the if statements lacks a terminating endif. Do unterminated if statements work in custom:mushroom-template-card?