Skip to content
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

Closed
mikenabhan opened this issue Sep 6, 2019 · 10 comments · Fixed by #348
Closed

Cannot Activate Routine #346

mikenabhan opened this issue Sep 6, 2019 · 10 comments · Fixed by #348
Assignees
Labels
alexapy Issue relates to the API bug Something isn't working

Comments

@mikenabhan
Copy link

Describe the bug
Trying to initiate a routine stopped working after update.

To Reproduce
Steps to reproduce the behavior:

  1. Go to developer tools
  2. Click on dervices
  3. Enter data
  4. See error
    "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.
image

System details

  • Home-assistant (version): 0.98.4
  • Hassio (Yes/No): yes
  • alexa_media (version from const.py or HA startup): '2.0.1'
  • alexapy (version from pip show alexapy or HA startup): 1.0.1

Logs
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.

@mikenabhan
Copy link
Author

I will also say that I can still do anything else with the component just fine.

@mikenabhan
Copy link
Author

I am also confirming the issue happens with alexapy 1.0.2

@drzuki
Copy link

drzuki commented Sep 6, 2019

having the same thing here

@alandtse
Copy link
Owner

alandtse commented Sep 6, 2019

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.

@broyuken
Copy link

broyuken commented Sep 7, 2019

I’m having the same issue, it’s not asking me to re-login.

Edit, deleted my pickle, logged back in, same issue

@alandtse alandtse self-assigned this Sep 7, 2019
@alandtse alandtse added alexapy Issue relates to the API bug Something isn't working labels Sep 7, 2019
@alandtse
Copy link
Owner

alandtse commented Sep 7, 2019

Ok, I've confirmed the bug. Looking into it.

@alandtse
Copy link
Owner

alandtse commented Sep 7, 2019

Funny, Amazon changed the content-type to text/html from application/json on the automation page. Ok I should be able to work around it.

@alandtse alandtse mentioned this issue Sep 8, 2019
alandtse added a commit that referenced this issue Sep 8, 2019
@alandtse alandtse mentioned this issue Sep 8, 2019
@broyuken
Copy link

broyuken commented Sep 8, 2019

Thank you, when will this fix be available in hacs?

@alandtse
Copy link
Owner

alandtse commented Sep 8, 2019

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.

alandtse added a commit that referenced this issue Sep 8, 2019
@alandtse
Copy link
Owner

alandtse commented Sep 8, 2019

2.1.2 should resolve. No need to delete pickle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alexapy Issue relates to the API bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants