Jump to content

Two Philips Hue Bridges on Polisy


theitprofessor

Recommended Posts

Posted
4 hours ago, theitprofessor said:

For anyone who may be confused I'm trying to add a second node server instance for Philip's Hue Bridge on Polyglot.

From what I remember the Hue Polyglot NodeServer supports multiple Hue bridges.  Have to get @xKing to answer this for sure though.

Posted

That worked perfectly.  These are the steps I took to get it to work.

1.  Added the "bridges" key (without quotes) to the custom configuration parameter.

2.  Added the value to the key exactly as your post above (with brackets and quotes), of course the IPs may vary.

3.  Clicked Save

4.  Restarted Polyglot

5.

Posted

5.  Logged into Polyglot

6.  The blue banner appears asking to press the button on the second Hue Bridge and restart the node server within 30 seconds, which I did and bingo I have the additional nodes showing up on Polygloy and the ISY.

Thank you Mr. King

Posted

Yes I'm using Alexa with Polyglot.  All the lights from the two bridges show up under a device called Hue Bridge when grouped on the ISY.  You can create a program, add any light or lights to it and configure any of the 8 different settings you want for each light such as color, brightness, etc.  Then setup a spoken voice for the program on the ISY Portal and now Alexa can turn that program on or off.

Posted
2 hours ago, theitprofessor said:

Yes I'm using Alexa with Polyglot.  All the lights from the two bridges show up under a device called Hue Bridge when grouped on the ISY.  You can create a program, add any light or lights to it and configure any of the 8 different settings you want for each light such as color, brightness, etc.  Then setup a spoken voice for the program on the ISY Portal and now Alexa can turn that program on or off.

Perfect! All I need is for Polisys to ship and I'll be all set!

  • 2 weeks later...
Posted

I would also upgrade to Polyglot 2.2.5 immediately after receiving your new Polisy, before adding anything....

1.   SSH to Polisy

2.  sudo pkg update

3.  sudo pkg upgrade

4.  sudo service polyglot restart

After it restarts you can browse to Polisy without the :3000 port number on the address bar, it's just normal HTTPS after the upgrade.

Posted
28 minutes ago, theitprofessor said:

I would also upgrade to Polyglot 2.2.5 immediately after receiving your new Polisy, before adding anything....

1.   SSH to Polisy

2.  sudo pkg update

3.  sudo pkg upgrade

4.  sudo service polyglot restart

After it restarts you can browse to Polisy without the :3000 port number on the address bar, it's just normal HTTPS after the upgrade.

Thanks for the tip. Maybe when they ship next month they will already be updated to Polyglot 2.2.5?

Posted

@xKing I’m seeing duplicate rooms names and “All Lights” on my ISY that do not equal what the combination of the two bridges should net.  Any idea how identify and remove a duplicate without affecting the correct/real one?  Also any idea how to Identify which “All Lights” goes with which bridge?  Note:  All Lights shows up 3 times on the ISY and I only have 2 bridges.  Note:  All Lights appears to be a built in hidden room name to each bridge.  Note: All room names on both bridges are unique (only exist on one bridge and not the other) but I still see some room names listed twice on the ISY.

Posted

best way to delete nodes would be via Polyglot admin interface -> pick node server -> hit nodes -> press on the X button. Best way to tell which bridge group belongs to is to look at the node ID, node names are not used by anything so feel free to rename nodes as you like.

Posted

@xKing  I figured out a few things...

1.    You cannot rename the nodes via Polisy.

2.    They can only be renamed via ISY.

3.    You can delete the the nodes in Polisy via the "x" however it's short lived.  As soon as you restart the node server they come right back.  So they cannot be removed permanently.

4.    The duplicates come from rooms/groups when you add in the second bridge by adding the custom configuration for "bridges".

5.    They are exact duplicates of all the rooms/groups from the first/original bridge connected to the node server before the second is added.

6.    So why is this a problem?  Because when you are trying to program something with these nodes it's hard to determine which node you are looking at in the program drop down boxes.

7.    Workaround....

        a.    When the first bridge is connected and they show up in the ISY, immediately rename the nodes by prepending "Bridge 1" to each node name.

        b.    Now add the second bridge by using the "bridges" custom configuration.

        c.    This will display all the new nodes from the second bridge plus duplicate rooms/groups from the first bridge.

        d.    Rename all the nodes from the second bridge by prepending "Bridge 2" to each node name.

        e.    Rename all the duplicate nodes from the first bridge by prepending "Duplicate" to each node name.

Not complicated by necessary.  Perhaps we could see a enhanced feature in a future node server version so it won't be necessary to compensate for this undocumented feature.  :-)

Posted

thanks :) I don't have 2 bridges to test with so you get what you get :)

can you send me the log of the node server restart and it creating duplicate nodes after you've deleted them?

  • 2 weeks later...
Posted

Thanks to Mr. King I've updated my findings on this duplicate name issue...

1.    You cannot rename the nodes via Polyglot.     Still Correct

2.    They can only be renamed nodes via ISY AC.     Still Correct

3.    You can delete the nodes in Polyglot via the "x" however you must delete the correct nodes or they will return upon a node server restart.     Updated

4.    The duplicates come from rooms/groups when you add in the second bridge by adding the custom configuration for "bridges".     Still Correct

5.    They are exact duplicates of all the rooms/groups from the first/original bridge connected to the node server before the second is added.     Still Correct

6.    So why is this a problem?  Because when you are trying to program something with these nodes it's hard to determine which node you are looking at in the program drop down boxes.     Still Correct

7.    How to cleanup the configuration after adding the second bridge.     Updated

        a.    When the first bridge is connected and the nodes show up in the ISY AC, immediately rename the nodes by prepending "Bridge 1" to each node name for any lights.

        b.    Rename the nodes by prepending "Duplicate" to each node name of a room/group.     Updated

        c.    Pay attention to the node addresses listed in Polyglot > Node Server (Hue) > Details > Nodes Button     Updated

        d.    All the rooms/groups will have node addresses starting with "n001_huegrp0", then "n001_huegrp1", the "n001_huegrp2" and so on.     Updated

        e.    Now add the second bridge by using the "bridges" custom configuration.     Still Correct

        f.    This will display all the new nodes from the second bridge plus duplicate rooms/groups from the first bridge.     Still Correct

        g.    Rename all the nodes from the second bridge by prepending "Bridge 2" to each node name.     Still Correct

        h.    Rename all the duplicate nodes from the first bridge by prepending "Bridge 1" to each node name.     Updated

         i.    Go back and look at the node address and you will notice a different address format where the 0,1,2 get prepended by the IP host address of each bridge.  For example if your bridge host IPs are x.x.x.17 & x.x.x.18 your new node addresses will be "n001_huegrp170", then "n001_huegrp171", the "n001_huegrp172".  This will be in addition to the "n001_huegrp0", "n001_huegrp1", "n001_huegrp2" that are already there.  This is where you get the duplicate names from.    Updated

         j.    Now you can delete the duplicate nodes in Polyglot via the "x" which have the original addresses starting with "n001_huegrp0", "n001_huegrp1", and "n001_huegrp2" and you will notice the prepended "Duplicate" node names disappear from the Admin Console permanently.     Updated

That's it, you are all set.  You should have the same number of nodes in the AC as you see in Polyglot now and you should easily be able to determine which bridge they belong to in the ISY AC.

Enjoy!

  • 2 weeks later...
Posted
8 hours ago, notslow said:

Next big question is will this work with three or four bridges as well?

The only way to know is to test if you have them. Most people only have 1. Not many have 2 let alone more than that

Posted

I haven't bought a polisy yet. I would prefer not to if i will be limited on how bridges. I have the now and will likely be adding a fourth eventually now that I'm adding outdoor and landscaping lights. Maybe I can check with UD directly to see if they know.

Or does anyone know if pollyglot can control 3-4 bridges running on another device, pc or raspberry pi?

I am pretty invested in the hue ecosystem so if isy can't control it, I may have to look into other options. I really want to use isy due to no cloud dependency and reliability as well as the really nice insteon keypads.

Posted

S is mostly curiosity...why does one need more than one bridge in a single house?  Is there some benefit to multiple bridges that I am missing?

Posted
35 minutes ago, oberkc said:

S is mostly curiosity...why does one need more than one bridge in a single house?  Is there some benefit to multiple bridges that I am missing?

Im with you. Mine is 5400 sq feet with a single bridge

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...