Skip to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

IP address change, how to update in Polisy?

Featured Replies

Hi all - I wonder if someone might be able to help with this.

I recently moved all of my IoT devices to a separate subnet, including my Polisy and Hue Bridge. They are both now on the same subnet again, but it's a different IP and subnet than it was before. Hue works fine independently, like through the Hue native app, but I can't get the devices to be found in Polisy. I assume it's because the IP changed. I don't see where to update the IP or have it recognize the new IP issued by the DHCP server.

HELP, please! )

Solved by Geddy

Are you using the Hue plugin? Have you tried rediscovering the Hue bridge (re-discover bulbs button in the main node) to have it learn the new bridge IP address?

  • Author

Thank you for the reply.

Yes, using the Hue plugin.

OK, I found "rediscover bulbs" but clicking on it seemingly didn't do anything. Nothing popped up or anything, and the status of the bulbs in the Console is the same (every bulb is blank).

  • Solution

@PeterP you'll probably need to tell the plugin where to find the Hue hub.

In the configuration area add a custom parameter: bridges

Then the IP should be in this format: ["10.0.1.1","10.0.2.1"]

Be sure you include the brackets [ ] and the quotes around the IP addresses of the bridges!

From the plugin setup information:

Notes

Poly assumes that Bridge IP address never change, so it is recommended that you create an IP address reservation for the Hue Bridge on your router.


Since the plugin isn't looking for the hub to move you've got to tell it where to look and perhaps re-link it. To re-link just restart the plugin then press the top button on the Hue Hub within a few moments of pressing restart (if you have the old style hue hub it should only one button - I think. I don't have new hubs and haven't looked at them to see if they're different).

  • Author

Thanks @Geddy. I tried both of these, and assigned a static IP to the bridge, and unfortunately neither seems to have resolved the issue. |

After I did both of those things, strangely, in Polyglot on the Nodes button it just says Nodes, whereas before it said Nodes[21]. And I used to be able to push that to see the different bulbs even though it wasn't connecting.

Interestingly when I removed the custom parameter, which had the correct IP, the Nodes[21] is back. So it's like somehow it knows it's there but isn't connecting or passing on the bulbs to the Console.

Any other thoughts?

Also, just want to make sure I'm using the best Hue plug-in for Polyglot. The one I have is called Hue, version 0.1.11. Is there something better?

5 minutes ago, PeterP said:

Also, just want to make sure I'm using the best Hue plug-in for Polyglot. The one I have is called Hue, version 0.1.11. Is there something better?

0.1.11 is the origianl one, probably what you've been using up until now. I have that one too. The newer one uses the V2 Hue API and is meant to also support the new Hub Pro, which only supports V2.

16 minutes ago, PeterP said:

Interestingly when I removed the custom parameter, which had the correct IP, the Nodes[21] is back. So it's like somehow it knows it's there but isn't connecting or passing on the bulbs to the Console.

Have you then tried exiting admin console and then logging back in, and try it again? Node discovery (or rediscovery) often need you to restart your console session.

3 hours ago, PeterP said:

Interestingly when I removed the custom parameter, which had the correct IP, the Nodes[21] is back. So it's like somehow it knows it's there but isn't connecting or passing on the bulbs to the Console.

Sounds like @Guy Lavoie might have it right. If you see the nodes in the dashboard side then restarting admin console should pull them into that view. Honestly, I don't really use/rely on the Hue plugin or IoX to control the hue other than a timer to turn them on off so not sure how well it works or doesn't work otherwise.

What version Hue Hub do you have? I honestly don't know all the versions they have, but know if it's the pro or a more recent hub that might not work with the older plugin and might need to get the newer one. I just run 0.1.11 since that worked when I first setup the eisy and my hue hub. I haven't tried with the newer version.

  • Author

Thanks guys - a few things to respond:

1) I currently have the older/white version of the Hue Bridge. And it was working just fine until this IP address change. I am planning on moving to the Bridge Pro at some point, particularly since some of the newer Hue lights only support Bridge Pro. Is it easier/better to move to this other plugin now?

2) I have tried rebooting my Polisy and logging out and back-in multiple times. Including after pushing "rediscover bulbs." No changes. Is that what you guys meant?

3) I saw someone's earlier post with a somewhat similar issue. They deleted the plug-in and re-installed and that seemed to solve their issue. Does anyone have experience with this? If I do this will I need to adjust any programs/scenes or will it match the bulbs back correctly? (This is really my only concern with deleting or changing the plug-in.)

2 hours ago, PeterP said:

2) I have tried rebooting my Polisy and logging out and back-in multiple times. Including after pushing "rediscover bulbs." No changes. Is that what you guys meant?

Have you restarted the plugin then pushed the button on the hue hub within a little while (few seconds) of the plugin starting? It's as though it's not making that connection. You might want to put the log status for the plugin into "debug" mode and restart and let it settle. Then check the log for lines around when you restart the plugin to make sure it's connecting to the hue hub. Otherwise, there might be errors suggesting it cannot find it at a certain IP address.

Make sure you do all this with the java admin console CLOSED.

2 hours ago, PeterP said:

3) I saw someone's earlier post with a somewhat similar issue. They deleted the plug-in and re-installed and that seemed to solve their issue. Does anyone have experience with this? If I do this will I need to adjust any programs/scenes or will it match the bulbs back correctly? (This is really my only concern with deleting or changing the plug-in.)

I'm not 100% sure, but if you delete and reinstall and it does connect and you keep admin console closed then it could bring back the bulbs in the same nodes and might not dissrupt your programs.

Although, I would strongly suggest you make a backup of your programs:

  • in the Java Admin Console right click on the "My Programs" folder (or whatever you might have named the "ROOT" folder in the program detail tab)

  • select "COPY folder to Clipboard" (be sure you use "COPY" - should be last item in the menu)

  • PASTE that text into a text editor (not a word processing app - for Windows I suggest Notepad)

  • Save that text file - you now have a text represnentation of ALL your programs. You'll be able to search for names and repair the programs easier if they are broken from removing and reinstalling the plugin.

I've not had experiance having to remove and reinstall the plugin (at least not recently). It coudl work. Mostly the issue is the plugin is not properly reconnecting with the hub. You probably need the IP address and then perform the pairing again for it to properly connect. It's odd that you said the node listing went away when you tried this before and came back when you removed it.

You might be best off trying a support ticket with UD at this time. I know @xKing is shown as the developer for this plugin so maybe there are some other tricks to try, but I'd say we've pretty much exhausted the typical fixes that we've known from helping others here and experienced ourselves. I'm sure in the end it will be something simple and probably related to your network setup.

  • Author

OK! I fixed it. I think this is how I did it...

I added the bridges parameter with the new IP back in and then restarted and pushed the button. That seemed to send some kind of authentication link which re-linked everything.

Not sure if that was the instruction before but I may have mis-read and thought I just needed to add the bridges parameter and restart, without pushing the button after.

THANK YOU for your help!!!

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.