I have a few flows that use Homey’s built in AND card, “Confirm question with user”, to confirm certain actions and then branch the flow based on my Yes/No selection.
However, since today, those specific cards are failing with an “Invalid refresh token” error.
Does anyone have any idea what could be causing this, or is anyone else experiencing the same issue? I’m wondering if it could be related to an issue with Homey’s servers, but I’m not even sure whether these notifications are handled through the cloud or locally?
Always via the cloud, that’s just how notifications on Android and iOS work. Android uses FCM for notifications. This means that your phone is always connected to a Google server, where it has a realtime communications channel. Apps can register a push notification token on their backend server when you log in, and then use this token together with an endpoint to send notifications to this channel, this is called Firebase Cloud Messaging (FCM). This improves the battery life since your phone only needs 1 connection to Google, instead of having to run all apps in the background. Apple has a similar service with APNS.
So it’s Google or Apple that delivers the notification to your phone, Homey simply sends it to Google/Apple via the Homey servers with your phone’s unique token, and then Google/Apple delivers the notification to your phone. Almost every app that sends notifications works like that.
I just wanted to try to send push notifications but I can’t even connect to Homey anymore, 429 Too Many Requests. Not sure what would cause that though
I’ve restarted it but then I started getting the “Disconnected” error on the same cards and can not access Homey anymore when on 5G. It’s only accessible locally when I’m on my wireless network.