-
-
Notifications
You must be signed in to change notification settings - Fork 29.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Signal Messanger - Add Markdown support #117554
Comments
Hey there @bbernhard, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) signal_messenger documentation |
Thank you for reaching out. We use GitHub for tracking issues, not for providing support or tracking feature requests. If you want to suggest a feature, you should try our Community Forum: Feature Requests. If you have additional questions, feel free to join our Discord chat server. Thanks! 👍 |
Just for info, it was already mentioned on the forum, but without any attention. |
Unfortunately I do not have that much time right now to look into the HA integration (the last time I've contributed to the project, the plugin architecture was quite different and at the moment I am lacking time to read into that). What I can offer you guys is, that we make the |
I suppose so, it is only 1 parameter to enable Markdown. |
The problem
Hey, currently all messages will be send without markdown support, to enable it you need to add
"text_mode": "styled"
to the data.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/
Diagnostics information
No response
Example YAML snippet
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: