# \[App\]\[Pro\] Wear OS and ESP32 Wallpanel Controller for Homey

**URL:** <https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700>\
**Category:** Apps\
**Tags:** app, homey-pro\
**Created:** [June 29, 2026, 3:49pm UTC](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700 "2026-06-29T15:49:39Z")\
**Posts on this page:** 14\
**Page:** 3

<div class="post-metadata">

**Author:** ![Meruem](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@Meruem](https://community.homey.app/u/Meruem)\
**Post date:** [October 26, 2026, 8:41am UTC](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700/43 "2026-10-26T08:41:59Z")

</div>

Thanks for your quick answers @Kaoh . About the device status indeed it’s good that way since I can force send “OFF” even when the device is “OFF” in the watch.  
About the versions:  
Homey Self-Hosted Server: 15.5.3  
Phone OS: Android 16  
Homey App on Phone: 10.1.3  
Homey Watch Control on Phone: 1.3.0  
Watch Version: One UI 9 Watch (Wear OS 7)  
Homey Watch Control on Watch: 1.3.0

I also tried to see the logs in my Homey (since it’s self hosted I have access to the logs) but it doesn’t give any error on Homey Server Side when the app shows the “Could not prove the PIN on this device” error, so it seems it could be a configuration on Homey Watch Control app in the watch.  
Thank you very much on your efforts and if I can help with anything else just ask me.

---

<div class="post-metadata">

**Author:** ![Kaoh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kaoh/32/9283_2.png) [@Kaoh](https://community.homey.app/u/Kaoh)\
**Post date:** [October 26, 2026, 9:15am UTC](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700/44 "2026-10-26T09:15:16Z")

</div>

Can you PM me the logs so I can analyse them?  
Your versions are correct, I made this change a couple versions ago and was carefull to release in the righ order but yours are all updated properly, so that version should not have this change. This error kind of tells me that the Homey app itself is outdated, but your version tells me otherwise.  
So please share the version, based on the code analysis this combination of versions should not block on this.

---

<div class="post-metadata">

**Author:** ![Kaoh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kaoh/32/9283_2.png) [@Kaoh](https://community.homey.app/u/Kaoh)\
**Post date:** [October 26, 2026, 9:17am UTC](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700/45 "2026-10-26T09:17:10Z")

</div>

At least if the WearOS app on the homey side is also up to date?

---

<div class="post-metadata">

**Author:** ![Meruem](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@Meruem](https://community.homey.app/u/Meruem)\
**Post date:** [October 26, 2026, 11:58am UTC](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700/46 "2026-10-26T11:58:06Z")

</div>

@Kaoh , you won’t belive it, but I have restarted my watch and when it opened the app today all worked fine! Just the Icon that I set in the phone app doesn’t reflect the device watch Icon, but that is not a problem. Thank you very much, the app is awesome and sorry for the trouble. Maybe the mobile app was really outdated and at the reboot updated it.

---

<div class="post-metadata">

**Author:** ![Kaoh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kaoh/32/9283_2.png) [@Kaoh](https://community.homey.app/u/Kaoh)\
**Post date:** [October 27, 2026, 7:42pm UTC](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700/47 "2026-10-27T19:42:24Z")

</div>

New and improved: Moods and Presence can now work direct.  
But it requires a special api permission, grant it in the app settings and then you can upgrade your mood card to the new one that works without flows.  
Same story for presence, altough it needs approval for every user you want to use for presence.

---

<div class="post-metadata">

**Author:** ![Ronald\_Nieuwenhuijs](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronald_nieuwenhuijs/32/181624_2.png) [@Ronald\_Nieuwenhuijs](https://community.homey.app/u/Ronald_Nieuwenhuijs)\
**Post date:** [November 1, 2026, 1:38pm UTC](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700/48 "2026-11-01T13:38:53Z")

</div>

![Screenshot_20261101-143014](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/b/bbcadba729eb91c38cfebde57af18fcc85f5937d.png)

Love this app but I’m probably doing something wrong; I can’t start a flow from a watchtiles. No errors, no lights on, nothing. Controlling lights individually works fine. I’ve reinstalled the software on Homey, phone and watch, restarted all the devices and chacked that everything is up to date, but still nothing happens when I tap on my watch tot start the “Verlichting AAN” flow. Any pointers that you might can give me ?

---

<div class="post-metadata">

**Author:** ![Kaoh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kaoh/32/9283_2.png) [@Kaoh](https://community.homey.app/u/Kaoh)\
**Post date:** [November 1, 2026, 3:15pm UTC](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700/49 "2026-11-01T15:15:24Z")

</div>

Can you try it from the watch and then directly after send me a diagnostic report from the homey wearos controller app?

---

<div class="post-metadata">

**Author:** ![Ronald\_Nieuwenhuijs](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronald_nieuwenhuijs/32/181624_2.png) [@Ronald\_Nieuwenhuijs](https://community.homey.app/u/Ronald_Nieuwenhuijs)\
**Post date:** [November 1, 2026, 6:28pm UTC](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700/50 "2026-11-01T18:28:56Z")

</div>

New to this community so still learning how everything works but I have send you a diagnostics report.

2fde75e6-f682-42fe-b8df-589d8b9c517d

Met vriendelijke groet,  
Ronald Nieuwenhuijs

---

<div class="post-metadata">

**Author:** ![Kaoh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kaoh/32/9283_2.png) [@Kaoh](https://community.homey.app/u/Kaoh)\
**Post date:** [November 1, 2026, 9:57pm UTC](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700/51 "2026-11-01T21:57:07Z")

</div>

thanks, I think I spotted the error, released a version to the homey store to fix it. Can you update and test?

---

<div class="post-metadata">

**Author:** ![Ronald\_Nieuwenhuijs](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronald_nieuwenhuijs/32/181624_2.png) [@Ronald\_Nieuwenhuijs](https://community.homey.app/u/Ronald_Nieuwenhuijs)\
**Post date:** [November 2, 2026, 10:57am UTC](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700/52 "2026-11-02T10:57:30Z")

</div>

Thanks for the effort.  
Updated app to v1.49.6; reinstalled app on phone and watch; added a few tiles with flows on watch \> still nothing happens when I tap a tile 🤔

---

<div class="post-metadata">

**Author:** ![Kaoh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kaoh/32/9283_2.png) [@Kaoh](https://community.homey.app/u/Kaoh)\
**Post date:** [November 2, 2026, 12:00pm UTC](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700/53 "2026-11-02T12:00:52Z")

</div>

Send a diagnostic please

---

<div class="post-metadata">

**Author:** ![Ronald\_Nieuwenhuijs](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronald_nieuwenhuijs/32/181624_2.png) [@Ronald\_Nieuwenhuijs](https://community.homey.app/u/Ronald_Nieuwenhuijs)\
**Post date:** [November 2, 2026, 5:43pm UTC](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700/54 "2026-11-02T17:43:59Z")

</div>

6aa868a1-f378-425a-b1c5-af5399e00255

Met vriendelijke groet,  
Ronald Nieuwenhuijs

---

<div class="post-metadata">

**Author:** ![Kaoh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kaoh/32/9283_2.png) [@Kaoh](https://community.homey.app/u/Kaoh)\
**Post date:** [November 3, 2026, 10:03pm UTC](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700/55 "2026-11-03T22:03:01Z")

</div>

check out the new test version. I decided to take the official route, that means you have to approve the wearos controller in its app settings to use your account to start flows. But once thats done you should be able to start any flow you like.  
Let me know if this works

---

<div class="post-metadata">

**Author:** ![Ronald\_Nieuwenhuijs](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronald_nieuwenhuijs/32/181624_2.png) [@Ronald\_Nieuwenhuijs](https://community.homey.app/u/Ronald_Nieuwenhuijs)\
**Post date:** [November 8, 2026, 11:05am UTC](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700/56 "2026-11-08T11:05:47Z")

</div>

Sorry for the time it took before I could test it, but ……… IT WORKS ! 🎉

Thank you for solving the problem. No more need for me to get my phone or tablet to start a flow 🤗

[Previous page](https://community.homey.app/t/app-pro-wear-os-and-esp32-wallpanel-controller-for-homey/156700.md?page=2)
