That’s what we all thought, but that doesn’t explain why a lot of people were having issues this morning.
Weird … i am using the beta app ( through testflight )
Every thing is back
Now itsts working again.
I was too, initially, but I got a message that the test had expired so I had to install the “official” app, which was the one crashing.
Maybe only the ones with an active mobile app screen weren’t logged out in some way?
WebApp seems to be back online, iOS app still says offline
Quite possible, yes.
K … mine is still valid for 88 days ( think i had a new beta last week ) … so should be working through testflight
All the stress is not worth it for so short.
Just wait.
My flows all work, that’s enough for me first
I have the old local homey (living in NL), this morning I thought it died, tried local as well, nothing, it simply can’t connect to Homey. Checked the Homey Status, that did not really give any helpful insights as to how huge this issue was.
Found this post, lots of people having the same issue. Why is this not mentioned as a HUGE item on the server status page? Why don’t people get an e-mail with a bit more explanation?
And even now finding more details is hard, the status page is mentioning an error with firmware.athom.com as well, did they break my homey somehow?
And indeed, the “it’s all working locally as well” seems to be a lie, I can’t even get into my Homey anymore. Hope this is auto-fixed somewhere today, otherwise I’m seriously considering swapping home automation systems.
Glad that it worked for you, but that wansn’t the case for everyone (myself included)
I am in! It seems fixed.
I only noticed it because I wanted to look something.
Otherwise everything runs normally
Nevertheless, the registration should also be on the Homey and not online.
It works for me now (Czech Republic), but I must admit that it was a shock to me, because all the time I lived under the illusion that this system was local and only needed servers for access from outside (outside my own network). Now I see that I chose the wrong system. I am very disappointed with this. So why buy an expensive local system when it works “the same” as a cloud one (meaning it doesn’t work without the cloud). The fact that flow works is nice, but without the possibility to work with the system, it becomes a black box without the possibility of administration and that is not what the marketing “sold”.
What I do nott understand that apparently there is no weekend / night shift solving issues.
I mean how can this be fixed 30 mins after the usual dutch working hours start ?
Looks like a simple server restart or something like that.
This is a system driving peoples home … and that should be monitored 24/7
I’m getting a “Homey is disconnected, could not communicate with Homey” with iPhone towards Homey Pro 2023.
I know it is probably a rare occurrence, but it is very frustrating.
Especially since I thought we were supposed to be able to communicate directly when on the same network…
Appearently Homey is able to run a webserver. Why can it not host it’s own local sever that can be reached by app or PC, and sync with or work from cloud if available.
Sort of like Outlook running locally default working with cloud servers but also able to use local mail folder copy if no connection. That way local functionality is guaranteed.
https://homey.app/en-us/app/com.sdn.webserver/Micro-Web-Server/
Same here, iOS app is not working.
Even when i go to settings and delete my Homey i get “The access token is not found” error ![]()
In my case, everything is not working local.
I was well aware that I couldn’t activate home mode this morning, however I activated a motion sensor that triggered the alarm.
Only 1 of 3 sirens went on (good thing in this case because I need to physically turn them off) and I noticed delays in lights turning on.