Andreas Motl

Dear sev, thanks for writing in. I am not 100% sure, but I think the value of the `message` item within a JSON payload submitted via MQTT will get used...

Hi again, it should work to submit attachments via mqttwarn => Apprise => Ntfy. However, we have not tested it, so it will be sweet to explore this detail together....

> we can explore how to propagate those parameters appropriately. I may think you want to use some field from the ingress message for that purpose? Ah, you actually don't...

> The image is sent in [another MQTT payload,](https://docs.frigate.video/integrations/mqtt#frigatecamera_nameobject_namesnapshot) so it first needs to be ingressed by the alldata function. Oh I see. So you will have to introduce a...

I am just now getting a bit more into the details while I am looking into the snippets you provided. I will add them to the `examples` directory if you...

>> My main concern now is why the filter function isn't working. > > All right, let's focus on this detail now. While getting the code snippet to my machine,...

>> I will your code snippets to the `examples` directory if you don't mind, so there will be a canonical reference to drive this forward. > > Feel free, but...

> I think the path can be constructed based on the payload. That would be excellent, so mqttwarn would not need to process the image at all? So, the `cam`...

I've just added the code and configuration snippets you provided with GH-635. When running the example as outlined at [README » Usage](https://github.com/jpmens/mqttwarn/blob/collab/frigate/examples/frigate/README.rst#usage), I am getting a huge error output. Those...

Oh I see. Such errors are apparently still hard to debug. It will be easier when tweaking `mqttwarn.context` a bit. ```diff diff --git a/mqttwarn/context.py b/mqttwarn/context.py index 1c1508e..ff1fa7f 100644 --- a/mqttwarn/context.py...