Shopping_list state attributes are gone with today's HA update

Configuration
1

Hello,

I always used an automation to send the shopping-list items to my phone like described here:

After todays update to HA Core 2023.6.1 I the sensor.shopping_list has only 1 attribute, which contains the number of active items in the list, but not the item names anymore.

Is it possible, to get it working like before?

My configuration.yaml:

# shopping list
command_line:
  - sensor:
      name: "Shopping List"
      unit_of_measurement: "items"

      json_attributes: 
        - name
        - complete

      command: "jq -r '.[] | select(.complete==false) | .name' .shopping_list.json"
2

thanks for posting this as I didn’t notice that it was broken

I managed to fix it (for now) by changing command_line config in yaml to the following:

command_line:
  - sensor:
      command: "jq -r '{complete: [.[] | select(.complete==true) | .name], incomplete: [.[] | select(.complete==false) | .name]}' .shopping_list.json"
      name: shopping_list
      unique_id: shopping_list_sensor
      scan_interval: 15
      json_attributes:
        - complete
        - incomplete
      value_template: "{{ value_json.incomplete | length }}"

and also this has to be deleted from automation as shopping_list sensor now become unavailable whenever I reload command_line integration:

  - service: command_line.reload
    data: {}

hopefully this will work for you as well

1 Like
3

This also brings only the number of items in the shopping_list in the message.

I tried in terminal jq -r '.[] .name' .shopping_list.json and i get listed all the names of the items on my shopping list. But if I use the same command in my .yaml, the message is “9 to buy” instead of “Butter, Milk to buy”.

Can someone explain this to me, please?

4

I am not sure what is the cause of the problem you experience, just wanted to note that this looks fine on my HA instance
shopping_list_sensor

5

Finally I’ve got it to work again after changing the order of the lines in my configuration.yaml
Thank you!

1 Like
6

Is there anyway to create multiple “Shopping Lists” based on the name prefix to use in automations?

For example, if I have items “Giant - Milk” and “Target - Deoderant” and I have each place set up as a location in HA, if I went to Giant it would only return the list of items starting with “Giant”? I think it would be a new json_attribute, but I’m not sure how I’d go about filtering the list down. Any thoughts?

7

Here’s a condition I use with a zone enter trigger around my local shop:

    - condition: and
      conditions:
      - condition: trigger
        id: hill_st
      - condition: template
        value_template: "{{ '### HILL ST ###' in states('sensor.shopping_list_items')}}"

It would be a lot easier if we had multiple lists.

1 Like
8

Is it possible to do this with the new integration with the to-do list?

9

I have not updated yet but I think what I am going to do is have separate todo lists for each shopping zone. The state of the todo list is the number of unchecked items, so the condition should be able to be simplified to something like this:

   - condition: and
      conditions:
      - condition: trigger # zone trigger
        id: hill_st
      - condition: numeric_state
        entity_id: todo.hill_st
        above: 0
10

I apologize for the confusion, but my question was about creating the sensor with items in the attributes for the new TODO list integration.

1 Like
11

I can’t find the file that stores the data for the TODO list. Only the ‘.shopping_list.json’ is visible.

12

Look for a local todo .ics file.

1 Like
13

I’ve already found the files locally in the .storage folder, but I couldn’t find the ones from Google Tasks

14

Google tasks does not have any local storage.

15

I am using Node-RED to filter the data contained in the file to obtain the list of items in this case, I can only use the “local” lists…

Is there any update planned to be able to obtain the data stored in each list? A good option would be to have in each list all entities, the items in the attributes field with both completed and uncompleted. It’s basically what I’m doing through Node-RED.

16

If/when it’s added, it will be a responding service. Just like getting calendar events.

2 Likes
17

It was great to see this implemented as soon as possible.

1 Like
18

Fully agree! Either as attributes or as a service similar to “Calendar.list_events”, but for todo-items.

Currently, it seems there is no way to include for example to-do list items in an email or notification text :frowning:

Really hope a solution will come around!

19

Okay, I have looked for the local to do list but cannot figure out where the data itself is stored. As I understand from the above discussion, there is no solution to this yet right?

20

The data is stored in a ics file in the .storage folder. It’s a file called “local_todo.[your todo list name].ics”. But there isn’t yet a smooth way to extract the attributes, yet.

3 Likes