-
Notifications
You must be signed in to change notification settings - Fork 183
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
Non-UTF-8 encoding causes error #634
Comments
Hi again, thanks for reporting this problem when receiving binary payloads. Of course, using base64 to encode the image payload, what we discussed 1 and implemented 2 the other day, is not of any value if mqttwarn would need to accept and process data from external systems, like, in this case, Frigate. I will see what I can do about it. With kind regards, Footnotes |
mqttwarn should definitively not crash or otherwise exit in such a situation, 2fd8c3d fixes it. Thanks! |
Hi again, with 5eb4c17, mqttwarn will be able to receive and process binary message payloads, and with 60c6229, store them into files. For the Frigate-to-Ntfy example, a58f7eb configures the new With kind regards, |
PR works for me, files are saved successfully. |
Excellent. Thanks! |
About
Coming from GH-632, I am trying to make mqttwarn subscribe to Frigate's
frigate/<camera_name>/<object_name>/snapshot
topic, where Frigate publishes a jpeg encoded picture.Problem
Currently mqttwarn expects a message encoded with UTF-8. Could it be possible to specify the encoding? I am trying to save a JPEG being sent over MQTT, and since it is obciously not UTF-8 encoded, mqttwarn exits with an error.
Details
mqttwarn.ini
Exception
The text was updated successfully, but these errors were encountered: