Announcement

Collapse
No announcement yet.

Comm Reliability getting worse

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • jono
    replied
    I second Mark’s comment on using groups as there will be many fewer commands. Also I believe keypads get subsequent error check type commands so your button b command could get interference from the button a error checking traffic. Finally every few days I have found it useful for HS3 to reset my plm which I usually do in the middle of the night when insteon commands are very unlikely to occur.
    i can’t explain your video, but you might check to see if button on or off commands trigger events that change the state of the buttons. If so the triggering of that event would show up on the hs3 log.

    Leave a comment:


  • davidz25
    replied
    I had a chance to take a look at this today and try to create a reliable reproducer... see the following event:
    Click image for larger version

Name:	insteon-onoff.png
Views:	221
Size:	220.9 KB
ID:	1374852



    See this video for what it looks like when the event runs: https://www.youtube.com/watch?v=wwOu8kTs3jM

    See [1] for the log for when this happens. After this runs Homeseer has "Foyer Keypad - Button C (Day)" to Off when it really is On (as you can see by the video). This is 100% reproducible... it happens every time.

    I think the problems that I see are similar in nature... that is, multiple Set Device on buttons on a keypad are in flight and issued at slightly different times. And I think this messes up the internal logic in the plug-in... exposes a race-condition, if you want... or a case where events are not serialized in the correct order.... of course, I'm 100% speculating here, I have no idea how the plug-in works... but I thought this problem might be interesting to share.

    This reproducer isn't 100% like the events I have where I also see problems... in particular in my events I don't set the same button multiple times shortly after each other (my events set different buttons shortly after each other). I'm going to try to create a repro that's closer to the problems I'm seeing.

    (As for "[...] you need a good RF network, AND a good Powerline network to have a rock-solid Insteon system." ... I hate for this to be a philosophical discussion... but... if we have retries and retries are working correctly, the underlying network shouldn't need to be rock-solid. Things will be slower, sure, but things would work either work 100% of the time or 0% of the time. Exactly how TCP connections work, they may be slow but you are guaranteed to get the data in the right order, no duplicates, and no missing data.)

    Thanks,
    David

    [1] :

    Apr-03 4:36:52 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:36:52 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:36:52 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 1F 2E 00 00 09 04 00 00 00 00 00 00 00 00 00 00 C5 06
    Apr-03 4:36:51 PM Insteon Sending command 02 62 52 5B D4 1F 2E 00 00 09 04 00 00 00 00 00 00 00 00 00 00 C5 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:36:51 PM Insteon Checking for keypadlinc button sync on device 52.5B.D4 src index 3, SrcIsSyncTarget=True...
    Apr-03 4:36:51 PM Insteon Setting status and value for device 52.5B.D4:3. Old status:0 Old Value:0, New Status:2 New Value:100
    Apr-03 4:36:51 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 00 00
    Apr-03 4:36:51 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 00 00
    Apr-03 4:36:51 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 0F 19 01 06
    Apr-03 4:36:51 PM Insteon Sending command 02 62 52 5B D4 0F 19 01 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:36:51 PM Insteon Attempting to get a KPL LED status response from Insteon device 52.5B.D4
    Apr-03 4:36:51 PM Insteon CAPIControl: Label=On, Value=100, ControlType=Button
    Apr-03 4:36:51 PM Device Control Device: First Floor Foyer Foyer Keypad - Button C (Day) to On (100) by/from: CAPI Control Handler
    Apr-03 4:36:51 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:36:51 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:36:50 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 1F 2E 00 00 09 00 00 00 00 00 00 00 00 00 00 00 C9 06
    Apr-03 4:36:50 PM Insteon Sending command 02 62 52 5B D4 1F 2E 00 00 09 00 00 00 00 00 00 00 00 00 00 00 C9 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:36:50 PM Insteon Checking for keypadlinc button sync on device 52.5B.D4 src index 3, SrcIsSyncTarget=True...
    Apr-03 4:36:50 PM Insteon Setting status and value for device 52.5B.D4:3. Old status:0 Old Value:0, New Status:3 New Value:0
    Apr-03 4:36:50 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 00 04
    Apr-03 4:36:50 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 00 04
    Apr-03 4:36:49 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 0F 19 01 06
    Apr-03 4:36:49 PM Insteon Sending command 02 62 52 5B D4 0F 19 01 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:36:49 PM Insteon Attempting to get a KPL LED status response from Insteon device 52.5B.D4
    Apr-03 4:36:49 PM Insteon CAPIControl: Label=Off, Value=0, ControlType=Button
    Apr-03 4:36:49 PM Device Control Device: First Floor Foyer Foyer Keypad - Button C (Day) to Off (0) by/from: CAPI Control Handler
    Apr-03 4:36:11 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:36:11 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:36:11 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 1F 2E 00 00 09 04 00 00 00 00 00 00 00 00 00 00 C5 06
    Apr-03 4:36:11 PM Insteon Sending command 02 62 52 5B D4 1F 2E 00 00 09 04 00 00 00 00 00 00 00 00 00 00 C5 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:36:11 PM Insteon Did not receive a response from Foyer Foyer Keypad (52.5B.D4). Try #1 failed.
    Apr-03 4:36:06 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 2E 00 Debouncing repeat.
    Apr-03 4:36:05 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 1F 2E 00 00 09 04 00 00 00 00 00 00 00 00 00 00 C5 06
    Apr-03 4:36:05 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:36:05 PM Insteon Sending command 02 62 52 5B D4 1F 2E 00 00 09 04 00 00 00 00 00 00 00 00 00 00 C5 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:36:05 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:36:04 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 1F 2E 00 00 09 0A 00 00 00 00 00 00 00 00 00 00 BF 06
    Apr-03 4:36:04 PM Insteon Checking for keypadlinc button sync on device 52.5B.D4 src index 4, SrcIsSyncTarget=True...
    Apr-03 4:36:04 PM Insteon Setting status and value for device 52.5B.D4:4. Old status:100 Old Value:100, New Status:3 New Value:0
    Apr-03 4:36:04 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 00 0C
    Apr-03 4:36:04 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
    Apr-03 4:36:04 PM Insteon ..Got NAK from the RF PLM for command
    Apr-03 4:36:04 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 00 0C
    Apr-03 4:36:04 PM Insteon Sending command 02 62 52 5B D4 1F 2E 00 00 09 0A 00 00 00 00 00 00 00 00 00 00 BF to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:36:04 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 0F 19 01 06
    Apr-03 4:36:04 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:36:04 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:36:03 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
    Apr-03 4:36:03 PM Insteon ..Got NAK from the RF PLM for command
    Apr-03 4:36:03 PM Insteon Sending command 02 62 52 5B D4 0F 19 01 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:36:03 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 1F 2E 00 00 09 0D 00 00 00 00 00 00 00 00 00 00 BC 06
    Apr-03 4:36:03 PM Insteon Attempting to get a KPL LED status response from Insteon device 52.5B.D4
    Apr-03 4:36:03 PM Insteon CAPIControl: Label=Off, Value=0, ControlType=Button
    Apr-03 4:36:03 PM Insteon Checking for keypadlinc button sync on device 52.5B.D4 src index 3, SrcIsSyncTarget=True...
    Apr-03 4:36:03 PM Insteon Setting status and value for device 52.5B.D4:3. Old status:100 Old Value:100, New Status:3 New Value:0
    Apr-03 4:36:03 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 00 0E
    Apr-03 4:36:03 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
    Apr-03 4:36:03 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 00 0E
    Apr-03 4:36:03 PM Insteon ..Got NAK from the RF PLM for command
    Apr-03 4:36:02 PM Insteon Sending command 02 62 52 5B D4 1F 2E 00 00 09 0D 00 00 00 00 00 00 00 00 00 00 BC to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:36:02 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 0F 19 01 06
    Apr-03 4:36:02 PM Insteon Checking for keypadlinc button sync on device 52.5B.D4 src index 1, SrcIsSyncTarget=True...
    Apr-03 4:36:02 PM Insteon Setting status and value for device 52.5B.D4:1. Old status:100 Old Value:100, New Status:3 New Value:0
    Apr-03 4:36:02 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 13 00
    Apr-03 4:36:02 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
    Apr-03 4:36:02 PM Insteon ..Got NAK from the RF PLM for command
    Apr-03 4:36:02 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 13 00
    Apr-03 4:36:02 PM Insteon Sending command 02 62 52 5B D4 0F 19 01 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:36:02 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 0F 13 00 06
    Apr-03 4:36:02 PM Insteon Attempting to get a KPL LED status response from Insteon device 52.5B.D4
    Apr-03 4:36:02 PM Insteon CAPIControl: Label=Off, Value=0, ControlType=Button
    Apr-03 4:36:02 PM Insteon Checking for keypadlinc button sync on device 52.5B.D4 src index 2, SrcIsSyncTarget=True...
    Apr-03 4:36:02 PM Insteon Setting status and value for device 52.5B.D4:2. Old status:100 Old Value:100, New Status:3 New Value:0
    Apr-03 4:36:02 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
    Apr-03 4:36:02 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 00 0F
    Apr-03 4:36:02 PM Insteon ..Got NAK from the RF PLM for command
    Apr-03 4:36:02 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 00 0F
    Apr-03 4:36:01 PM Insteon Sending command 02 62 52 5B D4 0F 13 00 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:36:01 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 0F 19 01 06
    Apr-03 4:36:01 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:36:01 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:36:01 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
    Apr-03 4:36:01 PM Insteon ..Got NAK from the RF PLM for command
    Apr-03 4:36:00 PM Insteon Sending command 02 62 52 5B D4 0F 19 01 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:36:00 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 1F 2E 00 00 09 0F 00 00 00 00 00 00 00 00 00 00 BA 06
    Apr-03 4:36:00 PM Insteon Attempting to get a KPL LED status response from Insteon device 52.5B.D4
    Apr-03 4:36:00 PM Insteon CAPIControl: Label=Off, Value=0, ControlType=Button
    Apr-03 4:36:00 PM Insteon CAPIControl: Label=Off, Value=0, ControlType=Button
    Apr-03 4:36:00 PM Insteon Sending command 02 62 52 5B D4 1F 2E 00 00 09 0F 00 00 00 00 00 00 00 00 00 00 BA to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:36:00 PM Insteon Checking for keypadlinc button sync on device 52.5B.D4 src index 4, SrcIsSyncTarget=True...
    Apr-03 4:36:00 PM Insteon Setting status and value for device 52.5B.D4:4. Old status:0 Old Value:0, New Status:2 New Value:100
    Apr-03 4:36:00 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 00 07
    Apr-03 4:36:00 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 00 07
    Apr-03 4:36:00 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 0F 19 01 06
    Apr-03 4:36:00 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:36:00 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:35:59 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
    Apr-03 4:35:59 PM Insteon ..Got NAK from the RF PLM for command
    Apr-03 4:35:59 PM Insteon Sending command 02 62 52 5B D4 0F 19 01 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:35:59 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 1F 2E 00 00 09 07 00 00 00 00 00 00 00 00 00 00 C2 06
    Apr-03 4:35:59 PM Insteon Attempting to get a KPL LED status response from Insteon device 52.5B.D4
    Apr-03 4:35:59 PM Insteon CAPIControl: Label=On, Value=100, ControlType=Button
    Apr-03 4:35:59 PM Insteon Sending command 02 62 52 5B D4 1F 2E 00 00 09 07 00 00 00 00 00 00 00 00 00 00 C2 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:35:59 PM Insteon Checking for keypadlinc button sync on device 52.5B.D4 src index 3, SrcIsSyncTarget=True...
    Apr-03 4:35:59 PM Insteon Setting status and value for device 52.5B.D4:3. Old status:0 Old Value:0, New Status:2 New Value:100
    Apr-03 4:35:59 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 00 03
    Apr-03 4:35:59 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 00 03
    Apr-03 4:35:58 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 0F 19 01 06
    Apr-03 4:35:58 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:35:58 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 2E 00
    Apr-03 4:35:58 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
    Apr-03 4:35:58 PM Insteon ..Got NAK from the RF PLM for command
    Apr-03 4:35:58 PM Insteon Sending command 02 62 52 5B D4 0F 19 01 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:35:58 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 1F 2E 00 00 09 03 00 00 00 00 00 00 00 00 00 00 C6 06
    Apr-03 4:35:57 PM Insteon Attempting to get a KPL LED status response from Insteon device 52.5B.D4
    Apr-03 4:35:57 PM Insteon CAPIControl: Label=On, Value=100, ControlType=Button
    Apr-03 4:35:57 PM Insteon Sending command 02 62 52 5B D4 1F 2E 00 00 09 03 00 00 00 00 00 00 00 00 00 00 C6 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:35:57 PM Insteon Checking for keypadlinc button sync on device 52.5B.D4 src index 2, SrcIsSyncTarget=True...
    Apr-03 4:35:57 PM Insteon Setting status and value for device 52.5B.D4:2. Old status:0 Old Value:0, New Status:2 New Value:100
    Apr-03 4:35:57 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 00 01
    Apr-03 4:35:57 PM Device Control Device: First Floor Foyer Foyer Keypad - Button D (Guest Mode) to Off (0)
    Apr-03 4:35:57 PM Device Control Device: First Floor Foyer Foyer Keypad - Button C (Day) to Off (0)
    Apr-03 4:35:57 PM Device Control Device: First Floor Foyer Foyer Keypad - Button B (Outside Lights) to Off (0)
    Apr-03 4:35:57 PM Device Control Device: First Floor Foyer Foyer Keypad - Button A/Load (Morning) to Off (0)
    Apr-03 4:35:57 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 00 01
    Apr-03 4:35:57 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 0F 19 01 06
    Apr-03 4:35:57 PM Insteon Checking for keypadlinc button sync on device 52.5B.D4 src index 1, SrcIsSyncTarget=True...
    Apr-03 4:35:57 PM Insteon Setting status and value for device 52.5B.D4:1. Old status:0 Old Value:0, New Status:2 New Value:100
    Apr-03 4:35:57 PM Insteon Received a Direct ACK from Foyer Foyer Keypad (52.5B.D4): 52 5B D4 4C 14 C5 2F 11 FF
    Apr-03 4:35:57 PM Insteon ..Retry #1 required. Pausing 250ms for RF PLM to clear...
    Apr-03 4:35:57 PM Insteon ..Got NAK from the RF PLM for command
    Apr-03 4:35:57 PM Insteon Received STX 0x50 (Raw Insteon Rec):52 5B D4 4C 14 C5 2F 11 FF
    Apr-03 4:35:56 PM Insteon Sending command 02 62 52 5B D4 0F 19 01 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:35:56 PM Insteon ..Got RF PLM Response 02 62 52 5B D4 0F 11 FF 06
    Apr-03 4:35:56 PM Insteon Attempting to get a KPL LED status response from Insteon device 52.5B.D4
    Apr-03 4:35:56 PM Insteon CAPIControl: Label=On, Value=100, ControlType=Button
    Apr-03 4:35:56 PM Insteon Sending command 02 62 52 5B D4 0F 11 FF to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    Apr-03 4:35:56 PM Insteon CAPIControl: Label=On, Value=100, ControlType=Button
    Apr-03 4:35:56 PM Device Control Device: First Floor Foyer Foyer Keypad - Button D (Guest Mode) to On (100)
    Apr-03 4:35:56 PM Device Control Device: First Floor Foyer Foyer Keypad - Button C (Day) to On (100)
    Apr-03 4:35:56 PM Device Control Device: First Floor Foyer Foyer Keypad - Button B (Outside Lights) to On (100)
    Apr-03 4:35:56 PM Device Control Device: First Floor Foyer Foyer Keypad - Button A/Load (Morning) to On (100)
    Apr-03 4:35:56 PM Event Event Trigger "Misc Insteon On/Off"
    Apr-03 4:35:56 PM Event Event Misc Insteon On/Off triggered by the event page 'Run' button.


    Leave a comment:


  • Burrington
    replied
    Here are a couple links to discussions on resolving Insteon/X10 Powerline Communication problems. In my experience, you need a good RF network, AND a good Powerline network to have a rock-solid Insteon system. When you achieve that, its even better than Z-wave because it has two paths to work with.

    http://board.homeseer.com/showthread...38#post1201038

    http://board.homeseer.com/showthread...ne#post1226477






    Leave a comment:


  • davidz25
    replied
    I don't have any log files right here but I just turned on "Detailed" logging and will follow up the next time this happens... might take a day or two!

    Leave a comment:


  • mnsandler
    replied
    do you have any insteon error report log files, or hs log exports that show the plugin giving up before it reaches 25 retries

    Leave a comment:


  • davidz25
    replied
    Thanks for the suggestion, I'll look into Groups and see if that works for how I'm using it.

    First, a comment about logging.. the plug-in obviously knows when something goes wrong (since it conveys the failure in the comm reliability numbers) but in the default setup, nothing is ever mentioned in the log. I tried playing around with the logging settings but it's either full firehose (with hard to understand language) or nothing useful at all. I would think that something as catastrophic as not being able to send a command to a keypad to turn a button on, would result in a log entry in the default install, no? I mean, something like

    Apr-03 12:42:58 PM Insteon Error while setting Foyer Foyer Keypad Button F: Foyer Keypad - Button F (Island) (52.5B.D4) to OFF (failed after 25 retries with 5 seconds between each retry)

    would be extremely helpful.

    Second, with full logging on, it doesn't seem like it actually performs 25 retries with 5 second timeouts... I don't pretend to understand how Insteon is working, but could it be possible that something is broken in the plug-in's retry logic?

    Leave a comment:


  • mnsandler
    replied
    if you haven't changed anything recently in your home automation setup, then it will be difficult to diagnose the comm issue. an 900Mhz RF freq scanner can do wonders for identifying noise that is interfering. Also, you still need to isolate noisy electrical devices that are plugged in.

    i do have one suggestion, instead of sending a bunch of individual on/off commands to the various keypad buttons, create a Group in the plugin that can control all the necessary buttons with one command. There are insteon actions to turn a Group on/off. this will reduce the insteon traffic significantly.

    Leave a comment:


  • davidz25
    started a topic Comm Reliability getting worse

    Comm Reliability getting worse

    Hi,

    I have a setup which is mostly Z-Wave and Philips Hue but where the keypads are Insteon (I have 5 Insteon keypads, 5 insteon outlets, 72 Z-Wave devices, and 25 Hue devices). These keypads are used mostly to enable/disable scenes and convey whether a scene is enabled [1]. Most scenes (think "night", "morning", "day", "evening") are triggered by either time-of-day or motion sensors ... that is, we rarely press any buttons.... as such, most of the traffic to my Insteon keypads are from Homeseer to enable/disable a button (and rarely from a keypad to Homeseer). So far, so good.

    Here's an example of the keypad in my foyer:





    and here are the rules that trigger the "Island" button (button F):





    This works reasonably well but I'm running into comm reliability problems and it's been getting worse the past few weeks... it used to be around 98-99%% but nowadays it seems to be in the low nineties. Essentially every other day, a button isn't updated (e.g. it fails to turn on or off) and I have to manually push it. It's annoying to the point that I'm ready to rip the keypads out of the wall and replace them with something else... but figured I'd post about it here before doing anything that drastic!

    Here are some more details about my setup:
    • Insteon 2413U USB Modem Interface, Dual-Band (White)
      • Placed centrally in house, no farther than 20 feet from any keypad and no more than 2-3 walls to penetrate
      • Only other device on the circuit is a lamp
    • 5 x dual-band keypads (combination of dimmers and switches, one 6-button, four 8-button)
    • 5 x dual-band dual on/off outlets
    I've configured the Insteon plug-in with
    • Maximum hops: 4
    • Command retries: 25
    • Response Timeout (sec): 5
    and the "[x] Perform group clean-ups when transmitting group commands" is checked (no idea what that even means).

    One other note about my setup is that a lot of the keypad buttons are turned on/off at the same time... e.g. when my house transitions from day to evening mode, the following happens:
    • Foyer Keypad:
      • Day button turns off
      • Evening button turns on
      • Outside Lights button turns on
    • Living Room Keypad
      • Lamps button turns on
    • Hallway Keypad
      • Driveway button turns on
    • Front Door Keypad
      • Path Lights button turns on
      • Post Light button turns on
    So this is 7 commands being sent from Homeseer to my keypads at the same time.. could that be the problem? I tried spacing out some of these events and it seemed to have helped a little bit... but it's still not good enough.

    FWIW, I'm surprised comm reliability is this bad... it's almost as if there are no retries being done at all and it's just like UDP where packets can be lost. I mean, with proper retries I'd expect comm reliability either to be 0% or 100% just like with how e.g. TCP works ... that is, it keeps retrying and may be slow but it'll get there eventually.... In stark contrast, my Z-Wave setup has been rock solid, never experienced any packet loss there... I have experienced slow-downs and pop-corn effects but that's fine, the point is that eventually it converges against being correct.

    Thanks for any insight!

    Regards,
    David

    [1] : the use of the word "scene" in this post is meant in the abstract sense... e.g. not Z-Wave or Insteon native scenes... e.g. the way I use scenes is that for each scene I have a device in Homeseer to track whether it's enabled and then events to configure lights when this device is turned on and off.
Working...
X