Error making Call to Alexa message gateway: < new weird error in logs?

WarlockWeary · June 11, 2026, 7:16pm

Just updated C8 to : 2.5.0.157

Never seen this before in the logs .. But generally, I don't have debugging on either.

Any Ideas ?

**dev:188**2026-06-11 2:09:21.482 pm

debug

BatteryReport: BatteryReport(batteryLevel:100)

**dev:188**2026-06-11 2:09:21.473 pm

debug

parse: zw device: 15, command: 8003, payload: 64 , isMulticast: false

**dev:188**2026-06-11 2:09:21.442 pm

debug

DoorLockOperationReport: DoorLockOperationReport(doorLockMode: 0, outsideDoorHandlesMode: 0, insideDoorHandlesMode: 1, doorCondition: 2, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254)

**dev:188**2026-06-11 2:09:21.436 pm

debug

parse: zw device: 15, command: 6203, payload: 00 01 02 FE FE 00 00 , isMulticast: false

**dev:188**2026-06-11 2:09:18.968 pm

debug

refresh()

**dev:188**2026-06-11 2:09:09.403 pm

debug

DoorLockOperationReport: DoorLockOperationReport(doorLockMode: 0, outsideDoorHandlesMode: 0, insideDoorHandlesMode: 1, doorCondition: 2, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254)

**dev:188**2026-06-11 2:09:09.400 pm

debug

parse: zw device: 15, command: 6203, payload: 00 01 02 FE FE , isMulticast: false

**dev:188**2026-06-11 2:09:09.390 pm

debug

DoorLockOperationReport: DoorLockOperationReport(doorLockMode: 0, outsideDoorHandlesMode: 0, insideDoorHandlesMode: 1, doorCondition: 2, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254)

**dev:188**2026-06-11 2:09:09.386 pm

debug

parse: zw device: 15, command: 6203, payload: 00 01 02 FE FE 00 00 , isMulticast: false

**dev:188**2026-06-11 2:09:09.370 pm

debug

supervision report for session: 26

**dev:188**2026-06-11 2:09:09.365 pm

debug

parse: zw device: 15, command: 6C02, payload: 1A FF 00 , isMulticast: false

**app:4**2026-06-11 2:09:08.909 pm

error

Error making Call to Alexa message gateway:

website temporarily unavailable

**dev:188**2026-06-11 2:09:08.839 pm

debug

DoorLockOperationReport: DoorLockOperationReport(doorLockMode: 0, outsideDoorHandlesMode: 0, insideDoorHandlesMode: 1, doorCondition: 2, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254)

**dev:188**2026-06-11 2:09:08.835 pm

debug

parse: zw device: 15, command: 6203, payload: 00 01 02 FE FE , isMulticast: false

**dev:188**2026-06-11 2:09:08.820 pm

debug

new supervised packet for session: 26

**dev:188**2026-06-11 2:09:08.815 pm

debug

unlock()

**dev:188**2026-06-11 2:09:08.584 pm

debug

DoorLockOperationReport: DoorLockOperationReport(doorLockMode: 0, outsideDoorHandlesMode: 0, insideDoorHandlesMode: 1, doorCondition: 2, lockTimeoutMinutes: 254, lockTimeoutSeconds: 254)

**dev:188**2026-06-11 2:09:08.579 pm

debug

parse: zw device: 15, command: 6203, payload: 00 01 02 FE FE 00 00 , isMulticast: false

**dev:188**2026-06-11 2:09:06.744 pm

debug

supervision report for session: 1

**dev:188**2026-06-11 2:09:06.740 pm

debug

parse: zw device: 15, command: 6C02, payload: 01 FF 00 , isMulticast: false

**dev:188**2026-06-11 2:09:05.451 pm

debug

new supervised packet for session: 1

**dev:188**2026-06-11 2:09:05.448 pm

debug

unlock()

marktheknife · June 11, 2026, 7:20pm

That copy/paste of log output is pretty hard for others to read.

It would make it easier for others to review if you share the log as a screenshot instead.

WarlockWeary · June 11, 2026, 7:22pm

jkudave · June 11, 2026, 9:05pm

What is app:4?

I’m not seeing that error on my hub, with the Amazon Echo Skill enabled.

WarlockWeary · June 11, 2026, 9:06pm

APP4 is the Alexa app ..

jkudave · June 11, 2026, 9:08pm

OK. It’s possible you’ve got a temporary issue with your hub being able to access Amazon and it’s respective services for Alexa. As mentioned, I’m on .157 and don’t see that error.

The website message pretty much tells you that.

I can’t think of anything else if it’s been working up until recently.

WarlockWeary · June 11, 2026, 9:16pm

Just never seen that “webpage” error .. like that ever .. No sure whats up.

jkudave · June 11, 2026, 9:18pm

One never knows with Amazon.

We’re seeing issues with Amazon and the Echo Speaks app the past few days.

I’d give it some time and see if it clears up on its own. Maybe others are seeing the error too and will post, but as mentioned, I’m not seeing it on my C8 Pro.

CAZ · June 11, 2026, 9:32pm

I’m getting them too. The last one that popped about 5 minutes ago was just text. My dots are acting up as well.

WarlockWeary · June 11, 2026, 9:32pm

same weird web page error thing ?

CAZ · June 11, 2026, 9:37pm

Yes, but that last one did not have the image in it. I just generated another one using my dots as they appear to be back. It had the image in it this time. Everything did work as it was supposed to but the error came up.

chrisbvt · June 11, 2026, 9:39pm

The logs will render any html in the message. The error being picked up has an image source in it.

<img src="http://g-ecx.images-amazon.com/images/G/01/website/errors/503/generic.png" alt="website temporarily unavailable" width="500" height="300">

website temporarily unavailable

WarlockWeary · June 11, 2026, 9:41pm

Ok .. Just have never seen any error like this ever..

since working with this hub for several years now

marktheknife · June 12, 2026, 1:52am

I’m seeing the error in my logs too.

Presumably something on Amazon’s end, likely to be temporary.

jkudave · June 12, 2026, 11:56am

Odd that I have yet to see this error at all.

marktheknife · June 12, 2026, 12:01pm

Interestingly, it doesn’t seem to affect my ability to control Hubitat devices with Alexa .

sburke781 · June 12, 2026, 1:07pm

Perhaps you could ask Alexa what the problem is? On behalf of everyone here…

jkudave · June 12, 2026, 1:15pm

She just told me to reboot my router and reset my Echo devices, when I asked.

sburke781 · June 12, 2026, 1:16pm

Let us know the results…

jshimota · June 12, 2026, 4:22pm

I erroneously posted in a separate thread - when I scanned this thread initially I saw the long log copy and skipped on - the other thread being closed (appropriately) led me back here. I saw the new HTML based error in my log files for the first time ever and it struck me since that was the first I’d ever seen it. Amazon continues to be in flux - these last 2-3 weeks have been - interesting. I’m feeling improved in many cases, but having a hard time keeping Alexa + out of my world.
My Dots are faster, and I’m getting less dumb responses than I used to. EG; ‘Alexa - turn off the bedroom’ would every once in a while respond with ‘Sorry - I didn’t find a group or device named Bedroom’. I change syntax to ‘Alexa, turn the Bedroom off’ and it works. The next day, I issue the command again ( - turn off the bedroom) and this time it will work without me being forced to restructure the query.

I’ve run the Echo Speaks drivers and apps through Gemini, and get very small things to fix, nothing important enough to implement. The burp with the cookie - that happened, and it did take a small effort to get it to work again - the suggestion somewhere to use a private browse window did fix my initial trouble during the recreate of the cookie, and I’m fine again. I’ve not had to re-login for 2 years, so that was a bit new as well but certainly an expectation. I moved from Heroku to local on my NAS and haven’t had many problems but I watch others stumble in the same places I remember struggling. Having to watch for Hunches getting enabled, I made a rule that uses ES against it, I send commands to Alexa via Rule ‘Alexa, can you stop saying by the way’ then after 10 second delay ‘Alexa, turn off hunches’ and ‘Alexa, cancel Alexa Plus’. I just run this daily when I’m away on my Garage unit so I don’t have to hear the device response. I do admit I’m enjoying the new Sensor support tho - Averaged Temps in room and a few other nice benefits have recently appeared!