# Suggestion for devs - Local authentication (aka, actual local Homey Pro)

**URL:** https://community.homey.app/t/suggestion-for-devs-local-authentication-aka-actual-local-homey-pro/139802
**Category:** Ideas & Suggestions
**Tags:** homey-pro
**Created:** [July 15, 2025, 9:09am UTC](https://community.homey.app/t/suggestion-for-devs-local-authentication-aka-actual-local-homey-pro/139802 "2025-07-15T09:09:24Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Timeraider](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/timeraider/32/120823_2.png) [@Timeraider](https://community.homey.app/u/Timeraider)
#### Post date: [July 15, 2025, 9:09am UTC](https://community.homey.app/t/suggestion-for-devs-local-authentication-aka-actual-local-homey-pro/139802/1 "2025-07-15T09:09:24Z")

</div>

In an age whereby connecting to the internet is more and more an issue or needs restricting, having an ecosystem built around running stuff local is always an pro.  
However this can easily be ruined by the fact that all authentication is done online meaning the moment this authentication doesnt work (no matter the reason, even if on the customer side .. there can be a lot more reasons than simply doomscenario’s) hardware like the Homey Pro become fancy bricks.

If any type of local authentication on a device we simply paid for would be possible, then its as simple as pointing the Homey app towards the IP of the Homey Pro and using a login saved locally.  
This would make everything so much more future proof and would give Homey another advantage to pick some customers away from Home Assistant.

I am sure this is something that can be done without losing control over their software. Whether the capability to create an local user is bound to an identifier or the specific hardware or anything else.

---

<div class="post-metadata">

### Author: ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)
#### Post date: [July 15, 2025, 9:11am UTC](https://community.homey.app/t/suggestion-for-devs-local-authentication-aka-actual-local-homey-pro/139802/2 "2025-07-15T09:11:50Z")

</div>

> [@Timeraider](#):
>
> If any type of local authentication on a device we simply paid for would be possible, then its as simple as pointing the Homey app towards the IP of the Homey Pro and using a login saved locally.

Homey _has_ local authentication (using [API keys](https://support.homey.app/hc/en-us/articles/8178797067292-Getting-started-with-API-Keys)), but Athom, for some reason, never updated the developer tools (or mobile/web apps) to use them.

---

<div class="post-metadata">

### Author: ![Emile](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/emile/32/115314_2.png) [@Emile](https://community.homey.app/u/Emile)
#### Post date: [July 21, 2025, 2:14pm UTC](https://community.homey.app/t/suggestion-for-devs-local-authentication-aka-actual-local-homey-pro/139802/3 "2025-07-21T14:14:32Z")

</div>

We are working on local user accounts, at first to use a local copy of the web app at [https://your-homey-ip/](https://your-homey-ip/). Maybe later we’ll add support in the mobile app, but that should already not be needed since it already maintains the access token — especially if the internet is offline.

I’m hoping we can ship this within a few months. 🫰
