I have actions running on everyone’s phones that just toggle their sleep on and off when they go to sleep or wake up, and the toggle their presence on and off when they come home or leave the house.
However, in Homey, there’s no easy way to determine how many people are actually asleep, at home, or asleep at home. This is why I created this homey script that does that for me. I use this information in almost every flow. I feel it should be basic functionality of homey actually.
Hey @Doekse ,
Question about this feature request. I requested this over a year ago. I still use this script a lot. Having these tags built into Presence seems like such a trivial ease-of-life improvement for many people that can also be implemented quite easily.
What’s the process around feature requests, and how can we see the status of them?
If a decision was made to pick up a feature request or to close it, it would be nice to receive an update.
I’m asking this not only for my feature requests, but for the many others that are created daily that almost never seem to be followed up on. Homey is largely driven by the community, and we all strive to keep improving the platform and make it more versatile. Having the possibility to create real tickets for feature requests that have proper status handling, could greatly benefit the entire platform and community.
I could also just build a custom app that introduces new presence trigger cards that automatically add these tags, but that seems a bit counterproductive. I would also be able to contribute to Homey’s source code if access would be public, but that might be a step to far.
First up, thanks a lot for sharing your idea and suggestion!
The forum and our Community Slack are exactly the right places for ideas and suggestions like these, and do know that we keep an eye on what’s being shared there. That said, the fact that an idea is posted doesn’t automatically mean it will make its way into Homey.
Anyhow, I’ll give this one a little nudge internally and bring it up with the team to help it along a bit 
Thanks @Doekse, I really appreciate that!
As a software developer, I’m aware that not all feature requests will be picked up. Some of them will be given higher priority, some of them lower. Some require more effort, some less. Some align with internal plans, some don’t. In the end, the product owner and the stakeholders decide, and whatever the decision is, I’m ok with that.
I was just wondering if we could have a bit more clarity about what’s actually going on around our feature requests. I see a lot of feature requests that never get a reaction from Homey. It makes you feel a bit left out. Other platforms or libraries allow you to create feature requests into a ticketing system. This makes it easier to see and track what is going on with the ticket.
Is it being reviewed? Is it being prioritized? Is it being worked on? Or is it simply closed?
One of the main things missing with. Athom/Homey is unfortunately transparency.
I would also like to see something like a roadmap, so the community can at least vaguely see where the journey goes to.
At least on the Apps SDK issue tracker on Github, I have reported many issues but none of my issues ever get fixed, one of them got a reply but the others don’t get any replies at all. Same with my PRs, only 1 got merged but the others don’t get any replies. If you check the apps SDK issue tracker, you can see that only 9 issues were closed this year, and there are over 100 open issues. It seems like Athom ignores most issues reported there.
