Alarm_stream only vibrating

Yes, no changes in the Settings/Sound & Vibration/Default alarm sound.

A few tests that I’ve performed:

  1. My default settings: vibration only for calls, notifs and max sound for alarm → HA notification just vibration
  2. Changed the overall setting from “vibration only” to “ring” → default alarm sound.
  3. Changed the notification volume to vibration → just vibration
  4. Changed the notification channel to alarm_stream_max and min notification volume → notification sound instead of alarm.

So, based on these tests, it looks like the alarm_stream still uses the alarm’s default sound but is now controlled by the notification volume instead of the alarm volume.

Unfortunately, my expertise lies in other areas and not android/mobile software dev, so I’m not sure if it can be related to e.g. some changes in the HA companion app…

Some interesting additional info:
I’ve checked my wife’s phone (same pixel 7) and it has exactly the same settings e.g. in the app notification streams, etc. However, it works as expected (vibration only mode but HA notifications play alarm sound).

The only difference is that she didn’t apply the last update (the phone says that it’s still pending) and as a result, her phone has AP3A.241105.007 build and my is AP4A.241205.013

Edit: HA Companion app version is the same: 2024.12.1-full

I’ll need to check if I’m updated is possible Google broke something. Not like it hasn’t happened in the past.

that will never work, TTS for that command https://companion.home-assistant.io/docs/notifications/critical-notifications#android-text-to-speech-alarm-stream-max-volume

yup looks to be the case here. Our code was overridden. Will need to file a bug with google issue tracker: Google Issue Tracker

2024-12-17 15:36:39.559  2850-2850  audioAttributes         io....stant.companion.android.debug  D  AudioAttributes: usage=USAGE_ALARM content=CONTENT_TYPE_SONIFICATION flags=0x801 tags= bundle=null
2024-12-17 15:36:39.801  1625-1625  AS.AudioService         system_server                        I  shouldNotificationSoundPlay false: muted stream:7 attr:AudioAttributes: usage=USAGE_NOTIFICATION content=CONTENT_TYPE_SONIFICATION

here is an internal bug to follow:

1 Like

Any alternative option? I would assume it will take many months before Google will fix it (if they will fix it)…

I’m using such notifications in Alarmo and a few other important places where I would need an “immediate reaction”. It would be super helpful if you have some alternative suggestions

yes TTS works :slight_smile: just tested

https://companion.home-assistant.io/docs/notifications/critical-notifications#android-text-to-speech-alarm-stream

It works! The only issue is that it “says” the text only once when the alarm keeps ringing until I acknowledge it…

Maybe I should create a loop with a check for input that would just “say” notification every few seconds until e.g. I click on an action in a notification… that would mean that I can’t use Alarmo’s built-in notifications but I guess it’s ok because I can create an automation around it.

Do you know if it is possible to play a sound instead of text via TTS?

another alternative is to use tasker if it still works, TTS is text only tahts how the service works :slight_smile:

not quite the same as alarm stream, your other option would be to change the phones ringer mode remotely and send teh text and set t back to vibrate once acknowledged

https://companion.home-assistant.io/docs/notifications/notification-commands#ringer-mode

thats teh current workaround for samsung folks who have a similar issue

These are good workarounds! Tested the ringer mode and it works! The only issue is that I need to “revert” it back based on action but I can have some “hooks”. That’s something what I can work with. Of course, the original alarm_stream was way more convenient but oh well…

Huge thank you for your help and your time!

your “hooks” can be other sensors or events from the app, maybe interactive sensor for when your screen turns on? or if you send yourself a notification you dismiss it or use an action https://companion.home-assistant.io/docs/notifications/notification-cleared or a timer after https://companion.home-assistant.io/docs/notifications/notification-received depends on your use cases :slight_smile:

Ooo, these are awesome suggestions!!! Did a few quick tests and looks like the Device locked sensor is not very reliable but the Interactive works like a charm. I probably will use it. Big thank you!

Actually, changed my mind: the mobile_app_notification_cleared works really good. I probably will use it instead

PS: that’s why I LOVE Home Assistant and the ecosystem! It’s so flexible and configurable!

1 Like