Amazon Echo Skill - Error making Call to Alexa message gateway: null

I have found a few posts regarding this error from numerous past years, but no one seems to have posted a solution. I did not notice when this started. I discovered it when trying to add a new device to Alexa. Alexa never got it. All my existing device integrations between HE and Alexa work for voice commands and routines but nothing new can be added and nothing old can be deleted from Echo.

These errors seem to be happening every time an Alexa command is given which involves HE devices. They then happen multiple times. Then it is quiet until the next command.

Does anyone have a solution to this?

LJ

If youโ€™re not on hub firmware 2.3.9.184, reboot your hub then update, as suggested here:

2 Likes

I was getting it the other day and it was some sort of internet connection issue. All devices were having internet issues. Ended up rebooting router, modem and hub and it all started working again.

2 Likes

Same.

2 Likes

I am on 188.

I rebooted the Hub. No luck. I can't reboot the router right now since two of us work from home. Can't bring down the network until my girlfriend is asleep. WAF is important. I will get back after trying that overnight. Thanks for the responses.

LJ

So I tried your simple fix and I had no luck. So I started digging a bit more into my firewall rules and my Piholes and ultimately identified the culprit. Apparently in some recent update to one of my block lists on pihole the domain โ€œapi.Amazonalexa.comโ€ was put on the list to be blocked. I whitelised it and all is working fine now. It looks like this was not related to general internet connectivity issues from earlier.

Thanks for all your help, as always,

LJ

3 Likes

My main blocklist I use is OSID Basic https://oisd.nl/
My whitelist is very short, most things work fine with that list.

Also using the Anudeep whitelist: GitHub - anudeepND/whitelist: A simple tool to add commonly white listed domains to your Pi-Hole setup.

Using AdguardHome instead of Pihole but works about the same.

Thanks for sharing those. I will take a look at them. I have not had problems with the ones I am using, but I can always improve things. I only have four whitelisted sites right now.

LJ

Also noticed that api.amazonalexa.com was getting hit by the blocklist.

When asking Alexa to turn off / on devices, it would perform the action successfully, and then after a few seconds would say "Sorry, that device isn't responding right now"

Whitelisting that URL to see if that resolves it.