After latest update I am seeing some warnings in the log during startup. I think most are related to things that haven’t fully initialized, but I am wondering if there is something I should be doing differently. My log has crazy numbers of similar warnings from all the Z-Wave things that aren’t ye…

Have a read of this: [image] Updating Templates with the new default values in 2021.10.x Configuration I keep seeing the same question about the new default argument for the templating. This post will cover all possible ways to define default. All the method…

Ok, but SHOULD this be done? Like I don’t even know what a reasonable default would be when the input data is invalid or missing. Its complaining about most of these things when the inputs are still being initialized by other things like Z-Wave, MQTT, etc. And to the other point, is there a way t…

[image] mmiller7: Ok, but SHOULD this be done? Yes, otherwise home assistant would not be warning you. [image] mmiller7: I don’t even know what a reasonable default would be Previously it would return 0, so you could copy that and use 0 as the default. Or a better choice would be none …

Can the default be another template? Looks like many of my cases where it complains it looks like I already wrapped in an if-check so “if the sensor is unavailable or out of range, return the previous value known” else “return a computed value”

Some warnings after update...what to improve?

Configuration

anon11644107 October 30, 2021, 2:51pm 2

Have a read of this: