Notification channel invalid command
driesvj opened this issue · comments
The problem
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:96
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 11:21:16 PM (1 occurrences)
Last logged: 11:21:16 PM
[139624430073984] Received invalid command: mobile_app/push_notification_channel
What version of Home Assistant Core has the issue?
2022.5.5
What was the last working version of Home Assistant Core?
2022.4.5
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
Core
Link to integration documentation on our website
No response
Diagnostics information
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:96
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 11:21:16 PM (1 occurrences)
Last logged: 11:21:16 PM
[139624430073984] Received invalid command: mobile_app/push_notification_channel
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:96
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 11:21:16 PM (1 occurrences)
Last logged: 11:21:16 PM
[139624430073984] Received invalid command: mobile_app/push_notification_channel
Additional information
No response
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (mobile_app
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
mobile_app documentation
mobile_app source
(message by IssueLinks)
is this happening on iOS or android?
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.