-
-
Notifications
You must be signed in to change notification settings - Fork 140
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
Unable to save Apprise notification body configuration #1033
Comments
I was just poking around, and I see that this value may be saved in
However, it is still not showing up in the UI as described above. |
I had the same issue. I think it's not correctly saving/displaying the value because of some some special characters in the JSON format. I also never got a notification (sending to MQTT as the target) I fixed this by simply using a comma separated list as the body. I'm parsing the notification in Nodered and changed it to CSV format there. However, $flickrimage is empty for me, but the rest works — see #1042 |
Thanks @rappazzo, I edited my Simplified example:
I then used "Tools -> Services -> Restart Core Services" and it started working as expected. There's a good chance this will break again next time the configuration file is rewritten, so I'm going to avoid changing any settings for a while. If that gets annoying I'll go the NodeRed route (or, you know, try to make a bugfix PR here) |
I am able to save the notification body for my apprise messages. I put this into the field, and I am able to successfully send (and receive) a test message. However, when I click the "Update Settings" button, once the response comes back, the notification body is cleared.
Here is the content of the body:
I did have a configuration successfully saved previously, but I tried to modify it today, and it is now exhibiting this behavior.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The Notification Body should save and be retained in the field
Additional context
On the receiver side, I did notice that the test message that I received appeared to be escaped json
(
\{"scientificName":"Anser caerulescens", ... \}
). To make sure that this wasn't a receiver side issue, I ran a test from the command line (ssh'd in)This was received without escaped
{
and}
charactersYour build
Raspberry Pi 3 B+ (PCB 1.3 Sony UK)
Running version: 762732c13434c5ab81d667da952e2345a04519cb
The text was updated successfully, but these errors were encountered: