andrew67 Posted September 8, 2022 Posted September 8, 2022 I have a system with both hue and insteon parts. I recently migrated to PG3, IOP, and am running all the latest versions. Everything seems OK, and connected. I have created some groups of hue lights in the hue app app, which show properly in PG3, and in the Navigation pane of IOP. one example is "kitchen hue" which the hue hub has controlling about 8 lights. If I click on "kitchen hue," change a setting, and press the appropriate button, the lights respond as expected. I also have Kitchen hue as part of a scene called Kitchen Main. Each controller in Kitchen Main has "kitchen hue" set at my desired levels and commands. For example for Keypad E1.B "kitchen hue" has "Color temperature 2400K, Brightness 32 in 100ms, as link type "Command" However, when I press the button, only the insteon lights are affected. The Hue do not change their intensity or color. This all worked prior to a couple of power failures we had (before the upgrades top IOP and PG3), and I'm confused as to what could be going on.... I compared the device links tables (which I could read, so communication with the PLM is OK...) and found one record mismatch, the 00 was 1F on the ISY's table. I have two additional questions, -Is this the correct way to operate hue lights with insteon controllers? Is there a better way to trigger hue lights to a particular mode? I have not tried doing anything complex with them yet since this seems super basic, and I can't really see how to send multiple commands, I'd like to make color loops work across a series of lights, but can't seem to figure out how that would be done with this type of interface. Thoughts?
andrew67 Posted September 9, 2022 Author Posted September 9, 2022 Restore PLM seems to have fixed this issue. I don't know how a system can lose its PLM links, in only one direction, but apparently that is what happened. I do not know if this is a part of the upgrade procedure, or just random.
Recommended Posts