Amazon Echo to Raspberry Pi

Question

How can we direct an Amazon Echo target to a private / internal https endpoint? Like raspberry pi running nodeJS.

• Using "Echo Proxy" still requires a service from the Internet (More on Echo Proxy: https://www.reddit.com/r/amazonecho/comments/3blkax/alexa_api_proxy_java/ )
• Using "HUE Bridge Emulator" will help you unlock Alexa request to a private (internal) https server. However, this setting restricts the use of Alexa intentions to “Enable” or “Disable” (and set a dim level, etc.). (More on the HUE Bridge emulator: https://github.com/armzilla/amazon-echo-ha-bridge )

I would like to hear feedback on how we can solve this problem.

EDIT: I now have a stable working setup for my Pi controlled by Amazon Echo. And here is how it is configured:

• Configure AWS Lambda to handle incoming calls from Echo
• On Lambda, draw an "ACEY KEYWORD" for each intent / slot
• In the corresponding concept / slot, send ACEY KEYWORD to PubNub
• Configuring my Pi for SUBSCRIBE for PubNub for new posts
• If Pi receives the corresponding ACTION KEYWORD channel on the channel, it calls the / script function
• This / script function in turn has full execution logic (example: Open the garage door)

I would like to hear feedback on this method and leave the question open to others in order to post an easier / better way to achieve this.