-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot Activate Routine #346
Comments
I will also say that I can still do anything else with the component just fine. |
I am also confirming the issue happens with alexapy 1.0.2 |
having the same thing here |
Thanks. The issue is the cookie may be expired so the next time you restart it'll probably force you to relogin. There may be a bug with the cookie creation in 2.0.1 that I found last night not to mention a login issue for some regions. If you run into that, 1.4.1 should recreate the cookie properly. |
I’m having the same issue, it’s not asking me to re-login. Edit, deleted my pickle, logged back in, same issue |
Ok, I've confirmed the bug. Looking into it. |
Funny, Amazon changed the content-type to |
Thank you, when will this fix be available in hacs? |
There's a bug that stopped the full release. You can see it under beta releases until we fix it for everyone. Issue is you have to delete your .pickle file before starting or it will have an error. The cookie migration code for the 1.x cookie had a bug in it that I want to fix before a full release. |
2.1.2 should resolve. No need to delete pickle. |
Describe the bug
Trying to initiate a routine stopped working after update.
To Reproduce
Steps to reproduce the behavior:
"Call-service API error. Error Message: 0, message='Attempt to decode JSON with unexpected mimetype: text/html'"
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System details
const.py
or HA startup): '2.0.1'pip show alexapy
or HA startup): 1.0.1Logs
Call-service API error. Error Message: 0, message='Attempt to decode JSON with unexpected mimetype: text/html'
Additional context
This automation was previously working fine. Happens when the service is called via node-red or direct from home assistant.
The text was updated successfully, but these errors were encountered: