[Incident] Service degraded - Integrations and API - 20260124T10h30 CET - Was: Homey Cloud is down

I noticed that my cloud connection is up again.

But Google Assistent is not working yet.

Automatically Created IncidentSubscribe

Investigating - Our automated systems have reported that there might be an issue with slack.athom.com.
Jan 24, 2026 - 13:42 CET

My homey only works when I connect locally, anything else and it refuses to connect

Android widgets don’t work either.

Why shouldn’t they work locally, as the same flows are working fine in the Homey app…?

That’s strange, I don’t use widgets on my Android phone but I would think that those work locally.

Push notifications are also not working, but that’s because it uses FCM for notifications

same problem

400€ hub…

Every cloud service will have an outage at some point (maintenance and updates for example), and yes, even the expensive smart devices.

I hope Athom publishes a blog post about what caused the outage once it’s resolved (like they did when the other major outage occured that caused the mobile app to crash)

Maybe a stupid suggestion, but maybe this has something to do with port forwarding? I’m not sure, but maybe when portforwarding is enabled it communicates directly to Homey instead of using the servers?

Updated title to [Incident] Service degraded - Integrations and API - 20260124T10h30 CET
Was: Homey Cloud is down

This incident affects:

  • Integrations (Amazon Alexa, Google Assistant)
  • and API (Apps API, Notifications API, Weather API).

So we can close and archive it when fixed.

1 Like

Yes, I would think the same.
These outages learn us that Homey is not so “local” as Athom likes us to believe…

Let’s hope this urges Athom to make Homey even more cloud independant.

They should make the widgets local IMO. Just use the same logic as for the mobile app: first try local, fall back to cloud connection if the local isn’t working

The push notifications should remain on the cloud in my opinion. If it doesn’t use FCM, it means that the app has to constantly be connected to Homey, which isn’t battery efficient.

Agreed. Or better (if possible): cloud first, local second if cloud not available.

I don’t think that’s possible, since the app doesn’t know if the cloud is offline (it doesn’t run in the background so it can’t open a local connection when the cloud goes offline)

1 Like

(post deleted by author)

Problem is SOLVED. Everything is working fine now!!!

The problem was at a cloud provider.

Yes, same here. It’s still a bit slower than usual, but that’s likely because everything is reconnecting

Yes indeed. Hopefully the cause can lead to some improvements together with some of the suggestions made earlier in this topic to improve local stability when cloud is temporarily unavailable.

Seems to be related to AWS

Webhooks are not working, withings app is not working - I do not see this as “solved”

The Flow (webhook.homey.app) webhooks are working fine here. What type of webhook? webhooks.athom.com or webhook.homey.app?