Announcement

Collapse
No announcement yet.

Significant delays and unreliable actions

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    Just tried changing those settings. First off, can you confirm I did it correctly?
    I quit out of H3Pro and then went to this file...

    C:\Program Files (x86)\HomeSeer HS3\Config\Insteon.ini

    added these lines...

    [Tuning]
    SettleTime=250


    I then started up H3Pro and tried both manual event running as well as FastON/OFF
    RESULTS
    Manual = STILL WORKS: lights come on immediately and all at the same time.
    FastON/OFF = STILL BROKEN: lights come on in scattered sequence, rather then all at once.



    I then quit out of H3Pro and went back to same file and updated those lines to...

    [Tuning]
    SettleTime=250
    PLMClearDelay=300


    I then started up H3Pro and tried both manual event running as well as FastON/OFF
    RESULTS
    Manual = STILL WORKS: lights come on immediately and all at the same time.
    FastON/OFF = STILL BROKEN: lights come on in scattered sequence, rather then all at once.

    Comment


      #32
      if you are still seeing the NAKs from the PLM in the log, then increase the settletime in 50ms increments.

      one other test, put in a 2 sec delay prior to the event action being fired. use the "After Waiting" associated with the Control a Device action
      Mark

      HS3 Pro 4.2.19.5
      Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway | Tuya Smart Plugs
      Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 | Ultra1Wire3 | RFXCOM | HS MyQ | BLRadar | BLDenon | Tuya | Jon00 Charting | Jon00 Links
      Platform: Windows Server 2022 Standard, i5-12600K/3.7GHz/10 core, 16GB RAM, 500GB SSD

      Comment


        #33
        Originally posted by mnsandler View Post
        if you are still seeing the NAKs from the PLM in the log, then increase the settletime in 50ms increments.

        one other test, put in a 2 sec delay prior to the event action being fired. use the "After Waiting" associated with the Control a Device action
        Ok, I'll test this out tonight.
        Can you offer up what you think the problem is and what might be the cause?
        What I mean is, if this might be noise on the line issue, maybe I can put filters on or something. If this is a legacy PLM hardware or FW issue, I'd be more then happy to buy a new one.

        But what I'd be pretty unhappy with, is if there is no real fix and I just have to accept that it will never work quite right.

        Comment


          #34
          Originally posted by iDVB View Post
          Ok, I'll test this out tonight.
          Can you offer up what you think the problem is and what might be the cause?
          What I mean is, if this might be noise on the line issue, maybe I can put filters on or something. If this is a legacy PLM hardware or FW issue, I'd be more then happy to buy a new one.

          But what I'd be pretty unhappy with, is if there is no real fix and I just have to accept that it will never work quite right.
          the problem is the triggering switch is still sending msgs while the plugin is trying to transmit the group cmd. the plm can't handle all the traffic at the same time even though your plm seems to be fairly new.

          focus on the timing settings i mentioned. this should help
          Mark

          HS3 Pro 4.2.19.5
          Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway | Tuya Smart Plugs
          Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 | Ultra1Wire3 | RFXCOM | HS MyQ | BLRadar | BLDenon | Tuya | Jon00 Charting | Jon00 Links
          Platform: Windows Server 2022 Standard, i5-12600K/3.7GHz/10 core, 16GB RAM, 500GB SSD

          Comment


            #35
            Sigh. I'm less and less hopeful with Insteon and Homeseer.
            I have a build coming up in a week, we're just about to order about 5K worth of Homeseer and Insteon gear and I can't even get the gear in my home to work.

            I've been monkeying with these timing settings and still have made zero progress.

            First off... each time I enter them into...
            C:\Program Files (x86)\HomeSeer HS3\Config\Insteon.ini

            I see this in the Homeseer logs on boot...
            3/20/2016 1:42:36 PM ~!~Error~!~In ReadINI:Item has already been added. Key in dictionary: 'tuning' Key being added: 'tuning'

            So first, I don't think how I'm adding them is correct, or something else is wrong. Second... since one of the two problems I see is that there is a large delay between the FastOff and the action.... I feel like even if I manage to get a 10min delay to finally get the group to turn off at the same time... I still have the issue of a 10min delay.

            It's like I can choose one or the other. Either they turn off in sync with a LARGE delay. Or I have a smaller delay but many times they don't turn off at all or in sync.

            Comment


              #36
              Ok, I figured out a single thing.... even though I add the Tuning to the bottom of the ini file.... on restart... Homeseer moves it further up in the file. So I should now be able to run more tests by editing it in place.

              Discovered another odd thing. If I set the event to...


              Then if I turn the light off... and wait 6-8 secs .. the group turns off IN-SYNC.

              If I run that same test but the moment the group of lights turns OFF, I then turn that switch ON.
              Then only that light goes ON...6-8sec delay ....then that light goes OFF ...6-8sec delay... and then they all come back on.
              .... no idea.


              Here is the log from that test...

              Mar-20 2:03:19 PM Insteon The device 2A.27.22 heard and executed the group broadcast command.
              Mar-20 2:03:19 PM Insteon Received STX 0x50 (Raw Insteon Rec):2A 27 22 23 9D 27 66 11 0A
              Mar-20 2:03:19 PM Insteon ..Got RF PLM Response 02 62 2A 27 22 4A 11 0A 06
              Mar-20 2:03:18 PM Insteon Received STX 0x50 (Raw Insteon Rec):2A 33 0A 23 9D 27 62 11 0A Debouncing repeat.
              Mar-20 2:03:18 PM Insteon Sending command 02 62 2A 27 22 4A 11 0A to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
              Mar-20 2:03:18 PM Insteon The device 2A.33.0A heard and executed the group broadcast command.
              Mar-20 2:03:18 PM Insteon Received STX 0x50 (Raw Insteon Rec):2A 33 0A 23 9D 27 66 11 0A
              Mar-20 2:03:18 PM Insteon ..Got RF PLM Response 02 62 2A 33 0A 4A 11 0A 06
              Mar-20 2:03:18 PM Insteon Sending command 02 62 2A 33 0A 4A 11 0A to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
              Mar-20 2:03:18 PM Insteon The device 2A.2B.2F heard and executed the group broadcast command.
              Mar-20 2:03:18 PM Insteon Received STX 0x50 (Raw Insteon Rec):2A 2B 2F 23 9D 27 66 11 0A
              Mar-20 2:03:17 PM Insteon ..Got RF PLM Response 02 62 2A 2B 2F 4A 11 0A 06
              Mar-20 2:03:17 PM Insteon Sending command 02 62 2A 2B 2F 4A 11 0A to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
              Mar-20 2:03:17 PM Insteon * Now Initiating group clean-ups for group 10...
              Mar-20 2:03:17 PM Insteon ..Got RF PLM Response 02 62 00 00 0A CA 11 00 06
              Mar-20 2:03:17 PM Insteon Sending command 02 62 00 00 0A CA 11 00 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
              Mar-20 2:03:17 PM Insteon TransmitGroupMsg called for device code: Group:10, RF PLM Group 10
              Mar-20 2:03:17 PM Insteon Setting status and value for device 2A.27.22:1. Old status:0 Old Value:0, New Status:2 New Value:100
              Mar-20 2:03:17 PM Insteon ProcessGroupBroadcastUpdateResponders: Located remote link record match for group broadcast - Device:2A.27.22 link record #7 target channel 1
              Mar-20 2:03:17 PM Insteon Setting status and value for device 2A.33.0A:1. Old status:100 Old Value:100, New Status:2 New Value:100
              Mar-20 2:03:17 PM Insteon ProcessGroupBroadcastUpdateResponders: Located remote link record match for group broadcast - Device:2A.33.0A link record #7 target channel 1
              Mar-20 2:03:17 PM Insteon Setting status and value for device 2A.2B.2F:1. Old status:0 Old Value:0, New Status:2 New Value:100
              Mar-20 2:03:17 PM Insteon ProcessGroupBroadcastUpdateResponders: Located remote link record match for group broadcast - Device:2A.2B.2F link record #7 target channel 1
              Mar-20 2:03:17 PM Insteon Setting value for Group:10
              Mar-20 2:03:17 PM Device Control Device: ManCave Group PotLights to On (1)
              Mar-20 2:03:15 PM Insteon The device 2A.27.22 heard and executed the group broadcast command.
              Mar-20 2:03:15 PM Insteon Received STX 0x50 (Raw Insteon Rec):2A 27 22 23 9D 27 66 13 0A
              Mar-20 2:03:15 PM Insteon ..Got RF PLM Response 02 62 2A 27 22 4A 13 0A 06
              Mar-20 2:03:15 PM Insteon Sending command 02 62 2A 27 22 4A 13 0A to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
              Mar-20 2:03:15 PM Insteon The device 2A.33.0A heard and executed the group broadcast command.
              Mar-20 2:03:15 PM Insteon Received STX 0x50 (Raw Insteon Rec):2A 33 0A 23 9D 27 66 13 0A
              Mar-20 2:03:14 PM Insteon Device ManCave PotLightsFrontRow (2A.33.0A) sent a group cleanup report. 1 devices didn't respond. 01 2A 33 0A 11 01 01 CB 06 01
              Mar-20 2:03:14 PM Insteon Received STX 0x50 (Raw Insteon Rec):2A 33 0A 11 01 01 CB 06 01
              Mar-20 2:03:14 PM Insteon Received STX 0x50 (Raw Insteon Rec):2A 33 0A 00 01 01 CB 11 01
              Mar-20 2:03:13 PM Insteon ..Got RF PLM Response 02 62 2A 33 0A 4A 13 0A 06
              Mar-20 2:03:12 PM Insteon ..Retry #1 required. Pausing 300ms for RF PLM to clear...
              Mar-20 2:03:12 PM Insteon ..Got NAK from the RF PLM for command
              Mar-20 2:03:12 PM Event Event Trigger "ManCave ManCave GroupON"
              Mar-20 2:03:12 PM Insteon Setting status and value for device 2A.33.0A:1. Old status:0 Old Value:0, New Status:2 New Value:100
              Mar-20 2:03:12 PM Insteon ProcessGroupBroadcast: Device ManCave PotLightsFrontRow (2A.33.0A) is group broadcast source (tgt group/button:1) sending cmd 11
              Mar-20 2:03:12 PM Insteon Received 2A.33.0A:1 (ManCave PotLightsFrontRow) Go ON
              Mar-20 2:03:12 PM Insteon Received STX 0x50 (Raw Insteon Rec):2A 33 0A 00 00 01 CB 11 00
              Mar-20 2:03:12 PM Insteon Sending command 02 62 2A 33 0A 4A 13 0A to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
              Mar-20 2:03:12 PM Insteon The device 2A.2B.2F heard and executed the group broadcast command.
              Mar-20 2:03:12 PM Insteon Received STX 0x50 (Raw Insteon Rec):2A 2B 2F 23 9D 27 66 13 0A
              Mar-20 2:03:12 PM Insteon ..Got RF PLM Response 02 62 2A 2B 2F 4A 13 0A 06
              Mar-20 2:03:11 PM Insteon Sending command 02 62 2A 2B 2F 4A 13 0A to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
              Mar-20 2:03:11 PM Insteon * Now Initiating group clean-ups for group 10...
              Mar-20 2:03:11 PM Insteon ..Got RF PLM Response 02 62 00 00 0A CA 13 00 06
              Mar-20 2:03:11 PM Insteon Sending command 02 62 00 00 0A CA 13 00 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
              Mar-20 2:03:11 PM Insteon TransmitGroupMsg called for device code: Group:10, RF PLM Group 10
              Mar-20 2:03:11 PM Insteon Setting status and value for device 2A.27.22:1. Old status:100 Old Value:100, New Status:3 New Value:0
              Mar-20 2:03:11 PM Insteon ProcessGroupBroadcastUpdateResponders: Located remote link record match for group broadcast - Device:2A.27.22 link record #7 target channel 1
              Mar-20 2:03:11 PM Insteon Setting status and value for device 2A.33.0A:1. Old status:0 Old Value:0, New Status:3 New Value:0
              Mar-20 2:03:11 PM Insteon ProcessGroupBroadcastUpdateResponders: Located remote link record match for group broadcast - Device:2A.33.0A link record #7 target channel 1
              Mar-20 2:03:11 PM Insteon Setting status and value for device 2A.2B.2F:1. Old status:100 Old Value:100, New Status:3 New Value:0
              Mar-20 2:03:11 PM Insteon ProcessGroupBroadcastUpdateResponders: Located remote link record match for group broadcast - Device:2A.2B.2F link record #7 target channel 1
              Mar-20 2:03:11 PM Insteon Setting value for Group:10
              Mar-20 2:03:11 PM Device Control Device: ManCave Group PotLights to Off (2)
              Mar-20 2:03:09 PM Insteon Device ManCave PotLightsFrontRow (2A.33.0A) sent a group cleanup report. 1 devices didn't respond. 01 2A 33 0A 13 01 01 CB 06 01
              Mar-20 2:03:09 PM Insteon Received STX 0x50 (Raw Insteon Rec):2A 33 0A 13 01 01 CB 06 01
              Mar-20 2:03:08 PM Insteon Received STX 0x50 (Raw Insteon Rec):2A 33 0A 00 01 01 CB 13 01
              Mar-20 2:03:06 PM Event Event Trigger "ManCave ManCave GroupOFF"
              Mar-20 2:03:06 PM Insteon Setting status and value for device 2A.33.0A:1. Old status:100 Old Value:100, New Status:3 New Value:0
              Mar-20 2:03:06 PM Insteon ProcessGroupBroadcast: Device ManCave PotLightsFrontRow (2A.33.0A) is group broadcast source (tgt group/button:1) sending cmd 13
              Mar-20 2:03:06 PM Insteon Received 2A.33.0A:1 (ManCave PotLightsFrontRow) Go OFF
              Mar-20 2:03:06 PM Insteon Received STX 0x50 (Raw Insteon Rec):2A 33 0A 00 00 01 CB 13 00

              Comment


                #37
                @mnsandler - Do I have the option of using an Insteon Hub with your plugin instead?
                - Would that maybe work more reliably?
                - Would I loose any functionality?

                Also, I'm reading over your docs again... and I don't believe I've ever installed the ftdi chipset drivers. Could that be it?

                I have a Serial PLM (but no serial port on my PC) and a USB-Serial adapter. This PLM seems to work flawlessly with my ISY so I was going to try it with my PC/Homeseer/InsteonPlugin but I can't seem to get your plugin to recognize it. I says it can't reach COM4 and that device on Windows says its not setup.

                Comment


                  #38
                  Originally posted by iDVB View Post
                  @mnsandler - Do I have the option of using an Insteon Hub with your plugin instead?
                  - Would that maybe work more reliably?
                  - Would I loose any functionality?

                  Also, I'm reading over your docs again... and I don't believe I've ever installed the ftdi chipset drivers. Could that be it?

                  I have a Serial PLM (but no serial port on my PC) and a USB-Serial adapter. This PLM seems to work flawlessly with my ISY so I was going to try it with my PC/Homeseer/InsteonPlugin but I can't seem to get your plugin to recognize it. I says it can't reach COM4 and that device on Windows says its not setup.
                  i wouldn't change to the hub. the response time is slower.

                  your usb-serial adapter already installed some drivers to make the serial port. the ftdi drivers are for making a virtual com port for the usb plm (2413U) device. no need for that with a 2413s.

                  does com4 show up in the windows device manager?
                  Mark

                  HS3 Pro 4.2.19.5
                  Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway | Tuya Smart Plugs
                  Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 | Ultra1Wire3 | RFXCOM | HS MyQ | BLRadar | BLDenon | Tuya | Jon00 Charting | Jon00 Links
                  Platform: Windows Server 2022 Standard, i5-12600K/3.7GHz/10 core, 16GB RAM, 500GB SSD

                  Comment


                    #39
                    have you tried the delay associated with any action?

                    see the attached pic
                    Attached Files
                    Mark

                    HS3 Pro 4.2.19.5
                    Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway | Tuya Smart Plugs
                    Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 | Ultra1Wire3 | RFXCOM | HS MyQ | BLRadar | BLDenon | Tuya | Jon00 Charting | Jon00 Links
                    Platform: Windows Server 2022 Standard, i5-12600K/3.7GHz/10 core, 16GB RAM, 500GB SSD

                    Comment


                      #40
                      Originally posted by mnsandler View Post
                      i wouldn't change to the hub. the response time is slower.



                      your usb-serial adapter already installed some drivers to make the serial port. the ftdi drivers are for making a virtual com port for the usb plm (2413U) device. no need for that with a 2413s.



                      does com4 show up in the windows device manager?

                      Yes, windows shows COM4 but says device could not be contacted.


                      Sent from my iPhone using Tapatalk

                      Comment


                        #41
                        Originally posted by mnsandler View Post
                        have you tried the delay associated with any action?



                        see the attached pic

                        Yes, I have a 5 second delay on both the on and the off of my example just above and still able to make that glitch happen.


                        Sent from my iPhone using Tapatalk

                        Comment

                        Working...
                        X