The Send Command action card will execute a http GET to the player: http://ip-of-player:port/command
So for example to pause a standard Bluesound player at 192.168.1.100 you could send command “Pause” resulting in this call: http://192.18.1.100:11000/Pause
(Which obviously doesn’t make sense as the pause function already exists.)
Hoi roelof, bedankt ! It is not pauze where I am aiming for. It is literally putting the entire sound system on standby that my aim is. There are nad native commands like (I have 47 pages of these commands given by nad support)
Example:
Main.CEC.Power=On
They claim on the document these commands can be send using Ethernet… was hoping we could send them over ip
Recently I deleted one of the Bluesound players from Homey (as it was moved to another room).
Now I have given the player a new Static IP and changed the name, however I can’t add it again to Homey as it says ERROR duplicated player. It seems like this is related to the MAC address, which I can’t change.
Is there a way to get rid of old devices without deleting the app as I have many flows with all the Bluesound players?
I have just received the Homey Pro ‘23. However BlueSound is not working.
If I install the app, it is in my app list but the devices say: app not available. After that the BlueSound app disappeared from the “my apps” list. If I reinstall it is the same story. Is this a known bug?
I have the bluesound-app deleted but now i can not install it again (the procedure within the app-store is ok, but the app is not installed at the Homey Pro).
I see this behavior:
-select and install the app in the app-store
-it is a few seconds visible in the app-list on the Homey Pro
-it disappears from the app-list and so it is not installed
app is added to the HP2023 compatibility list ([Homey Pro (Early 2023)] App unsupported list)
This seems to be a known issue with apps and developers are notified by Athom how to fix it.
@RoelofO do you still have the intention to support the development of this app?
It’s not a matter of upgrading. The app is already on SDK3. Someone would need to debug why it’s not starting properly by running the app on the command line on HP2023 and see what causes the issue.
I would like to help, but i have no idea what Phuturist means with: “ debug why it’s not starting properly by running the app on the command line on HP2023 and see what causes the issue.”
I have managed to use URL’s to control the functions described in their API DOC.
And just made flows where i use logic GET commands and insert the following URL’s and attached them to a physical button. (IP Addresses are mine, but yours will be different)