jim_

Thanks, I will test with some spare switches and report back ...

I know what's happening in the program(s), but having trouble describing in a short question ... I have 2 different KPL's which monitor devices on and can shut them off using the KPL button. At each KPL, the button will light up when any devices in the list turns on. If have one KPL for all basement devices and a main KPL for every device connected to EISY. Here's a sample of the main KPL .... if a device is turned on , the KPL light is also turned on, if all devices are off, the KPL will turn off If Kitchen Sink Status is ON or Living Room Light is ON or ..... A long list of every device to monitored .... Then Set 'KPL Front Dr D Mon' On Else Wait 5 seconds Set 'KPL Front Dr D Mon' Off If any devices are ON anywhere in the house, I can turn it off at the main KPL by pressing the button If KPL Front Dr D Monitor Status is Off Then Set 'Kitchen Sink' Off Wait 1 second Set Living Room Light Off etc ... Problem ... Based on my limited understanding of writing programs, it appears in the first program, Else " Set 'KPL Front Dr D Mon' Off " is triggering the 2nd program "If KPL Front Dr D Monitor Status is Off" and running a global off to all devices How do I stop this .... ??? (discovered this when Christmas Lights were manually turned on (LampLinc) during the day and someone turned off the basement KPL, global turns off the LampLinc)

Thanks for the direction, I figured out what changed in my enviroment ... IoX launcher dropped the 8443 from the network discovery IP showing Everything that worked before continues to work the same way: IoX will respond to API requests on port 8080/8443 and require the same local username & password

apostolakisl, Please explain how this logs me into the eisy via IoX launcher ? Trying to use the legacy login default admin / admin or my backup user / password BTW, the URL does not work >>> http://192.168.1.200:8080 page can’t be found https://192.168.1.200 works perfectly into the UI

Upgraded the other day and thought all was good after upgrading to 0.7.2 Tried to login today using via IoX Launcher using admin/admin ... nope, then tried logging in with my backup user / pass nope Noted the login shows "Use your Portal userid/password" Question: 1) Why are the local accounts gone 2) In an event that the Portal login fails, how in the "H" will I login to the eisy ?

Poking around the new eisy-ui, and I know scenes and program edits are not yet supported ... I have a question about support for KPL buttons For example, Kitchen Sink light and a KPL buttom linked in a scene. Using UD Mobile, open the devices and scenes, select the KPL button, turn the light on / off ... simple I added both my Kitchen light and related KPL button as new tiles into eisy-ui. Manually turning light on / off via either the switchlinc or KPL, both tiles update showing status. But if I turn the switchlinc on / off via the tile buttons, the KPL status does not update. and there are no options to control the KPL button within the tile ? What am I missing here ?

check this post out, I've have it set for Christmas starting Dec1 and ending Dec 31 Christmas Timer If Time is Sunset And $sDate_valid is 1 And $iDate_month is 12 Then Set 'XMAS Tree' On The Integer values should look like this

One of those items you forget to add ... caught in heavy rain today, no shortcut to open the garage door on my cell. I had a look through other posts and can't find a simple guide to creating a FAV for my garage door opener on UD Mobile. I have the Garage Door Sensor and Relay (IO Link) listed as hardware, I also have Scenes connecting garage door KPL's, but nothing seems to work when adding as a new FAV I found this on Google, but not clear on what in my devices to assign to "select your garage door opener" Step-by-Step Guide to Adding a Garage Door Opener Favorite Navigate to the Favorites Page: Open the UD Mobile app and go to the Favorites screen. Enter Add Mode: Tap the + (plus) icon, which will be located on the Favorites page. Select the Node: Tap on Display Node. Choose Your Device: From the list of devices, find and select your garage door opener. Save the Favorite: Click the Save button to add the garage door opener to your Favorites.

Thanks everyone for your support Long story short, been chatting with Michel ... I'm screwed ... Michel may look later on why Insteon support magically became unchecked. We (family) lost our virtual (internet) backup drive back in the summer which had all my backups, so lesson learned, now have NAS on site for all our auto backups. So restoration the hardway has begun

Thanks for the tip Techman, Insteon was NOT checked ... Now, how does an option mysteriously change? I checked and found the last time I logged into eiesy was Aug 14 ... so exactly how does an option that was set 2 years ago become un-checked ? Fast forward, every Insteon device was NOT responding once the PLM showed connected. After many hours of manually Restoring Devices or Write updates to each device ... eI now have every Insteon device back on line execpt for 1 motion (2844). Some were extremely stubborn particularly 3 or 4 way slave switches. Scenes that involve a KPL work, example garage door opener via KPL button or a 3 / 4 way light switch. BUT anything involving programs will NOT run. Some programs show true status, others show no change in status when something is triggered. My nightly dusk program just started, none of the lights in program are turning on e.g. Kitchen Sink. From admin console, I can turn the Kit light on / off no issues. Anything with timers will not run ... e.g. Fireplace Fan Timer If 'Fireplace Fan 4F.E4.85' Status is On Then Wait 1 minute Set 'Fire Place Fan' Off I created a new timer, using a test switch and it works AAA test If 'AAA Test Switch' Status >= 1% Then Wait 10 seconds Set 'AAA Test Switch' Off I'm completely confused on how to debug this issue I opened a ticket ... I just found a new twerk ... all switches can be controlled by the admin console, but if you manually turn on / off a switch, the console never see's the state change. Watching the event viewer ... manual changes are not logging

Everything was running fine until dusk tonight, then no lights turned on at dusk. After a short trouble shooting exercise, checked tools / diagnostics / PLM info / status => (Not Connected) Factory reset the PLM, changed the USB cable to new, swapped the PLM and Zmatter USB ports (power cycled EISY for each change) ... PLM remains Not Connected Where can I see an OS message that shows USB device status ? or log message that documents PLM failure ? NOTE : The EISY is always popping up "System Busy" do not unplug ... the pop-ups have no information and and take 20+ minutes to close after each reboot ----------------------------------------------------------------------------- Assuming the 2413U is dead , ordering one will take many weeks to obtain where I live ... (Thanks Mr Trump) How do I go back to my 994 ? 98% of the config would be identical ... I have 95% insteon and 5% zwave Is there go back guide ?

JUST FYI To close this post ... a good solution to detect simple switch closures. The Wave i4's a very inexpensive compared to other ZW switch detectors on the market After many emails with Shelly support, the conclusion is as follows: The i4 have two purposes The main one is to be used with a button (spring loaded switch) in order to trigger the scenes (or other automation) with the Command Class Central Scene which is usually used in the Z-Wave remote controllers. The second is to be used by a toggle switch (normal On Off switch) this feature was added on users request. The main purpose of that is to report the state of an attached sensor (switch no button) so On or Off. There is a toggle function, but requires a value 0 (zero) mode and the switch speed is ~500 milliseconds as shows in these traces. As documented, value 2 (toggle) is specific to " Command Class Central Scene " using specific switch(s) and ZW controller Normal 1 second button (on / off) : where messaging follows button closure Thu 02/20/2025 13:55:52 : [ZY025_201N001 ] FDUP 2 (uom=115 prec=0) <<<<<<<<<<<< button closed = FDUP Thu 02/20/2025 13:55:53 : [ZY025_201N001 ] FDSTOP 4 (uom=115 prec=0) <<<<<<<<<<< button open = FDSTOP Fast ~500ms button cycle (on / off) : where button cycle changes the messaging state Thu 02/20/2025 13:57:04 : [ZY025_002_1 ] ST 0 (uom=78 prec=0) <<<<<<<< Transition from previous state to OFF (ST 0) Next Button Cycle Thu 02/20/2025 13:57:07 : [ZY025_002_1 ] ST 100 (uom=78 prec=0) <<<<< Transition from previous state to ON (ST 100) Also worth mentioning, in value 1 mode, the EISY controller can set the initial state to either ON or OFF for each switch 1-4, so function can be set to follow on / off or off / on which is a big PLUS when integrating with 3rd party equipment. e.g. if your connected to a generic motion detector where the relay operates normally closed, trigger to an open. I have 2 x i4's deployed, 4 standalone motion detectors, 2 connected to door switches (parallel) DSC alarm and NVR alarm out ... all controlling lights

Trying not to go down a deep hole here, but a NEW i4 out of the box, same issue After inclusion to EISY, value shows the default "0" value for switch 1 using the Zwave Config Param pop-up In event viewer, one see's this using a spring push button, hold count for 1-onethousand, release X2 Sun 02/02/2025 16:08:11 : [D2D EVENT ] Event [ZY025_201N001] [ST] [2] uom=115 prec=0 Sun 02/02/2025 16:08:11 : [ZY025_201N001 ] ST 2 (uom=115 prec=0) Sun 02/02/2025 16:08:11 : [D2D EVENT ] Event [ZY025_201N001] [FDUP] [2] uom=115 prec=0 Sun 02/02/2025 16:08:11 : [ZY025_201N001 ] FDUP 2 (uom=115 prec=0) Sun 02/02/2025 16:08:12 : [D2D EVENT ] Event [ZY025_201N001] [ST] [4] uom=115 prec=0 Sun 02/02/2025 16:08:12 : [ZY025_201N001 ] ST 4 (uom=115 prec=0) Sun 02/02/2025 16:08:12 : [D2D EVENT ] Event [ZY025_201N001] [FDSTOP] [4] uom=115 prec=0 Sun 02/02/2025 16:08:12 : [ZY025_201N001 ] FDSTOP 4 (uom=115 prec=0) Changing values are pretty clear in event viewer Sun 02/02/2025 16:13:31 : Create REST U7 [/rest/nodes/ZY025_1/cmd/CONFIG?NUM.107=1&VAL.111=1] Sun 02/02/2025 16:13:31 : U7 Rest: submitCmd([ZY025_1],[CONFIG],[NUM.107=1&VAL.111=1]) Sun 02/02/2025 16:13:31 : [ZW-TX-A 00296 25.0 ] [ZY025_1] Config Set parameter=1 value=1 (x1) size=1 Sun 02/02/2025 16:13:31 : [ZW-DONE 00296 25.0 ] [ZY025_1] Config Set parameter=1 value=1 (x1) size=1 Sun 02/02/2025 16:13:39 : Create REST U7 [/rest/nodes/ZY025_1/cmd/CONFIG?NUM.107=1&VAL.111=2] Sun 02/02/2025 16:13:39 : U7 Rest: submitCmd([ZY025_1],[CONFIG],[NUM.107=1&VAL.111=2]) Sun 02/02/2025 16:13:39 : [ZW-TX-A 00297 25.0 ] [ZY025_1] Config Set parameter=1 value=2 (x2) size=1 Sun 02/02/2025 16:13:39 : [ZW-DONE 00297 25.0 ] [ZY025_1] Config Set parameter=1 value=2 (x2) size=1 Testing the spring loaded switch in mode 2, same 1-onethousand count push / release ... same ON / OFF as mode 1 NOTE how the functional output jumps from Scene Button 1 >>> to >>> Binary Switch in Mode 1 or 2 Sun 02/02/2025 16:16:05 : [ZWAVE-CTL-EVENT ] Basic Set from 25.0 unmapped (ignored) Sun 02/02/2025 16:16:06 : [D2D EVENT ] Event [ZY025_002_1] [ST] [100] uom=78 prec=0 Sun 02/02/2025 16:16:06 : [ZY025_002_1 ] ST 100 (uom=78 prec=0)3e Sun 02/02/2025 16:16:07 : [ZWAVE-CTL-EVENT ] Basic Set from 25.0 unmapped (ignored) Sun 02/02/2025 16:16:07 : [D2D EVENT ] Event [ZY025_002_1] [ST] [0] uom=78 prec=0 Sun 02/02/2025 16:16:07 : [ZY025_002_1 ] ST 0 (uom=78 prec=0) AND ... in XRAY, Config confirms mode for switch 1 does change when this value is observed Switch 1 > Integer DATA devices.25.instances.0.commandClasses.112.data.1.val = 2 (0x00000002) verses Switch 2 > Integer DATA devices.25.instances.0.commandClasses.112.data.2.val = 0 (0x00000000) etc In the end, It is what it is ...

Thanks Rob ... I was hoping someone would twig if I was missing a step ... I've using both ways of configuration (both on the pop-up menu and on the root entry page of the console) and while setting mode 0 or 1 work, mode 2 just doesn't take. I understand that Shelly is offering these devices with the expectation they will be deployed into a normalized Zwave enviroment and typically interlink with "other" Shelly modules ... it is what it is So far all of my installs work in Mode 1, just wanted to have mode 2 available ... I'll keep poking it

While EnvisaLink-DSC is a available on Poly, my internet can be questionable at times, so me (in the minority of users), I'd rather run on something local. With over 130 network devices of various function(s), I actual run a network monitor [PRTG] to advise on any failures. DSC Link ran on the same PC, so having a deadicated PC already in place, may as well use it. If an EISY compatibale version of NodeLink were to be made available, it would be greatly appreciated For my small installation [3 zones], I found a cheat using Shelly Zwave i4 modules wiring them in parallel to DSC sensors such as door contacts or motion detectors. So far, integration has been very stable and no false triggers to date in almost 2 months running