In the sensor definition, the project_id is not a URL, it should look something like this:
params:
project_id: 2312181948
Great friend, this is the problem. Now, all ok. Thanks crack
1 Like
You just need a reload, probably. Either close the app and reopen it, or reboot your phone.
I think it’s a great card since I’ve been using it. As a newbie to it, and after having done many tests, I can’t find a way to change the size of the text and icons, I say this in case any Guru here could help me. Thanks in advance to everyone.
1 Like
As a work around, you can edit the CSS styles near the end of powertodoist-card.js
But it won’t be upgrade-safe, you’ll have to merge your changes when you install a new version.
I want to make CSS styles more configurable from the configuration files, but I’m not there yet…
1 Like
Hi,
Thanks for this, I have got the card working but show_card_labels: false doesn’t seem to be working as It seems to be ignored. and the labels are still being displayed.
type: custom:powertodoist-card
entity: sensor.alexa_shopping_list
show_header: false
show_completed: 5
use_quick_add: false
filter_today_overdue: false
show_item_add: false
show_item_close: true
show_item_delete: false
show_card_labels: false
Is there anything I have missed?
@Jon_White that option is actually meant to control the card-level labels, not the item-level labels.
I better explain what that means: I figured out that if I create a label filter for a card, so that, for example, it lists only the Urgent tasks, I probably just want to see a label on top, along the card title, saying Urgent, instead of seeing a label with that name in every single item below - not very informative.
The show_card_labels option controls that.
I believe what you’re looking for would be a show_item_labels option, which I don’t currently have! 
As an undocumented work-around, any label name that starts with an underscore character will not be shown in the PowerTodoist UI. So if you call your label _secretLabel it won’t show. I realize this is not an ideal solution for many situations, but might help you work around the problem for now.
EDIT: adding a few things here
- If all your items have Alexa label, try using that as a filter and then play with the
show_card_labelsoption to get your preferred effect
filter_labels:
- "Alexa"
This makes Alexa a card-level label.
- It will be easy for me to add a proper
show_item_labelsoption, and it certainly makes sense to have one. BUT I am on vacation now, I don’t promise anything in the coming two weeks.
1 Like
Did you manage to create it in the meantime? Love your card the best out there! Congratulations
Hi. Thanks for the compliment. 
I’m afraid I didn’t get back to this project yet, I’ve just been too busy with work. But I still intend to do a bit more work on this card after I finish a couple of work projects.
1 Like
New version is out
@Jon_White @HVPereira I just released a new v0.11-beta version with the option requested: show_item_labels (defaults to true).
Now available in HACS
To everyone: I am also announcing that HACS accepted my application (it takes them months) so now you can download my card directly by searching inside HACS, and you can install the card easily from there. It also facilitates upgrades, you get warned and you just need to click to upgrade.
If somebody can please confirm that this works well, I’d appreciate it - I never tried it myself.
Date filtering bugfix
I also fixed a bug breaking date filtering. So @chicknlil25 if you’re still having trouble with dates filtering, please try the new version.
Thanks.
1 Like
Awesome! Thank you.
@kulnis182 your YAML looks correct to me… what is going wrong, do you get error messages?
Did you do the secrets.yaml part?
If you don’t get errors, if it’s just that you don’t see data in the card, my advice during this initial set up phase is to forget about the card and just check that you see data coming into the sensor, but going into **Developer Tools / States ** and filtering for the sensor name (probably to-do-list).
I’ll answer the other one separately…
If you get this warning…
Command-line YAML configuration has moved
then you need to change part of the PowerTodoist configuration.
Before
sensor:
- name: label_colors
platform: command_line
command: !secret todoist_cmd_with_api_token
value_template: >
{{ value_json.label_colors | length }}
json_attributes:
- label_colors
scan_interval: 200
After the corrective changes, this goes outside the sensor section, and into a command-line section:
# --------------------------------------------------------
command_line:
- sensor:
name: label_colors
command: !secret todoist_cmd_with_api_token
value_template: >
{{ value_json.label_colors | length }}
json_attributes:
- label_colors
scan_interval: 200
So you need to do a few things to get this working:
- Cut-and-paste the section from inside a
sensorheading, into a (possibly new)command_linesection - Turn
sensor:into- sensor: - Indent
nameand everything below it a further two spaces.
In general, make sure you pay attention to the indents, they’re critical - Notice that
namelost the dash - Remove the line saying
platform: command_line - Restart Home Assistant
Thanks for quick reply.
Moving command line worked!
Checked the documentation ant yes, command line should be a seperate section, like you just mentioned.
For clarification it worked and before, just got this error/notification that it will not work since the 2023.12
As the developer, I am seeing almost 500 people clicked the link to the repo, but I’m not sure if it’s really being used, and how. I have almost zero feedback.
If anyone wants to tell their story and comment on the card, that would definitely be helpful (and motivational).
I would be especially interested in case people have found other uses besides the basic shopping list or to-do list. If anyone has this more connected to Home Assistant itself, due to the “low-code” features, the ability to distinguish users, etc.
Thanks
Hi there for sure I wanted to use it and also make some feedback, I’m dev too unfortunetly not Python.
I have tried to setup your card but currently I have an error with the rest part and more in detail this :
json_attributes:
- project
- items
- sections
- project_notes
Dev tool complain about things not be a string, I had created an issue in Git.
Thanks for this card, excited about to use it
Enregistreur: homeassistant.config
Source: config.py:1335
S’est produit pour la première fois: 17:25:28 (1 occurrences)
Dernier enregistrement: 17:25:28
Invalid config for ‘sensor’ from integration ‘rest’ at sensors.yaml, line 51: template value should be a string for dictionary value ‘params->json_attributes’, got [‘project’, ‘items’, ‘sections’, ‘project_notes’], please check the docs at RESTful - Home Assistant
Ok, so this is my first time digging into yaml and I’m not a porgram0r as my friends say. I fly jets. Which takes far fewer brain cells. I grabbed yours and the other todoist hacs frontend. I’m using your code in the yaml which seems to differ from the other project only in the order it is in.
When adding both cards, the other one comes up fine (except I really want the ‘today’ list, not a project. However ‘today’ doesn’t have a project ID so for testing I’m using a random project). Your code shows “Sensors don’t have any data yet. Please wait a few seconds and refresh.” It has been saying that for over ten minutes now and I’ve modify the list on todoist to see if it was looking for recent modifications.
Happy to help you delve into what isn’t working right (more than willing to admit it’s me, but what am I doing wrong and how can we prevent others from doing that) and also, how do I show “Today” items since I take from my various projects and grab just what I need done today and don’t give a rats what’s on the project list outside of that?
My dream is creating an HA dakboardish thing, if that matters.