EDIT II:
I figured it out by myself - although it’s not the cleanest way.
I ended up using the TRIGGER type and created a rule to handle this trigger (although the trigger payload is the string stuff above)
As it is http traffic accoding to your post I would do some debugging and use a network sniffer like wireshark or tshark or tcpdump and try to capture the traffic being send from the Akuvox to the openhab host to check what is being sent if it is being sent.
You also can do a manual run calling curl from an other host/PC to check what is being sent back ( ok message / error message ) from openhab.
I am know configuring this from the UI, because my akuvox firmware does not allowed that. I am using Upgrade → Advanced → Manual AUTOP. First you export config from the intercom, modify this and use the modified file with Manual AUTOP.
Please note, that there is really two urls, one for event you pass a card known to the intercom and one for event you pass unknown card.
I suggest that after configuring yhe listener binding you use your web browser and go to the url you expect to be called to like “http://192.168.2.138/httplistener/903a02986d?card=ACC5FB82”. You will then if it works on the OH side.
Thanks Piotr, yes I came to the same conclusion. I couldn’t find any combination that works with (multipart) form-data, so I’ve gone down the node red road instead.
I use the bindig to integrate my Garmin watches to OH.
I’m using the APICall App on the Garmin, to send the get calls to the httplistener.
It communicates via SSL trough myopenhab.org and it works like a charm.
I’d also like to see the httplistener as an offical binding.