kzboray

Yes, I moved all my LifX to Home Assitant.

Thank you @IndyMike I especially appreciate the testing methodology and tools. Your detailed post of the bit difference that creates an all on event is exactly the kind of info I've been trying to figure out.

@IndyMike Prior to 2016/17 most Insteon devices had an ALL ON function in FW. It was notorious for causing ALL ON events unexpectedly so they removed it reportedly from all devices, but as it turns out it's still present in PLM's, Micro Modules, and IOLinc's. It may be present in other devices as well. i3 devices seem to be free from ALL ON in FW. I am going to start replacing all IOLinc's and Micro Modules with similar Shelly devices to eliminate as many potential ALL ON Events as possible for my clients. There's nothing to be done about the PLM except to put pressure on Insteon to fix it. In the mean time I will also be removing all programs that change back lighting because Michel has indicated this is a common cause of ALL ON events (See the post above.). Some of my clients will hate this and I will need to evaluate each situation independently, but I can't have pumps running dry, security gates opening, or fire-pits coming on unattended. Michel also detailed how this happens and given the processing speed increase with Polisy and eisy, it makes sense to me that this can occur more often. So as indicated I am going to start replacing HW to eliminate this possibility.

Just a quick update. Micro Module 2443-222 v.49 also responds to an ALL ON command. EDIT: I also left a note on the Insteon forums about this and I hope they remove the ALL ON from FW soon.

@paulbates I had no idea the "ALL ON" button in AC would activate the ALL ON bit in FW. I always thought it would just send an ON to all devices. I had never tried it until your post. Thank you! Using the "ALL ON" button in AC produced the following results in my home. I'll have to test at my clients...all of them now 8( Micro module 2443-222 FW v.48 turned on. PG3x NS controlling Harmony Hub turned on to last used state. PG3x NS controlling Lifx lights in all locations turned on to last used state I/OLinc 2450 v 4.1 controlling a GDO opened the garage door. I have two new I/O linc modules that are FW version .49 to test with but they won't add to the system. I have opened a ticket to get that resolved. If I find they ignore the ALL ON I will update this post. It's interesting that the Harmony Hub and LifX NS's also responded to the ALL ON button press. I don't believe this is a desirable feature and will let @Jimbo.Automates and @Michel Kohanim / xKing know.

@SMorgan I have a client that has a Insteon only installation working first on an ISY994i and now a Polisy. After the initial install in 2016 there were ZERO events that couldn't be explained. Recently in the last three months they have had three events that UD and the community would call ALL ON events. This makes little sense to me since they have had the same programming in place with minor changes for years and the same Insteon devices. The other piece of this puzzle that makes little sense to me is that the consensus seems to be to remove devices from any scenes and any programs to avoid possible ALL ON events. If they can't be in a scene or part of a program what is the use of having smart devices in the home? In each case the logs show that the SYSTEM was responsible for the device being activated. I'm not convinced this is the classic ALL ON event that used to plague the Insteon brand. It is also impossible to get any real information on what devices have the ALL ON FW. I have reached out to the community here and also Insteon directly. Insteon simply ignored my emails which asked for a list of FW versions that were susceptible to the ALL ON command or a way to check devices myself. Unfortunately I have also learned that all past and present PLM's still have the ALL ON command set potentially making this entire venture of tracking down which individual devices with ALL ON supported in FW mote. In my clients case the one common denominator has been the GDO controlled by a 74551. It has activated three times now in the last three months. Once by itself, and the other two times in combination with first 4 other devices, and the second time with two other devices. Unfortunately the GDO is part of a scene with eight (8) button switches and several 2477s's and integrated into the ELK alarm system for FOB control as well. All of this making it impossible to decouple from the scene or programs. Short of catching one of these events live on the event viewer I don't know how to give adequate feedback on the root cause. If it happens again I am going to put the ISY994i back in place which ran perfectly for almost 6 years without incident. Unfortunately this will mean a dramatic reduction in integration for the client as they have several system using PG3x. But I can't have their fire-pit coming on in the middle of the night again. The last time this happened the day before the ALL ON event the fire-pit had been covered with plywood for protection during a small construction project. If the fire-pit had come on even one day before there would have been a fire that could have spread to who knows where. Since this happened at 3am no one would have known until the fire alarm went off.

I may be missing something here so I thought I'd throw this out to the community. I am trying to use an i3 Dial to dim / brighten LifX lights connected via PG3x. There doesn't seem to be a way to capture the dial movement in IoX or did I miss something? I also tried writing a program using STATUS set to 25% and then forcing the LifX lights to 25% brightness, but that failed to work as well. It's as if changes to the dial don't actually register in IoX, but that's not entirely true because if you turn the dial clockwise devices in a scene will eventually respond in the full ON. You cannot do the opposite however and turn the dial counter clockwise to turn OFF the same device/s in the scene. Only clockwise movement works and even this requires almost a full turn of the dial before you get a response. The dial seems to be very limited and I am wondering if anyone else has tried anything like this with any success?

@NewTech I'm guessing you didn't default the devices you are adding to the eisy. Because of this you are getting the link tables from your old devices. You will need to default not only your devices, but your PLM as well if you really want to start fresh. Otherwise you are going to continue to pick up pieces of your old configuration. Factory Resetting Insteon Devices

@WestSeattleBoi This is probably due to a bug that was introduced with an earlier version of IoX. The fix is to contact support by opening a ticket and have UD give you a hand recovering your system. Michel was able to assist me when I had the same issue.

@CTBigman As @Techman indicated you will need to set each device in the scene and you have to set Scene | Controller | Set for each device as well. This has to be done using the adjust scene function. As a reference you can read this post. Adjust Scene And here's the program that switches my hall lights from 100% during the day to 35% at night. This allows local control. Notice how each of the three switches has four program changes made to make this work. I have asked UD to make this more intuitive, but it's not really something that's a priority. You really should only have to set Scene | Controller | Set once, but you have to actually call out every permutation possible to make it work correctly. Don't be fooled by some of these program lines looking exactly the same. the differences are in the adjust scene area not shown. Read the linked doc above. 2nd FL Hall Lights Power Setting - [ID 000A][Parent 001F] If From 12:00:00AM To Sunrise (same day) Then In '2nd Floor Hallway / 2nd Fl Hall Lights(M) West' Set '2nd Floor Hallway / 2nd Fl Hall Lights(M) West' To 35% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(M) West' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) East' To 35% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(M) West' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) North' To 35% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(S) East' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) East' To 35% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(S) East' Set '2nd Floor Hallway / 2nd Fl Hall Lights(M) West' To 35% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(S) East' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) North' To 35% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(S) North' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) North' To 35% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(S) North' Set '2nd Floor Hallway / 2nd Fl Hall Lights(M) West' To 35% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(S) North' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) East' To 35% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Floor Hallway' Set '2nd Floor Hallway / 2nd Fl Hall Lights(M) West' To 35% in 0.1 seconds In '2nd Floor Hallway / 2nd Floor Hallway' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) East' To 35% in 0.1 seconds In '2nd Floor Hallway / 2nd Floor Hallway' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) North' To 35% in 0.1 seconds Else In '2nd Floor Hallway / 2nd Fl Hall Lights(M) West' Set '2nd Floor Hallway / 2nd Fl Hall Lights(M) West' To 100% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(M) West' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) North' To 100% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(M) West' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) East' To 100% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(S) East' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) East' To 100% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(S) East' Set '2nd Floor Hallway / 2nd Fl Hall Lights(M) West' To 100% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(S) East' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) North' To 100% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(S) North' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) North' To 100% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(S) North' Set '2nd Floor Hallway / 2nd Fl Hall Lights(M) West' To 100% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Fl Hall Lights(S) North' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) East' To 100% in 0.1 seconds, No retries In '2nd Floor Hallway / 2nd Floor Hallway' Set '2nd Floor Hallway / 2nd Fl Hall Lights(M) West' To 100% in 0.1 seconds In '2nd Floor Hallway / 2nd Floor Hallway' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) East' To 100% in 0.1 seconds In '2nd Floor Hallway / 2nd Floor Hallway' Set '2nd Floor Hallway / 2nd Fl Hall Lights(S) North' To 100% in 0.1 seconds

@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

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.

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

@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

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.