You can’t. But all things (not using Athom’s cloud) you had programmed keep functioning.
I do not consider automated messages as communication from the Athom team. A product like Homey Pro thrives on its community. Involvement with your community/customers, should be a nr1 priority. (just like for any other business)
It’s back.
update it down again
2 Likes
@Arie_J_Godschalk maybe you are the lucky one 
I am glad you don’t experience issues. I am sad that you don’t, for it makes identifying the source of the problem harder.
Maybe if you restart Homey you will be on our team 
Normally restarting solves issues, but now it might get you into it. So better you don’t (need to).
To be continued…
Theo, yes it expires every 2 weeks. But if your internet breaks, and the expiration counter is at day13, you’ll have only one day left. Not 14.
(If correctly I understood mr. @robertklep 's explanation on this matter, that is)
Today we’ve seen the most fragile part: when it can’t check if it’s still valid, login becomes impossible.
Did you activate port forwarding? I guess that’s the option needed in case the cloud is down.
Port forwarding still requires Athom’s cloud servers.
1 Like
Thx for sharing @Sharkys !! Appreciate it.
yes… which explains what Robert wrote.
However then I don’t understand that workaround with VPN, which worked for me (reported to Athom btw)
Not saying that it’s not true, but that wouldn’t make any sense at all.
I suggest to all users reading this topic to let their homey app quiet for a few hours just to let Athom doing their job without adding more charge on the servers🤗
1 Like
I can login now (09:00 in NL)
2 Likes
Agree, app should be able to access local homey ip. Using ssl and private certificate security.
The owner is then responsible for securing port forwarding if you want to access it over internet.
Just like home assistant
I guess the authentication is still required, or? But there are mechanism how to cache that (aka sessions?), I believe.
It’ back online here!
Confirmed, I’m logged on again
Using SSL/TLS locally cannot be done without some dependency on external services (unless you want to depend on self-signed certificates).
That’s crazy… thanks for sharing!
