2023.9: New climate entity dialogs, lots of tile features, and template sensors from the UI!

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).

i have the exact same error as you, have you resolved it?

Yep it is. Depending on the error (500 on GitHub = ratelimit) it will be auto fixed sooner or later with a restart.

1 Like

a restart of what ? :slight_smile:

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ā€¦

1 Like

seems indeed lots of users are reporting it on github now, ok no worry then :slight_smile:

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.

Hmmā€¦i see, but I donā€™t agree about the configuration; they are configurable:


My guess is that it is curently missing, and will (hopefully) come later :stuck_out_tongue:

Ahā€¦I just found outā€¦they are also mentioned under helpers, and can also be added there :smiley:

I was doing it under intergrations :thinking:

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.

Home Assistant. Just wait an hour

1 Like


Humidity card not working for ecobee integration. The humidity % is missing.

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.

2 Likes

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.

Use the modern format for template sensors and use icon.

Edit: Just realised you are probably talking about in the GUI.

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.ā€

Try with

mdi
{% else %} 
{% if (is_state xxxxxx
mdi
{% else %}
{% if (is_state xxxxxx
mdi
{% endif %}

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.

OK, my bad totally misunderstood the question then, however, the syntax works for me, thou in custom:mushroom-template-card (could be the reason)

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?

Or did that example simply contain a mistake?