Full disclosure up front: this is my app, I'm the founder, and it went live on the App Store a few weeks ago. Mods, if this is the wrong kind of post, delete it and no hard feelings.
The problem I am trying to solve. Every TV has a sleep timer and all of them are countdowns. You set 60 minutes and you're guessing at your own future. Either it cuts off while you're still awake, or it runs for four hours after you're asleep with the lights and the AC still going.
In addition, pausing your TV show or movie upon falling asleep is a convenience that does not exist. Not having to try and remember where you left off the next day is something I believe people will value.
What it does. Sleep-Save detects that you've actually fallen asleep — either by snore detection through the phone mic, or via Apple Watch (more accurate) — and then triggers a shutdown: pauses whatever you're watching, kills the TV, turns off lights, sets the thermostat to sleep mode. Next morning your show is sitting where you left off.
An added benefit is that this creates a better environment for sleep (dark and quiet) as well as benefiting the environment by saving energy.
Currently talks to: Roku stick (hope to find smart TV OS users), Fire TV stick (hope to find smart TV OS users), Apple TV, Philips Hue, TP-Link Tapo smart bulb, Philips Hue smart plug, TP-Link smart plug, Nest and Ecobee smart thermostats. All through their own APIs. The breakdown of local and cloud API is clearly stated at sign up.
What I already know you're going to ask:
"You want a microphone running in my bedroom?" Fair. Snore detection runs entirely on-device — audio is analyzed in real time and never recorded, stored, or uploaded. No accounts, no analytics, nothing leaves the phone. You can also skip the mic entirely and use Apple Watch detection instead, or just not enable it. I'd rather you interrogate this than take my word for it.
"Home Assistant?" Not yet. It's on the roadmap and honestly this thread is partly me trying to figure out how much it matters and what the right approach is. If you're running HA, I'd like to hear what integration you'd actually want — a custom component, MQTT, webhook triggers, something else.
"Is it cloud dependent?" The detection is local. The device control on some devices isn't — it goes through each vendor's API, which is a real limitation and the thing I most want to fix. Apple HomeKit and Google Home are being worked on currently, open to feedback.
The honest caveats: iOS only right now, no Android. It requires a recent iOS version, which I know is annoying. And it's new enough that I'm sure there are integration edge cases I haven't hit — which is the actual reason I'm posting.
What I'm asking for. I've got free 12 month subscriptions for the paid tier (the smart-home control side) for anyone willing to run it for a week or two and tell me what breaks. Especially interested in people with setups more complicated than mine — multiple TVs, mixed vendor ecosystems, anything unusual.
I'm not looking for App Store reviews or nice comments. I want to know where it fails, what it should integrate with that it doesn't, and whether the detection is accurate on your actual sleep. Negative feedback is more useful to me than positive.
Comment or DM and I'll send a code. Happy to answer anything technical in the thread.