home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
70.84k stars 29.54k forks source link

Synology Chat Message isn't received if '%' is used #108068

Closed robertgetch closed 1 month ago

robertgetch commented 7 months ago

The problem

If you send a message that has a "%" in the text it will fail to be received but there is no relevant failure on the HA side from what I can tell. I was attempting to move my battery status notifications to Synology Chat which sends the relevant low batteries current percentage.

What version of Home Assistant Core has the issue?

2024.1.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Synology Chat

Link to integration documentation on our website

https://www.home-assistant.io/integrations/synology_chat/

Diagnostics information

No response

Example YAML snippet

service: notify.hass_synchat
data:
  message: Low battery detected in Jarrods Room Bed Right Switch Battery 2%
  title: Home Assistant - Battery Monitor

Anything in the logs that might be useful for us?

No response

Additional information

did test some other things like "(" or ")" and it seems fine

home-assistant[bot] commented 7 months ago

synology_chat documentation synology_chat source

issue-triage-workflows[bot] commented 4 months ago

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.

robertgetch commented 4 months ago

Still unresolved

issue-triage-workflows[bot] commented 1 month ago

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.