Bluesound App

app

#1

bluesound

Bluesound for Homey

App Store Page: https://apps.athom.com/app/com.bluesound

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.


#2

Changelog

v 1.2.5 and v1.2.6 - 2018-09-21

  • FIX: fixed a bug after refactoring
  • REFACTORING: switched from request node module to node-fetch (reduced footprint from 7MB to 500kB)

v1.2.4 - 2018-08-22

  • UPDATE: updated app manifest to include id of new forum support topic
  • UPDATE: updated node packages to latest versions

v1.2.3 - 2018-06-09

FIX: fix the is (not) playing condition card


#3

I’ve added my NAD T777 v3 as a device, It can connect, but after 1min or so it becomes unreachable.
Have to remove it, and ad it again, but then it becomes unreachable.
This behaviour came with the latest update.
Any thoughts?
I can reach the unit with my browser without any issues.
(wired connection)


#4

Hmmm, I don’t own this device myself so I can’t test updates. I have updated some node modules, perhaps there is now an issue with one of these node modules resulting in connection issues. Do you know how to do a CLI install. I could create a custom version which shows more logging and point me in the right direction.


#5

Never done it, but a quick google gave me this:

How hard can it be :slight_smile:


#6

I currently dont have time to make a version which spits out debug logging but you could already try with the current version. Perhaps it already shows an error.


#7

EDIT: It worked for 5min this time with the version on github, now the unit is unreachable again


#8

I have created a branch on Github with extra logging. Use the CLI install and the ‘athom app run’ command to run the app. You should then see the results in the console which will hopefully tell us what is going on,.


#9

well isnt this typical, the branch u created works like a charm.
No drop outs since I installed it.


#10

I haven’t changed any functionality in this branch. My guess is that it was a network hiccup of some kind. You should install the app version again to receive future updates.


#11

v1.2.5 beta - 2018-09-08

REFACTORING: switched from request node module to node-fetch (reduced footprint from 7MB to 500kB)

I have released a version in the beta channel which reduces the size of the app a lot. Functionality has not been changed. But since I dont own a BlueSound device myself I can not test these changes. Could someone install the beta and let me know if everything is still working. Thanx in advance.


#12

Hi,

i’m on the beta channel on the 1.2.5 version. But my devices keep stating ‘Unreachable’ while if I visit the device via the browser, its perfectly working:

I tried restarting Homey and the app, but both of my bluesound devices keep being offline.


#13

Are you familiar with command line installs? It would help a lot if you could run the app from the command line and tell me what the console says. Please use the debug tree for this on the apps repo.


#14

Hi, i’m not familiar with the command line install. Is there any other way i can debug it?


#15

Find somebody else who is familiar with the command line or get familiar with the command line … :thinking:

Not really, this is the down side of creating an app without actually owning the device.


#16

:frowning: then i’ll need to find time to do so I guess.

where’s the cmd line guide? :slight_smile:


#17

#18

While i didnt had time yet to do the cmd line test. I did try to add the device again and it gave me this error in the network console when I press the test-connection button:

btw. will a VPN to my network help you out testing?


#19

Thanx, this points me in the right direction of the bug which has been causing the issues with the beta. I will release a new version with a fix soon.


#20

v1.2.6 beta - 2018-09-21

  • FIX: fixed a bug after refactoring

Could someone in beta test this and give me some feedback it work now.