Garage door opened at 2:57am by itself! Help

[stusviews]

Momentary B works for me. I don't care if an On or Off is sent, I want to control the garage door with one tap like virtually all garage door remotes.

[Blackbird]

Thanks for all your replies and help.  Not sure if we solved it but I did change the things that were suggested and I guess time will tell.

[Silversop]

Hi Everyone,

 

I am really new at all of this and have some questions based on all of the discussion and also my setup...

 

I installed an IO Linc as follows... I only have the IO Linc and not a button opener. I use the normal ones of the garage. I setup the Sensors "backward" in that... When the door is open the sensors are together (ON) and when the door is down.. the sesors are apart (Off)...

 

I had the momentary A setup without a trigger revers for the sensors...

 

It seems now, all of the functions are working as expected but if someone sees something out of wack with my setup let me know...

 

Second part of this is the notifications...

 

I want the door to notify me when open for longer than X... I open the door and close it within 30 seconds of opening it... I have X = 1 min for testing purposes. Even if the door is closed within 30 seconds.. it triggers an alert. I look at the iSY and it still shows "on" even though the door is closed...

 

It's almost like I need a continuous query after the trigger?

​Can someone give me some examples on the proper way to do a notification in this situation? How do I almost a constant query of the door while open to ensure that it really is open or closed.

 

Regards,

 

S

[stusviews]

Post your program. (Right click and copy to clipboard, then paste to forum.)

[Silversop]

Garage Door - [iD 0002][Parent 0001]

 

If

        Status  'Garage_Door_Sensor' is On

 

Then

        Wait  1 minute

        Send Notification to 'All' content 'Garage Door Notification'

        $Garage_Left_Open  = 1

 

Else

   - No Actions - (To add one, press 'Action')

 

Post your program. (Right click and copy to clipboard, then paste to forum.)

[oberkc]

The only concern I have with the hardware setting is that a door partially closed will show CLOSED from a sensor perspective. From a security perpective, I find this less desirable.

 

Regarding the program, I am having trouble finding any flaw. I expect this program to do as your stated desires suggest. My inclination would be to start some basic troubleshhooting investigation.

 

- does the light on the iolinc reliably reflect the garage door status?

- does the status of the ISY state of the sensor reliably represent the state of the iolinc?

[Silversop]

The only concern I have with the hardware setting is that a door partially closed will show CLOSED from a sensor perspective. From a security perpective, I find this less desirable.

 

Regarding the program, I am having trouble finding any flaw. I expect this program to do as your stated desires suggest. My inclination would be to start some basic troubleshhooting investigation.

 

- does the light on the iolinc reliably reflect the garage door status?

- does the status of the ISY state of the sensor reliably represent the state of the iolinc?

 

Oberkc,

 

Let me ask this though... When I close the garage door, It's almost like I need to run a query to ensure the state of the device is accurate. right?

[Silversop]

As well as my above posts.. one more odd thing ..

 

When I open the garage door and it gets to the top my sensors come together... As soon as they do, the door closes automatically... What the hell is screwed up

 

Here are the Level 3 logs from the event.

​

Sat 02/06/2016 08:44:32 : [iNST-TX-I1  ] 02 62 3D 51 45 0F 11 02

Sat 02/06/2016 08:44:32 : [iNST-ACK    ] 02 62 3D.51.45 0F 11 02 06          LTONRR (02)

Sat 02/06/2016 08:44:33 : [iNST-SRX    ] 02 50 3D.51.45 2A.1C.D7 2B 11 02    LTONRR (02)

Sat 02/06/2016 08:44:33 : [std-Direct Ack] 3D.51.45-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sat 02/06/2016 08:44:33 : [D2D EVENT   ] Event [3D 51 45 2] [sT] [255] uom=0 prec=-1

Sat 02/06/2016 08:44:33 : [  3D 51 45 2]       ST 255

Sat 02/06/2016 08:44:46 : [iNST-SRX    ] 02 50 3D.51.45 00.00.01 CB 11 00    LTONRR (00)

Sat 02/06/2016 08:44:46 : [std-Group   ] 3D.51.45-->Group=1, Max Hops=3, Hops Left=2

Sat 02/06/2016 08:44:46 : [D2D EVENT   ] Event [3D 51 45 1] [DON] [0] uom=0 prec=-1

Sat 02/06/2016 08:44:46 : [  3D 51 45 1]      DON   0

Sat 02/06/2016 08:44:46 : [D2D EVENT   ] Event [3D 51 45 1] [sT] [255] uom=0 prec=-1

Sat 02/06/2016 08:44:46 : [  3D 51 45 1]       ST 255

Sat 02/06/2016 08:44:46 : [D2D-CMP 0002] STS [3D 51 45 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true

Sat 02/06/2016 08:44:47 : [iNST-SRX    ] 02 50 3D.51.45 2A.1C.D7 41 11 01    LTONRR (01)

Sat 02/06/2016 08:44:47 : [std-Cleanup ] 3D.51.45-->ISY/PLM Group=1, Max Hops=1, Hops Left=0

Sat 02/06/2016 08:44:47 : [iNST-DUP    ] Previous message ignored.

Sat 02/06/2016 08:44:47 : [iNST-SRX    ] 02 50 3D.51.45 11.01.01 CB 06 00           (00)

Sat 02/06/2016 08:44:47 : [std-Group   ] 3D.51.45-->11.01.01, Max Hops=3, Hops Left=2

Sat 02/06/2016 08:44:47 : [iNST-INFO   ] Previous message ignored.

Sat 02/06/2016 08:44:47 : [iNST-SRX    ] 02 50 3D.51.45 00.00.01 CB 13 00    LTOFFRR(00)

Sat 02/06/2016 08:44:47 : [std-Group   ] 3D.51.45-->Group=1, Max Hops=3, Hops Left=2

Sat 02/06/2016 08:44:47 : [D2D EVENT   ] Event [3D 51 45 1] [DOF] [0] uom=0 prec=-1

Sat 02/06/2016 08:44:47 : [  3D 51 45 1]      DOF   0

Sat 02/06/2016 08:44:47 : [D2D EVENT   ] Event [3D 51 45 1] [sT] [0] uom=0 prec=-1

Sat 02/06/2016 08:44:47 : [  3D 51 45 1]       ST   0

Sat 02/06/2016 08:44:47 : [D2D-CMP 0002] STS [3D 51 45 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> false

Sat 02/06/2016 08:44:47 : [D2D EVENT   ] Event [3D 51 45 2] [sT] [0] uom=0 prec=-1

Sat 02/06/2016 08:44:47 : [  3D 51 45 2]       ST   0

Sat 02/06/2016 08:44:47 : [iNST-SRX    ] 02 50 3D.51.45 2A.1C.D7 41 13 01    LTOFFRR(01)

Sat 02/06/2016 08:44:47 : [std-Cleanup ] 3D.51.45-->ISY/PLM Group=1, Max Hops=1, Hops Left=0

Sat 02/06/2016 08:44:47 : [iNST-DUP    ] Previous message ignored.

Sat 02/06/2016 08:44:47 : [iNST-SRX    ] 02 50 3D.51.45 13.01.01 CB 06 00           (00)

Sat 02/06/2016 08:44:47 : [std-Group   ] 3D.51.45-->13.01.01, Max Hops=3, Hops Left=2

Sat 02/06/2016 08:44:47 : [iNST-INFO   ] Previous message ignored.

[paulbates]

As well as my above posts.. one more odd thing ..

 

When I open the garage door and it gets to the top my sensors come together... As soon as they do, the door closes automatically... What the hell is screwed up

 

 

 

Make sure that "Relay follows input" is  not checked in the iolinc's options

 

[LeeG]

Looks like the magnet and magnetic switch are not correctly positioned.    Thirteen seconds after door starts to move the Sensor turns On.  However, the Sensor immediately turns Off.  It looks like the magnet is 'sliding' to/past the magnetic switch rather than meeting side by side.

 

I have a switch that operates when the door is fully closed and a separate switch that operates when door is fully open.  I had to put fully open switch on a flexible metal strip because of slight variations in fully open position.  Also the magnet and switch should not 'slide' past each other.  That can cause the switch to read On then Off then On.

 

When a single switch is used it should operate when door reaches fully closed rather than fully open. 

 

Sat 02/06/2016 08:44:33 : [iNST-SRX    ] 02 50 3D.51.45 2A.1C.D7 2B 11 02    LTONRR (02) - door starts to move

Sat 02/06/2016 08:44:33 : [std-Direct Ack] 3D.51.45-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sat 02/06/2016 08:44:33 : [D2D EVENT   ] Event [3D 51 45 2] [sT] [255] uom=0 prec=-1

Sat 02/06/2016 08:44:33 : [  3D 51 45 2]       ST 255

Sat 02/06/2016 08:44:46 : [iNST-SRX    ] 02 50 3D.51.45 00.00.01 CB 11 00    LTONRR (00) - Sensor turns On

Sat 02/06/2016 08:44:46 : [std-Group   ] 3D.51.45-->Group=1, Max Hops=3, Hops Left=2

Sat 02/06/2016 08:44:46 : [D2D EVENT   ] Event [3D 51 45 1] [DON] [0] uom=0 prec=-1

Sat 02/06/2016 08:44:46 : [  3D 51 45 1]      DON   0

Sat 02/06/2016 08:44:46 : [D2D EVENT   ] Event [3D 51 45 1] [sT] [255] uom=0 prec=-1

Sat 02/06/2016 08:44:46 : [  3D 51 45 1]       ST 255

Sat 02/06/2016 08:44:46 : [D2D-CMP 0002] STS [3D 51 45 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true

Sat 02/06/2016 08:44:47 : [iNST-SRX    ] 02 50 3D.51.45 2A.1C.D7 41 11 01    LTONRR (01)

Sat 02/06/2016 08:44:47 : [std-Cleanup ] 3D.51.45-->ISY/PLM Group=1, Max Hops=1, Hops Left=0

Sat 02/06/2016 08:44:47 : [iNST-DUP    ] Previous message ignored.

Sat 02/06/2016 08:44:47 : [iNST-SRX    ] 02 50 3D.51.45 11.01.01 CB 06 00           (00)

Sat 02/06/2016 08:44:47 : [std-Group   ] 3D.51.45-->11.01.01, Max Hops=3, Hops Left=2

Sat 02/06/2016 08:44:47 : [iNST-INFO   ] Previous message ignored.

Sat 02/06/2016 08:44:47 : [iNST-SRX    ] 02 50 3D.51.45 00.00.01 CB 13 00    LTOFFRR(00) - Sensor turns Off

Sat 02/06/2016 08:44:47 : [std-Group   ] 3D.51.45-->Group=1, Max Hops=3, Hops Left=2

Sat 02/06/2016 08:44:47 : [D2D EVENT   ] Event [3D 51 45 1] [DOF] [0] uom=0 prec=-1

Sat 02/06/2016 08:44:47 : [  3D 51 45 1]      DOF   0

Sat 02/06/2016 08:44:47 : [D2D EVENT   ] Event [3D 51 45 1] [sT] [0] uom=0 prec=-1

Sat 02/06/2016 08:44:47 : [  3D 51 45 1]       ST   0

Sat 02/06/2016 08:44:47 : [D2D-CMP 0002] STS [3D 51 45 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> false

Sat 02/06/2016 08:44:47 : [D2D EVENT   ] Event [3D 51 45 2] [sT] [0] uom=0 prec=-1

Sat 02/06/2016 08:44:47 : [  3D 51 45 2]       ST   0

Sat 02/06/2016 08:44:47 : [iNST-SRX    ] 02 50 3D.51.45 2A.1C.D7 41 13 01    LTOFFRR(01)

Sat 02/06/2016 08:44:47 : [std-Cleanup ] 3D.51.45-->ISY/PLM Group=1, Max Hops=1, Hops Left=0

Sat 02/06/2016 08:44:47 : [iNST-DUP    ] Previous message ignored.

Sat 02/06/2016 08:44:47 : [iNST-SRX    ] 02 50 3D.51.45 13.01.01 CB 06 00           (00)

Sat 02/06/2016 08:44:47 : [std-Group   ] 3D.51.45-->13.01.01, Max Hops=3, Hops Left=2

Sat 02/06/2016 08:44:47 : [iNST-INFO   ] Previous message ignored.

 

Could also be the "relay follows input" as Paul has already posted. 

[Silversop]

Looks like the magnet and magnetic switch are not correctly positioned.    Thirteen seconds after door starts to move the Sensor turns On.  However, the Sensor immediately turns Off.  It looks like the magnet is 'sliding' to/past the magnetic switch rather than meeting side by side.

 

I have a switch that operates when the door is fully closed and a separate switch that operates when door is fully open.  I had to put fully open switch on a flexible metal strip because of slight variations in fully open position.  Also the magnet and switch should not 'slide' past each other.  That can cause the switch to read On then Off then On.

 

When a single switch is used it should operate when door reaches fully closed rather than fully open. 

 

Sat 02/06/2016 08:44:33 : [iNST-SRX    ] 02 50 3D.51.45 2A.1C.D7 2B 11 02    LTONRR (02) - door starts to move

Sat 02/06/2016 08:44:33 : [std-Direct Ack] 3D.51.45-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sat 02/06/2016 08:44:33 : [D2D EVENT   ] Event [3D 51 45 2] [sT] [255] uom=0 prec=-1

Sat 02/06/2016 08:44:33 : [  3D 51 45 2]       ST 255

Sat 02/06/2016 08:44:46 : [iNST-SRX    ] 02 50 3D.51.45 00.00.01 CB 11 00    LTONRR (00) - Sensor turns On

Sat 02/06/2016 08:44:46 : [std-Group   ] 3D.51.45-->Group=1, Max Hops=3, Hops Left=2

Sat 02/06/2016 08:44:46 : [D2D EVENT   ] Event [3D 51 45 1] [DON] [0] uom=0 prec=-1

Sat 02/06/2016 08:44:46 : [  3D 51 45 1]      DON   0

Sat 02/06/2016 08:44:46 : [D2D EVENT   ] Event [3D 51 45 1] [sT] [255] uom=0 prec=-1

Sat 02/06/2016 08:44:46 : [  3D 51 45 1]       ST 255

Sat 02/06/2016 08:44:46 : [D2D-CMP 0002] STS [3D 51 45 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true

Sat 02/06/2016 08:44:47 : [iNST-SRX    ] 02 50 3D.51.45 2A.1C.D7 41 11 01    LTONRR (01)

Sat 02/06/2016 08:44:47 : [std-Cleanup ] 3D.51.45-->ISY/PLM Group=1, Max Hops=1, Hops Left=0

Sat 02/06/2016 08:44:47 : [iNST-DUP    ] Previous message ignored.

Sat 02/06/2016 08:44:47 : [iNST-SRX    ] 02 50 3D.51.45 11.01.01 CB 06 00           (00)

Sat 02/06/2016 08:44:47 : [std-Group   ] 3D.51.45-->11.01.01, Max Hops=3, Hops Left=2

Sat 02/06/2016 08:44:47 : [iNST-INFO   ] Previous message ignored.

Sat 02/06/2016 08:44:47 : [iNST-SRX    ] 02 50 3D.51.45 00.00.01 CB 13 00    LTOFFRR(00) - Sensor turns Off

Sat 02/06/2016 08:44:47 : [std-Group   ] 3D.51.45-->Group=1, Max Hops=3, Hops Left=2

Sat 02/06/2016 08:44:47 : [D2D EVENT   ] Event [3D 51 45 1] [DOF] [0] uom=0 prec=-1

Sat 02/06/2016 08:44:47 : [  3D 51 45 1]      DOF   0

Sat 02/06/2016 08:44:47 : [D2D EVENT   ] Event [3D 51 45 1] [sT] [0] uom=0 prec=-1

Sat 02/06/2016 08:44:47 : [  3D 51 45 1]       ST   0

Sat 02/06/2016 08:44:47 : [D2D-CMP 0002] STS [3D 51 45 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> false

Sat 02/06/2016 08:44:47 : [D2D EVENT   ] Event [3D 51 45 2] [sT] [0] uom=0 prec=-1

Sat 02/06/2016 08:44:47 : [  3D 51 45 2]       ST   0

Sat 02/06/2016 08:44:47 : [iNST-SRX    ] 02 50 3D.51.45 2A.1C.D7 41 13 01    LTOFFRR(01)

Sat 02/06/2016 08:44:47 : [std-Cleanup ] 3D.51.45-->ISY/PLM Group=1, Max Hops=1, Hops Left=0

Sat 02/06/2016 08:44:47 : [iNST-DUP    ] Previous message ignored.

Sat 02/06/2016 08:44:47 : [iNST-SRX    ] 02 50 3D.51.45 13.01.01 CB 06 00           (00)

Sat 02/06/2016 08:44:47 : [std-Group   ] 3D.51.45-->13.01.01, Max Hops=3, Hops Left=2

Sat 02/06/2016 08:44:47 : [iNST-INFO   ] Previous message ignored.

 

Could also be the "relay follows input" as Paul has already posted. 

 

 

Make sure that "Relay follows input" is  not checked in the iolinc's options

 

gdo.JPG

Thanks Lee and Paul... it does turn out it was the relay follows input checkbox... Been pulling my hair out and it turns out it's a freakin check box that causes that ..

 

Thanks!

[jerlands]

Oberkc,

 

Let me ask this though... When I close the garage door, It's almost like I need to run a query to ensure the state of the device is accurate. right?

 

Apparently you have the sensor contacts mounted in a position very near the garage door opener (the motor) itself (or at least on the same plane?)  In your configuration any position of the garage door 2" away from the contacts will show the garage door closed and there's no query to prove otherwise.  The door could be 4' open and show closed and you'll never know unless you have a camera

 

 

Jon...

[Blackbird]

I came up with a secure method of using the insteon garage door opener so I will never have to worry about this happening again.  I installed a insteon wall plug and plugged the opener into that that is normally off.  When I enter the garage the power to the opener turns on for 15 min then shuts off again.  When I drive home and enter my geofence while connected to bluetooth, the power to the opener turns on.  Been working great and very secure.

[MWareman]

I came up with a secure method of using the insteon garage door opener so I will never have to worry about this happening again. I installed a insteon wall plug and plugged the opener into that that is normally off. When I enter the garage the power to the opener turns on for 15 min then shuts off again. When I drive home and enter my geofence while connected to bluetooth, the power to the opener turns on. Been working great and very secure.

More secure, yes. Not sure I would say 'very secure' though. It's still based on an insecure protocol transmitted in the clear.

 

If someone was so inclined, they could still just turn the outlet on first.

[Teken]

I came up with a secure method of using the insteon garage door opener so I will never have to worry about this happening again.  I installed a insteon wall plug and plugged the opener into that that is normally off.  When I enter the garage the power to the opener turns on for 15 min then shuts off again.  When I drive home and enter my geofence while connected to bluetooth, the power to the opener turns on.  Been working great and very secure.

 

May I ask if you can provide the Insteon part number along with the hardware production date and revision? Please also include the ISY firmware for that Insteon device.

 

Lastly, could you offer some insight as to what you have done to validate this new method?

[Blackbird]

May I ask if you can provide the Insteon part number along with the hardware production date and revision? Please also include the ISY firmware for that Insteon device.

 

Lastly, could you offer some insight as to what you have done to validate this new method?

 

Cant give you the revision number (purchased about 2 months ago) as it is a pain in the *** to remove and replace the large plate but the part number is 2663-222.  Nothing to validate it except common sense I guess.  I do not have to worry as much about a program problem or all on event as in order to open the door it requires 2 stages 1 to power on the plug then 2 to activate the iolinc.  if the isy does that by itself then there is something seriously wrong.  Also if someone had my garage door opener code, it would be useless to them as the power to the opener is normally off.  I'm sure some can shoot holes in this idea or find flaws but I'm more than happy with it.  Just thought I would share.

[Teken]

Cant give you the revision number (purchased about 2 months ago) as it is a pain in the *** to remove and replace the large plate but the part number is 2663-222.  Nothing to validate it except common sense I guess.  I do not have to worry as much about a program problem or all on event as in order to open the door it requires 2 stages 1 to power on the plug then 2 to activate the iolinc.  if the isy does that by itself then there is something seriously wrong.  Also if someone had my garage door opener code, it would be useless to them as the power to the opener is normally off.  I'm sure some can shoot holes in this idea or find flaws but I'm more than happy with it.  Just thought I would share.

 

Having a two step method does indeed offer more protection as I use a similar technique. I would like to add the following for your consideration and thought. Your premise is based on several ideas and assumptions which again requires validation, testing, and follow up.

 

Key things that come to mind in no specific order of importance are these:

 

1. What hardware / firmware 2413S PLM do you have? This is important to know because this would validate the ALL ON / ALL OFF command set is not present.

 

2. Like number one the 2663-222 must be confirmed to have removed the ALL ON / ALL OFF command set. As the process of removing the command was brought in mid stream of production. This is why testing and validation is paramount to ensure known variables are present.

 

3. ALL ON / ALL OFF: Assume both devices still include the ALL ON / ALL OFF command set. Just because both devices are powered off has no impact to the 2663-222 being activated from off to on. The possible benefit assuming the command still existed is that that slight delay of powering up may very well negate the ALL ON / ALL OFF from impacting the GDO.

 

4. Validation: Have you short cycled the power in duration and voltage?

 

5. Have you confirmed the 2663-222 always respects its *Last Known State*? This is important because (4) can impact the consistency of the last known state.

 

6. Have you considered applying some old school technology to accomplish the same? Specifically using relays, mechanical timer, industrial I/O closures?

 

7. Fail Over: Its important to note most if not all people ever consider extra measures of fail over. You have obviously taken some time to consider this but would encourage you to think about other methods separate and independent of the Insteon network. Doing so and applying 3rd party hardware will ensure that measure of *Fail Over* because these systems are independent and isolated from the primary systems which can not be impacted by related ALL ON / ALL OFF conditions.

 

Your response to the above is appreciated . . . 

[Blackbird]

1.the plm is 2413s v2.0 1440  The wall outlet isRev.7.3  1616

2.  The outlet is not part of the all on all off and wasn't used during the door open event

3. I don't believe the cause of the door opening by itself was an all on all off I think it was a program or scene problem.  I think one of you recommended not having the door sensor and the relay in the same scene which mine was at the time.  I removed it since.

4.  No idea what you mean

5. not sure of this either

6.  I only had this happen once and since I made these changes I am comfortable with it and didn't intend or changing the setup

 

Thanks

[Teken]

1.the plm is 2413s v2.0 1440  The wall outlet isRev.7.3  1616

2.  The outlet is not part of the all on all off and wasn't used during the door open event

3. I don't believe the cause of the door opening by itself was an all on all off I think it was a program or scene problem.  I think one of you recommended not having the door sensor and the relay in the same scene which mine was at the time.  I removed it since.

4.  No idea what you mean

5. not sure of this either

6.  I only had this happen once and since I made these changes I am comfortable with it and didn't intend or changing the setup

 

Thanks

 

1. The outlet is fine and more than likely does not include the command but you can test it by simply pressing the ALL ON / ALL OFF in the ISY to confirm. The PLM is a mixed bag and a level 3 log would need to be reviewed.

 

2. If the dual outlet relay still has the ALL ON / ALL OFF command class - If that condition should ever happen again it will turn on a outlet that was off. Since electricity is almost the speed of light both the I/O linc and outlet could be live at the same time.

 

As stated, due to amount of time for the outlet to *boot up* this could very well negate that issue. But testing and validation is a must to ensure this is factually true. Hoping doesn't change what can happen not (IF).

 

4. Short Cycling: Is tripping the breaker quickly from on-off-on doing so will mimic in a small way what a loss of power will look like. Rapid succession of quick and brief trips of the breaker will also cause a surge in voltage to be seen on the line. Obviously great care must be used when short cycling is performed because it can damage end devices down the branch circuit.

 

5. The dual outlet relay has a firmware feature known as *Last Known State*. Meaning if the device was on during a power loss upon the return of said power it will resume its last known state. If it was off it will remain off also but should note short cycling can force the device to *Forget* said last known state.

 

Anyone who has installed a micro dimmer / relay will know this fact to be true . . .

[stusviews]

The effect of electricity travels at, not almost, the speed of light. Resistance my limit the current, but not the speed.

 

Any Insteon device produced this year has the ALL ON/ALL OFF command removed. The command was a carryover from the X10 protocol.

[Teken]

I believe its fair to say anything produced in 2016 should be void of the ALL ON / ALL OFF command set. But since Smartlabs has never confirmed this in public our views are purely speculative.

 

Keeping in mind this doesn't address slow moving items like the 240 VAC load controller. 

 

With respect to electricity going the speed of light as you noted resistance plays a major factor here. Voltage is highly dependent upon wire length, diameter, dielectric insulation, cable material, number of wires in a bundle, and the applied voltage(s). Since we do not live in a vacuum all of the above plays a factor in the end to end speed of what is received.

 

Albeit, this variance isn't something anyone will notice in daily life . . .

[larryllix]

Electricity does not travel at the speed of light. electrons travel at the speed of light.

 

But like the water in a house travels a x feet per second, and can take a full minute to go through the hose, the water coming out of a hose is instantaneous when you turn the valve on, with a full hose.

 

 

Electrical conductors are full of electrons and when a new one tries to push it's way into the conductor, an existing one pops out the other end, at the same time.

 

Resistance is futile, You too, will be assimilated.

[stusviews]

The effect of electricity travels at, not almost, the speed of light. Resistance my limit the current, but not the speed.

 

That's what I indicated