Hello
First time posting here - kinda new to Hubitat but not to debugging, I do this for a living.
Did spend a few hours reading any info in past support tickets - no luck.
Basically, I was attempting to connect HE (C8 Pro running latest 2.4.3.171) to my amazon echo.
Did install the Amazon Echo Skill, did the login to link, selected my HE hub, everything was smooth sailing.
I added all the devices, Alexa found them fine after a discovery.
Also, when I add or remove devices in the skill, get synced flawlessly with Alexa app.
What doesnt work:
- Cant set any setpoint temperature from Alexa
- Alexa doesnt display the correct actual temp of the termostat.
To simplify debugging, I finally removed all devices, remove the sync, redid it from scratch with a single thermostat.
However:
-
When trying to set temp using Alexa app, I get "Device not responding"
-- Tried with the option to spoof the response, same result -
When I change the temp on any thermostat (manually on the termostat or within HE), I see that a notification made to 'tell' the Echo Skill that the temp changed e.g. 'Thermostat Bureau thermostatSetpoint is 22.0°C'
-
But alexa never 'get' the modified value
-
In fact, Alexa always shows 16 and 21 for setpoint and current temp, which was never set
-
Looking further in the logs, at exactly the same second I manually changed the temps, I can see this error message:
Error making Call to Alexa message gateway: {"header":{"namespace":"System","name":"Exception","messageId":"ASRLS_63611fed-4349-4704-84cf-ce2e4a42bb5f_1765834074353.0..ASRLS_63611fed-*****-4704-84cf-ce2e4a42bb5f_1765834074353"},"payload":{"code":"INVALID_REQUEST_EXCEPTION","description":"Cannot read the request payload as: Cannot construct instance ofcom.amazon.iota.driver.v3.StateReportProperty, problem: value\n at [Source: UNKNOWN; byte offset: #UNKNOWN] (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 also noticed that the Amazon Echo Skill has a run-once scheduled job: "getAlexaAccessToken" but it never completes, it always gets rescheduled 1h in the future whenever it runs
-
Each time it run, I get a very similar error message:
Error making Call to Alexa message gateway: {"header":{"namespace":"System","name":"Exception","messageId":"ASRLS_ba6bd260-e184-4dec-9c43-547a3161fc9a_17658******.0..ASRLS_ba6bd260-e184-4dec-9c43-547a3161fc9a_1765834537565"},"payload":{"code":"INVALID_REQUEST_EXCEPTION","description":"Cannot read the request payload as: Cannot construct instance ofcom.amazon.iota.driver.v3.StateReportProperty, problem: value\n at [Source: UNKNOWN; byte offset: #UNKNOWN] (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[1])"}} -
I tried rebooting the hub, same result.
-
But I do get this error message after a reboot:
Error making Call to Alexa message gateway: {"header":{"namespace":"System","name":"Exception","messageId":"609344f1-5a3e-42d4-bbba-5a664dc06926"},"payload":{"code":"INVALID_REQUEST_EXCEPTION","description":"com.amazon.iota.container.exception.NoCorrelationSessionFound: No active session found for correlation token : SUdTVEs6AAE6AAg6ey******zZjljMTBmLWZhMjYtNGY5NS04YTIzLTEwMTg0ZDE3NzE4NCIsInVyaSI6Imh0dHBzOi8vZC1hY3JzLW5hLXAtN2UzLTRkYzk4ZDViLnVzLWVhc3QtMS5hbWF6b24uY29tOjk0NDQiLCJzZXNzaW9uSWQiOiIyNjQwZmJjNC1kMzJmLTQ0NTctYjNkMS1lNTA4MDM2ZWY2ODgifQ=="}}
I checked my firewall as some tickets mentionned calls to api.amazon were blocked and could cause this issue, it is not the case for me, everything is allowed from HE and from my Echo devices.
I made sure to have HE updated to the latest release as some post mentionned that was the fix.
If I had to guess, HE is unable to get its Amazon access token working, and that affect all api calls triggered to 'update' changed data to Amazon.
What is weird, if I add a device in Amazon Echo Skill on HE, few seconds later Alexa sees it. So the 'login' sync from HE to Amazon seems to be working.
Is there any more debugging I can turn on ?
I am at lost to debug this further. Any help would be much appreciated.
