You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it is described in an example HA should be able to receive messages. However this requires JSON-RPC via Websockets support. Current implementation will flood Signal-cli-rest-api logs with 400 errors and not receive any message:
Hey there @bbernhard, mind taking a look at this issue as it has been labeled with an integration (signal_messenger) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of signal_messenger can trigger bot actions by commenting:
@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign signal_messenger Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
The problem
As it is described in an example HA should be able to receive messages. However this requires
JSON-RPC
viaWebsockets
support. Current implementation will flood Signal-cli-rest-api logs with400
errors and not receive any message:What version of Home Assistant Core has the issue?
core-2024.5.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
signal_messenger
Link to integration documentation on our website
https://www.home-assistant.io/integrations/signal_messenger/#sending-messages-to-signal-to-trigger-events
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: