I'm a little worried, in your example, that there might be some configuration required that could be frustrating without a way to do it on the device.
For example, I helped someone transfer their stuff from their old iPhone to their new one a few years ago. The way you're supposed to do it is touch your old iPhone to the new one and it'll just work. Needless to say, it didn't. I think it was about an hour of rebooting the old and new ones before it finally caught. Since there weren't any logs or settings to change or any way at all to influence the process it was more frustrating than magic.
Now, it's possible your product really is as simple as turning it on and it'll just work, in the same way a lamp is "turn on and it works", but if there's any configuration at all that the device does, please expose it to the users. Human brains are incredible at finding patterns, generally better than computers, and if there's a mismatch between the human's model of how something works and the device's model, it's best to allow the human to change the device's model
I think there is the difference of calm in everyday use and initial set-up, maintenance, etc is...less calm.
There are functions managed in the app but we aim for those to be rarely interacted with. All the interactions that you have with the device should be as simple as your wireless earbuds, maybe even easier.
Maybe this depends on the person, but I find a device with some buttons to configure it infinitely easier and less frustrating than an app.
An app to my brain screams "depends on your phone and will be outdated at some point; requires picking and unlocking your phone to use it; will have updates that change/ruin it at some point".
I just want to feel a button and press it, especially for things supposed to be used in the dark while sleeping.