Thanks a lot for the creation of the fork and driving this integration further!
Just installed 0.6.0: The data model for device / entieties looks now much leaner. The GT-Icon is visible at Integrations view as well as in the list of devices.
Regarding subtasks: Very nice, with lovelace card beta version v1.5-alpha those subtasks show up.
Probably a future feature of an option at configuration level for the card could switch on/off subtasks.
I am using a conditional card to show a custom:gtasks-card to my dashboard when there is a task due. For this i make use of binary_sensor.gtasks_xyz switching from off to on.
Unfortunately this status changes from off to on when a task becomes overdue only, but if a task becomes due it still remains off. Is this the correct behavior of that sensor?
I can’t get this working, am new to Google tasks. Created the OAuth credentials and placed the JSON in the gtasks folder, that all works.
Try to add the integration, click the link to get the auth code between ‘code=’ and ‘&scope=’, but it comes back ‘unknown error ocurred’.
Have tried uninstalling and reinstalling the integration via HACS, restarting HA and creating a new OAuth credential, all to no avail. What should I do?
@brettfk is there anything that shows up in the logs when you get the error? If you can post anything from the logs I may be able to help better.
Deleting the ‘token.pickle’ file maybe be necessary to do a proper uninstall and reinstall if you set your directory to somewhere that would not have been uninstalled.
Looks like I never created a version after I pushed the fix. I’ve released 0.6.1 now. Let me know if that fixes things. You might need to delete all the excess devices.
Every time I try to configure this I get “unknown error occurred” we are supposed to copy between not including the code= and &scope not include them correct? Using version 0.6.1. Any advise would be appreciated.
You are correct that code= and &scope are not included. A few people seem to be having these issues. Can you see anything in the logs? I suspect it is likely a Google API issue usually and that is where I would first go double checking everything.
This is a bit beyond the scope of my knowledge and this topic. You can achieve this with jinja templating which is separate to anything this integration does.
However, here is my crack at it
{% for attr in state_attr('sensor.gtasks_google_tasks', 'tasks') -%}
{% if "due_date" in attr and attr.due_date == states('sensor.date') -%}
{{ attr.task_title }} {{ attr.due_date }} {{"\r\n"}}
{%- endif %}
{%- endfor %}