kzboray

@Techman Yes, thank you. AC shows the firmware version, but not the revision code. And as you so aptly pointed out, knowing what versions of firmware actually have this vulnerability is the next step. @IndyMike started to document this by testing a variety of devices. I figured I'd have to do the same with the devices not on his list. I need to test approximately 129 devices. I'd like to cut that list down to a more manageable size by first identifying which versions of FW still have the ALL ON enabled but short of that I'll need to start testing myself. To do that I need a tool that will allow me to send a special packet (unknown as of yet) to trigger the ALL ON firmware code. IndyMike mentions something about sending FF, but I suspect there's more to it than that. So I started this tread hoping a few of my fellow propeller heads had some ideas.

Can someone suggest a way to test Insteon devices for the older firmware that supported ALL ON events? As a bonus if I could do this from a console and not have to physically remove devices to see the Rev. version that would be a huge win.

@aaronw I would add to @Javi 's post that all you need to do is contact UD support. They are without a doubt the best support I have ever had to work with. They are responsive and extremely helpful. And as Javi said it's free so why not open a ticket? Submit a ticket

@IndyMike Thank you for following up on this. I've got the stove all put together and it's integrated into a titled wall that makes it difficult to get back into. If you read the post above, I choose a different route to getting the signal from the stove that it's on without having to mess with the Napoleon stove's controller at all. However I did run an 8 conductor line between the stoves controller and a cabinet near by. So if need be I can tie that line into an I/O linc or something similar in the future. If my currently planned integration route fails. I'll have to pull the stove apart and I'll grab a few photos for you and maybe we can come up with a plan "B" Thank you for your offer to help! It means a great deal.

@dbwarner5 That would be a great solution, but unfortunately there are multiple start relays on the controller for this stove. When I contacted Napoleon as I indicated they first lied to me, and finally just stated they would not give me the information on what relays did what? I managed to figure out the three involved with turning on the gas line, but without knowing the supply amperage and the draw from the solenoids, I didn't want to add any additional current draw to the circuit. I'm positive there is a contact point on the controller that either presents a voltage or goes high when the stove is on, but without a schematic or input from Napoleon I choose a different route. I ended up buying a ESP32 which I setup as a bluetooth bridge, it's located in a cabinet about 4' from the stove controller. My hope is to use Home Assistant to signal the fans once the ESP32 detects that the stove is on. The only downside to this is that the remote that came with the stove can't be used or it screws up the ESP32 bridge. Phone app is fine. I bought the ESP32 linked below. I grabbed the one with an external bluetooth antenna. These are POE and have both bluetooth as well as ethernet built in. Olimex ESP-32-POE-ISO-EA Here's a link to the HA integration I found, but have yet to try. eFire HA Integration I haven't had time to put it all together as the install of the theater took precedence. But on paper it looks like a viable solution.

Just for reference here's a good restart of the NS. Nothing else changed. Just restart after restart. This was restart 27. 2023-12-26 13:05:14,441 Command udi_interface.interface INFO interface:_handleInput: Received stop from Polyglot... Shutting Down. 2023-12-26 13:05:14,443 Thread-8 udi_interface INFO lifx-poly:stop: Stopping LiFX Polyglot v2 NodeServer version 2.1.26 2023-12-26 13:05:20,271 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-12-26 13:05:20,273 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2023-12-26 13:05:20,274 MainThread udi_interface INFO __init__:<module>: User=000db9560fac_3 2023-12-26 13:05:20,275 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/000db9560fac_3 2023-12-26 13:05:20,276 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/000db9560fac_3 2023-12-26 13:05:20,276 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MGQ6Yjk6NTY6MGY6YWMiLCJwcm9maWxlTnVtIjozLCJsb2dMZXZlbCI6IklORk8iLCJ0b2tlbiI6Ik4qSTl3NSVzKEdEbEsyZDciLCJtcXR0SG9zdCI6ImxvY2FsaG9zdCIsIm1xdHRQb3J0Ijo4ODgzLCJzZWN1cmUiOjEsImlzUEczeCI6dHJ1ZSwicGczVmVyc2lvbiI6IjMuMi4xNyIsImlzeVZlcnNpb24iOiI1LjcuMSIsImVkaXRpb24iOiJGcmVlIn0= 2023-12-26 13:05:20,277 MainThread udi_interface INFO __init__:<module>: Loading interface module 2023-12-26 13:05:21,008 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2023-12-26 13:05:21,241 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2023-12-26 13:05:23,054 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2023-12-26 13:05:23,061 MainThread udi_interface INFO __init__:<module>: Loading node module 2023-12-26 13:05:23,062 MainThread udi_interface INFO __init__:<module>: Loading custom module 2023-12-26 13:05:23,063 MainThread udi_interface INFO __init__:<module>: Loading isy module 2023-12-26 13:05:23,063 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2023-12-26 13:05:23,064 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.4 Starting... 2023-12-26 13:05:23,521 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.2.17 [ISY: 5.7.1, Slot: 3] 2023-12-26 13:05:23,524 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '10.0.0.241', 'netmask': '255.255.255.0', 'broadcast': '10.0.0.255'} 2023-12-26 13:05:23,527 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-12-26 13:05:23,531 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-12-26 13:05:23,532 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 000db9560fac_3.cert key: 000db9560fac_3.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2023-12-26 13:05:23,534 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: lifxctl not found in database. 2023-12-26 13:05:23,537 MainThread udi_interface.interface INFO interface:addNode: Adding node LiFX Controller(lifxctl) [None] 2023-12-26 13:05:23,633 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-12-26 13:05:23,636 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:56:0f:ac_3 - MID: 2 Result: 0 2023-12-26 13:05:23,683 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-12-26 13:05:23,801 Thread-2 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-12-26 13:05:23,808 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Starting LiFX Discovery thread... 2023-12-26 13:05:23,922 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-12-26 13:05:24,006 Thread-6 udi_interface INFO lifx-poly:start: Starting LiFX Polyglot v2 NodeServer version 2.1.26, LiFX LAN: 1.2.7 2023-12-26 13:05:24,010 Thread-6 udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2023-12-26 13:05:24,253 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2023-12-26 13:05:24,528 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': '<h1>UDI LiFX Poly</h1>\n\n<p>This is a simple integration of LiFX lights to ISY994i. Please install via <a href="https://github.com/UniversalDevicesInc/polyglot-v2">Polyglot v2</a> Store. Report any problems on <a href="https://forum.universal-devices.com/topic/19021-polyglot-lifx-nodesever/">UDI User Forum</a>.</p>\n\n<h3>Custom parameters supported:</h3>\n\n<ul>\n<li><code>devlist</code> - link to a YAML manifest of devices, skips automatic discovery. See <a href="https://forum.universal-devices.com/topic/19021-polyglot-lifx-nodesever/?do=findComment&comment=257145">this post</a>.</li>\n<li><code>change_no_pon</code> - change of color won\'t power the device on.</li>\n<li><code>ignore_second_on</code> - power on command will be ignored if device is already on.</li>\n</ul>\n'} 2023-12-26 13:05:24,569 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2023-12-26 13:05:30,363 Thread-4 udi_interface INFO lifx-poly:_discovery_process: 9 bulbs found. Checking status and adding to ISY if necessary. 2023-12-26 13:05:30,731 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found Bulb: LIFX Chand-5 Mini 3D90ED(d073d53d90ed) 2023-12-26 13:05:30,734 Thread-4 udi_interface.interface INFO interface:addNode: Adding node LIFX Chand-5 Mini 3D90ED(d073d53d90ed) [None] 2023-12-26 13:05:31,034 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found LiFX Group: Chandelier 2023-12-26 13:05:40,856 Thread-4 udi_interface.interface INFO interface:addNode: Adding node LIFX Group Chandelier(chandelier) [None] 2023-12-26 13:05:41,155 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found Bulb: LIFX Bedroom-2 340A63(d073d5340a63) 2023-12-26 13:05:41,158 Thread-4 udi_interface.interface INFO interface:addNode: Adding node LIFX Bedroom-2 340A63(d073d5340a63) [None] 2023-12-26 13:05:41,474 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found LiFX Group: Bedroom 2023-12-26 13:05:50,388 Thread-4 udi_interface.interface INFO interface:addNode: Adding node LIFX Group Bedroom(bedroom) [None] 2023-12-26 13:05:50,670 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found Bulb: LIFX Chand-1 Mini 519C71(d073d5519c71) 2023-12-26 13:05:50,673 Thread-4 udi_interface.interface INFO interface:addNode: Adding node LIFX Chand-1 Mini 519C71(d073d5519c71) [None] 2023-12-26 13:05:51,280 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found Bulb: LIFX DiningRm-2 67D1DC(d073d567d1dc) 2023-12-26 13:05:51,284 Thread-4 udi_interface.interface INFO interface:addNode: Adding node LIFX DiningRm-2 67D1DC(d073d567d1dc) [None] 2023-12-26 13:05:51,623 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found LiFX Group: Dining Room 2023-12-26 13:06:00,525 Thread-4 udi_interface.interface INFO interface:addNode: Adding node LIFX Group Dining Room(diningroom) [None] 2023-12-26 13:06:00,806 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found Bulb: LIFX Chand-2 Mini 3F2BB9(d073d53f2bb9) 2023-12-26 13:06:00,809 Thread-4 udi_interface.interface INFO interface:addNode: Adding node LIFX Chand-2 Mini 3F2BB9(d073d53f2bb9) [None] 2023-12-26 13:06:01,450 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found Bulb: LIFX Bedroom-1 33D74D(d073d533d74d) 2023-12-26 13:06:01,453 Thread-4 udi_interface.interface INFO interface:addNode: Adding node LIFX Bedroom-1 33D74D(d073d533d74d) [None] 2023-12-26 13:06:02,027 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found Bulb: LIFX Chand-4 Mini 3D8961(d073d53d8961) 2023-12-26 13:06:02,030 Thread-4 udi_interface.interface INFO interface:addNode: Adding node LIFX Chand-4 Mini 3D8961(d073d53d8961) [None] 2023-12-26 13:06:02,666 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found Bulb: LIFX Chand-3 Mini 383074(d073d5383074) 2023-12-26 13:06:02,670 Thread-4 udi_interface.interface INFO interface:addNode: Adding node LIFX Chand-3 Mini 383074(d073d5383074) [None] 2023-12-26 13:06:03,259 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found Bulb: LIFX DiningRm-1 67165F(d073d567165e) 2023-12-26 13:06:03,262 Thread-4 udi_interface.interface INFO interface:addNode: Adding node LIFX DiningRm-1 67165F(d073d567165e) [None] 2023-12-26 13:06:03,604 Thread-4 udi_interface INFO lifx-poly:_discovery_process: NOTICE: Bulb count 9 is different, was 1 previously 2023-12-26 13:06:03,605 Thread-4 udi_interface INFO lifx-poly:_discovery_process: LiFX Discovery thread is complete.

@Bumbershoot Excellent write up thank you so much! Unfortunately using devlist.yml didn't help. It actually made things worse. Quick note I had to change file owner on the devlist.yml file to "polyglot" before it would work at all. Afterwards here's what it looks like on startup. Again it finds the bulbs, but doesn't seem to be able to add them. 2023-12-26 12:41:43,475 Command udi_interface.interface INFO interface:_handleInput: Received stop from Polyglot... Shutting Down. 2023-12-26 12:41:43,478 Thread-24 udi_interface INFO lifx-poly:stop: Stopping LiFX Polyglot v2 NodeServer version 2.1.26 2023-12-26 12:41:49,224 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-12-26 12:41:49,226 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2023-12-26 12:41:49,227 MainThread udi_interface INFO __init__:<module>: User=000db9560fac_3 2023-12-26 12:41:49,228 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/000db9560fac_3 2023-12-26 12:41:49,229 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/000db9560fac_3 2023-12-26 12:41:49,229 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MGQ6Yjk6NTY6MGY6YWMiLCJwcm9maWxlTnVtIjozLCJsb2dMZXZlbCI6IklORk8iLCJ0b2tlbiI6Ik4qSTl3NSVzKEdEbEsyZDciLCJtcXR0SG9zdCI6ImxvY2FsaG9zdCIsIm1xdHRQb3J0Ijo4ODgzLCJzZWN1cmUiOjEsImlzUEczeCI6dHJ1ZSwicGczVmVyc2lvbiI6IjMuMi4xNyIsImlzeVZlcnNpb24iOiI1LjcuMSIsImVkaXRpb24iOiJGcmVlIn0= 2023-12-26 12:41:49,230 MainThread udi_interface INFO __init__:<module>: Loading interface module 2023-12-26 12:41:49,733 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2023-12-26 12:41:50,036 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2023-12-26 12:41:52,067 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2023-12-26 12:41:52,073 MainThread udi_interface INFO __init__:<module>: Loading node module 2023-12-26 12:41:52,074 MainThread udi_interface INFO __init__:<module>: Loading custom module 2023-12-26 12:41:52,075 MainThread udi_interface INFO __init__:<module>: Loading isy module 2023-12-26 12:41:52,076 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2023-12-26 12:41:52,077 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.4 Starting... 2023-12-26 12:41:52,503 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.2.17 [ISY: 5.7.1, Slot: 3] 2023-12-26 12:41:52,505 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '10.0.0.241', 'netmask': '255.255.255.0', 'broadcast': '10.0.0.255'} 2023-12-26 12:41:52,508 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-12-26 12:41:52,513 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 000db9560fac_3.cert key: 000db9560fac_3.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2023-12-26 12:41:52,515 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-12-26 12:41:52,518 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: lifxctl not found in database. 2023-12-26 12:41:52,519 MainThread udi_interface.interface INFO interface:addNode: Adding node LiFX Controller(lifxctl) [None] 2023-12-26 12:41:52,614 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-12-26 12:41:52,616 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:56:0f:ac_3 - MID: 2 Result: 0 2023-12-26 12:41:52,662 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-12-26 12:41:52,884 Thread-2 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-12-26 12:41:52,890 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Starting LiFX Discovery thread... 2023-12-26 12:41:52,892 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Attempting manual discovery... 2023-12-26 12:41:53,032 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-12-26 12:41:53,150 Thread-6 udi_interface INFO lifx-poly:start: Starting LiFX Polyglot v2 NodeServer version 2.1.26, LiFX LAN: 1.2.7 2023-12-26 12:41:53,170 Thread-6 udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2023-12-26 12:41:53,170 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Found Bulb: Chand-1 Mini 519C71(d073d5599c71) 2023-12-26 12:41:53,175 Thread-4 udi_interface.interface INFO interface:addNode: Adding node Chand-1 Mini 519C71(d073d5599c71) [None] 2023-12-26 12:41:53,192 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Found Bulb: Chand-2 Mini 3F2BB9(d073d53f2bb9) 2023-12-26 12:41:53,211 Thread-4 udi_interface.interface INFO interface:addNode: Adding node Chand-2 Mini 3F2BB9(d073d53f2bb9) [None] 2023-12-26 12:41:53,239 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Found Bulb: Chand-3 Mini 383074(d073d5383074) 2023-12-26 12:41:53,255 Thread-4 udi_interface.interface INFO interface:addNode: Adding node Chand-3 Mini 383074(d073d5383074) [None] 2023-12-26 12:41:53,273 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Found Bulb: Chand-4 Mini 3D8961(d073d53d8961) 2023-12-26 12:41:53,283 Thread-4 udi_interface.interface INFO interface:addNode: Adding node Chand-4 Mini 3D8961(d073d53d8961) [None] 2023-12-26 12:41:53,301 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Found Bulb: Chand-5 Mini 3D90ED(d073d53d90ed) 2023-12-26 12:41:53,317 Thread-4 udi_interface.interface INFO interface:addNode: Adding node Chand-5 Mini 3D90ED(d073d53d90ed) [None] 2023-12-26 12:41:53,329 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Found Bulb: Vanity-1 3289B6(d073d53289b6) 2023-12-26 12:41:53,339 Thread-4 udi_interface.interface INFO interface:addNode: Adding node Vanity-1 3289B6(d073d53289b6) [None] 2023-12-26 12:41:53,343 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Found Bulb: Vanity-2 3303BC(d073d53303bc) 2023-12-26 12:41:53,346 Thread-4 udi_interface.interface INFO interface:addNode: Adding node Vanity-2 3303BC(d073d53303bc) [None] 2023-12-26 12:41:53,367 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Found Bulb: Vanity-3 3303CC(d073d53303cc) 2023-12-26 12:41:53,372 Thread-4 udi_interface.interface INFO interface:addNode: Adding node Vanity-3 3303CC(d073d53303cc) [None] 2023-12-26 12:41:53,377 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Found Bulb: Vanity-4 330C09(d073d5330c09) 2023-12-26 12:41:53,380 Thread-4 udi_interface.interface INFO interface:addNode: Adding node Vanity-4 330C09(d073d5330c09) [None] 2023-12-26 12:41:53,384 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Found Bulb: Vanity-5 349CB2(d073d5349cb2) 2023-12-26 12:41:53,388 Thread-4 udi_interface.interface INFO interface:addNode: Adding node Vanity-5 349CB2(d073d5349cb2) [None] 2023-12-26 12:41:53,404 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2023-12-26 12:41:53,416 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Found Bulb: Bedroom-1 33D74D(d073d533d74d) 2023-12-26 12:41:53,443 Thread-4 udi_interface.interface INFO interface:addNode: Adding node Bedroom-1 33D74D(d073d533d74d) [None] 2023-12-26 12:41:53,446 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Found Bulb: Bedroom-2 340A63(d073d5340a63) 2023-12-26 12:41:53,450 Thread-4 udi_interface.interface INFO interface:addNode: Adding node Bedroom-2 340A63(d073d5340a63) [None] 2023-12-26 12:41:53,452 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Found Bulb: DiningRm-1 67165F(d073d567165f) 2023-12-26 12:41:53,454 Thread-4 udi_interface.interface INFO interface:addNode: Adding node DiningRm-1 67165F(d073d567165f) [None] 2023-12-26 12:41:53,462 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Found Bulb: DiningRm-2 67D1DC(d073d567d1dd) 2023-12-26 12:41:53,466 Thread-4 udi_interface.interface INFO interface:addNode: Adding node DiningRm-2 67D1DC(d073d567d1dd) [None] 2023-12-26 12:41:53,469 Thread-4 udi_interface ERROR lifx-poly:_manual_discovery: Group Bathroom Vanity light Vanity-1 is not found 2023-12-26 12:41:53,470 Thread-4 udi_interface ERROR lifx-poly:_manual_discovery: Group Bathroom Vanity light Vanity-2 is not found 2023-12-26 12:41:53,471 Thread-4 udi_interface ERROR lifx-poly:_manual_discovery: Group Bathroom Vanity light Vanity-3 is not found 2023-12-26 12:41:53,472 Thread-4 udi_interface ERROR lifx-poly:_manual_discovery: Group Bathroom Vanity light Vanity-4 is not found 2023-12-26 12:41:53,472 Thread-4 udi_interface ERROR lifx-poly:_manual_discovery: Group Bathroom Vanity light Vanity-5 is not found 2023-12-26 12:41:53,473 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Group Bathroom Vanity, 0 members 2023-12-26 12:41:53,474 Thread-4 udi_interface ERROR lifx-poly:_manual_discovery: Group Bedroom light Bedroom-1 is not found 2023-12-26 12:41:53,474 Thread-4 udi_interface ERROR lifx-poly:_manual_discovery: Group Bedroom light Bedroom-2 is not found 2023-12-26 12:41:53,475 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Group Bedroom, 0 members 2023-12-26 12:41:53,478 Thread-4 udi_interface ERROR lifx-poly:_manual_discovery: Group Dining Room light DiningRm-1 is not found 2023-12-26 12:41:53,481 Thread-4 udi_interface ERROR lifx-poly:_manual_discovery: Group Dining Room light DiningRm-2 is not found 2023-12-26 12:41:53,482 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Group Dining Room, 0 members 2023-12-26 12:41:53,482 Thread-4 udi_interface ERROR lifx-poly:_manual_discovery: Group Chandelier light Chand-1 is not found 2023-12-26 12:41:53,483 Thread-4 udi_interface ERROR lifx-poly:_manual_discovery: Group Chandelier light Chand-2 is not found 2023-12-26 12:41:53,484 Thread-4 udi_interface ERROR lifx-poly:_manual_discovery: Group Chandelier light Chand-3 is not found 2023-12-26 12:41:53,484 Thread-4 udi_interface ERROR lifx-poly:_manual_discovery: Group Chandelier light Chand-4 is not found 2023-12-26 12:41:53,485 Thread-4 udi_interface ERROR lifx-poly:_manual_discovery: Group Chandelier light Chand-5 is not found 2023-12-26 12:41:53,486 Thread-4 udi_interface INFO lifx-poly:_manual_discovery: Group Chandelier, 0 members 2023-12-26 12:41:53,486 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Manual discovery is complete 2023-12-26 12:41:54,983 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': '<h1>UDI LiFX Poly</h1>\n\n<p>This is a simple integration of LiFX lights to ISY994i. Please install via <a href="https://github.com/UniversalDevicesInc/polyglot-v2">Polyglot v2</a> Store. Report any problems on <a href="https://forum.universal-devices.com/topic/19021-polyglot-lifx-nodesever/">UDI User Forum</a>.</p>\n\n<h3>Custom parameters supported:</h3>\n\n<ul>\n<li><code>devlist</code> - link to a YAML manifest of devices, skips automatic discovery. See <a href="https://forum.universal-devices.com/topic/19021-polyglot-lifx-nodesever/?do=findComment&comment=257145">this post</a>.</li>\n<li><code>change_no_pon</code> - change of color won\'t power the device on.</li>\n<li><code>ignore_second_on</code> - power on command will be ignored if device is already on.</li>\n</ul>\n'} 2023-12-26 12:41:55,024 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2023-12-26 12:41:55,339 MQTT udi_interface.interface INFO interface:_message: Successfully set lifxctl :: GV0 to 14 UOM 56 This is a very old issue with the LifX NS. Since PG3 it has never reliably added devices it finds; PG2 was much better. It has always required a few restarts to get all the devices connected. Several users over the years have abandoned the NS due to the many issues around this problem. I have multiple clients using them and I use LifX myself. The cost to replace them all is higher than I care to adsorb so I keep trying to work around the issues. Now having to restart the NS twenty to thirty times to get it to finally find and add all devices is just too much. I opened a ticket with the merry band of elves at UD. Maybe they can shed some light on whats going on.

@Bumbershoot Here's what happens when I try that. First without sudo...permission denied as expected. Then with sudo, but I still can't access the directory where the LifX NS is installed. I am using the default sudo password => admin. What did I do differently than you? [admin@polisy ~]$ cd /var/polyglot/pg3/ns [admin@polisy /var/polyglot/pg3/ns]$ ls 000db9560fac_1 000db9560fac_10 000db9560fac_11 000db9560fac_2 000db9560fac_3 000db9560fac_4 000db9560fac_5 000db9560fac_6 000db9560fac_7 000db9560fac_8 000db9560fac_9 [admin@polisy /var/polyglot/pg3/ns]$ sudo cd 000db9560fac_3 Password: [admin@polisy /var/polyglot/pg3/ns]$ ls -A 000db9560fac_1 000db9560fac_10 000db9560fac_11 000db9560fac_2 000db9560fac_3 000db9560fac_4 000db9560fac_5 000db9560fac_6 000db9560fac_7 000db9560fac_8 000db9560fac_9 [admin@polisy /var/polyglot/pg3/ns]$

@Bumbershoot Yes! Using devlist.yml was a good solution, but unfortunately it's no longer an option as the new NS directories are locked down and you can't change, add to or delete files.

I've been using the lifX NS since it was first Introduced. It has always been flaky but recently it has become almost unusable. This seems to be the problem. 2023-12-25 11:05:51,591 Thread-4 udi_interface ERROR lifx-poly:_discovery_process: discovery Error: WorkflowException: Did not receive [<class 'lifxlan.msgtypes.StateVersion'>] from d0:73:d5:32:89:b6 (Name: None) in response to <class 'lifxlan.msgtypes.GetVersion'> On startup of the node server during discovery inevitably this error will occur. It happens at different points during startup and for different bulbs (MAC addresses) with each restart; sometimes even prior to any bulbs being added. If the NS has found 10 bulbs and is adding them and this error happens on the second bulb that's it. Additional bulbs fail to be added. It always seems to occur early in the bulb addition process. Restarting the NS time after time will eventually result in a clean start, but it sometimes takes 30 restarts to get that one good time, and the minute I need to reboot for a system update etc. it's a nightmare to get the LifX NS running again. Any suggestions? System Configuration: *** OS *** FreeBSD polisy 13.2-RELEASE-p4 FreeBSD 13.2-RELEASE-p4 releng/13.2-n254638-d20ece445acf POLISY amd64 *** Package Information *** udx-3.5.4_4 ---- Name : isy Version : 5.7.1_7 LiFX Current Status: Connected Current Version: 2.1.26 [Production] Startup Log: 2023-12-25 11:20:32,347 Command udi_interface.interface INFO interface:_handleInput: Received stop from Polyglot... Shutting Down. 2023-12-25 11:20:32,350 Thread-37 udi_interface INFO lifx-poly:stop: Stopping LiFX Polyglot v2 NodeServer version 2.1.26 2023-12-25 11:20:37,943 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-12-25 11:20:37,946 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2023-12-25 11:20:37,947 MainThread udi_interface INFO __init__:<module>: User=000db9560fac_3 2023-12-25 11:20:37,948 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/000db9560fac_3 2023-12-25 11:20:37,949 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/000db9560fac_3 2023-12-25 11:20:37,949 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MGQ6Yjk6NTY6MGY6YWMiLCJwcm9maWxlTnVtIjozLCJsb2dMZXZlbCI6IklORk8iLCJ0b2tlbiI6Ik4qSTl3NSVzKEdEbEsyZDciLCJtcXR0SG9zdCI6ImxvY2FsaG9zdCIsIm1xdHRQb3J0Ijo4ODgzLCJzZWN1cmUiOjEsImlzUEczeCI6dHJ1ZSwicGczVmVyc2lvbiI6IjMuMi4xNyIsImlzeVZlcnNpb24iOiI1LjcuMSIsImVkaXRpb24iOiJGcmVlIn0= 2023-12-25 11:20:37,950 MainThread udi_interface INFO __init__:<module>: Loading interface module 2023-12-25 11:20:38,355 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2023-12-25 11:20:38,590 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2023-12-25 11:20:40,633 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2023-12-25 11:20:40,639 MainThread udi_interface INFO __init__:<module>: Loading node module 2023-12-25 11:20:40,640 MainThread udi_interface INFO __init__:<module>: Loading custom module 2023-12-25 11:20:40,641 MainThread udi_interface INFO __init__:<module>: Loading isy module 2023-12-25 11:20:40,642 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2023-12-25 11:20:40,642 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.4 Starting... 2023-12-25 11:20:41,068 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.2.17 [ISY: 5.7.1, Slot: 3] 2023-12-25 11:20:41,070 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '10.0.0.241', 'netmask': '255.255.255.0', 'broadcast': '10.0.0.255'} 2023-12-25 11:20:41,073 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-12-25 11:20:41,078 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-12-25 11:20:41,079 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 000db9560fac_3.cert key: 000db9560fac_3.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2023-12-25 11:20:41,080 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: lifxctl not found in database. 2023-12-25 11:20:41,083 MainThread udi_interface.interface INFO interface:addNode: Adding node LiFX Controller(lifxctl) [None] 2023-12-25 11:20:41,178 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-12-25 11:20:41,182 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:56:0f:ac_3 - MID: 2 Result: 0 2023-12-25 11:20:41,228 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-12-25 11:20:41,431 Thread-2 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-12-25 11:20:41,437 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Starting LiFX Discovery thread... 2023-12-25 11:20:41,573 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-12-25 11:20:41,626 Thread-6 udi_interface INFO lifx-poly:start: Starting LiFX Polyglot v2 NodeServer version 2.1.26, LiFX LAN: 1.2.7 2023-12-25 11:20:41,627 Thread-6 udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2023-12-25 11:20:41,854 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2023-12-25 11:20:41,933 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': '<h1>UDI LiFX Poly</h1>\n\n<p>This is a simple integration of LiFX lights to ISY994i. Please install via <a href="https://github.com/UniversalDevicesInc/polyglot-v2">Polyglot v2</a> Store. Report any problems on <a href="https://forum.universal-devices.com/topic/19021-polyglot-lifx-nodesever/">UDI User Forum</a>.</p>\n\n<h3>Custom parameters supported:</h3>\n\n<ul>\n<li><code>devlist</code> - link to a YAML manifest of devices, skips automatic discovery. See <a href="https://forum.universal-devices.com/topic/19021-polyglot-lifx-nodesever/?do=findComment&comment=257145">this post</a>.</li>\n<li><code>change_no_pon</code> - change of color won\'t power the device on.</li>\n<li><code>ignore_second_on</code> - power on command will be ignored if device is already on.</li>\n</ul>\n'} 2023-12-25 11:20:41,977 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2023-12-25 11:20:51,287 Thread-4 udi_interface INFO lifx-poly:_discovery_process: 14 bulbs found. Checking status and adding to ISY if necessary. 2023-12-25 11:20:51,633 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found Bulb: LIFX Chand-4 Mini 3D8961(d073d53d8961) 2023-12-25 11:20:51,636 Thread-4 udi_interface.interface INFO interface:addNode: Adding node LIFX Chand-4 Mini 3D8961(d073d53d8961) [None] 2023-12-25 11:20:51,966 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found LiFX Group: Chandelier 2023-12-25 11:20:57,833 Thread-4 udi_interface ERROR lifx-poly:_discovery_process: discovery Error: WorkflowException: Did not receive [<class 'lifxlan.msgtypes.StateVersion'>] from d0:73:d5:51:9c:71 (Name: None) in response to <class 'lifxlan.msgtypes.GetVersion'> 2023-12-25 11:20:57,835 Thread-4 udi_interface INFO lifx-poly:_discovery_process: NOTICE: Bulb count 1 is different, was 0 previously 2023-12-25 11:20:57,836 Thread-4 udi_interface INFO lifx-poly:_discovery_process: LiFX Discovery thread is complete. 2023-12-25 11:20:58,066 MQTT udi_interface.interface INFO interface:_message: Successfully set lifxctl :: GV0 to 1 UOM 56 2023-12-25 11:21:07,755 MQTT udi_interface.interface INFO interface:_message: Successfully set d073d53d8961 :: GV1 to 45800 UOM 56 2023-12-25 11:21:07,840 MQTT udi_interface.interface INFO interface:_message: Successfully set d073d53d8961 :: GV2 to 65535 UOM 56 2023-12-25 11:21:07,877 MQTT udi_interface.interface INFO interface:_message: Successfully set d073d53d8961 :: GV3 to 65535 UOM 56 2023-12-25 11:21:07,917 MQTT udi_interface.interface INFO interface:_message: Successfully set d073d53d8961 :: CLITEMP to 9000 UOM 26 2023-12-25 11:21:08,044 MQTT udi_interface.interface INFO interface:_message: Successfully set d073d53d8961 :: ST to 0 UOM 51 2023-12-25 11:21:08,086 MQTT udi_interface.interface INFO interface:_message: Successfully set d073d53d8961 :: GV5 to 1 UOM 2 2023-12-25 11:21:08,147 MQTT udi_interface.interface INFO interface:_message: Successfully set d073d53d8961 :: RR to 0 UOM 42

@david-4 I'd suggest you open a support ticket for this question. If your router isn't setting the DHCP address via a DHCP reservation then Michel's merry band of elf's will need to sleigh this beast.

For lighting Insteon is still king, particularly due to the way it handles scenes for multi switch circuits, and it's ability to send signals both via the AC line and OTA. There is a caveat to this because it sends the signal at the same zero point on the AC cycle and noise can be a problem. If you have a device or devices on a particular leg of your homes electrical lines; something as simple as a noisy wall wart. This can cause signal degradation that can be hard to track down. The positive here is that when you find the device causing the noise and eliminate it with prejudice your problems go away completely. Also as compared to Z-Wave a fully meshed Insteon deployment seems to be much better at getting signals to out laying regions of a home. i.e. the backyard lighting, detached garages, etc If it's available from Insteon and I am working in an Insteon home then that's my first choice for what ever is needed from wall outlets to garage door openers. I avoid Z-wave explicitly for lighting due to it's many issues with creating scenes. Each manufacturers implementation is different and even from the same manufacturer different products can behave differently. I believe in the Z-wave 800 there have been some changes to "associations" (scenes) that attempts to address this, but it's not robust and still needs changes to be as easy to use as Insteon. There are single case situations where Z-wave or other technologies will be a better fit. Z-wave LR (Long Range) is an example of that. If you have a gate that's a quarter mile from the house, Z-wave LR would be my first choice for that controller. Obviously there will be other isolated situations that require you to become creative, but for lighting I'd stick with Insteon.

@K-bert Try changing the URL to https://xxx.xxx.xxx.xxx:3000/ where xxx is the IP address of your eisy.

I've experienced similar issues with the outdoor modules. The fix was to install more Insteon devices creating a better mesh around the area where the outdoor module was located.

@BGage You have to use adjust scene for each switch in the scene. I wrote a how to a while back for setting up automated brightness changes by time of day. It talks a lot about adjust scene and how to use it correctly. Take a look at it and I think it will fix your problems. How to setup automated brightness changes

I have a fireplace already installed that has a ceiling exhaust port that I'd like to add something like this to for basic on / of monitoring of the fireplace. I want to turn on a couple of ceiling fans when it's in use. Or if someone has knowledge of Napoleon fireplace controllers and can direct me to what pins on the controller I might tap off of when it is on, that would work too. Napoleon has bar none the worst customer support I've ever experienced. When I called to ask about this I was on hold over two days for over four hours before someone answered. After talking a couple of field tech's this is the norm. Once i final got someone on the phone they lied about the controller having outputs that trigger when the fireplace is turned on saying they didn't support home automation. I emphasized I didn't want home automation but simply to know what pins on the controller to use to trigger a relay. Obviously it has to activate the gas solenoid so somewhere on the controller is some kind of a relay that I could tap off of. But they refused to tell me and lied about it even existing. Sorry for the rant, but I thought I'd share and if anyone has recommendations for either a wifi type thermometer that has a supported NS available that I can stick in the vent or has experience with the Napoleon controllers and can point me to what pins to use, I would appreciate it.

You might check out the Noyito-Relay NS. It supports several relay modules that you could easily trigger from 12v. https://www.amazon.com/NOYITO-2-Channel-Module-Control-Intelligent/dp/B081RM7PMY There is also the BASAO NS which also supports relay control. https://github.com/sjpbailey/udi-poly-baspi-sys6u4r2ao-master-v3/blob/master/README.md

Here's the link for a thermostat. https://www.nuheat.com/products/thermostats/home-thermostat This is supported via the ST-NuHeat Nodeserver in the production store.

@oskrypuch Honestly the worst case scenario is that you have all your programs disabled and simply restart IoX to fix it. It's an extra step, but not catastrophic should things go wonky.

@AllDigital You can setup a duress user. I often use 5150 as the code. In this example it's user 32 which is set as duress in Area RC and User RC. That gets the alarm company on board and while I haven't tried it. I bet you can activate that code or user from the Elk NS. I don't have access to an ELK NS atm to try, but this is how I'd set it up.

Updated from PG3x 3.2.8 to 3.2.9 on a Polisy Pro. All Programs where marked as disabled and had to be manually re-enabled. No other issues noted at this time.

AC upgrade Packages. I haven't used SSH since 5.5.x

Upgraded Polisy IoX 5.7.0, PG3x 3.2.4, OS 13.1 to IoX 5.7.0, PG3x 3.2.8, OS 13.2 Took about 5 minutes with two reboots that happened automatically. No issues on restart.

@bmercier Thank you! You got it in one. Disabled VPN and no more 406.

PoliSy Pro PG3x 3.2.28 IoX 5.7 I've tried on two different Polisy both up to date and they both give a 406 error when I click the authenticate button.