But a developer can overrule thos icons right?
(At least, i think its possible, im certain for custom capabilities, but since its done through the capabilityOptions, i would assume you can overrule default capabilities as well).
And yes im talking about the icons above and below the sliders.
Wauw, i jist checked out the curtain and media widget, many thanks m8!
My dashboard is really tranforming 
Just two points:
The curtain widget doesnt exactly line up with the light widget, its a few pixel bigger.
Not a big issue 
but well, i thought i would mention it.
And, maybe its me being precis , but the media widget, it feels a bit weird that the blue play button isnt in the middle.
Keep up the excellent work! And many thanks!
Hi Thomas @ThomasRS
Having a teeny-tiny issue with one of my ReoLink cameras, it won’t load the live view when I tap on it… I suspect it it trying to load the main stream rather than the sub stream… which would fail due to the H.265 high resolution of the main stream (which also fails to load in the Homey native camera view and even the ReoLink official Homey app. The implementation of WebRTC that Homey uses doesn’t officially support H.265, and when you try to load a 4K H.265 stream it 
's the bed… but the lower res sub-stream usually loads, just about.
I actually was referring to the icons that alternate on the quick action button and on the on/off button on the devices on/off tab 
. See also the picture in my prior post. But I assume those are the same as displayed by the slider. Not sure if an app can change them. The blind is the default one.
Ah, yeah, those look like the default once.
But your curtain device has an open/clodse button in Homey?
Mine (Forest) sont anymore since about 5 years, they (or athom) removed the default open/clode for curtains.
I just checked by editing a AVD. All available classes and capabilities are automaticly updated when i update the homey-lib library.
For curtains there is only one button type: "closed (windowcovering_closed).
I added one (and checked what happend if i pushed the button: nothing, the icon doesnt change, first as non default (the checkbox real flowcards was off).
Then i switched to Create Real fields and flowcards: nothing changed.
I made another on, and wauw! It the same field, same properties, everything is the same: but its the icon of windows opened instead of closed 
And as you can see, the icons are different and non responsive to pressing the button (the button itself lights up though).
So something isnt going correctly on homey
Yes, it seems that the windowcovering_closed capability is the one that drives the on/off button and the corresponding quick action button.
I have curtain motors from Aqara and SwitchBot. The former does not have the indicated capability. Hence no on/off button or quick action button. The latter does have that capability and the buttons.
However Homey’s UI and mobile vs. web app aren’t consistent with displaying the correct icon (closed or open blinds). Hence my earlier post and ticket to Athom.
Yeah i can imaging, certainly since even on the homey app alone they arent even consistent, which i find very weird. Afaik,no other icons have that issue, although i havent tested all available buttons in AVDs yet
I’ve actually been thinking quite a bit about this since you wrote it — and I think it warrants a proper response. 
First of all, Widgetkeeper is built using AI (Claude Code specifically). Although I have a background in Computer Science and UX, I haven’t coded any major projects for quite some time — and don’t plan to, as I’d like to keep my job and family. 
So why doesn’t Athom just do the same?
In my professional life, I work closely with software developers from a business and product management perspective, and this is something we’re discussing too (as I am sure Athom does too these days).
A few reflections:
-
Cost of creation vs. total cost of ownership. For me, the cost is basically a Claude subscription and some spare time. Athom has to consider testing, support, security, compatibility and maintenance for years to come.
-
Risk is almost nonexistent for me. I can experiment with whatever idea I have, and if it doesn’t work out, who cares?
I can throw it away or try something else. Athom has a production platform, paying customers and a reputation to protect. They can’t afford to experiment quite as freely. -
Maintenance and technical debt. I could decide tomorrow that I don’t want to maintain Widgetkeeper anymore, or take three months off and ignore everything. Athom, on the other hand, needs to ensure that what they build continues working for years.
-
It’s incredibly easy to agree with yourself. I don’t need to align with anyone, discuss priorities, get approvals or consider an existing roadmap. I get an idea and just build it. If I change my mind halfway through, that’s fine too. In a company, there’s a good reason why decisions involve more people.
-
The definition of “done” is very different. For me, it’s done when it works and I’m happy with it. For Athom, it needs to work for thousands of users, across different setups, and continue working after future updates. There’s a big difference between making something work and making it a reliable product.
-
Priorities are different. I build whatever I find interesting or useful. Athom has to balance new features against bug fixes, security, device integrations, platform development and everything else on their roadmap. Just because something is possible to build doesn’t necessarily mean it’s the best use of their resources. It comes back to the business case in things.
-
Athom has already done the hard work. I’m building on top of their platform, APIs, dashboard framework and design. They’ve provided the foundation that makes it so easy for me to build these widgets.
-
Organizations don’t change overnight. Athom has developers, established processes and responsibilities. Adopting AI isn’t just about giving everyone a Claude subscription. It also changes how people work, what their roles are, and how development is organized.
AI makes it incredibly easy to create software. Making sure that software remains reliable and maintainable for years is a different challenge altogether.
One final thing: Widgetkeeper is open source and MIT licensed. Anyone can clone the repository, build their own widgets, fork the project or submit a pull request if they’ve made something worth including. You’re very welcome to do so!
You mean for the web dashboards? Athom already have their own widget for the regular dashboards that I think work great - or?
You mean in the exact middle (horizontal) of the widget? I don’t think that would work with the current design and options for the widget.
Just so I understand more clearly - why would you want this? What is the use-case?
Ha ha oops 
I wasn’t meaning to be serious, it was more a throw-away comment for fun 
I don’t disagree with any of your points… and I should probably filter my random thoughts, even if just for fun, a little more to make sure I don’t upset anyone
Yeah - I had the feeling it might be Still though it is a relevant question though!
Indeed… they’ve already done the majority of the hard work creating Dashboards for the mobile app… I always thought Dashboards made more sense on the web side… more lightweight and versatile on the client side (like my Shelly Wall Didplay XL example… without your web dashboard it was likely to become very expensive ewaste as the Android app was just too resource intensive for it)
Hmm, where to find this option?
Can‘t spot it in your app/ widget nor in the foscam app.
Where have you found this option?
It seems to be a setting on the device itself - not something in Widgetkeeper. So find your device in the device list of Homey and go into settings there.
Yeah, i figured that. I just thought i would mention it.
Its no complained, the new widgets also look gorgeous and a huge improvement over the default homey media widget.
Many thanks!
