Problem with Bluesound IP control

Forum to ask for any help
Post Reply
DemoIan
Posts: 11
Joined: Tue Aug 01, 2017 9:59 am

Problem with Bluesound IP control

Post by DemoIan » Sun Oct 17, 2021 10:14 pm

I am trying to control a Bluesound Node 2, the API documentation says

"All the requests described in this document are sent as HTTP GET requests. The parameters are a standard URL
encoded name/value pair. BluOS players receive these commands and then respond with UTF-8 encoded XML
data.
All requests are in the form of http://<player_ip>:<port>/<request> where:
• player_ip is the IP address of the BluOS player (e.g., 192.168.1.100)
• port is the TC port used for communications. Port 11000"

I have set up a new device as generic IP device, port 11000, with UDP not ticked and command suffix \x0D\X0A

I have tried various commands but without success
GET /Preset?id=1 HTTP/1.0 does not work but if I use Hercules the command works

"Connecting to 192.168.1.42 ...
Connected to 192.168.1.42
GET /Preset?id=1 HTTP/1.0
HTTP/1.0 200 ok
Connection: close
Access-Control-Allow-Origin: *
Content-Length: 78
Cache-Control: max-age=0
Content-Type: text/xml; charset=utf-8
Date: Sun, 17 Oct 2021 21:06:16 GMT
Expires: Sun, 17 Oct 2021 21:06:16 GMT

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<state>stream</state>
Connection closed"

Can anyone see what I am doing wrong?

User avatar
DemoPad
Site Admin
Posts: 769
Joined: Thu Jun 14, 2012 10:46 am
Contact:

Re: Problem with Bluesound IP control

Post by DemoPad » Tue Oct 19, 2021 11:13 am

Presume you mean \x0D\x0A as the suffix, not \x0D\X0A

Try changing the IP address of the device to match your PC, and use Hercules in TCP Server mode to see what data comes in, and compare with what you send yourself from Hercules. Usually you need an extra \x0D\x0A at the end of the command. Does the 'Test Command' in Designer report 'Command Sent'?

DemoIan
Posts: 11
Joined: Tue Aug 01, 2017 9:59 am

Re: Problem with Bluesound IP control

Post by DemoIan » Wed Oct 20, 2021 10:06 pm

Thanks for having a look, you were right I had miss spelt the EOL characters, I changed them but still no luck. I un-linked the device from the processor (centro 8) and then used the feedback, to see what was happening, it said the command was sent but nothing occured. Hurcules would only work if manually pressed the <rtn> key so as a thought I added x0D\x0A to the end of the command and this has solved the problem

the commands are formatted like GET http://192.168.1.42:11000/Preset?id=1 HTTP/1.0\x0D\x0A although device also has \x0D\x0A set against it

Thanks for you help

Post Reply