This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Closed Official
[APP] Bluesound
Bluesound for Homey
App Store Page: https://apps.athom.com/app/com.bluesoundLatest version - 2018-06-09 -- v1.2.3
- FIX: fix the is (not) playing condition card
Description
Use Homey to control your Bluesound devices.
Supported Cards
- [TRIGGER] Started playing (tags for artist, track and album if available)
- [TRIGGER] Playing artist changed (tags for artist, track and album if available)
- [TRIGGER] Playing track changed (tags for artist, track and album if available)
- [TRIGGER] Stopped playing
- [CONDITION] is/is not playing
- [CONDITION] is shuffled
- [ACTION] All default action cards for speaker capability like play, stop, pause and change volume
- [ACTION] Change input
- [ACTION] Play preset
- [ACTION] Shuffle on/off
- [ACTION] Repeat on/track/off
Instructions
Add the device as you would add any device to Homey. Enter the IP address of the device (can be found in your router or the settings of the device itself), the port it listens to (default is 11000) and the polling frequency. The polling frequency is used to update the status of the device in Homey (like what is currently playing) based on the actual status of the device. To avoid excessive network traffic the minimum and default is set to 4 seconds.
Tagged:
This discussion has been closed.
Comments
Can't find any traces of the Bluesound App in the loggfile, except when I will restart the app. Mention also the IP Webcam in the orange text
Edit:
Ok, sorry, to quick with my comment. I installed yesterday the app from the store, which was version 1.0. This one wasn't working. now I checked Github and there was an update available (version 1.0.1).
If there is another way to debug please let me know, I will try to have a look at it.
The logfile from the Bluesound don't show anything from the Homey IP (x.x.x.154). Only other devices with the BluOs player.
Did you see your Bluesound mac address while pairing the device?
I just add the Bluesound again and checked the MAC address, I think this is the problem. None of the MAC's in the Bluesound looks like the one in the Bluesound App in Homey (there are two HW adresses: Eth0 Ethernet HWaddr XX:XX:XX:XX:ED:A5 and wlan0 Link encap:Ethernet HWaddr xx:xx:xx:xx:96:8D and a network_serial
btw, there is no such device with MAC ending with 17:45 in my entire network.
Sorry about this.
One thing I noticed is that the Trigger Card Artist and Track aren't working in a radio stream. The artist will stay the same (name of the stream) but the description of the song will change, just like the album name but the flow isn't triggerd. When playing from the library it is working as it should. Attached are two screenshots of the Status output when playing a stream, maybe it is a bug in the app, or it is working like you designed it. The time between the <secs> tags is the total time the stream is playing.
It seems the name tag is not available when streaming.
The flow not triggering seems like a bug, I'll look into this.
Unfortunately the title tags dont seem to be consistent. Below is an XML dump I have received which indicates that title2 is the same as Artist and title3 is the same as Album. In your posted dump this is the other way around. If this is not consistent it's not reliable as fallback for the artist, name and album tag. In other dump I even notice these title fields get filled with other meta data.
I was unable to find anything wrong with the artist changed trigger card. This may require some further testing on your end. Could it be you did not wait long enough for Homey to recognize a change in artist (due to Homey having to poll the Bluesound and there is always a little bit behind). I did notice an issue with the track changed card which I will push to GitHub and app store in a second.
Latest version - 2018-01-31 -- v1.0.1-beta
Thanks for developing
i did not had the time yet to fully test it. What I did notice is:
Change input shows the following values:
- radio paradise
- spotify
- bluetooth
while my inputs are different.
http://192.168.1.93:11000/SyncStatus
the inputs are:
- TV
- Platenspeler
- Bluetooth
- BluOS
The mute/un-mute card seems to be broken. That's all i could test in 5min. Sorry
According to the reversed API documentation the command for getting the inputs is:/RadioBrowse?service=Capture
The respons on this request as send to you in xml give me the inputs:
- "Radio Paradise"
- "Spotify"
- "Bluetooth"
With this info I can build the URL's for switching to this input, for instance /Play?url=Capture%3Abluez%3Abluetooth&preset_id&image=/images/BluetoothIcon.pngThese differ from the inputs you are now describing ("TV", "Platenspeler", another "BlueTooth" and "BluOS"). I can find these inputs in the xml from StatusSync but there is nothing in the API described on how to switch to these inputs. So I cant really do anything with these inputs as far as I can tell.
Do you know the api command to switch to these inputs?
I'll look into the mute / unmute card.
i think it’s different than others because I have the build in version. It’s part of my receiver.
let me do some research.
About the volume, I could save the previous volume level as a parameter and use that to set the volume level once the unmute action card is used. Will look into that when I investigate the issue of the (un)mute not working all together.
Latest version - 2018-02-06 -- v1.0.2
Thank you for this app. For the moment I just use basic functionalities (play, pause, volume). I noticed that when I try to set the volume with a variable, it sets the volume rounded to one decimal after the comma. Eg, when I want to set the volume to 0.12, it actually sets it to 0.1. Am I overlooking something?
I'm not saying everything is a bug. But these are the things I noticed.
Nr #2, #7 and #8 are important to me. I'm already very happy with what you accomplished. I will do my promised donation once these are done.
i have bluesound module built into a NAD sound system. I don't think the bluesound module can change the sound systems input to something else. At least i'm not sure.
The http://192.168.1.93:11000/SyncStatus displays my other inputs, but i don't think it can switch.
btw. I don't know why Tidal is not listed as a Service in:
- http://192.168.1.93:11000/RadioBrowse?service=Capture
And for example TuneIn is missing there as well. I think because they are handled differently. Because they are listed in:
- http://192.168.1.93:11000/Services
As if RadioBrowse displays 'external' services and Services displays nativly built in services.
1. The way the artist, track and album tags are updated by Bluesound devices is tricky. They are not consistent and appearently even change when the music is paused. I cant really do much about that since I dont have any control over it. I have added some extra checks that might avoid this behaviour (not updated the tags when state is 'stop' or 'pause').
2. I will most likely have this fixed in the next release.
3. is shuffled means the playback is currently set to shuffle / random. A not very useful condition card.
4. Hmm, that is common behaviour when using a remote where you need to hit the previous button twice to actually skip to the previous song. I'll see if I can implement it so it will send to "back" api calls shortly after each other which should fix this.
5. I'm pretty sure you have overlooked this action card. Code looks good and I just tested it myself, the card is there.
6. The stop playing will probably be fixed in this scenarion, the track playing I have no control over. It's the same scenario as described under point 1, these actions update the artists, track and/or album tag and thus triggering this action card.
7. I have added a new action card that lists all services of the type 'CloudService', 'LocalMedia' and 'RadioService' and use this to execute the command http://<<ip>>:11000/Genres?service=<<name of the selected service>>. Hopefully this works for you.
8. I will most likely have this fixed in the next release.
I have just pushed it to the app store. So 2, 7 and 8 should be fixed with this release, let me know how it goes.
Latest version - 2018-02-12 -- v1.1.0