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

Good initiative! Makes the new Homey Portal obsolete. One little bug: when I want to control the volume of a Google Chromecast device, it shows a percentage sign, but it really is the absolute number. So where it shows 1% it really is 100%. And there is no way to set it somewhere between 0 and 100%

I’m looking into this app, very pleased to have this option to control some of my Homey devices using my smartwatch!
It does seem I don’t have all the devices available when I choose the ‘control’ option in the companion app. For instance: Eufy Homebase 3 doesn’t show, with as a result, I can’t change the presence/security status.

I’m also trying to find the flows I created on Homey. Is there a way to add a flow directly to one of the tiles in the companion app?

@Hans_Hoefjeniettewet I am busy on another project that’s weeks, as soon as that settles I’ll fix that bug. It is on my radar.

@Wout_Reynaert I do filter capabilities that don’t seem actionable, so maybe there is a filter to strict or they don’t expose it as capabilities. Can you send me the device capabilities overview from the Homey development dashboard?
The flow is/was supported but indeed in my effort to clean up it seems you can not add the as action anymore, I’ll look into that in the same time line as the bug above.

Thanks for the feedback, this helps the project forward, keep them coming :+1:

Hi Kaoh,

These are the capabilities of the Eufy Homebase:

Thx for all your effort for making this app available to the communitiy!
Wout

@Hans_Hoefjeniettewet in the test track (both on homey version as android and wear) there is now a version that attempts to fix your % issue
@Wout_Reynaert that device doesnt expose any caps I supprted, I see the enum there as usefull so I added support for that in this test version also.
I also looked at the flow support, it is there in tiles, but in the new test version you can do more flows now.

Major new feature, see my second post:

It now also supports a Round display with custom build firmware.

Looks great, thinking of buying the esp32 panel to try this out.

Do you have any pics, videos of your display? Hows the performance?

Thanks

See second post for some images, and I’ll add a movie on the git repo I think soon

Thanks, looks good.

For the people who want to try this, you can install the Test version as long as your also in the Android test flight. But the android release that is linked to this Homey Test server is taking Google review time again. So be aware it might lock your watch control until its released.
This new version holds major security improvments.

For more pictures and a recording please check out the GitHub - kaohlive/homey-wallpanel: A round touchscreen on the wall that drives a room in Homey: firmware images, enclosures and how to set one up. · GitHub repo.

I am willing to support more panels than this escrow model, but since its true low level firmware to keep the performance fine its going to be a debate how to do this without me buying new panels for every idea out there.

So my current thoughts are, buy one yourself, send it over to my house (on your costs) WITH an return package pre paid to your desired location. I will create a firmware for it, test and send it back, release the firmware into the repo. You create nice models and share them with the community through a PR on that repo.

Great initiative and project! I’m curious to see how Athom responds to this, given that it’s a counterpart to the much more expensive 2.8-inch Homey Portal.

Although I don’t have much technical expertise, I came across similar hardware that looks better than the CrowPanel 2.1" rotary. It is the Makerfabs MaTouch ESP32-S3 Rotary IPS Display with Touch 2.1“ ST7701


Could the software be used on that device as well? Could you make a list of alternative devices that can also be used?

It’s never safe to flash the firmware as is to another device, but it’s very similar so it’s probably just a quick pin layout, channels and bandwidth on mem blocks check. But that’s is the risk, they all use a different pin, other mem size etc.
I build to be able to optimize but I need the device on my computer to do so.
But I like that device, I selected the crow panel since it’s base is small enough to fit in a wall box with a psu… This looks a bit wider…
Like state above, I am willing to do this firmware for any board if your willing to ship it to me and include a return shipping label pre paid. Order it with my address as delivery address send a prepaid transport label for postnl and one I tested and made its firmware I’ll send it over.

Here are some pictures of the wall panel flush mounted in place of where some light switches used to be :flexed_biceps:

I bought the same device and installed everything like you described. Works pretty good. The only thing that doesn’t seem to work are de moods. I can put them in but when I try to activate it nothing happens.

But besides that it’s nice. All I need is a 3D printer for the case.

Some are for trigger based, moods and present for example. I can’t find an sdk api etc for an app to set those.

Hi @Kaoh , first of all thank you for your app. I have added this Homey App to my Homey Self-Hosted Server and have paired successfully. I also installed the Homey Wear Control app on my Android and on my Galaxy Wear 7. I configured 6 devices to sync and it appeared on my Galaxy Wear 7, but when I tried to tur it ON or OFF I received the error “Could not prove the PIN on this device” as it can be seen in the image below. I’m sure it was not configured with the “REQUIRE PIN TO ACT” and I tried without configure a PIN and configuring a PIN but with the REQUIRE PIN disable. I also tried enabling the REQUIRE PIN but the error was the same. Could you please help me? Could this happen because I’m using Homey Self-Hosted Server that has something different then Homey Pro? If you need any log or anything more just ask me that I’d gladly try to help. Thanks.
PS: The phone configurations of collecting phone info is working great.

Some device types are force to use the PIN, you need to setup the pin in the server side. Devices like Locks are there in the forced list.
You can add more to the device list that are force and on the server side. So all the way to the bottom check your pin coniguration, are the other device protected by the server side pin?
The one on the app side is more to revent accidental control, if your one of those people with whom the watch sometimes dont ignore false touches you dont want to remotely open the garage without knowing it.

I don’t have any locks configured, it’s only Lights, Smart Plugs and Sensibo I tried to add and had that problem. When I added the PIN requirement on server side and synced it asked me the PIN for a lamp the first time and it did what I asked (turned ON the lamp) the first time. But when I asked (without closing the app) to turn it off it doesn’t asked the PIN and did the same error. Also the device status when I close the watch app and open again doesn’t reflect on the real device status (show ON when it’s Off). But when I close the app and open it again and try to change device status (On/OFF) it asks the PIN and works, but when I try again same problem. Can I help with some other test?

PS: In my server-side requirement for PIN it wasn’t showing any device (I changed with te lamp I was testing after this printscreen).

that looks good indeed, what versions of the apps do you have installed?
Homey version+phone+wear version please

Device states dont refresh constantly, it would drain the watch battery, so the phone does the heavy lifting and puts it on the wear data sync. So yes that can take several minutes to update. I think thats a fair tradeoff to ensure the app would not have negative impact on the battery life :wink: