Command_ringer_mode doesn't work anymore on Pixel 10 Pro XL

I used the command_ringer_mode for months to switch my phone from silent or vibrate to normal ring mode and back, etc. For weeks now it doesn’t work anymore. I have a Pixel 10 Pro XL. I use the following to change the state of the phone:

action: notify.mobile_app_lbr81_pixel_10_pro_xl
data:
  message: command_ringer_mode
  data:
    command: vibrate

Did anything changed about how one need to use these commands? My phone does only spit a popup out with the text command_ringer_mode but nothing else happens. It is really annoying for me, because I always forget to set my phone from silent/vibrate to normal and I miss calls, etc.

I checked all the possible options to resolve this error but I don’t find anything.

I use HA in a container with version 2026.2.1, my companion app is on version 2026.2.3-full. The app have “full” controll over the phone and as said above it worked a few weeks ago without a problem.

Did you ever figure anything out? I just got a pixel 10 pro and im having the same issue. I found if i trigger it with the app open it works, but as soon as you close the app it wont work anymore. The companion app also show the notification was received. Very frustrating, i also always forget to change modes and rely on these automatons for work every day.

Yes, however I forgot the specific setting which was reset by one of the updates. However I remember it was a really dumb and easy solution the second I noticed it...

I'll try to find it and post it if I got it.

I remember now, you need to go to on your phone into the companion settings, choose your HA server and at the security part, activate the app and device control. For some reason it was deactivated for me after an app update at some point. Now it is on and works everything as expected.

haha, thanks for that!! But It wasnt the case for me. I had that setting on, but you made me think to check other settings more carefully. Turns out in my case, for some reason the read notifications permission for the android app was off. I allowed that permission and all is well now. Thanks for reporting back after so long, I was ready to chalk it up to the pixel!!