Homey Community Forum

Bluesound App



Thanks, as soon as I have time I’ll let you know.

Btw. In the (v2) app I can not change the volume. I can mute, But not un-mute.


Added some extra debug logging to the (un)mute action card as well. Please test this while running the app from the command line so I can see what is going on.


v1.2.7 - 2018-12-14

  • NEW: action card for changing input to next or previous input
  • EXPERIMENTAL: action card for changing input to a given input (will switch through inputs until given input matches the switched input)


Hi @Phuturist,

Just tried the update. Switch input card seems not to be doing anything. If i do a flow with the card it just keeps loading. No errors, the card keeps loading. While if i do it manually in browser it works.

I’m still getting sometimes a Unreachable error. I just wait 10min and the device is back ‘online’. I know, one day i’ll install the CLI version. I checked all router settings but can’t find anything that would explain it. Router settings are OK according to bluesound support. And if the device would be completely unreachable the app would not work. I’m assuming that somehow connection lost between Homey and the Bluesound device. Maybe Bluesound bans ip’s sometimes for x minutes. I don’t know.

The experimental card does switch inputs. But it doesn’t stop at the correct one and it always stops on the BlueOS input. I guess because the BlueOS respons is different then the others.

BlueOS respons: https://pastebin.com/KjDhNXRg
Platenspeler respons: https://pastebin.com/BiYP0Jnk


Without feedback from the command line there is nothing I can do.


Dear Jelger,
Top addition for my Homey. Thé app I was hoping for…
Very happy and used the Donate button to express my happy state of mind… :slight_smile:
I have made several flows already managing a set of 5 series 1 Bluesound’s successfully.
I have 4 types running; VAULT, power Node, nodes and Pulse.
Let me know if I can be of help one way or the other?
If I reduced the 4 sec polling to for instance 10, what would be effect?
Would I gain much by reducing network traffic? Why 4 sec?


Thank you for your donation, it’s much appreciated! :pray:

The 4 seconds are there to make sure an update request is handled before a new request is fired, also on slower WiFi networks. I dont wanna DDOS any Bluesound devices out there … :slight_smile: . Having a higher polling frequency will result in a delayed sync between the Bluesound device and it’s representation within Homey. Let’s say you want to trigger a flow based on “is turned on” action card and you switch on the device with the remote or Bluesound app. Worst case your flow will trigger 10 seconds after you actually switched on the device because Homey is not yet aware of this because it has not polled the device state yet.

About helping out, I’m really curious what happens with the new action cards I made for Quakerix. Appeareantly they both do not work but since I dont own a Bluesound device I can not test this. If you have any technical skills I could create a debug version on Github that would give me some more feedback so I might be able to troubleshoot the issues. Just let me know if you can be of assistance here.


Tech yes, but not familiar with Github. Would need to dive into that to be of help.

Is there a way to take this offline?

I may have a spare node I could let you experiment with?

Met vriendelijke groet,


[mod break: removed phone numbers for user safety - caseda]


This e-mail and its attachments may contain information which is confidential and/or legally privileged.

If you are not the intended recipient of this e-mail please notify the sender immediately by e-mail and delete this e-mail and its attachments from your computer and IT systems.

You must not copy, re-transmit, use or disclose (other than to the sender) the existence or contents of this e-mail or its attachments or permit anyone else to do so.


v1.3.0 - 2018-02-07

  • FIX: improvements to pairing template for firmware 2.x
  • FIX: removed experimental card for switching input based on user input
  • FIX: code refactoring in driver (replace callbacks with promises)