I have 2 android phones but on one of them I can’t use the widget to send action.
I do the same setup on both phones but on one I am getting “Unable to send action”. The phone permissions are the same on both phones.
Is there any log which I could check because the one in HA doesn’t show anything so I assume it’s local to the phone/app.
Phones: Samsung S23 Ultra and Samsung A55.
Android app is on 2025.11.3-full.
For now I’d just need more info since the versions, permissions and other are same.
IP addresses of the phones please? (see Android settings/connections).
What is showing from your router end?
Is one phone connected directly to your local LAN via WiFi and the other trying via the phone network? Any intervening networking such as VPN, DuckDNS, NabuCasa, VLANs, etc?
Both phones are on the same network. They have both local IP (192.168.1.xxx).
No VPN or any other network related differences. The app works on both devices without any problem, the only difference is that the A55 has this widget problem.
I had the same issue since a week or two.
One Android phone (Android 15) was able to use my custom widget while the other one (Pixel 10 Pro on Android 16) worked only when connected to wifi, never on mobile data.
What fixed it for me was adding the Home Assistant app as an exemption to data saving (although data saving was disabled in Android). This can be done under Settings → Apps → Home Assistant → Mobile Data Usage → Unlimited Usage (…)
(this is on stock Android 16, ymmv, it may also be called “unrestricted data”).
This saved me a ton of headache. Apparently I had enabled this on my phone, but not on my wife’s phone. Hers was not able to send actions but mine was. Your suggestion to allow unlimited data usage in mobile fixed it. Thanks for the tip!
Great solution, and dependency discovery. This seems like it should be in the installation documentation and setup routine. Have you brought it to the developers attention, so others don’t have the same issue?
there is a mention in the troubleshooting docs about checking data saver settings which are similar to this, every manufacturer will call it something else so impossible to capture all the names it may be under