No internet connection
  1. Home
  2. Support

How To Set Up Soundflow + HUE

By Gabriel Lundh @Gabriel_Lundh
    2020-09-30 11:58:13.863Z

    Hi!
    I've been trying to get the hue packade to work with my bridge - but it seems as if SF are not prompting the bridge when I am supposed to press the button. I spoke to the Hue support, who clarified that nothing happens if you press the button without any prompts from a program trying to connect to it. The same network config (all to the same router) worked with the streamdeck app, so connection should not be an issue.

    Do you have any ideas on what can be the problem?

    Thank you for developing this, really looking forward on getting it to work!
    All the best,
    Gabriel

    Solved in post #20, click to view
    Reply
    • 21 replies

    There are 21 replies. Estimated reading time: 12 minutes

    1. Christian Scheuer @chrscheuer2020-09-30 12:13:10.484Z

      Hi Gabriel,

      Thanks for reaching out about this.

      SoundFlow automatically tries to establish a connection to the Hue bridge whenever you run any command in the Hue package.

      So the workflow to authorize would be:

      • Try running any command in the package.
      • If not already connected to a bridge, it'll say - Please press the Hue bridge button and run the command again.

      If you follow those steps, it should work (it does here).

      If it doesn't work, there's a chance your Hue bridge version is not supported. Can you give us the model name/number and version of your bridge?

      Also, it may help to get your log files:
      Please click here to send us the information we need

      Reply
      1. GGabriel Lundh @Gabriel_Lundh
          2020-09-30 15:30:28.964Z

          Hi Christian!

          Thank you for your reply. Just tried the workflow once again, and it did not work.
          I just sent off the logs to the info@soundflow.org adress. It failed to upload automatically.

          Regarding the model, here is what I can find:
          Modell (in the app): BSB002
          On the bridge: 3241312018A

          Thank you again!
          Best,
          Gabriel

          Reply
          1. Christian Scheuer @chrscheuer2020-09-30 15:48:35.979Z

            Thanks for the log.
            I can see you didn't fill out any of questions in the bug report, which is why it wouldn't upload. The steps to reproduce are really important, and it's really important that we know exactly what you see.
            When you say it doesn't work, we can't help if we don't know what that means. Do you see an error, does nothing happen, etc.
            Please fill this info out as thoroughly as you can :)

            Reply
            1. Christian Scheuer @chrscheuer2020-09-30 16:04:08.222Z

              My guess is though that you keep seeing the same error (in which case I need to know which one)?

              Reply
              1. Christian Scheuer @chrscheuer2020-09-30 16:05:38.673Z

                In the Hue documentation that we're following, they distinguish between what they call Bridge V1 and Bridge V2. SoundFlow only supports V2.
                In their own words:

                Bridge V1 = Round-shape bridge
                Bridge V2 = Square-shape bridge (support Apple HomeKit)

                FWIW - Hue themselves don't support V1 any longer.
                So the first thing to rule out is whether you have a V1 or V2.

                Reply
                1. GGabriel Lundh @Gabriel_Lundh
                    2020-09-30 18:10:15.491Z

                    Hi Christian!
                    So sorry about the lack of info. Thought you only needed the logs. I will fill it in now, so you have that as well!
                    But first - just googled around and I definitely have the new bridge V.2. I also use Apple HomeKit daily.

                    I never get further than the first error message "Please click the button on your Hue Bridge and try again
                    (__ Hue line 55) "
                    Even though I've tried to click the button on the bridge in all different ocassions - Before, after - even had a macro when I had triggers for one of the Hue commands and waiting times in between - so that I could stand by the bridge, pressing the button directly when the error message came up.

                    I'll fill in the report now!
                    All the best,
                    Gabriel

                    Reply1 Like
                    1. Christian Scheuer @chrscheuer2020-09-30 18:54:54.141Z

                      Hm, that's really weird.

                      Can you try running this in Terminal to see what it outputs?

                      dns-sd -B _hue._tcp
                      Reply
                      1. Christian Scheuer @chrscheuer2020-09-30 20:55:20.531Z

                        This should give you output like the following if your Hue is discoverable on the network:

                        Browsing for _hue._tcp
DATE: ---Wed 30 Sep 2020---
22:54:51.649  ...STARTING...
Timestamp     A/R    Flags  if Domain               Service Type         Instance Name
22:54:51.649  Add        2   4 local.               _hue._tcp.           Philips Hue - 005E18
                        Reply
                        1. GGabriel Lundh @Gabriel_Lundh
                            2020-10-01 08:10:28.964Z

                            Hi Christian!
                            Just ran the command line and got the following output:
                            "
                            Browsing for _hue._tcp
                            DATE: ---Thu 01 Oct 2020---
                            10:09:00.241 ...STARTING...
                            Timestamp A/R Flags if Domain Service Type Instance Name
                            10:09:00.241 Add 3 7 local. _hue._tcp. Philips Hue - AEF90D
                            10:09:00.241 Add 2 4 local. _hue._tcp. Philips Hue - AEF90D
                            "
                            Really wierd!

                            Reply
                            1. Christian Scheuer @chrscheuer2020-10-01 09:20:40.206Z

                              Hi Gabriel

                              I don't think there's anything wrong in this. But this is still a good first step of troubleshooting.

                              The next command to run would be:

                              dns-sd -L "Philips Hue - AEF90D" _hue._tcp
                              Reply
                              1. GGabriel Lundh @Gabriel_Lundh
                                  2020-10-01 09:24:19.393Z

                                  Hi Christian!
                                  This is what I got back from the terminal:
                                  "
                                  Lookup Philips Hue - AEF90D._hue._tcp.local
                                  DATE: ---Thu 01 Oct 2020---
                                  11:23:40.164 ...STARTING...
                                  11:23:40.222 Philips\032Hue\032-\032AEF90D._hue._tcp.local. can be reached at Ljudbildsverket.local.:443 (interface 4)
                                  bridgeid=001788fffeaef90d modelid=BSB002 "

                                  Thank you!

                                  Reply
                                  1. Christian Scheuer @chrscheuer2020-10-01 09:25:57.339Z

                                    Great, then please try this:

                                    curl http://Ljudbildsverket.local/description.xml
                                    Reply
                                    1. GGabriel Lundh @Gabriel_Lundh
                                        2020-10-01 09:27:37.035Z2020-10-01 09:29:48.819Z

                                        Here we go:

                                        Last login: Thu Oct  1 11:23:37 on ttys000
gabrielundh@Gabriels-MacBook-Pro-2 ~ % curl http://Ljudbildsverket.local/description.xml
<?xml version="1.0" encoding="UTF-8" ?>
<root xmlns="urn:schemas-upnp-org:device-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>http://192.168.1.101:80/</URLBase>
<device>
<deviceType>urn:schemas-upnp-org:device:Basic:1</deviceType>
<friendlyName>Ljudbildsverket (192.168.1.101)</friendlyName>
<manufacturer>Signify</manufacturer>
<manufacturerURL>http://www.philips-hue.com</manufacturerURL>
<modelDescription>Philips hue Personal Wireless Lighting</modelDescription>
<modelName>Philips hue bridge 2015</modelName>
<modelNumber>BSB002</modelNumber>
<modelURL>http://www.philips-hue.com</modelURL>
<serialNumber>001788aef90d</serialNumber>
<UDN>uuid:2f402f80-da50-11e1-9b23-001788aef90d</UDN>
<presentationURL>index.html</presentationURL>
<iconList>
<icon>
<mimetype>image/png</mimetype>
<height>48</height>
<width>48</width>
<depth>24</depth>
<url>hue_logo_0.png</url>
</icon>
</iconList>
</device>
</root>
gabrielundh@Gabriels-MacBook-Pro-2 ~ %
                                        Reply
                                        1. Christian Scheuer @chrscheuer2020-10-01 09:30:59.012Z

                                          Awesome!

                                          Now please do this:

                                          curl -X POST -d '{"devicetype":"org.soundflow#test"}' http://Ljudbildsverket.local/api

                                          It should give out an error "link button not pressed".

                                          Then, please:

                                          • Click the link button momentarily (don't hold)
                                          • Within 30 seconds or so, run the above line again.

                                          EDIT: Fixed the address.

                                          Reply
                                          1. GGabriel Lundh @Gabriel_Lundh
                                              2020-10-01 10:32:14.832Z2020-10-01 10:58:46.081Z

                                              Hi Christian!
                                              I got the success! But SF package still gives the same error :( Here is the output:

                                              Last login: Thu Oct  1 11:27:07 on ttys000
gabrielundh@Gabriels-MacBook-Pro-2 ~ % curl -X POST -d '{"devicetype":"org.soundflow#test"}' http://Ljudbildsverket.local/api
[{"error":{"type":101,"address":"","description":"link button not pressed"}}]%  gabrielundh@Gabriels-MacBook-Pro-2 ~ % curl -X POST -d '{"devicetype":"org.soundflow#test"}' http://Ljudbildsverket.local/api
[{"success":{"username":"t-2sILlAsrH6wZSL5A0yk4O5MgQ0T0ZRjTCXMXh8"}}]%          gabrielundh@Gabriels-MacBook-Pro-2 ~ %
                                              Reply
                                              1. Christian Scheuer @chrscheuer2020-10-01 11:00:39.066Z

                                                Alright, please try running this in Terminal now.
                                                This should store the authentication in SoundFlow:

                                                echo -n '{"001788fffeaef90d":{"username":"t-2sILlAsrH6wZSL5A0yk4O5MgQ0T0ZRjTCXMXh8"}}' > ~/.soundflow/hue/bridges.json
                                                Reply
                                                1. GGabriel Lundh @Gabriel_Lundh
                                                    2020-10-01 11:04:53.535Z

                                                    THAT DID IT!
                                                    Just managed to change a scene thorugh the package!

                                                    Thank you again Christian!

                                                    ReplySolution
                                                    1. Christian Scheuer @chrscheuer2020-10-01 11:06:54.125Z

                                                      Awesome :) So apparently we have some bug where SF doesn't really like to save the authentication in some cases. We should look into that, but happy we made it work for you at least for now :)

                                                      Reply
                    2. G
                      In reply toGabriel_Lundh⬆:
                      Gabriel Lundh @Gabriel_Lundh
                        2020-10-01 08:12:32.334Z

                        Just ran it again and it seems as if it always finds two versions of the same bridge? I only have one bridge on the network though. Do you think this could be a part of the problem?

                        Thank you!

                        Reply
                        1. G
                          In reply toGabriel_Lundh⬆:
                          Gabriel Lundh @Gabriel_Lundh
                            2020-10-01 08:15:41.386Z

                            Just tried to dissconnect from the wifi (I had both wifi and ethernet connected to the same network - and now I only get one bridge:
                            10:13:47.350 ...STARTING...
                            Timestamp A/R Flags if Domain Service Type Instance Name
                            10:13:47.350 Add 2 4 local. _hue._tcp. Philips Hue - AEF90D

                            Although, unfortunately this did not solve the problem as I tried to run the Hue Command again and still no connection to the bridge.

                            Reply
                            1. W
                              In reply toGabriel_Lundh⬆:
                              Will Robertson @Will_Robertson
                                2023-07-12 01:46:12.737Z

                                Hi Christian - I went through all of this (subbing in my values for Gabriel's) and I keep getting the same error. Soundflow says it can't find my bridge. I posted more details here: Soundflow cannot connect to Hue brideg.
                                Hope this can get figured out - thank you!

                                -Will

                                Reply1 Like
                                ReplyAdd progress note