jim_

@IndyMike I will look in a few weeks if the messages have returned in the trace ... mean time, "Delays are your friend" which I completely agree on But this program is about as generic as possible with consideration to humans wishing to descend the stairs ASAP preferably with the light ON. Motion is set to report "On Only" & timeout 10 seconds ... so I'm not sure where I could insert a delay here ? Basement Stairs Light On - [ID 005D] If 'Basement Stairs Mot 54.68.42' is switched On And $sBasement_Stairs_Light_Status is 0 Then Set 'Basement Stair 3 Way' On Wait 2 minutes Set 'Basement Stair 3 Way' Off

Thank you ... The information always seems to be right in front of you, you don't see it I deleted the disabled programs and re-ran a trace matching MS ON msg's as you did, down to 3 ON msg's. No idea if it helps, but like any protocol, any reduction in messaging helps in general 15:10:04 [INST-SRX ] 02 50 54.68.42 00.00.01 CB 11 01 LTONRR (01) > Motion Sensor On #1 - ISY Triggers Program 15:10:05 [INST-SRX ] 02 50 54.68.42 00.00.01 CF 11 01 LTONRR (01) > Motion Sensor On #2 - ISY Re-triggers Program 15:10:06 [INST-SRX ] 02 50 54.68.42 71.1C.76 46 11 01 LTONRR (01) > Motion Sensor On #3

@IndyMike WOW ... ok lots to digest, thanks for providing this analysis .... it will take a while for me to slowly walk through. But let me address this last elephant you identified re: "motion sensor at address 54.68.42 that is used as a control in two programs (0033 and 005D)." Yes [Basement Stairs Mot 54.68.42] is valid and the only "Insteon" motion in active deployment with one associated ACTIVE program. I cautiously respond saying ... I was about to ask how one finds a Program by ID, but I had a learning moment . Copy a program in text mode and in the first line of the program NAME and the program ID > Basement Stairs Light On - [ID 005D][Parent 005C] ... always wondered what that text was for Question ... 54.68.42 in two programs (0033 and 005D) 54.68.42 was found in three programs, the current ACTIVE program and two others that are set DISABLED (my previous TEST samples) Many moons ago, I recall reading that ISY / EISY can still read the program entry set DIABLED, but doesn't execute / ignores ... something like that ??? Based on your diagnostics, a program that is is clearly tagged "Disabled" / Basement Stairs Trigger - [ID 0033][Parent 0040][Not Enabled] COULD and is still be executing .... Is this not a bug ? Another educate me question un-related Where program --- Basement Stairs Light On - [ID 005D][Parent 005C] Parent ID matches program ID of 5D ... meaning its standalone ? Where does "Parent 0040" come from in the disable program ... Basement Stairs Trigger - [ID 0033][Parent 0040] ... where Parent 0040 is also found on other disable programs, but there is no program ID 0040 on my ISY / EISY

Hey @IndyMike ... 24 hours of Event Viewer L3 attached ... And as per Murphy's Law, the random event did NOT occur BTW, I understand standard IP protocol and use wireshark to isolate troubles, but was looking for an Insteon protocol cheat sheet ... the old UD wiki is to vague. Could you point me to any doc's ? (I have the original 2006 SmartLabs, Inc design doc, but there no procedure / state charts to review) 24 hour Event Viewer L3.txt

Thanks for the descriptive reply, this helps me understand .... Just to clarify .... request to post L3 events log > would this be a general capture (normal MS activation of basement lights ) or specific to the random event ?

learning enabled ... I understand a collision @ PLM, but not understanding "All-On" + "Devices that have not had the command removed will be affected" How does one remove the command "All-On" per device ? MS is hardwired to 5v and was factory reset ~ 6 months ago, but days after this random event was still occurring. I'm not convinced it's the MS as root cause ... Since it's always the same devices affected (Lamp, Garage Door, and Garage Light (wife confirmed specifically these 3 only) and there is zero association with the MS / basement lights, we do know that when after 60 second-ish the MS is triggered, then these other 3 devices are affected. Since its not practical to share all my devices and related programs, but there are KPL's with control for this group of devices as well as others .... is it possible for data collision in a KPL ? (and yes the KPL(s) have been reset) .... Back to the question of tools ... should I expect to see messaging in event viewer or is there other tools that I should explore or I'm SOL from a logging perspective ?

Appreciate the response and I think I understand what you are suggesting by "instigators", but there are no associations of my basement light control via programs, sensors or KPL's here to my garage door control or a standalone light .... I also discovered today, the garage light was also turned on ... which is new

I have a random event which starts when a motion sensor (2844-222) triggers a scene for basement lights, but (not related) my garage door (IOLinc) opens and a light (LampLinc) turns on. This is very rare event occurring once every 4 weeks ... The motion sensor is top of basement stairs and controls basement light scenes ... Post event, looking through LOG (Tools) the motion sensor, the garage door (IOLinc) or the LampLinc do NOT appear when this event log and when I look at the LampLinc status, it shows off state, and If I look at a scene containing the LampLinc, it shows OFF status, but a mini remote button (4 Scene) shows ON associated with the LampLinc I have run Tools / Diagnostics / Event Viewer for weeks hoping to catch what triggers this event ... no luck ... Looking for direction on how to capture / diagnose this random event Cheers

At this point, I'm not going to invest in a technology which is not reached any industry deployment standard ... it's just not worth it Maybe I'll spend my time modding an Insteon switch into a laser trip sensor or turn a dimmer into proximity distance switch, something useful But I will keep my eye on matter & UD progression more closely

Thanks for the reply and it seems to be a deep subject ... when I first read the spec on Matter, it sounded very simple in as much ... all these companies signing on to provide one command method of coms across a vast offering of hardware .... but they had to make it difficult :-( Specific questions, well it's winter here, snow is deep, stuck inside, thought maybe I could play and just maybe, get something working and a bonus would be voice commands

I wanted to continue this thread started by Ristin, but its closed ... so Matter for Dummies II is created I need a Dummies guide to Matter dongle on the EISY. I have a mix of Insteon and z-wave devices, google home (speaker) and / or Alexa Dot It would be nice to a comprehensive guide as per UD of how this should all work

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