Billy Ferguson

As for the docker stuff, thanks so much for clarifying. I didn't know if you went the docker route or the manually swapping out the python packages like @digiltd did....

The post I was talking about originally was #232, which moved us over to #220 which @Bronskiy is the person I said was from Eastern Europe, he's actually from Russia.

Is anyone still following this issue? I think I have a fix for this that I wanna try tommorrow. It revolves around using a docker container to `zappa deploy` instead...

Added the owner of the household to the developer account for my Alexa Skill for Gee Music. Will post results tonight.

Figured it out. If you are in an Amazon household with another Alexa user you must be the registered user for the device. For example, if the two email addresses...

Yeah. It ONLY works when the owner of the household is the developer account that geemusic is setup on.

Possibly related: https://forums.developer.amazon.com/questions/78973/skill-on-firetv-throws-invalid-directive-audioplay.html

Sample message from [The Alexa Docs](https://developer.amazon.com/docs/alexa-voice-service/audioplayer.html#play) ``` { "directive": { "header": { "namespace": "AudioPlayer", "name": "Play", "messageId": "{{STRING}}", "dialogRequestId": "{{STRING}}" }, "payload": { "playBehavior": "{{STRING}}", "audioItem": { "audioItemId": "{{STRING}}", "stream":...

It seems we don't split into header/payload. We don't have any of the header information it seems. More reading in the doc link provided above though seems to think that...

Hey @phreakmonkey could you try the @aplocher PR and see if that fixes this issue for you.