Problem getin Alexa work with intents

Configuration
21

yes still 405 not allowed

22

Sorry I am out of ideas hereā€¦there must be something that I am not thinking of right nowā€¦just donā€™t know what. Just double check all your settings in the amazon development consoleā€¦maybe even try starting from scratch with a new skill on alexa?

Sorry for not being of much help.

~Cheers

23

is there a way to lacily test if hass Alexa component is working correct? Like for lights or media player where i can add a json object for testing.

24

Maybe you have an unsupported Key in your API-Password. I had the same Problem, with a # in my Password. Changing my Password to contain only Letters and Numbers solved it.

Head over hear for more information:

1 Like
25

the api password is the same i use to login to hass Gui correct?

26

Yes, you also provide it in the Link on the Amazon Developer Console.

27

ok got it now, the response came after i made port redirect from 443 to hass port. So problem was that the url uses a port. Thats a problem because i also have other website on the same server that want to use https and not only hass.

Any idea how to use url like https://my.url.com:8123/api/alex?api_password=XXXXXXX

28

He,

this is not possible. Amazon only allow using Port 443.

Just as documented here in the Requirments Section:

https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/developing-an-alexa-skill-as-a-web-service#requirements-for-your-web-service

1 Like
29

I donā€™t think this is possible with amazon. But you should be able to use a reverse proxy like nginx to map different locations.

~Cheers

30

ok thanks for the help, extra thanks to @PhyberApex :slight_smile:

I will try with that at the moment

1 Like
31

Completely OT, but @PhyberApex - TIL that English was your second language. Never would have guessed. Iā€™m so disappointed with my country; it seems like everyone I meet outside it speaks multiple languages and most Americans canā€™t even speak their own language well enough.

1 Like
32

@rpitera You are now officially known as OT-King. But thank you for your kind words. My English skills probably originate from the amount of anime I watched as a kid (and still do) and the fact that I watch all movies (and tv shows) in their original audio if possible (I donā€™t even have my tv plugged into cable at this point). Also I am a software engineer so English is a must.

~Cheers

33

Iā€™m sorry. I should have PMā€™d you but I wanted to complement you in the clear. :wink:

1 Like
34

Iā€™m having the same issue, but only with certain intents. Simple ones, like this:

SpeakIntent:
  speech:
    type: plaintext
    text: This is magic

ā€¦work fine and get a ā€œgoodā€ response back from Amazon:

{
  "version": "1.0",
  "response": {
    "outputSpeech": {
      "type": "PlainText",
      "text": "This is magic"
    },
    "speechletResponse": {
      "outputSpeech": {
        "text": "This is magic"
      },
      "shouldEndSession": true
    }
  },
  "sessionAttributes": {}
}

However, more difficult ones ā€“ like situations where long-running scenes are in play ā€“ will ā€œworkā€ (in that they do the correct action in our home), but Amazon will give me an error. For example, this intent:

ActivateSceneIntent:
  action:
    service: scene.turn_on
    data_template:
      entity_id: scene.{{ Scene | replace(" ", "_") }}
  speech:
    type: plaintext
    text: !include alexa-confirmations.yaml

ā€¦has the aforementioned wonky behavior when I run my ā€œGood Nightā€ scene:

name: Good Night
entities:
  alarm_control_panel.simplisafe:
    state: armed_home
  cover.garage_door:
    state: closed
  lock.front_door_locked:
    state: locked
  lock.garage_door_locked:
    state: locked
  group.living_room_lights:
    state: off
  group.living_room_tv:
    state: off

ā€¦which returns this Amazon response:

The remote endpoint could not be called, or the response it returned was invalid.

My gut tells me that since the ā€œeasierā€ one works, thereā€™s some sort of timeout going on.

35

Do other scenes work? Do any of your scenes work? How about a simple scene where a single light is turned on?

This may help rule some things out.

36

Great question ā€“ yes, other scenes work (i.e., the action is performed and Amazon returns the correct response). For instance, this scene works as expected:

scene:
  name: Watch Plex
  entities:
    switch.media_center:
      state: on
    remote.watch_roku:
      state: on
    script.switch_roku_to_plex:
      state: on

switch:
  platform: wake_on_lan
  mac_address: "4C:AE:6A:1234: :90:D4"
  name: "Media Center"
  host: "media-center.lan"

remote:
  platform: harmony
  name: Watch Roku
  host: harmony-hub.phil.lan
  activity: 22580034

script:
  switch_roku_to_plex:
  sequence:
    - service: 'media_player.select_source'
      data:
        entity_id: 'media_player.roku_yp005n794105'
        source: 'Plex'
37

Iā€™m kinda stumped then - your code looks fine to me. Iā€™m guessing it is more in the config of the connection somehow.

38

What do you mean by ā€œI made port redirect from 443 to hass portā€?
What all did you change?
Did you change the url to amazon to be https://myurl.com:443ā€¦ , then foward 443 to 8123 in your router?
or did you leave the url as httpsL//my.url.com:8123ā€¦ and forward 443 to 8123 in your router?

Iā€™m having a very similar issue I think.

39

Hey, @Paul_Kline. Did you ever get your issue figured out? I have the same issue.