Hi, you may be aware that Amazon will shut down their List API on July 1st 2024. This is bad as the Echo devices serve as a convenient endpoint to add stuff to all sorts of lists including integrations with Todoist, Bring and therefore HA.
You can use Bring, but you have to relearn yourself to say “ask Bring to add X to the list”. It has a HA integration and is unaffected by the list API deprecation.
We used to use Bring with Google home before they shuttered their lists, but the Bring Alexa skill isn’t available in my country even though I’ve asked them for it many many times. We shifted to anylist.
Trying to convince my partner to say “ask to add X to the shopping list” is going to be near impossible given I can’t even convince them to say “alexa, turn the lights on” using plural “lights” instead of singular “light” because alexa doesn’t recognise the singular word.
In the same boat as many others. We were using the Alexa list API to sync a grocery list into any list so that we had a usable front end. I had plans to display that on a HA dashboard too, but it looks like that’s not going to happen. No way the family will use a new skill that requires the user to evoke an integration first.
Since the API is shut down, it seems it will be impossible to connect HA to the built in Amazon lists. I was starting to look into replacing Alexa as a voice assistant entirely. I really only use them for timers and Spotify now that this is happening.
Amazon’s annoying decisions like this are why I moved away from them for smart home management in the first place.
Great to hear! For the MFA I tinkered a little and it seems that otpauth works without external apps. I went to the 2FA page in the Amazon account and scanned the QR code to retrieve the otpauth URL, then I changed these files:
I was able to run on my end and get the list populated in my HA.
However, every 5 minutes (when the script runs) I receive a text message with the OTP code.
Is there a config that?
Using the method suggested by @emilypeek would cause the same?
If you want to create one-time passwords from an app instead of having them delivered to your phone, clear your two-step verification settings. To do this, tap or click “Disable,” then check the box next to “Also clear two-step verification settings” in the window that appears. Finally, re-enable two-step verification using your authenticator app as your preferred method.
I then have two registered apps one for use though the browser and one for the script
I just have adapted a few things in the automation. It also helps to simplify and get rid of the command line sensor.
You can check if the item is already in the list, directly within the automation like this:
- action: todo.get_items
data:
status: needs_action
target:
entity_id: todo.yourlist
response_variable: todo
- if:
- condition: template
value_template: >
{{trigger.json.name not in todo['todo.yourlist']['items'] |
map(attribute='summary') | list}}