I've noticed that this keeps happening and if we can just get a toggle to remove logging for this app since we cannot directly modify the app code (I assume). It's hogging the log entries and is unappealing to see unfortunately. Not a gripe, just wondering if there can be a way to just not see the alexa skill app not log.
Error making Call to Alexa message gateway: {"header":{"namespace":"System","name":"Exception","messageId":"ASRLS_40566cc9-1d7b-43dc-a808-4017922d8dd6_1737560491598.0..ASRLS_40566cc9-1d7b-43dc-a808-4017922d8dd6_1737560491598"},"payload":{"code":"INVALID_REQUEST_EXCEPTION","description":"Cannot read the request payload as: Cannot construct instance of com.amazon.iota.driver.v3.StateReportProperty, problem: value\n at [Source: UNKNOWN; line: -1, column: -1] (through reference chain: com.amazon.iota.driver.directive.v3.MessageEnvelope$V3Builder["context"]->com.amazon.iota.driver.directive.v3.Context["properties"]->com.amazon.iota.driver.v3.StateReportPropertyArray[2])"}}
I've looked at everyone else post about this to no avail, other than a firewall (something about whitelisting)?
I typically only see Alexa integration errors when the HE hub is unable to connect to the internet. For me, this happens when I perform maintenance on my home network or when my ISP connection is down. Otherwise, these Alexa errors rarely occur.
Thanks for the response. It seems to be persistent at the tune of 5 minutes per request. I've noticed you and a few people (other searches about this issue) mention the "connection to internet" part. I'm under the assumption that with my ethernet cord into the hubitat to the router that I am LAN, as far as the internet connection you've mentioned, I do have access to my cloud dashboards, if that helps. I am NOT using the hubitat on WLAN.
tl;dr This reply belongs in another category, namely Echo Speaks app.
Surely I can't be the only one still getting these blasted "Error making Call to Alexa message gateway" errors for the Amazon Echo Skill app in Logs? Happening daily. Not sure of the cause nor any potential things to check.
Sounds like your Internet connection might be having intermittent issues. Could be your ISP, modem, or router? Just a hypothesis. Could also be on Amazaon’s side, but probably not if occurring daily.
Do you have any automatic reboots configured for your router? Or any other network equipment?
Nope, no resets or WAN outages of any kind. Judging from Logs (not shown here ... yet), I'm thinking these entries somehow coincide with Alexa routines running. Will dive deeper tomorrow and report back. Thx.
I've traced this Error message to the built-in Alexa Skill app, which was already clear from Logs. BUT... it's being generated in response to a VoiceCmdAsText() action in Rule Machine. This eliminates my earlier theory of being associated with an Alexa Routine (yes, a routine was running, but all it does is turn On a switch, which triggers RM5.1).
I wonder if anyone else is using that Custom Action in RM?? And, if so, whether any subset of those users happen to be commanding an Echo Spot to "Turn off the screen" as I'm doing. I'm the king of edge cases.
Sounds like you’re using the custom Echo Speaks integration, correct?
If so, this has nothing to do with the Built-In Hubitat Amazon Echo App and associated Hubitat Skill for Alexa. There is no VoiceCmdAsText() command using the built-in Alexa integration.
Was thinking the same here. I didn't dive deeply enough into that rule to see what was being called, but Echo Speaks makes 100% sense. (I need to revisit how its child devices are set up.) That also leaves me dissecting what's going on under the hood in Echo Speaks ... where this sub-thread obviously belongs.
