You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
While the volumeMax-property is very useful, it's not very satisfying as a customer using the app, because it is extremely loud.
And setting volumeMax to false may comes with the risk of having the volume set at zero and therefore no alarm ringing.
Describe the solution you'd like
Change the volumeMax property to a forcedVolume? property, where the programmer can specify a number from 0.0 (silent) to 1.0 (maximum volume). This way, the volume can be forced to e.g. 0.7, which is loud enough to get notified.
Ideally, make the forcedVolume nullable, so when null, the device-volume is used.
The text was updated successfully, but these errors were encountered:
Thanks for you feedback. I'm going to start developing these changes now but they might be released later for version 3.0.0 because it will involve breaking changes.
Is your feature request related to a problem? Please describe.
While the volumeMax-property is very useful, it's not very satisfying as a customer using the app, because it is extremely loud.
And setting volumeMax to false may comes with the risk of having the volume set at zero and therefore no alarm ringing.
Describe the solution you'd like
Change the volumeMax property to a forcedVolume? property, where the programmer can specify a number from 0.0 (silent) to 1.0 (maximum volume). This way, the volume can be forced to e.g. 0.7, which is loud enough to get notified.
Ideally, make the forcedVolume nullable, so when null, the device-volume is used.
The text was updated successfully, but these errors were encountered: