Does someone has experience how to control a Teufel 3Sixty device using http?
I found some information on the Teufel Raumfeld devices, but it seems that the 3sixty has a completely different firmware.
The device is not discovered by the Chromecast binding so I suppose it doesn’t support Chromecast. I did not yet tried to sniff the Teufel App with Wireshark.
Beside the player functions I’m mostly interested in powering the device on/off and selecting the audio source.
It doesn’t look as though Teufel have made a HTTP API so it will be very hard to control it outside the included app.
My suggestion would be to download some sort of internet package tracker similar to Wireshark on your phone and identify the HTTP requests the app is making to control the device. Identify the target address and content in the request, then send the same from OpenHAB.
Manufacturers protect against this though so that your smart home cannot be hacked, and sometimes make it impossible to do this.
Another way would be to use Bluetooth to control it. This is still a difficult way to do it though, would probably require an Arduino and some extensive programming knowledge to copy all the Bluetooth commands
It has google home control, maybe there is a way to create some rules/scenes linked to OpenHAB?
Thanks for the suggestions. Those were also my thoughts.
One point I disagree 
Manufactures are usually not well protecting those interfaces, even when having cloud functions. However, it helps if the App just uses unencrypted http requests, which can be sniffed with Wireshark or tcpdump even the App runs on the mobile. I just want to check out other options before digging into this.
Is there a broader interest for a binding?
ok, I found out that the device supports the FS API (Frontier) and there is already a OH binding:
Auto discovery is not supported, because the reported manufacturer / model is not in the bindings’s list of supported devices. It works when using a .things definition:
fsinternetradio:radio:radioInKitchen [ ip="192.168.xx" ]
Then you could link the supported channels in PaperUI
Maybe I’ll find the time to add the manufacturer/model to the binding and add some channels for EQ settings etc., some stuff fpr this could be found here: https://github.com/flammy/fsapi/blob/master/FSAPI.md and https://github.com/tiwilliam/fsapi/blob/master/fsapi.py