Cool, then you don’t need a “flashing” Alarm template 
1 Like
Question.
The new release suddenly starts reporting these two errors.
2024-01-03 22:34:09.038 ERROR (MainThread) [homeassistant.helpers.template] Template variable error: 'value_json' is undefined when rendering '{{ value_json.state }}'
2024-01-03 22:34:09.041 ERROR (MainThread) [homeassistant.helpers.template] Error parsing value: 'value_json' is undefined (value: online, template: {{ value_json.state }})
So the first thing I thought was - let me search for value_json.state in my YAML.
Guess what. It is nowhere to be found. And it is not in the .json files either.
I tried to set the logger level for homeassistant.helpers.template to debug but that does not help.
Does anyone else have these errors in the log?
And any idea how to debug it?
Love the dedication from the teams to all the new stuff that makes Home Assistant easier to use for newbies. Greatly appreciated! 
1 Like
Try searching “from_json”, “to_json”.
Any templates with device_class_power or state_class_measurement ?
EDIT: Never mind, Was just warnings, deprecated, end-of-life 2025.1
It’s an issue with zigbee2mqtt:
If you don’t actually use it you can disable the setting legacy_availability_payload. Or put up with it until there’s a zigbee2mqtt update.
It doesn’t actually break anything.
2 Likes
Super. Thanks.
Bit off topic for this release as its a custom component with the issue, but try this alt to the one you are using as the one you reference seems no longer maintained
Hi, i can’t swap between setpoint and current temperature in thermostat card.
can you explain how to do it?
thank you
3 Likes
Write that issue up on HA as well. There should only be a warning in the logs, not that error. We found many of these in beta and patches were made to simply warn in the logs but the entity should have still been created.
Another zigbee2mqtt related thing.
The new release starts warning against attributes in selects defined by mqtt discovery as being too large in size and will not be recorded.
I cannot imagine why anyone would want to log these selects at all. Or why these entries have so many attributes.
To get rid of that warning (and make your logs a little smaller) you can add this to configuration.yaml
recorder:
exclude:
entities:
- select.zigbee2mqtt_bridge_log_level
- switch.zigbee2mqtt_bridge_permit_join
- sensor.zigbee2mqtt_bridge_permit_join_timeout
- sensor.zigbee2mqtt_bridge_version
There are some nice threads on this forum about how to limit the log sizes. If you do not already do this search for the topics (there are several topics)
3 Likes
Possible bug with the new thermostat update:
After updating to 2024.1.0, my Hot Tub thermostat card defaulted itself to minimum temp setpoint and appears to have actually sent that request. Not a huge deal for me but might be a major issue for someone using that card for their home temp and doesn’t notice quickly.
2 Likes
Check your secrets file.
It is normal & has not been changed for a few months.
Are you using anything that affects HA loading? Like lovelace_gen, dwains theme, homekit theme?
None of what you mentioned…
Btw, I have several “secrets” files - 1 main & some amount inside packages. I hope secrets in packages are still supported??? There is nothing about secrets in release log.
I just started updating using the homeassistant.local on my laptop, it loaded for a bit then reloaded the page and now the page won’t load at all with error code 500 Internal Server Error, i’m running ha on a raspberry pi and i’ve tried restarting the pi but with no success. How can i fix this??
They aren’t going away. Are you sure there’s not an error in one of your secrets in your packages that’s sat idle? Maybe an accidental -? search all your secrets files and make sure they are dictionaries. If they all are, write up an issue.
I love the small change to the Thermostat card! However, if you use that option and the thermostat is off, the card does not show the current temp in the room. I’d really like it to keep showing the current temp largely in the middle! I hope it’s just me and I can fix it, but it might be a wider issue.
