Announcement

Collapse
No announcement yet.

Mark Sandler Insteon plugin issues

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

    Mark Sandler Insteon plugin issues

    Please excuse my ignorance. I am new to homeseer and the 3rd party plugins. I have been using Insteon devices for years via ISY99i with a PLM 2413S PowerLinc interface. Because I also have RadioRA Classic, Lutron Caseta, NEST and Autelis I thought it was time to consolidate under one system. Homeseer seems to be the perfect choice. I have muddled through the setup and have been able to transition my RadioRA, NEST and LutronCaseta devices with some hiccups along the way. However, the Insteon transition has been much more problematic. I am unable to get the plugin to recognize the PLM. Maybe there is something obvious I am overlooking. I don't think it's the PLM interface because it works fine when connected to the ISY99i.

    Currently, I have the PLM connected directly to the HomeTroller S6 via a serial to RJ45 adapter cable plugged into the COM1 port on the troller. Also, I have set the plugin to COM1 on the configuration page. However, I keep getting the same error.

    ** Unable to communicate with the Insteon powerline interface ***
    Please make sure the interface is configured correctly and restart the plug-in.

    Any help would be greatly appreciated.

    Here is the error log report.


    Insteon Plug-in Error Log Generated 12/15/2017 11:05:56 AM
    -----------*Error Message*----------------
    Error: Forced error / log generation -- 12/15/2017 11:05:56 AM
    --------*Initialization Log*--------------
    12/15/2017 10:56:08 AM - Host System: 10.0.1.221 (HomeTrollerS) 3.0.0.368
    12/15/2017 10:56:08 AM - Plugin HSPI_Insteon.exe version: 3.0.6.0
    12/15/2017 10:56:08 AM - Insteon Support library (Insteon.dll) version: 1.0.6.0
    12/15/2017 10:56:08 AM - RegisterCallback Completed
    12/15/2017 10:56:08 AM - Enter InitIO
    12/15/2017 10:56:08 AM - Enter InitPlugin
    12/15/2017 10:56:08 AM - Global initialization of plug-in required, starting up.
    12/15/2017 10:56:08 AM - Initializing Insteon hardware interface...
    12/15/2017 10:56:08 AM - In ProcessRawReceiveThread
    12/15/2017 10:56:08 AM - Initializing Interface...
    12/15/2017 10:56:08 AM - In PLMBuffer_ProcessBufferThread
    12/15/2017 10:56:08 AM - Sending command 02 60 to Interface, (Expecting 6 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    12/15/2017 10:56:09 AM - ..did not receive a response from the Interface
    12/15/2017 10:56:09 AM - ..Retry #1 required. Pausing 250ms for Interface to clear...
    12/15/2017 10:56:11 AM - ..did not receive a response from the Interface
    12/15/2017 10:56:11 AM - ..Retry #2 required. Pausing 300ms for Interface to clear...
    12/15/2017 10:56:12 AM - ..did not receive a response from the Interface
    12/15/2017 10:56:12 AM - Insteon hardware interface initialization failed.
    12/15/2017 10:56:12 AM - Exit InitIO
    12/15/2017 10:58:06 AM - Global initialization of plug-in required, starting up.
    12/15/2017 10:58:06 AM - Initializing Insteon hardware interface...
    12/15/2017 10:58:06 AM - Initializing Interface...
    12/15/2017 10:58:06 AM - In ProcessRawReceiveThread
    12/15/2017 10:58:06 AM - In PLMBuffer_ProcessBufferThread
    12/15/2017 10:58:06 AM - Sending command 02 60 to Interface, (Expecting 6 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    12/15/2017 10:58:08 AM - ..did not receive a response from the Interface
    12/15/2017 10:58:08 AM - ..Retry #1 required. Pausing 250ms for Interface to clear...
    12/15/2017 10:58:09 AM - ..did not receive a response from the Interface
    12/15/2017 10:58:09 AM - ..Retry #2 required. Pausing 300ms for Interface to clear...
    12/15/2017 10:58:10 AM - ..did not receive a response from the Interface
    12/15/2017 10:58:10 AM - Insteon hardware interface initialization failed.
    12/15/2017 10:58:10 AM - Exit InitX10
    12/15/2017 10:58:10 AM - Could not contact Interface on COM1
    12/15/2017 10:58:10 AM - Scheduled polling enabled.
    12/15/2017 11:00:07 AM - ***:Forced error / log generation
    12/15/2017 11:01:08 AM - Saving comm stats...
    12/15/2017 11:01:08 AM - ..finished saving comm stats.
    12/15/2017 11:03:54 AM - Submit Changes Selected
    12/15/2017 11:03:54 AM - Enter InitX10
    12/15/2017 11:03:54 AM - Please first Enable the Insteon plugin on the Homeseer Plugin Manage page.
    12/15/2017 11:03:54 AM - Enter InitPlugin
    12/15/2017 11:03:54 AM - Global initialization of plug-in required, starting up.
    12/15/2017 11:03:54 AM - Initializing Insteon hardware interface...
    12/15/2017 11:03:54 AM - Initializing Interface...
    12/15/2017 11:03:54 AM - In ProcessRawReceiveThread
    12/15/2017 11:03:54 AM - In PLMBuffer_ProcessBufferThread
    12/15/2017 11:03:54 AM - Sending command 02 60 to Interface, (Expecting 6 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    12/15/2017 11:03:55 AM - ..did not receive a response from the Interface
    12/15/2017 11:03:55 AM - ..Retry #1 required. Pausing 250ms for Interface to clear...
    12/15/2017 11:03:57 AM - ..did not receive a response from the Interface
    12/15/2017 11:03:57 AM - ..Retry #2 required. Pausing 300ms for Interface to clear...
    12/15/2017 11:03:58 AM - ..did not receive a response from the Interface
    12/15/2017 11:03:58 AM - Insteon hardware interface initialization failed.
    12/15/2017 11:03:58 AM - Exit InitX10
    12/15/2017 11:03:58 AM - Could not contact Interface on COM1
    12/15/2017 11:04:02 AM - ***:Forced error / log generation
    12/15/2017 11:05:56 AM - ***:Forced error / log generation

    -----------*Pre-Error Log*----------------
    12/15/2017 10:56:12 AM - Could not contact Interface on COM1
    12/15/2017 10:56:45 AM - ***:Forced error / log generation
    12/15/2017 10:57:55 AM - Submit Changes Selected
    12/15/2017 10:58:06 AM - Submit Changes Selected
    12/15/2017 10:58:06 AM - Enter InitX10
    12/15/2017 10:58:06 AM - Please first Enable the Insteon plugin on the Homeseer Plugin Manage page.
    12/15/2017 10:58:06 AM - Enter InitPlugin
    --------*End Pre-Error Log*--------------
    --------*Start C:\Program Files (x86)\HomeSeer HS3\Config\Insteon.ini*--------------

    #2
    linux uses a different set of values for the port


    Use one the following for the Port name:

    /dev/ttyS0 is COM1
    /dev/ttyS1 is COM2
    /dev/ttyUSB0 is USB
    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


      #3
      My HomeTrollerS is running Windows 10 not linux. I have the PLM attached to COM1 but the plug-in will not recognize it. I have tried two separate serial to RJ45 cables to attach the PLM to the hometroller. Is there a better way to attach it?

      Comment


        #4
        the cable that comes with the PLM is pretty simple, it connects Tx, Rx, and Gnd. i doubt its the cable assuming you have one that meets the specs of the standard cable.

        have you tried a factory reset on the PLM?

        can you try a different COM port?
        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


          #5
          When I first installed the Insteon PI, I too had problems connecting the PLM. Mark helped me over those problems and things have been smooth sailing since. I was attaching my serial PLM via USB. Special cable was needed. I didn't have a real serial port on my server.

          Once the PLM was working, and you know the address of a device, I've never had problems adding them. I did buy some of my switches/dimmers used so I would often get links to devices that didn't exist. There is a function to delete them. I am really impressed with the PI and am very happy that we have access to the developer.

          A tip:
          One thing that I didn't initially realize the greatness of is being able to group devices. Generally, I control scenes and it is no big deal to set 3 or 4 switches in an event. Then I created a 'High Alert' scene that flashes all the lights in the house until disabled. That is over 20 devices. If I referenced each one separately in the event, it worked but it seemed slow and random and would eventually fail. It kind of worked but was not acceptable. Sometime later I learned about groups and put all lighting devices into one group. Now in the High Alert event, I just toggle the group on/off. Instantly they all go off/off at once. I haven't found a need for other groups but you might. When controlling many devices at once, it is much nicer. Makes the events simpler too.

          Here is link to my getting started thread with the PLM and the plugin. It is short but may help.
          https://forums.homeseer.com/showthread.php?t=185589

          Thanks Mark!

          Comment


            #6
            Originally posted by mnsandler View Post
            the cable that comes with the PLM is pretty simple, it connects Tx, Rx, and Gnd. i doubt its the cable assuming you have one that meets the specs of the standard cable.

            have you tried a factory reset on the PLM?

            can you try a different COM port?
            Thanks Mark I will give those a try. Currently I have my RadioRA Chronos attached to COM 2 and the PLM to COM 1. I’ll try switching them tomorrow.

            If that doesn’t do it then I’ll try resetting the PLM.

            Comment


              #7
              Originally posted by logbuilder View Post
              When I first installed the Insteon PI, I too had problems connecting the PLM. Mark helped me over those problems and things have been smooth sailing since. I was attaching my serial PLM via USB. Special cable was needed. I didn't have a real serial port on my server.

              Once the PLM was working, and you know the address of a device, I've never had problems adding them. I did buy some of my switches/dimmers used so I would often get links to devices that didn't exist. There is a function to delete them. I am really impressed with the PI and am very happy that we have access to the developer.

              A tip:
              One thing that I didn't initially realize the greatness of is being able to group devices. Generally, I control scenes and it is no big deal to set 3 or 4 switches in an event. Then I created a 'High Alert' scene that flashes all the lights in the house until disabled. That is over 20 devices. If I referenced each one separately in the event, it worked but it seemed slow and random and would eventually fail. It kind of worked but was not acceptable. Sometime later I learned about groups and put all lighting devices into one group. Now in the High Alert event, I just toggle the group on/off. Instantly they all go off/off at once. I haven't found a need for other groups but you might. When controlling many devices at once, it is much nicer. Makes the events simpler too.

              Here is link to my getting started thread with the PLM and the plugin. It is short but may help.
              https://forums.homeseer.com/showthread.php?t=185589

              Thanks Mark!
              Thanks for the tip. And glad to hear there’s hope for my remaining Insteon devices. Currently using MobiLinc for smartphone control which works pretty well. However, I’m tired of having multiple separate apps to control all my devices. I’m sure once I have everything figured out and under control of HomeSeer I’ll never look back. Thanks again.

              Comment


                #8
                Ok. So changing the port (physical and within configuration) from COM1 to COM2 and resetting the PLM to factory default did not work.

                PLM seems good and works fine when restored to ISY.

                Comment


                  #9
                  any progress? I'm wondering if the cable you are using is designed to work with a com port versas the ISY port
                  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


                    #10
                    Homeseer Zee S2 Insteon Plug Not Working

                    I''ve done this at least ten times before but of course just before I'm going out to install 4 systems (Zee S2s) and I've purchased the Mark Sandler Insteon Plug in and none will recognize either a 2413s or 24513u using different cables and combinations. I know it has to be something stupid because this many 2413S' and the one 2413u and with different cables cannot be all bad.

                    tried:
                    /dev/ttys0
                    /dev/ttys1
                    /dev/ttys2
                    /dev/ttys3
                    and the usb 2413u /dev/ttyUSB0

                    HELP!!!!!

                    Comment


                      #11
                      the port names are case sensitive on the linux based installation

                      try the following for COM1 with the 2413S

                      /dev/ttyS0
                      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


                        #12
                        Tried that no go.
                        ** Unable to communicate with the Insteon powerline interface ***
                        Please make sure the interface is configured correctly and restart the plug-in.

                        Should I be restarting the Zee S2 as well each time. My brain has gone dead as what worked flawless before doesnt work anymore. Right now I'm just concentrating on 1 Zee S2 because whatever is wrong with it must be wrong with everything else (I think)

                        Comment


                          #13
                          I too am new to Homeseer and have 5 years with ISY and about 50 devices (both zwave and insteon).
                          I purchased a S6 PRO and the Zwave is working perfectly. Today, I decided to start moving some Insteon units for testing purposes. I purchased the plug-in and connected my 2413U (which is new). I kept getting the message that it could not find the interface. I then connected my new 2413S (I keep a spare because they fail after a couple of years). It connected after some playing around with it. It is connected to the built in COM1 port on the S6.
                          But my issue is that if the S6 PRO is restarted, I get the same message that it cannot connect. I have to stop the plug-in and restart it for it to work again. This can't be normal!

                          I travel many nights per month, and expect everything to recover if there is a power issue that lasts longer than my UPS can support.

                          The plugin page shows: "** Unable to communicate with the Insteon powerline interface ***
                          Please make sure the interface is configured correctly and restart the plug-in."


                          Current Date/Time: 2/11/2018 8:25:07 PM
                          HomeSeer Version: HS3 Pro Edition 3.0.0.368
                          Operating System: Microsoft Windows 10 Home - Work Station
                          System Uptime: 0 Days 0 Hours 21 Minutes 10 Seconds
                          IP Address: 192.168.1.xxx
                          Number of Devices: 23
                          Number of Events: 3
                          Available Threads: 200

                          Enabled Plug-Ins
                          3.0.6.0: Insteon
                          3.0.1.190: Z-Wave

                          Any ideas?

                          Comment


                            #14
                            Originally posted by paweng View Post
                            Tried that no go.
                            ** Unable to communicate with the Insteon powerline interface ***
                            Please make sure the interface is configured correctly and restart the plug-in.

                            Should I be restarting the Zee S2 as well each time. My brain has gone dead as what worked flawless before doesnt work anymore. Right now I'm just concentrating on 1 Zee S2 because whatever is wrong with it must be wrong with everything else (I think)
                            restarting the plugin should be good enough between tests.

                            did you try just COM1, etc

                            i don't know how the zee s2 exposes the ports. I've never actually tested one
                            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


                              #15
                              Originally posted by rg65 View Post
                              I too am new to Homeseer and have 5 years with ISY and about 50 devices (both zwave and insteon).
                              I purchased a S6 PRO and the Zwave is working perfectly. Today, I decided to start moving some Insteon units for testing purposes. I purchased the plug-in and connected my 2413U (which is new). I kept getting the message that it could not find the interface. I then connected my new 2413S (I keep a spare because they fail after a couple of years). It connected after some playing around with it. It is connected to the built in COM1 port on the S6.
                              But my issue is that if the S6 PRO is restarted, I get the same message that it cannot connect. I have to stop the plug-in and restart it for it to work again. This can't be normal!

                              I travel many nights per month, and expect everything to recover if there is a power issue that lasts longer than my UPS can support.

                              The plugin page shows: "** Unable to communicate with the Insteon powerline interface ***
                              Please make sure the interface is configured correctly and restart the plug-in."


                              Current Date/Time: 2/11/2018 8:25:07 PM
                              HomeSeer Version: HS3 Pro Edition 3.0.0.368
                              Operating System: Microsoft Windows 10 Home - Work Station
                              System Uptime: 0 Days 0 Hours 21 Minutes 10 Seconds
                              IP Address: 192.168.1.xxx
                              Number of Devices: 23
                              Number of Events: 3
                              Available Threads: 200

                              Enabled Plug-Ins
                              3.0.6.0: Insteon
                              3.0.1.190: Z-Wave

                              Any ideas?
                              are the ftdi chipset drivers already installed on your windows box. they are required for the 2413U

                              when you plugin in the 2413U , you should see a new COM port show in the device manager. this is what you would use on the plugin config page.
                              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

                              Working...
                              X