This is not related to Ping.
or to removing YAML functionality. 
After installing 2023.12 i noticed an annoying behavior with the Themostat card.
When I scroll through a dashboard on my phone, I accidently keep adjusting the target temperature of any Thermostat card that is visible, when I frantically scroll.
I have never done that previously.
Has anyone else seen the same?
Maybe the area on the screen where the card registers interaction has been increased?
Hi,
Does it take some time? I’ve waited an hour, but the new sensor is starting from zero and (probably of course) the old sensor isn’t udpated.
I’m talking about the “monitor individual devices”-part:
Best thing to do is open a new topic with details of your problem.
Unfortunately, not.
The message I’m getting is:
Failed to call service script/shopping_list. Error rendering data template: TypeError: 'builtin_function_or_method' object is not iterable
I think ‘items’ is a bad key name.
Edit: My Script is as follows:
alias: Notify - Shopping List
sequence:
- service: todo.get_items
data:
status:
- needs_action
response_variable: mylist
target:
entity_id: todo.shopping_list
enabled: true
- service: notify.notsobadger_s_phone
data:
title: Shopping List
message: >-
{% set todos = mylist.items %}{% for singletodo in todos %}{{
singletodo.summary }}{% endfor %}
mode: single
icon: mdi:cart
Yea, i’m also out of luck.
Have anyone succes with the todo.get_items
I want to get a list of tasks to display on a epaper display.
alias: "!Test todo"
description: ""
trigger: []
condition: []
action:
- service: todo.get_items
target:
entity_id: todo.my_tasks
data:
status: needs_action
response_variable: agenda
- service: notify.michael_2
data:
title: Daily agenda for {{ now().date() }}
message: >-
Your agenda for today: <p> </p>
{% for itmes in "agenda.todo.my_tasks" %} {{ itmes }} {{itmes.summary}}
<br> {% endfor %}
mode: single
Done, hope it was the right way to do it:
It’s great that history graph is now showing long time statistics (I have to admit that I didn’t even know that HA is storing data to LTS by itself), I don’t think I need grafana anymore. But does that mean I don’t need influxdb either anymore, and MariaDB is enough? And I could just remove the current setting of purge_keep_days: 30 from Recorder?
Currently I have quite a list of entities that I include to influxdb so that it keeps my database better under control, so should I just check which entities LTS have already and only keep those that it doesn’t have? And if there are few sensors that are not included to LTS, then I guess I could add them somehow and then get rid of influxdb?
I noticed that although someone said LTS has been around since 2021, my temperature data etc is showing from 2nd of October 2022 forward only, although I know I have had those sensors a lot longer than that. I don’t remember anymore, but maybe I have had to reinstall Home Assistant completely at that point and that’s why I don’t have even older sensor data available anymore?
My goodness, I just want to say such a BIG thank you to karwosts · GitHub and the History stats feature. I know a lot of people will be ditching Grafana just because of this and for a quick look at the history - without creating statistics graphs cards is just amazing. Very good idea, very well executed, and from the bottom of my heart, thank you <3
Well while checking my test system that’s running for 6 months, i do see i have not even put recorder: in the config… i just noticed, but my DB is already huge…
But still my DB is compared to my original system 250MB, so this is from around 6 months, what means it will be 1GB in 2 years.
How is that possible?
Do i need to add purge_keep_days: 10 and recorder: or leave it default as the db is big now.
On my main i use MariaDB and its really fast, there i record unlimited data and i can compare my data from last year with today in an entity card in 2 seconds, so for my main i do not see a reason to start purging anytime soon, as i need the changes within 15 minutes instead of hour.
But i must say LTS doesn’t use any data at all, i did do the same thing with google sheets for all my temperature sensors recording every change, its on 12mb for a year, and import it into grafana in no time
regards
You have default_config: which includes the recorder integration. It has the default purge keep days of 10 days.
1GB is not huge.
this! a big step backwards in usability :-/
Okay, rolling back. Losing my history sux bigtime :-(.
You have a typo on the word items not sure if that will get it working.
Can you let me know if you do as i want to do this later as well.
Sorry, I tried that, the result:
Your agenda for today: <br>
a
<br> g
<br> e
<br> n
<br> d
<br> a
<br> .
<br> t
<br> o
<br> d
<br> o
<br> .
<br> m
<br> y
<br> _
<br> t
<br> a
<br> s
<br> k
<br> s
it has been fixed:
- service: todo.get_items
target:
entity_id: todo.hass_ideas
response_variable: mylist
- service: system_log.write
data:
message: >
{%- for item in mylist['todo.hass_ideas']['items'] %}
{{ item.summary }}
{%- endfor %}
I am not extremely excited about the thermostat card either. Although it looks good the main number showing is the target where it’s more important to see the actual temperature what most if not all thermostats do. It’s quite annoying to look at the target where the actual temp is small below.
EDIT: I played around a bit but there are no options to change it. I rolled back because looking at target settings on my mobile doesn’t suit me. I know I will caught up some day and I have to upgrade. Until that time I hope this will be changed or selectable in the settings of the card.
Before (great and clear):
After (messy):
And in case of a full screen before:
Actual temperature large in the middle. Target small below.
agree with Ih8rain2, having the target in large font and the current temp very small is very inconvenient, at least offer the option to switch both on the card
2023.12.0
What happened to HACS, getting an error telling me that 2023.12.0 is not supported:
While I greatly appreciate all the work that is put in to HA, how can you really defend the change with “The old card has been removed. The new design is much nicer IMO.”: it is far less functional and has now removed the ability to do what the old card did. Loss of the critical functionality of easily doing one of the primary tasks that has to be done with an air conditioner, being able to turn it on or off. Due to a regular update now people are going to go and have to work out how to build custom functionality to get back what they already had before what is usually a routine update with no breaking interface changes?
If I have missed some shortcut for how to use the interface to turn it on or off, I’ll be happy to learn the new way (without going into the properties of the card), but if it’s there it’s not obvious.
ok thanks Tom for the clarification
