Jordan Scott

Thank you Bob; a full power cycle does appear to have fixed the issue!

Hi All, I tried to update PG3 this morning from 3.1.11 to 3.1.15. I followed the directions: - Admin Console, Configuration, Upgrade Packages. Heard 5 beeps (not 4?) - Restarted PG3 from System -> Restart Polyglot 3 (heard a few more beeps.) After logging back into the ISY Console, I noted: - ISY Launcher has changed its name to IoX Launcher; not a big deal I guess. - The UUID of my ISY is showing as 00:00:00:00:00:01: - Still can access ISY though, however the console is stuck in a “System Busy” loop. After it reaches 100, it repeats: - None of my Node Servers are showing up in the left under “Network” (I only have three - Hue, Elk and Camect) In the PG3 log, it shows this in a loop : The blanked out UUID are my correct UUID. Any thoughts on how to fix this? Thank you! Jordan

Thank you @JimboAutomates!

Hello, I am running Polygot v3.0.63, and am unable to upgrade the Camect node server from v3.0.8 to v3.0.9 ... When I restart the node server (in an attempt to apply the upgrade), when it first comes back online, v3.0.9 is shown at the top, under current version, then literally a few seconds later it goes back to v3.0.8. Any insight would be appreciated! Thank you! Jordan

Figured it out! For whatever reason (still don't know) devices that were added into an ISY Scene that contained Hue devices, got "reset". Their ramp rate and dim level were reset. I didn't realize it, but once I did, and adjusted it (from the device properties outside of the scene), it worked as intended. Super weird! Thanks everyone for the help! Jordan

Thank you @vbphil!!! This was actually half of my issue. I had forgotten about each "controller" in a scene can have separate settings! What this doesn't fix, is the locally applied ramp rate and dim level. I can't even adjust it for some reason in the scene, see below: Thoughts? Thanks again for your help!

Hello! I’ve searched the forums for related answers, and didn’t find anything. If I’ve missed the answer elsewhere, sorry!! Please simply provide the link. No need to re-create the wheel here! Here is my scenario: I’m running Polsy v3.0.63 and ISY v5.4.4 . I have the Hue Node v0.1.11 (by xKing) installed (from the PG3 Node Server Store). My goal is to have ISY scenes, that include Hue lights, and have the scenes adjusted/triggered by controllers (Insteon Switches) within the scenes. As an example: I have the Insteon paddle switch called “L1 – Great Room – Cans” as a Controller for this scene, with the Hue lights all as responders. Based upon the screen shot above, when the scene is triggered (via the included switch), I would expect the ramp rate of the switch (2sec) and the brightness (50%) of the switch to be applied. In addition, I would expect Great Room Can 2 (a Hue bulb, in an always hot socket) to be set to the color red, and the remaining Hue bulbs to go to their default setting. However, this is the not the actual behavior. The switch mimics the “Fast On” behavior, and all hue lights in the scene simply go on to the last on setting. What is interesting is I am able to adjust the brightness of the Hue lights, via the Insteon Paddle, and if I trigger the scene via the ISY or Mobile app directly, the scene is applied correctly. Any thoughts? I feel like I am missing something stupid here. Thank you ahead of time for your help! ~J