Announcement

Collapse
No announcement yet.

Insteon PLM Plug-in Version 1.5 (license required)

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

    #61
    Originally posted by kuntakintay View Post
    GroupBaseCode and DeviceBaseCode both equal [. The Only group I have configured has a code of [1. The devices all use the [ code. So it appears to be configured correctly? Or should these be different? However if I change the group device value it shows that it is changing it in the hs log but nothing happens. If I try to change a device, not group value it works fine. Also, the plm is recieving and logging device button presses and on/off commands. Its really strange and I am at a total loss as to what to do next...

    With the x10 part, if I hit enable, it leaves the status as disabled and gives me the changes not saved. when i save it stays disabled. I tried disabling other then enabling x10 but that didnt work either...
    the GroupBaseCode and DeviceBaseCode should not be the same. shutdown hs, clear the value on the GroupBaseCode entry and restart hs. the plugin should pickup another/different housecode.

    did you notice the com port change when you hit enabled on the x10 interface?

    are there any errors in the hs log you can post
    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


      #62
      I have this same sort of strange issue enabling the Ocelot X-10 features. For some reason, Homeseer sometimes truncates the interface name when trying to enable it and can't find that truncated name (check your log, you see it's trying to enable "Inste"). At first I just shut down Homeseer and then enabled the interface by editting the settings.ini file and inserting the full name. Later, I discovered that I could localize the problem to attempting to enable the interface from a remote client, so ever since, whenever I have the problem I just open a browser on the HS box itself and to do the enabling and voila, it works. I don't know why and can't really even postulate (unless it has some strange thing to do with how HS handles a localhost request), but frankly, since the workaround has worked everytime since, I ceased to be interested enough to try to find out.

      Comment


        #63
        This "truncation" happens when using FireFox with HomeSeer pages. Try IE and it shouldn't truncate the entries.
        💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

        Comment


          #64
          I tried enabling using IE browser and worked fine. So it looks like I am good. Thanks to all 3 for assisting.

          PS - I use chrome, so looks like the truncation occurs both on Firefox and Chrome.
          HS 3.0.0.199 Pro/Insteon 3.0.5.20/3 Venstar Insteon Therms / Insteon Thermostat 3.0.2.2 / DirecTV 3.0.0.14 / OpenSprinkler 2.0.5.21 / ITunes DAAP 3.0.0.23/ UltraM1G3 3.0.5437.37424/ UltraWeatherbug3 /HSTouch Svr 3.0.0.68/Zwave 3.0.1.25/Ultramon3/Global Cache 5.0.0.17/Various BLXXX Plugins.

          Comment


            #65
            Originally posted by kuntakintay View Post
            I tried enabling using IE browser and worked fine. So it looks like I am good. Thanks to all 3 for assisting.

            PS - I use chrome, so looks like the truncation occurs both on Firefox and Chrome.
            glad you have it workiing.
            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


              #66
              mark, what is the latest release ? 1.5.0.2 ?

              thanks

              sjw

              Comment


                #67
                Originally posted by stevewinick View Post
                mark, what is the latest release ? 1.5.0.2 ?

                thanks

                sjw
                yah, that sounds right. i posted a small fix for you in the version
                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


                  #68
                  KPL Errors - Replaced PLM

                  Hi,
                  I have the paid version 1.5.0.0, and recently replaced my 2413S with a new one. Most of the address updating I had to do manually. I probably messed up in the replacement process.
                  The big problem I am having is with my KPLs which are mostly 8 button.
                  When I select Insteon->manage devices->Edit Insteon Device, none of the links show and I can not update the PLM/KPL/homeseer links. See bmp for "Edit Insteon Device" screen shot and attached zipped log.
                  Thanks for all your work and help.
                  Attached Files

                  Comment


                    #69
                    Sonny, please find 1.5.0.2 on the following thread. it should fix the issue.

                    http://forums.homeseer.com/showpost....0&postcount=37

                    thanks for your support
                    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


                      #70
                      post script on IOLinc polarity anomoly

                      hi, mark. as you recall, we left as an open question the issue of the behavior of the linking of a keypadlinc button to an iolinc. we did a workaround that functions correctly by linking "OFF" instead of "ON". in this first case, coincidently, when the sensor input for the IOLinc was closed (sensor LED lit), that was the correct state for the device i was controlling and linking to the keypadlinc also lit its LED. HS's reflected state and the results of polling were all the same. ON was ON was ON

                      i have a second application that i wanted to be the opposite. in this case, when the sensor input is closed and the LED lit, the device to be controlled is OFF. it's actually a garage door with a reed switch that is closed when the door is closed. i want my keypadlinc LED to light when the door opens as a warning. if the LED is ON, someone left the door open. i tried reversing all the states in the workaround and ended up looping the door's operation. what i realized is that as far as HS is concerned, its state is always wrong because no matter how the parameters are set, the result of a poll to HS is ALWAYS in sync with the sensor LED even if you want it to be the opposite and have set the "SetONCmd" accordingly. SetONCmd has no effect on the result of a poll

                      does this make sense? perhaps there is another parameter needed for the IOLinc to invert the sensed state when HS polls

                      hope i'm making myself clear

                      thanks, as always

                      sjw

                      Comment


                        #71
                        Just a couple more

                        Hi again,
                        Thanks for the fix, but there are a couple of stragglers.
                        One KPL and one LampLinc don't show links and will not update. Also, I have noticed that randomly the PLM would stop responding while "programing device for homeseer". If I unplug the AC and plug it in again the PLM starts to respond again.

                        Attached is the log from the new error perion.
                        Thanks again,
                        Attached Files

                        Comment


                          #72
                          problems with HS controlling IOLinc in Momentary C

                          hi, mark. found are more fundamental problem with controlling a momentary C iolinc from HS. we had a workaround for syncing keypadlincs to the iolinc. however, what i have found is that pure control from HS has some issues too. to be sure, i completely removed all links from the iolinc including HS and reprogrammed so that only HS is linked to the IOlinc

                          from the HOME STATUS page, i can properly control the iolinc. if i click ON, HS sends GoON and reflects ON in the status. same for OFF. i can't really tell if the Iolinc Momentary C is actually working because HS doesn't send anything at all if i click ON when it's already ON according to HS, but the HOME STATUS page works ok

                          however, if with an initial state of ON, i create a simple event that says GoOFF for the Iolinc, and i manually run it, it has no effect at all on the IOLinc. the event runs in the log, but nothing happens at the IOLinc. HS show the device OFF, but it's actually ON. i can run the event multiply with no changes. now the really weird part. if i go back to HOME and click OFF, nothing happens (HS thinks it's OFF so it does nothing). however, if i click ON, it goes OFF! HS thinks its ON, but it's OFF. if i click ON again, it goes ON and now it's back in sync. at this point HS is OK again. no event will ever turn the IOLinc OFF

                          so i experimented with events that turn the IOLinc ON. what i found is that if i create an identical simple event except this time programmed to GoON, every time i RUN the event, the state of the IOLinc toggles as though it was in Momentary A not C. below is a log clip that you can see. i am running the same event each time but it does the opposite each time. did it 4 times. twice it went on. twice it went off, alternating

                          it's as though HS is treating the IOLinc differently (like momentary A vs C) for an the event than when done manually

                          hope this helps. don't know if this is fundamentally related to the polarity inversion, but i can't find a workaround for this condition. i can't create any event that will turn the IOLinc OFF and can toggle every time with an ON event

                          thanks for your help. let me know if there is any other info that you need

                          sjw

                          10/24/2010 11:22:42 AM ~!~Event~!~Event Trigger "Stereo ON"
                          10/24/2010 11:22:42 AM ~!~Device Control~!~Device: Den Stereo - Zone 2 On/Off - Insteon (^12) ON
                          10/24/2010 11:22:42 AM ~!~Insteon~!~Processing SetIOEx for device - ^12 Cmd: 2 Bright: 0 Data1: 0 Data2: 0
                          10/24/2010 11:22:42 AM ~!~Insteon~!~Setting status and value for device ^12. Old status:3 Old Value:0, New Status:2 New Value:100
                          10/24/2010 11:22:42 AM ~!~Insteon~!~Sending command 02 62 0F 88 B1 0F 11 FF to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
                          10/24/2010 11:22:42 AM ~!~Insteon~!~..Got RF PLM Response 02 62 0F 88 B1 0F 11 FF 06
                          10/24/2010 11:22:43 AM ~!~Insteon~!~Received STX 0x50 (Raw Insteon Rec):01 0F 88 B1 13 AC A9 23 11 FF - Event: New msg for RF PLM, Src[0F.88.B1] Dst[13.AC.A9] {Ack/Dir} Cmd1: 11 Cmd2: FF
                          10/24/2010 11:22:43 AM ~!~Insteon~!~SyncResponderDevices called for device code: ^12
                          10/24/2010 11:22:43 AM ~!~Insteon~!~Received STX 0x50 (Raw Insteon Rec):01 0F 88 B1 00 00 01 CB 11 00 - Event: New msg for RF PLM, Src[0F.88.B1] Dst[--.--.--] {Grp Brdcst} Cmd1: Go ON Cmd2: 00
                          10/24/2010 11:22:43 AM ~!~Insteon~!~Received ^12 (Den Stereo - Zone 2 On/Off - Insteon) Go ON
                          10/24/2010 11:22:43 AM ~!~Insteon~!~ProcessGroupBroadcast: Device index 42 0F.88.B1 is group broadcast source (tgt group/button: 1) sending cmd 11
                          10/24/2010 11:22:43 AM ~!~Insteon~!~Setting status and value for device ^12. Old status:2 Old Value:100, New Status:2 New Value:100
                          10/24/2010 11:22:43 AM ~!~Insteon~!~Received STX 0x50 (Raw Insteon Rec):01 0F 88 B1 13 AC A9 41 11 01 - Event: New msg for RF PLM, Src[0F.88.B1] Dst[13.AC.A9] {Grp Cln} Cmd1: Go ON Cmd2: 01
                          10/24/2010 11:22:45 AM ~!~Event~!~Event Trigger "Stereo ON"
                          10/24/2010 11:22:45 AM ~!~Insteon~!~Processing SetIOEx for device - ^12 Cmd: 2 Bright: 0 Data1: 0 Data2: 0
                          10/24/2010 11:22:45 AM ~!~Device Control~!~Device: Den Stereo - Zone 2 On/Off - Insteon (^12) ON
                          10/24/2010 11:22:45 AM ~!~Insteon~!~Setting status and value for device ^12. Old status:2 Old Value:100, New Status:2 New Value:100
                          10/24/2010 11:22:45 AM ~!~Insteon~!~Sending command 02 62 0F 88 B1 0F 11 FF to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
                          10/24/2010 11:22:45 AM ~!~Insteon~!~..Got RF PLM Response 02 62 0F 88 B1 0F 11 FF 06
                          10/24/2010 11:22:45 AM ~!~Insteon~!~Received STX 0x50 (Raw Insteon Rec):01 0F 88 B1 13 AC A9 27 11 FF - Event: New msg for RF PLM, Src[0F.88.B1] Dst[13.AC.A9] {Ack/Dir} Cmd1: 11 Cmd2: FF
                          10/24/2010 11:22:45 AM ~!~Insteon~!~SyncResponderDevices called for device code: ^12
                          10/24/2010 11:22:46 AM ~!~Insteon~!~Received STX 0x50 (Raw Insteon Rec):01 0F 88 B1 00 00 01 C7 13 00 - Event: New msg for RF PLM, Src[0F.88.B1] Dst[--.--.--] {Grp Brdcst} Cmd1: Go OFF Cmd2: 00
                          10/24/2010 11:22:46 AM ~!~Insteon~!~Received ^12 (Den Stereo - Zone 2 On/Off - Insteon) Go OFF
                          10/24/2010 11:22:46 AM ~!~Insteon~!~ProcessGroupBroadcast: Device index 42 0F.88.B1 is group broadcast source (tgt group/button: 1) sending cmd 13
                          10/24/2010 11:22:46 AM ~!~Insteon~!~Setting status and value for device ^12. Old status:2 Old Value:100, New Status:3 New Value:0
                          10/24/2010 11:22:46 AM ~!~Insteon~!~Received STX 0x50 (Raw Insteon Rec):01 0F 88 B1 13 AC A9 41 13 01 - Event: New msg for RF PLM, Src[0F.88.B1] Dst[13.AC.A9] {Grp Cln} Cmd1: Go OFF Cmd2: 01
                          10/24/2010 11:22:47 AM ~!~Event~!~Event Trigger "Stereo ON"
                          10/24/2010 11:22:47 AM ~!~Device Control~!~Device: Den Stereo - Zone 2 On/Off - Insteon (^12) ON
                          10/24/2010 11:22:47 AM ~!~Insteon~!~Processing SetIOEx for device - ^12 Cmd: 2 Bright: 0 Data1: 0 Data2: 0
                          10/24/2010 11:22:47 AM ~!~Insteon~!~Setting status and value for device ^12. Old status:3 Old Value:0, New Status:2 New Value:100
                          10/24/2010 11:22:47 AM ~!~Insteon~!~Sending command 02 62 0F 88 B1 0F 11 FF to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
                          10/24/2010 11:22:47 AM ~!~Insteon~!~..Got RF PLM Response 02 62 0F 88 B1 0F 11 FF 06
                          10/24/2010 11:22:47 AM ~!~Insteon~!~Received STX 0x50 (Raw Insteon Rec):01 0F 88 B1 13 AC A9 27 11 FF - Event: New msg for RF PLM, Src[0F.88.B1] Dst[13.AC.A9] {Ack/Dir} Cmd1: 11 Cmd2: FF
                          10/24/2010 11:22:47 AM ~!~Insteon~!~SyncResponderDevices called for device code: ^12
                          10/24/2010 11:22:47 AM ~!~Insteon~!~Received STX 0x50 (Raw Insteon Rec):01 0F 88 B1 00 00 01 CB 11 00 - Event: New msg for RF PLM, Src[0F.88.B1] Dst[--.--.--] {Grp Brdcst} Cmd1: Go ON Cmd2: 00
                          10/24/2010 11:22:47 AM ~!~Insteon~!~Received ^12 (Den Stereo - Zone 2 On/Off - Insteon) Go ON
                          10/24/2010 11:22:47 AM ~!~Insteon~!~ProcessGroupBroadcast: Device index 42 0F.88.B1 is group broadcast source (tgt group/button: 1) sending cmd 11
                          10/24/2010 11:22:47 AM ~!~Insteon~!~Setting status and value for device ^12. Old status:2 Old Value:100, New Status:2 New Value:100
                          10/24/2010 11:22:48 AM ~!~Insteon~!~Received STX 0x50 (Raw Insteon Rec):01 0F 88 B1 13 AC A9 41 11 01 - Event: New msg for RF PLM, Src[0F.88.B1] Dst[13.AC.A9] {Grp Cln} Cmd1: Go ON Cmd2: 01
                          10/24/2010 11:22:49 AM ~!~Event~!~Event Trigger "Stereo ON"
                          10/24/2010 11:22:49 AM ~!~Device Control~!~Device: Den Stereo - Zone 2 On/Off - Insteon (^12) ON
                          10/24/2010 11:22:49 AM ~!~Insteon~!~Processing SetIOEx for device - ^12 Cmd: 2 Bright: 0 Data1: 0 Data2: 0
                          10/24/2010 11:22:49 AM ~!~Insteon~!~Setting status and value for device ^12. Old status:2 Old Value:100, New Status:2 New Value:100
                          10/24/2010 11:22:49 AM ~!~Insteon~!~Sending command 02 62 0F 88 B1 0F 11 FF to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
                          10/24/2010 11:22:49 AM ~!~Insteon~!~..Got RF PLM Response 02 62 0F 88 B1 0F 11 FF 06
                          10/24/2010 11:22:49 AM ~!~Insteon~!~Received STX 0x50 (Raw Insteon Rec):01 0F 88 B1 13 AC A9 23 11 FF - Event: New msg for RF PLM, Src[0F.88.B1] Dst[13.AC.A9] {Ack/Dir} Cmd1: 11 Cmd2: FF
                          10/24/2010 11:22:49 AM ~!~Insteon~!~SyncResponderDevices called for device code: ^12
                          10/24/2010 11:22:49 AM ~!~Insteon~!~PLM_ProcessInBuffer received STX 0x50 (Raw Insteon Rec): Debouncing repeat.
                          10/24/2010 11:22:49 AM ~!~Insteon~!~Received STX 0x50 (Raw Insteon Rec):01 0F 88 B1 00 00 01 CB 13 00 - Event: New msg for RF PLM, Src[0F.88.B1] Dst[--.--.--] {Grp Brdcst} Cmd1: Go OFF Cmd2: 00
                          10/24/2010 11:22:49 AM ~!~Insteon~!~Received ^12 (Den Stereo - Zone 2 On/Off - Insteon) Go OFF
                          10/24/2010 11:22:49 AM ~!~Insteon~!~ProcessGroupBroadcast: Device index 42 0F.88.B1 is group broadcast source (tgt group/button: 1) sending cmd 13
                          10/24/2010 11:22:49 AM ~!~Insteon~!~Setting status and value for device ^12. Old status:2 Old Value:100, New Status:3 New Value:0
                          10/24/2010 11:22:50 AM ~!~Insteon~!~Received STX 0x50 (Raw Insteon Rec):01 0F 88 B1 13 AC A9 41 13 01 - Event: New msg for RF PLM, Src[0F.88.B1] Dst[13.AC.A9] {Grp Cln} Cmd1: Go OFF Cmd2: 01

                          Comment


                            #73
                            Steve,
                            I understand the problem and i think i already have a solution.

                            I have changed the way the plugin deals with the iolinc...

                            the plugin now create two hs devices: 1 for the relay and 1 for the input sensor.

                            the relay hs device can be shutoff automatically after the timeout and this will not affect the status of the input sensor. the idea is to keep the hs device in sync with the actual device.

                            does this sound like it would help? if so post a msg to my visitor page with your email address and i will send you a build to test.
                            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


                              #74
                              thanks for the response, mark

                              not sure i understand how i'd use this. do you literally mean in HS that two separate devices will appear? if so, then i think you're saying that the relay device only pulses momentary ON and then stays OFF (essentially working like a toggle, not momentary C?). the other device shows the state of the sensor. if so, then i just have to program my events with a condition dependent on the state of the sensor?

                              not sure how this works with the keypadlinc. i want the led on the linc to indicate the correct state of the device being controlled, which i guess is the sensor device state. so do i link the sensor device to the keypad led but link the keypad button to the momentary relay?

                              am i asking this right?

                              thanks as always

                              i'll send you my email separately

                              sjw

                              Comment


                                #75
                                just to clarify, i have two different applications. one involves an ON/OFF device function with momentary C (the device being controlled is pulsed, each pulse toggling on/off. the sensor output is on/off). this app would do just fine with the plugin just the way it is if the status was accurately reflected and my problem resolved. this app doesn't need the relay state just the sensor state.

                                my other one, the garage door, would do very well with the devices separated. the keylinc button could be a momentary A toggle and the LED in the keylinc would reflect the actual sensor state (door is up or down).

                                my vote would be to make it optional, one device or two. if one, relay status is ignored and state reflects the sensor. if two, then two separate devices and individual status.

                                hope this helps. in any case, be happy to test anything you are working on

                                Comment

                                Working...
                                X