Errors in the log from Amazon Echo Skill since updating to 2.2.4.x

[aaiyar]

@bcopeland

These errors have started showing up in the log. They are from the Amazon Echo Skill, and only started after updating to 2.2.4. There's no correlation between using the Echo for a voice command and the errors appearing.

Here's how I have the skill configured. The configuration hasn't changed since updating to 2.2.4.

[bcopeland]

This has been address already and the fix is in the next hot fix release.. Thanks for reporting it.

[aaiyar]

Sorry - didn’t know that! Or check before posting!!

[pomonabill220]

I have done a moderate amount of searching for my errors, but have come up empty handed.
first, I have 5 ecobee 4's with Alexa and they all seem to be functioning. IE, i can ask alexa for something, and she responds.

But I get these errors consistently in Hubitat;
app:12021-01-25 12:23:33.502 errorError making Call to Alexa message gateway: {"header":{"namespace":"System","name":"Exception","messageId":"ASRLS_762ae368-942e-49c5-b6d3-393a6d175083_1611606213050.0..ASRLS_762ae368-942e-49c5-b6d3-393a6d175083_1611606213050"},"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[3])"}}

app:12021-01-25 12:19:32.964 errorError making Call to Alexa message gateway: {"header":{"namespace":"System","name":"Exception","messageId":"ASRLS_38a5401d-9fe2-4ff3-879c-82b14e17dbe9_1611605972513.0..ASRLS_38a5401d-9fe2-4ff3-879c-82b14e17dbe9_1611605972513"},"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[3])"}}

app:12021-01-25 12:08:35.510 errorError making Call to Alexa message gateway: {"header":{"namespace":"System","name":"Exception","messageId":"ASRLS_68828565-4add-424d-82e2-300800a87e76_1611605315068.0..ASRLS_68828565-4add-424d-82e2-300800a87e76_1611605315068"},"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[3])"}}

Are these errors due to the Ecobees not being a "real" Alexa speaker?
Or since I have one of the mics muted on one of the stats, will this throw the errors?