# Driver works via \`app run\` but not via \`app install\`?

**URL:** <https://community.homey.app/t/driver-works-via-app-run-but-not-via-app-install/135025>\
**Category:** Developers\
**Created:** [April 19, 2025, 8:30pm UTC](https://community.homey.app/t/driver-works-via-app-run-but-not-via-app-install/135025 "2025-04-19T20:30:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jedrzej\_Nowak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jedrzej_nowak/32/121159_2.png) [@Jedrzej\_Nowak](https://community.homey.app/u/Jedrzej_Nowak)\
**Post date:** [April 19, 2025, 8:30pm UTC](https://community.homey.app/t/driver-works-via-app-run-but-not-via-app-install/135025/1 "2025-04-19T20:30:24Z")

</div>

So I have weird issue, I’m experimenting with custom app and one of my drivers just refuses to “load” when used with `install` but works perfectly fine with `run`.  
What I mean by that is that I cannot enter the pairing process because the driver seems to be forever loading in the browser, and I cannot “click” it to move forward. It’s the first view after selecting the app (before entering onPairListDevices).

When I set up device with the app executed via `run` and then `install` the app, then the result is that the device shows “app unavailable”.

What’s super strange is that I have two drivers, and only one behaves like that. The second one works perfectly in both cases. It’s also possible to add a device to an app executed with `run`, and then it works with `install`, too (and the other way around, too).

There are 0 logs in the app that would allow me to debug that issue further, and I’m somewhat stuck.

Does anyone have any ideas?

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [April 19, 2025, 8:42pm UTC](https://community.homey.app/t/driver-works-via-app-run-but-not-via-app-install/135025/2 "2025-04-19T20:42:31Z")

</div>

Use `homey app run --remote`

> [@Third-Party Node Module Issue - App Crashing Post Install](https://community.homey.app/t/third-party-node-module-issue-app-crashing-post-install/81401/2):
>
> If you’re developing on a HP2023 try `homey app run -remote` / `homey app run -r`. Then the apps runs on the Homey Pro itself and not in a docker image.

---

<div class="post-metadata">

**Author:** ![Jedrzej\_Nowak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jedrzej_nowak/32/121159_2.png) [@Jedrzej\_Nowak](https://community.homey.app/u/Jedrzej_Nowak)\
**Post date:** [April 19, 2025, 9:17pm UTC](https://community.homey.app/t/driver-works-via-app-run-but-not-via-app-install/135025/3 "2025-04-19T21:17:34Z")

</div>

> [@Peter\_Kawa](#):
>
> homey app run --remote

Oh man… thanks 🙂

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [April 19, 2025, 9:28pm UTC](https://community.homey.app/t/driver-works-via-app-run-but-not-via-app-install/135025/4 "2025-04-19T21:28:20Z")

</div>

YW! Afaik it’s not mentioned in the “how to build an app manual”.

The introduction of Homey Cloud introduced this flag, to be able to develop on a docker image (as far as I know).

Imho they should"ve turned it around: `homey app run --local` for Docker development and `homey app run` for any physical Homey.

---

<div class="post-metadata">

**Author:** ![Jedrzej\_Nowak](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jedrzej_nowak/32/121159_2.png) [@Jedrzej\_Nowak](https://community.homey.app/u/Jedrzej_Nowak)\
**Post date:** [April 19, 2025, 9:37pm UTC](https://community.homey.app/t/driver-works-via-app-run-but-not-via-app-install/135025/5 "2025-04-19T21:37:07Z")

</div>

Agree, also kinda surprise for me that the normal `run` is not fully isolated even though it’s also docker based env… it’s some room for improvement for sure.

I honestly skipped the `cloud` part of introduction as … well I’m not using cloud but local with pro so… 😃

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [April 19, 2025, 9:46pm UTC](https://community.homey.app/t/driver-works-via-app-run-but-not-via-app-install/135025/6 "2025-04-19T21:46:23Z")

</div>

Yea haha, I think we all skip what’s not needed 😛

The flag is not mentioned in here, it even didn’t make it to ‘Useful commands’:

 ![1000046671](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/8/c8d53461ec96400b6446a472e7d455624c8b168e.jpeg)

Doesn’t `homey --help` show it?
