x046866x

I just went in today and noticed there is an update. I updated the PlugIn and everything magically re-appeared. There is now a cost component, but if it will continue to work the price is acceptable. NOTE: I still see some of the same ugly error messages, but things appear to be working.

I deleted the PlugIn, restarted both ISY and Hue, re-installed the Plugin; same error. It seems to south just after discovery and I see the "db_getNodeDrivers:..... not found in database" 2025-10-25 09:56:29.203 Thread-3 (parameter_handler) udi_interface INFO hue:_discover: Hub 192.168.1.31 4 bulbs found. Checking status and adding to ISY if necessary. 2025-10-25 09:56:29.203 Thread-3 (parameter_handler) udi_interface INFO hue:_discover: Hub 192.168.1.31 Found Extended Color Bulb: Garage smart plug(c62bbb770a285f) 2025-10-25 09:56:29.203 Thread-3 (parameter_handler) udi_interface.interface WARNING interface:db_getNodeDrivers: c62bbb770a285f not found in database. 2025-10-25 09:56:29.203 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: Exception in thread 2025-10-25 09:56:29.203 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: Thread-3 (parameter_handler) 2025-10-25 09:56:29.203 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: : 2025-10-25 09:56:29.203 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2025-10-25 09:56:29.203 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.11/threading.py", line 1045, in _bootstrap_inner 2025-10-25 09:56:29.204 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: self.run() 2025-10-25 09:56:29.204 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.11/threading.py", line 982, in run 2025-10-25 09:56:29.205 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2025-10-25 09:56:29.205 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9025fac_10/hue.py", line 65, in parameter_handler 2025-10-25 09:56:29.205 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: self.discover() 2025-10-25 09:56:29.205 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9025fac_10/hue.py", line 188, in discover 2025-10-25 09:56:29.205 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: self._discover(idx) 2025-10-25 09:56:29.206 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9025fac_10/hue.py", line 222, in _discover 2025-10-25 09:56:29.206 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: self.poly.addNode(HueEColorLight(self.poly, self.address, address, name, light['id'], light, hub_idx, parent_dev, zb_conn)) 2025-10-25 09:56:29.206 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 09:56:29.206 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 09:56:29.206 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^

I've tried all the basics. I've deleted the node, rebooted, and re-installed it. Still NG. I will continue poking through the forum. I saw there was a beta version, but not sure if that is more well suited to the newer bridge.

I'm not sure if it is related to the 6.0.0 upgrade, but my Hue plugin is not longer operational. It finds the bridge, and detects that I have 4 devices, but they all fail to load. 2025-10-25 08:24:37.934 Thread-3 (parameter_handler) udi_interface INFO hue:_discover: Hub 192.168.1.31 4 bulbs found. Checking status and adding to ISY if necessary.2025-10-25 08:24:37.934 Thread-3 (parameter_handler) udi_interface INFO hue:_discover: Hub 192.168.1.31 Found Extended Color Bulb: Garage smart plug(c62bbb770a285f) 2025-10-25 08:24:37.934 Thread-3 (parameter_handler) udi_interface.interface WARNING interface:db_getNodeDrivers: c62bbb770a285f not found in database. 2025-10-25 08:24:37.934 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: Exception in thread 2025-10-25 08:24:37.934 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: Thread-3 (parameter_handler) 2025-10-25 08:24:37.934 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: : 2025-10-25 08:24:37.935 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2025-10-25 08:24:37.935 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.11/threading.py", line 1045, in bootstrapinner 2025-10-25 08:24:37.935 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: self.run() 2025-10-25 08:24:37.936 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.11/threading.py", line 982, in run 2025-10-25 08:24:37.936 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2025-10-25 08:24:37.936 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9025fac_1/hue.py", line 65, in parameter_handler 2025-10-25 08:24:37.936 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: self.discover() 2025-10-25 08:24:37.937 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9025fac_1/hue.py", line 188, in discover 2025-10-25 08:24:37.937 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: self._discover(idx) 2025-10-25 08:24:37.937 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9025fac_1/hue.py", line 222, in _discover 2025-10-25 08:24:37.937 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: self.poly.addNode(HueEColorLight(self.poly, self.address, address, name, light['id'], light, hub_idx, parent_dev, zb_conn)) 2025-10-25 08:24:37.938 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.938 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.938 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.938 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.938 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.938 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.938 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.938 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.938 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.938 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.938 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.938 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.938 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.938 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.939 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.939 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.939 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.939 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.939 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.939 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.939 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.939 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.939 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.939 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.939 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.939 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.940 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.940 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.940 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.940 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.940 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.940 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.940 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.940 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.940 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.940 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.940 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.940 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.940 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.940 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.940 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.941 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.942 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.942 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.942 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.942 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.942 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.942 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.942 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.942 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.942 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.942 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.942 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.942 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.942 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.942 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.943 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.944 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.945 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.945 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9025fac_1/node_types.py", line 259, in init 2025-10-25 08:24:37.945 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: self.updateInfo() 2025-10-25 08:24:37.945 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9025fac_1/node_types.py", line 293, in updateInfo 2025-10-25 08:24:37.945 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: self._updateInfo() 2025-10-25 08:24:37.945 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9025fac_1/node_types.py", line 418, in _updateInfo 2025-10-25 08:24:37.946 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: super()._updateInfo() 2025-10-25 08:24:37.946 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9025fac_1/node_types.py", line 385, in _updateInfo 2025-10-25 08:24:37.946 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: super()._updateInfo() 2025-10-25 08:24:37.946 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9025fac_1/node_types.py", line 303, in _updateInfo 2025-10-25 08:24:37.946 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: self.brightness = self.data['dimming']['brightness'] 2025-10-25 08:24:37.947 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ~ 2025-10-25 08:24:37.947 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ~ 2025-10-25 08:24:37.947 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ~ 2025-10-25 08:24:37.947 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ~ 2025-10-25 08:24:37.947 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ~ 2025-10-25 08:24:37.947 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ~ 2025-10-25 08:24:37.947 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ~ 2025-10-25 08:24:37.947 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ~ 2025-10-25 08:24:37.947 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ~ 2025-10-25 08:24:37.947 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.947 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.947 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.947 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.948 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.948 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.948 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.948 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.948 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.948 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.948 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: ^ 2025-10-25 08:24:37.948 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: KeyError 2025-10-25 08:24:37.948 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: : 2025-10-25 08:24:37.948 Thread-3 (parameter_handler) udi_interface ERROR udi_interface:write: 'dimming' 2025-10-25 08:24:39.322 MQTT udi_interface.interface INFO interface:_message: Profile installation finished

I've noticed that over the past week or so none of my timed programs were executing. I have a couple that turn lights off at 10:30PM every night but I woke up in the morning to find all the lights still on. I performed a reboot and everything seemed to work for about 4 days and then exhibited the same behavior (all lights on in the AM). I also noticed that on every reboot I get a message telling me the "Upgrade complete!", but I don't think it is actually upgrading every time. I did it twice in one day and receive the same message every time. I did it again this morning and received the "Upgrade complete!" notification. Thoughts?

Wait.....I dug through the code again and found this. Pretty sure this is what I was looking for. COLORS_HCSEL-1 = Aqua COLORS_HCSEL-2 = Azure COLORS_HCSEL-3 = Beige COLORS_HCSEL-4 = Blue COLORS_HCSEL-5 = Chartreuse COLORS_HCSEL-6 = Coral COLORS_HCSEL-7 = Crimson COLORS_HCSEL-8 = Forest Green COLORS_HCSEL-9 = Fuchsia COLORS_HCSEL-10 = Golden COLORS_HCSEL-11 = Gray COLORS_HCSEL-12 = Green COLORS_HCSEL-13 = Hot Pink COLORS_HCSEL-14 = Indigo COLORS_HCSEL-15 = Lavender COLORS_HCSEL-16 = Lime COLORS_HCSEL-17 = Maroon COLORS_HCSEL-18 = Navy Blue COLORS_HCSEL-19 = Olive COLORS_HCSEL-20 = Red COLORS_HCSEL-21 = Royal Blue COLORS_HCSEL-22 = Tan COLORS_HCSEL-23 = Teal COLORS_HCSEL-24 = White

I am trying to use a small program that sets all of my Hue devices to the same color. The program works fine: Set 'MyHueDeviceName' Set Color '$HueColorCode Index' and I just set '$HueColorCode' variable to an integer and call the program and all works fine. The problem is that I don't know what the index values correspond to. I mimicked the drop-down and am able to set colors using index 1 to 20, but any value higher than that doesn't have any affect. I found a table somewhere that showed the values from 1 to 145 (see below for an example) but this does not seem to be what the Polyglot integration is using. I downloaded the code expecting to see it somewhere in there, but to no avail (likely because I just don't know what I'm looking for). What I'm looking for is something like: 1=Aqua 2=Azure 3=Beige etc. Any ideas? Table I dug up (somewhere): # Value: Name: # 1 Alice Blue # 2 Antique White # 3 Aqua # 4 Aquamarine # 5 Azure # 6 Beige # 7 Bisque # 8 Black # 9 Blanched Almond ... # 132 Snow # 133 Spring Green # 134 Steel Blue # 135 Tan # 136 Teal # 137 Thistle # 138 Tomato # 139 Turquoise # 140 Violet # 141 Wheat # 142 White # 143 White Smoke # 144 Yellow # 145 Yellow Green

FURTHER UPDATE: I performed the (virtual) "three-finger-salute" (Windows CTRL-ALT-DEL) and when it came back up the Interview was successful. I'm not sure if this was leftover cobwebs or kinks still being ironed out or the ever present problem somewhere between the chair and the keyboard....the first device was finally added. I'm now adding the second. It look a NUMBER of clicks on the device to get recognized but it was finally recognized and an "interview" attempt was made but was not successful. I did a reboot and when it came back up did a Synchronize and it interviewed successfully. It appears I'm in. Sorry for the verbose thread....but hopefully my experience might be helpful to others. Some takeaways: - Toggle the device you are adding MANY times in order to ensure recognition. - Re-boot before trying the Synchronize.

UPDATE: Minutes after I hit <SUBMIT> I tried the outdoor switch again and it was recognized by the eisy. When I went back to the Admin Console, however, it was not there. I then tried the Synchronize and it seemed to be thinking as it queried "Device 2" and said "Timeout in 336", but that dialog went away in about 20 seconds. Still no love on the device in the console though. I do see this now on the X-Ray DH All Devices: Devices list: 1 Interview Not done 2 Interview Not done I am not getting any activity on the "Interview"....is that just between the devices?

The nodes are completely gone from my configuration. This implies that I didn't follow the instructions to the letter....but I don't have so many that it would be impossible to set up again (I think 3 right now). I did try this: but nothing ever happened. I reset one of the devices (the GE outdoor switch) and am trying to set it up as new, but when I go to add a new device I get this screen: and regardless of how I press the button on the Z-Wave device it does not seem to acknowledge the device. The new Z-Matter dongle is in the same location as my ISY994 was and that is only about 20 feet from the switch(e) I'm trying to dd. FYI: I do see the following XML in the "Z-Wave X-Ray"->"All Scene Links", which could be my old devices? (they were all switches). <groups> <group id="ADR0001"> <ctl id="ADR0001"> <rsp/> </ctl> </group> <group id="54661"> <ctl id="54661"> <rsp> <link type="native" node="4D FF 6 1" linkdef="I_RELAY"> <p id="OL"> <val prec="0" uom="51">100</val> </p> </link> <link type="native" node="14 4D 16 1" linkdef="I_RELAY"> <p id="OL"> <val prec="0" uom="51">100</val> </p> </link> <link type="native" node="31 9F 4D 1" linkdef="I_RELAY"> <p id="OL"> <val prec="0" uom="51">100</val> </p> </link> <link type="native" node="47 8D EA 1" linkdef="I_RELAY"> <p id="OL"> <val prec="0" uom="51">100</val> </p> </link> <link type="native" node="49 8 BF 1" linkdef="I_RELAY"> <p id="OL"> <val prec="0" uom="51">100</val> </p> </link> </rsp> </ctl> </group> <group id="879"> <ctl id="879"> <rsp> <link type="native" node="39 50 B1 1" linkdef="I_DIMMER"> <p id="OL"> <val prec="0" uom="51">100</val> </p> <p id="RR"> <val prec="0" uom="25">28</val> </p> </link> <link type="native" node="2F FC 93 1" linkdef="I_DIMMER"> <p id="OL"> <val prec="0" uom="51">100</val> </p> <p id="RR"> <val prec="0" uom="25">28</val> </p> </link> </rsp> </ctl> </group> <group id="28998"> <ctl id="28998"> <rsp> <link type="native" node="4C D3 55 2" linkdef="I_RELAY"> <p id="OL"> <val prec="0" uom="51">100</val> </p> </link> </rsp> </ctl> </group> </groups>

It seems I may have the same problem? I had an ISY994 with the Z-Wave board and it recognized my devices just fine (GE Enbrighten switches, GE outdoor light switch), but now I get nothing on my eisy. Everything is updated to 5.5.3, the Z-Matter dongle appears to be functioning. Although perhaps it is not? It responds to the Z-Wave X-Ray "DHController" with a bunch of information and the "All Scene Links" seems to show some hardware references, but nothing shows up anywhere on the Admin Console. I noticed that none of my previous Z-Wave devices were migrated after following instructions.

Same here. I can't really do anything on the isy portal as I get: and the hover-over on the portal shows: Approval at the eisy screen fails:

Understood. Just suggesting that ones time may be better spent supporting the product (any product really) in it's most natural and simplest form. It'll be less to figure out later. That being said; I agree that it should be made available in some capacity as there will always be cases where it is needed.

I work in both commercial and residential settings and while I don't have my ISY (soon to be eisy) set up in the commercial space I am a BIG proponent of the KISS methodology...and DHCP is simple! If I manage something manually then I need to remember that manual setting and my human-RAM just isn't what it used to be. My DHCP server will reserve a lease to a MAC for as long as I'm connecting. I haven't tested when it might release the address, but the persistent devices stick around so it is not a problem. I'm sure I could check the lease TTL in the DHCP server (I'm running a PiHole), but fortunately I don't have to. I'm sure I can see some commercial situations where a static IP would be helpful/necessary....but I'd rather spend my time figuring out why DHCP wouldn't work and fixing that. DHCP means one less thing to figure out when things go haywire down the road and makes things more resilient to changes outside the eisy/ISY scope. Especially in a commercial configuration where sub-nets beyond the simple 192.168.1 space exist (which, I understand, may be why you need static IP...I get it). I'm not saying they shouldn't allow static IP support, but I completely understand why it is disabled by default as an accidental change by someone that doesn't completely understand that level of networking would result in a lot of unnecessary support call noise. I get that too.

Any news on "eisy" availability?