Notifications in the Android app of OpenHab work great, but I would like to extend these features for one particular use-case: alarms.
If I silence my phone, all notifications are being muted but still delivered (not only OpenHab’s, but with any Anrdoid app). Unfortunately, as far as I know, I cannot exempt certain notifications to still ring, regardless of the muting of all sounds. It has nothing to do with “Do-not-disturb-mode”, but simply turning off all sounds to either vibrate-only or mute.
Now, for flood sensors, fire alarms or intrusion detection, this is most unfortunate. Although these notifications would still be delivered to the phone, we cannot override the Android sound settings. However, if the OpenHab app - on upmost important events like these - would create a timer to immediately go off (just like a regular alarm clock would go off), then the phone indeed would make sounds (that could even be adjusted to the user wishes).
As far as I understand it, the OH app would require new priviledges, namely to set and alter alarms. And I’m sure the SendBroadcastNotifications-function would need to be able to handle a flag for these critical messages, or to explicitly use this behaviour.
Would it be possible to implement this in the long-term? Is there a better, alternative way to deliver critical alarm messages to the app-user and enforce sounds on the Android device?