Web service seems to be having issues

Question

Web service seems to be having issues

DragRedSim opened this issue 3 years ago · 10 comments

I've been having some issues lately with this package. When speaking to Alexa, there are no commands being sent to the IR blaster device, as shown by the serial output not updating when it should be recieving requests. To help debug this, I attempted to set up a new "other" device with a single command calling to a server I control, to log the request; but the new device isn't showing up in the Alexa app either. Updates to some older devices (changing the name displayed in the Alexa app) also aren't working (the old names still show up). Web requests still work from the local network, as expected, and are blocked from outside (calling the hostname returns HMAC failure); there seems to be a breakdown between the PythonAnywhere service and the Alexa service.

Answer 1 · 2022-04-02T14:53:33.000Z

Try now, seems like there was a backend problem with the lambda instance

Answer 2 · 2022-04-03T04:26:41.000Z

Just tried it again, same results or lack thereof.

Answer 3 · 2022-04-03T08:52:56.000Z

Try logging in and out if the skill. Also you need to rerun device discovery for any changes to take effect regarding device additions or renaming

Answer 4 · 2022-04-03T11:36:11.000Z

Actually looks like they changed around how some of the AWS policy definitions work and there might have been residual issues if you were in the EU or on US-West servers, try now

Answer 5 · 2022-04-04T08:43:17.000Z

Disabled and re-enabled the skill, and things are working now. Thanks for looking into it!

Answer 6 · 2022-04-27T10:43:13.000Z

There seems to be an issue with activating scenes at the moment; commands aren’t being issued when activating them in a routine. The input commands are fine for manual activation, however if a scene is programmed then that will not be called.

Answer 7 · 2022-04-27T11:46:33.000Z

Do scenes work individually? IE not part of a routine?

Based on your comment I would suspect that to be the case but just want to confirm

From the API/programming standpoint, there's no difference between routines and manual activation, and the script cannot tell the difference (its transparent as far as the API call goes) so if it's working individually but not in a routine it might be a problem with the routine itself but it's not something I can address or adjust

Answer 8 · 2022-04-28T11:35:42.000Z

Scenes do not work on their own. When activating a scene by name, eg. “Alexa, turn on Test Scene”, the response is “Test Scene doesn’t support that.” The target of said scene is the same URL as my other commands, just with no parameters in the URL, eg. “http://example.com:port/msg”. What I meant by the input commands working; I have a scene set up to send the IR blaster the commands to change the TV input for example, and that doesn’t work; but if I say “Alexa, set TV to HDMI 2”, that does work; both the scene and the input controller on the TV object on the site point to the same URL. However, I can’t add multiple calls to multiple input controllers into a routine, since it uses the natural language processing, and I can only add one customised action to a routine.

Answer 9 · 2022-04-28T14:33:16.000Z

Looks like Amazon broke version 1.0 SceneController support, migrated to version 3.0 which fixes things

You'll need to go to the pythonanywhere interface and hit "Update Device" to have it migrate to 3.0 and then re-discover devices

Answer 10 · 2022-05-02T14:39:27.000Z

Yep, all working now. Thanks!