I have a Lenovo Tab Plus (TB351FU) running the Home Assistant Companion App.
The device is connected and working — sensors update correctly (battery,
screen brightness, light sensor, etc.) and the device appears in HA under
“Mobile App” integration.
However, the notify action has never worked:
notify.lenovo_tab_plus shows as “unknown” in Developer Tools → States
When trying to call the action, HA returns “Action notify.lenovo_tab_plus not found”
Spook reports it as an unknown action
What I have already tried:
Android notification permissions for HA app: fully enabled
Restarted the Companion App multiple times
Renamed the device in HA (no effect)
Checked disabled entities — no notify entity found there
Setup:
Device: Lenovo Tab Plus TB351FU
Android firmware: 36
Home Assistant Companion App (latest version)
Home Assistant 2026.8
Integration: Mobile App
The device has 25+ disabled entities. Is it possible the notify channel
was never registered? Is there a way to force re-registration of the
push notification channel without clearing all app data?
That’s the “new” notification type and I don’t think it’s been fully integrated into the companion app (it’s missing a bunch of extra params). Try using notify.mobile_app_lenovo_tab_plus, which is the official way of doing it . Introduction | Home Assistant Companion Docs
Thanks for the tip! Using notify.mobile_app_lenovo_tab_plus worked perfectly.
Just to clarify for anyone landing on this thread: the “new” notifier
(notify.lenovo_tab_plus) shows as “unknown” in HA and the action is not
found, while the classic notify.mobile_app_<device_id> works correctly.
In my case the device was renamed, so the correct action ended up being notify.mobile_app_lenovo_tab_cucina.
I’m using it with command_screen_on / command_screen_off to silently
control the screen of an Android tablet running Fully Kiosk — no visible
notification, just screen control. Works great!
The correct action to use with your notify.lenovo_tab_plus entity is notify.send_message. This is a “general purpose” notification action that currently only supports message and title configuration variables, but can be targeted at one or more notify entities, even those from disparate integrations.
Like other entities, the “new” notify entities can also be targeted by using other other entity context properties like Areas, Floors, and Labels; and they can be grouped using a Group Helper in the UI.
A notify entity’s state will remain “unknown” until the notify.send_message action is called on it. Then it’s state will be a datetime string representing the last time the action was called on that entity.
Thank you for the detailed explanation! That makes perfect sense now.
So to summarize for anyone finding this thread:
Old system (still works):
action: notify.mobile_app_<device_id>
data:
message: “your message”
New system (entity-based):
action: notify.send_message
target:
entity_id: notify.lenovo_tab_plus
data:
message: “your message”
The new notify entities (like notify.lenovo_tab_plus) are proper HA
entities that can be targeted by Area, Floor, Label, or grouped via
Group Helper. Their state remains “unknown” until the first
notify.send_message call, after which it becomes a datetime of the
last notification sent.
For my use case (silent screen control on an Android tablet with
command_screen_on / command_screen_off), both systems work. I’ll
stick with the classic notify.mobile_app_* for now since it’s fully
supported, but good to know the new approach for the future.