Diesel

Smart outlet with hardware built-in watchdog that monitors your gateway connectivity Keep Connect | Automatic Router Rebooter Rebooter Pro – Automatic Router and Modem Rebooter Also possible to reboot most modems with a curl command. For example for Aaris Surfboard cable modems curl -u admin:password http://<modem ip>/goform/Goform_Reboot (Replace admin:password with your credentials).

Create 3 scenes. Don't control individual devices. Scene A - All basement lights you want turned ON with keypad button X Scene B - All the OTHER basement lights NOT in Scene A you want turned OFF with keypad button X Scene Basement KPD X LED - include only the keypad X button as a responder Create 2 programs KPD X basement lights ON If Basement KPD X is switched On Then Set Scene A On KPD X basement lights OFF If Basement KPD lights is switched Off Then Set Scene A Off Set Scene B Off Optional - 2 Programs for Keypad LED Trackers that also show if any lights are ON anywhere in the basement Basement Lights Status LED ON If KPD X Status is Off And Basement Light 1 Status is not 0.000% Or Basement Light 2 Status is not 0.000% Or ......add as many OR ....Status is not 0.000% as needed Then Set Scene Status Basement KPD X LED On Basement Lights Status LED OFF If KPD X Status is not Off And Basement Light 1 Status is 0.000% Or Basement Light 2 Status is 0.000% Or ......add as many OR ....Status is 0.000% as needed Then Set Scene Status Basement KPD X LED Off

There was an announcement a few days ago that Polisy is nearing EOL and in maintenance mode. I would keep your Polisy on 5.9.1 and eventually upgrade to Eisy when you're ready.

@dbwarner5 If memory serves, S2 was introduced in 2017. Most Yale locks were S0 before 2018. If your lock is really 10 years old it won't support S2. You can always look up the model spec. S0 is slow & chatty. S2 is quieter, faster, better battery management, and more reliable. To pair an S2 supported lock it needs to be paired close to the main controller using either a QR code or manual DSK entry. Sorry, I don't have a Z-wave radio on my Eisy since I moved all my Zwave & Zigbee devices to Hubitat a long while back. But maybe check Z-Wave-Tools-Z-Wave Diagnostics-Node Information and look for COMMAND_CLASS_SECURITY. If it's 0x98 then it's S0, if 0x9F then it's S2. But hey, if the locks are working like they should sometimes ignorance really is bliss!

@dbwarner5 The SECURITY=True flag in Xray only means the lock is encrypted. It doesn’t distinguish between S0 and S2. To confirm S2, you'd need to see COMMAND_CLASS_SECURITY_2 (0x9F) or S2 Access Control listed. Eisy + Zooz 800 stick improves inclusion reliability, but it doesn’t eliminate the need for close proximity during first-time S2 pairing. Including locks next to the main controller is still the most reliable way to ensure a clean S2 handshake.

Hey, Not sure what brand/model Zwave locks you have, but for secure S2 pairing they need to be right next to the main controller when pairing the locks the 1st time. Then move the locks to their final location and repair network. I had to do this with 3 locks a few years ago when I changed Zwave control from ISY to Hubitat. It was just easier to buy a cheap 75ft ethernet cable off Amazon and temporarily move Hubitat to the locks during S2 pairing then taking 3 locks off the doors. Waiting for decent matter locks to materialize so I can be done with Zwave once and for all.

@sjenkins Very nicely done. Great work! Thank you

Looks solid! Just a bit confused on the static/dynamic terminology change. In the first post you referred to Insteon-like as dynamic, but now default = Insteon = Static? Calling the default “Insteon = Static” may confuse some (many think of “resume last” as “Insteon-like”). In any case; GV0: Mode with editor choices Preset (Static) / Last On (Dynamic). Keeps your proposed behavior; avoids confusion over what is “Insteon-like” Per-node mode with a default and an optional dynamic mode is perfect. Proposed ranges make sense. Static (default) OL (5–100) is a preset the user/programs set. DON/DOF/DFON/DFOF/BRT/DIM do not change OL. Matches lots of non-Insteon devices’ “preset OL” behavior. Dynamic (optional) BRT/DIM update OL to the current level (clamped 5–100). DOF/DFOF set ST→0 and set OL to the last (pre-off) level (“last on”). OL can still be set manually or programmatically (clamped 5–100).

There's no imminent rush to upgrade, so chill and enjoy the serenity in your life for now. The web UI is still very rudimentary and limited at the present time. For example, there's no ability to create/edit programs. Scenes are not there at all. Current Admin Console isn't going away any time soon.

It could be helpful to add two optional params (global or per-node) that default to current behavior so nothing changes for existing users, but power users have the flexibility to fine tune: MIN_ON = 10 → floor used when OL is 0 or DIM reaches 0 so the next DON isn’t zero. STEP_PCT = 3 → brighten/dim step size.

Yes. Make a backup in Admin Console (File...) and nothing to lose if you also take a backup in PG3x. They are free

As Michel clearly states on that post " If your OS is below 13.2p11 please do not attempt the upgrade. It will brick your system." Either order the USB flash drive or file a ticket with UDI Support and ask if they'll send you the fw file to create a flash drive yourself, but DO NOT try to Upgrade Packages in AC! Yes, your installed version is 14.1 which is newer than 13.2p11 so good to go. Be sure to take an IoX backup in AC and a PG3x backup.

At the very top of the page your OS version is indicate in the line below *** OS *** What you posted is the UDX version.

You'll find many different perspectives on these forums. Such is the variety of life. But there's some basic fundamental covenants to a properly working IoX/Insteon system; 1. Never use manual links between devices unless you enjoy pain. IoX, the main brain of your system, is not aware of them. 2. For Multi-way circuits (3way, 4way, etc) always create a scene, and add all members to the scene as controllers. 3. A device can only be a controller for 1 scene, but a responder to many scenes. 4. When controlling more than 1-2 devices, a scene is considerably more efficient and reliable. 5. Identify a proper naming convention for your devices and scenes, and stick to it. With that out of the way, here's my perspective; I only use programs when I can't achieve what I want from using a scene. From what I gather from your post, you have a multi-way stair case scene with your master and slaves. These devices should be factory reset to remove any manual links, then added in IoX to a StairCase scene. Stair Case1 (this is the master) - controller to Stair Case Stair Case2 (this is a slave) - controller to Stair Case Stair Case (this is the scene) I don't think you'd want to control your daily lights (ie turn on your Daily Lights scene) every time you turn on your staircase lights so there's no point in making it a controller to the Daily Lights scene. Instead use a keypad button as the Daily Lights controller. You can add more than 1 from strategic locations, main floor, entrance, bedroom, etc and control the daily lights from all of them. We also want all devices in a multi-way circuit to remain in sync if they're part of the Daily Lights. To achieve this, Install the Virtual plugin in PG3x and create a virtual switch called Stair Case VS. Add that to the Stair Case scene as a controller. Then add that virtual switch to the Daily Lights scene as a responder. Then when Daily Lights is turned on, your Stair Case lights (and scene) are turned on, and your master and slave are also in sync. Simple, efficient, and no complicated programs needed. Use a program for Daily Lights scene to turn on/off conditionally (time of day or event).