PeterP

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!!!

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.)

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?

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).

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!

Thanks guys. I agree managing the scene seems painful with so many items. @paulbates what I was referring to is that once I have my scene with all of the items I want turned off as responders and I add a new controller (let's say I add a remote I also want to trigger "All Off") then I need to select that controller in the scene and individually set each responder item to 0%. Was wondering if there's a way I can just say "apply all settings from another controller" within the scene.

Hi guys - I searched for other threads in the forum re turning every device off using a single button. It seems the prevailing recommendation is to use a scene, which I agree. I also like someone's idea of a program to indicate the status of the "All Off" lights by checking if the status is "not off." I made an "All Off" scene and added all of the items I want to turn off as responders. Added a keypad button (set to toggle off) as the controller. Then Set those devices to 0% for that button within the scene. Two things: I have some other keypad buttons that do not turn off when the "All Off" scene is triggered. This is mainly because those buttons are in a different scene and trigger microcontrollers. One simple example is I have a light scene called "Garage Hall Accent Light Scene." This scene has one keypad button and one microcontroller that's tied to under cabinet lighting. If I add the microcontroller to my "All Off" scene it will turn off the microcontroller but the button on that keypad remains lit. Do I need to keep adding those additional trigger buttons as responders to my "All Off" scene and set them to "Off"? My concern is that it's creating a super-bloated scene. Is there performance issues to consider? A better way? I want to have multiple "All Off" buttons throughout the house (eg. one at each door, a remote for the car, etc.). Is there a way to add another controller to my "All Off" scene without having to re-do all of the "Insteon -> 0%" settings for each device within that scene for the new controller? (Like... copy default settings from controller A to controller B within this scene.) Thank you! Peter.

Awesome, thanks. I will continue to build out my setup 😅

Thanks @Guy Lavoie. I'm just finishing a renovation on our house and setting up Insteon and other smart home stuff, and I think I will have that scenario of multiple locations to turn something on, so will refer back to this, or look further into virtual switches. I'm actually a bit surprised that something like turning off a secondary button isn't built-in to UD... Btw, unrelated, have you ever done an "all off" scene like in a hotel? Do I just create a scene and add all of the lights, fans, and whatever as responders to that scene, and add secondary Keypadlinc buttons as controllers (like by my front door, garage, etc.)?

Yep, that's what I thought @tazman's suggestion was 😅 Here is my final program, nice and simple: If 'Powder Room / Powder Room Fan' Status is On Then Set 'Powder Room / Powder Room Fan Control' On Wait 30 minutes Set 'Powder Room / Powder Room Fan Control' Off Else - No Actions - (To add one, press 'Action') I added the first line of 'then' to set the scene in case the fan is triggered by something else, such as Alexa or directly in the app, then it will also light up the 'C' button through that scene. I also like @Guy Lavoie's approach but need to further look into how these virtual variables work.

Thank you, this was very helpful!

Hi All - hoping someone can help with a quick answer here that has been eluding me. In my powder room I have one 6 button Keypadlinc. The load on/off controls the lights. Buttons A & B are linked to a scene for the same lights. I would like to set button C to turn on the fan in that room but so that it automatically turns off after 30 minutes. The fan itself is wired to a microcontroller. I created a program: If 'Powder Room.C' Status is On Then Set 'Powder Room Fan' On Wait 30 minutes Else Set 'Powder Room Fan' Off This works in that if someone pushes the button, it turns the fan on and the button is lit. If someone pushes it again to turn the light off, it turns the fan off. The problem is that I can't get it to actually turn off Powder Room.C after 30 minutes. If I just add a line that says "Set 'Powder Room Fan' Off after Wait 30 minutes, it will turn the fan off, but it won't actually turn the light off. The admin panel will not let me add a switch off line to "then". I realize there may be a way to do this by changing the button toggle, but my preference is to have button C show the current status of the fan -- if the fan is on, the light is lit up. That way someone in the bathroom has confirmation that the fan is currently on. Would love any feedback on how to make this work! Seems pretty simple but can't get over being able to turn button C off. Thanks!

Just tried it, and that worked. Thank you very much guys!

OK... maybe I'm going about this all wrong. 😅 The main reason I changed the button to 'non-toggle off' mode is that I want that button to trigger a scene or program but then not remain lit. (The main reason for that is, let's say the scene triggers two Hue bulbs turning on to 50% for an "evening" scene, but then I subsequently use a different control, like Hue Tap, to turn off those bulbs. The button will stay on.) The two ways I thought to resolve this are: Add a step in the program to wait a few seconds then turn off the light by setting a scene where that button is set to off (this would only work if it's a program, I couldn't find a way to turn off the button with only a scene). Use the 'non-toggle off' mode since that itself turns off the light after flashing twice. No good?

OK. Then how do I write a program that's triggered by the button being pressed in Non-Toggle [Off] mode? 😅