Announcement

Collapse
No announcement yet.

Interface Issue

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

    Interface Issue

    Good Morning

    Found my system dead in the water this morning. Restarted and saw error message in log regarding Insteon plug in. (1.5.5)

    Full cold start of machine and hardware - no difference.

    Log:

    <TABLE border=0 cellSpacing=2 cellPadding=0 width="100%"><TBODY><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:05:59 AM </TD><TD class=LOGType0 colSpan=3 align=left>Error </TD><TD class=LOGEntry0 colSpan=8 align=left>Initializing interface: Insteon->Could not contact Interface on COM7</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:05:37 AM </TD><TD class=LOGType1 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry1 colSpan=8 align=left>Initializing Plug-in: Insteon on COM port 7</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:05:36 AM </TD><TD class=LOGType0 colSpan=3 align=left>Startup </TD><TD class=LOGEntry0 colSpan=8 align=left>Initializing Plug-Ins</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:05:36 AM </TD><TD class=LOGType1 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry1 colSpan=8 align=left>Found plug-in: UPB, version: 1.0.2.7</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:05:35 AM </TD><TD class=LOGType0 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry0 colSpan=8 align=left>Found plug-in: Media Player, version: 2.4.0.36</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:05:34 AM </TD><TD class=LOGType1 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry1 colSpan=8 align=left>Found plug-in: iTunes, version: 2.4.0.36</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:05:32 AM </TD><TD class=LOGType0 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry0 colSpan=8 align=left>Found plug-in: Insteon, version: 1.5.5.0</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:05:29 AM </TD><TD class=LOGType1 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry1 colSpan=8 align=left>Found plug-in: HSTouch iPhone, version: 1.0.0.0</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:05:28 AM </TD><TD class=LOGType0 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry0 colSpan=8 align=left>Found plug-in: HSTouch Server, version: 1.0.0.10</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:05:24 AM </TD><TD class=LOGType1 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry1 colSpan=8 align=left>Found plug-in: X10 CM15AUSB, version: 1.0.0.3</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:05:22 AM </TD><TD class=LOGType0 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry0 colSpan=8 align=left>Found plug-in: X10 CM11A/CM12U, version: 1.0.1.0</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:05:19 AM </TD><TD class=LOGType1 colSpan=3 align=left>Startup </TD><TD class=LOGEntry1 colSpan=8 align=left>Checking for available plug-ins</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:50 AM </TD><TD class=LOGType0 colSpan=3 align=left>Startup </TD><TD class=LOGEntry0 colSpan=8 align=left>Restoring Device Status</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:48 AM </TD><TD class=LOGType1 colSpan=3 align=left>HSPhone </TD><TD class=LOGEntry1 colSpan=8 align=left>HomeSeer Phone Web Interface initializing.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:38 AM </TD><TD class=LOGType0 colSpan=3 align=left>Startup </TD><TD class=LOGEntry0 colSpan=8 align=left>Initializing phone interface...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:30 AM </TD><TD class=LOGType1 colSpan=3 align=left>Startup </TD><TD class=LOGEntry1 colSpan=8 align=left>Creating Speaker Client Interface Object...</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:30 AM </TD><TD class=LOGType0 colSpan=3 align=left>Startup </TD><TD class=LOGEntry0 colSpan=8 align=left>Starting remoting (Remote client connection monitor)</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:30 AM </TD><TD class=LOGType1 colSpan=3 align=left>Startup </TD><TD class=LOGEntry1 colSpan=8 align=left>HomeSeer version is: 2.4.0.1</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:25 AM </TD><TD class=LOGType0 colSpan=3 align=left>Database </TD><TD class=LOGEntry0 colSpan=8 align=left>HomeSeer configuration database C:\Program Files\HomeSeer HS2\Config\homeseer 091810.mdb has been closed.</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:25 AM </TD><TD class=LOGType1 colSpan=3 align=left>Load Config </TD><TD class=LOGEntry1 colSpan=8 align=left>259 total events loaded.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:23 AM </TD><TD class=LOGType0 colSpan=3 align=left>Load Config </TD><TD class=LOGEntry0 colSpan=8 align=left>Loading Events...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:23 AM </TD><TD class=LOGType1 colSpan=3 align=left>Load Config </TD><TD class=LOGEntry1 colSpan=8 align=left>Finished checking device type settings.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:23 AM </TD><TD class=LOGType0 colSpan=3 align=left>Load Config </TD><TD class=LOGEntry0 colSpan=8 align=left>Checking device type settings for all devices...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:23 AM </TD><TD class=LOGType1 colSpan=3 align=left>Load Config </TD><TD class=LOGEntry1 colSpan=8 align=left>231 total devices loaded.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:16 AM </TD><TD class=LOGType0 colSpan=3 align=left>Database </TD><TD class=LOGEntry0 colSpan=8 align=left>Loading Devices...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:07 AM </TD><TD class=LOGType1 colSpan=3 align=left>Database </TD><TD class=LOGEntry1 colSpan=8 align=left>Opening (Mode=Read) up HomeSeer database: C:\Program Files\HomeSeer HS2\Config\homeseer 091810.mdb</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:07 AM </TD><TD class=LOGType0 colSpan=3 align=left>System </TD><TD class=LOGEntry0 colSpan=8 align=left>Loading device types file...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:07 AM </TD><TD class=LOGType1 colSpan=3 align=left>Startup </TD><TD class=LOGEntry1 colSpan=8 align=left>Loading configuration file ...</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:07 AM </TD><TD class=LOGType0 colSpan=3 align=left>Startup </TD><TD class=LOGEntry0 colSpan=8 align=left>Settings Loaded.</TD></TR></TBODY></TABLE>


    HomeSeer starts, just no Insteon anymore.

    #2
    Have you tried moving it to another comport? The interface could be dead.
    💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

    Comment


      #3
      Interface

      Yes I have. No difference.

      I know I had read sometime that you cannot use port #1.

      Comment


        #4
        Originally posted by gjtherk@comcast.net View Post
        Good Morning

        Found my system dead in the water this morning. Restarted and saw error message in log regarding Insteon plug in. (1.5.5)

        Full cold start of machine and hardware - no difference.

        Log:

        <TABLE border=0 cellSpacing=2 cellPadding=0 width="100%"><TBODY><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:05:59 AM </TD><TD class=LOGType0 colSpan=3 align=left>Error </TD><TD class=LOGEntry0 colSpan=8 align=left>Initializing interface: Insteon->Could not contact Interface on COM7</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:05:37 AM </TD><TD class=LOGType1 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry1 colSpan=8 align=left>Initializing Plug-in: Insteon on COM port 7</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:05:36 AM </TD><TD class=LOGType0 colSpan=3 align=left>Startup </TD><TD class=LOGEntry0 colSpan=8 align=left>Initializing Plug-Ins</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:05:36 AM </TD><TD class=LOGType1 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry1 colSpan=8 align=left>Found plug-in: UPB, version: 1.0.2.7</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:05:35 AM </TD><TD class=LOGType0 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry0 colSpan=8 align=left>Found plug-in: Media Player, version: 2.4.0.36</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:05:34 AM </TD><TD class=LOGType1 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry1 colSpan=8 align=left>Found plug-in: iTunes, version: 2.4.0.36</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:05:32 AM </TD><TD class=LOGType0 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry0 colSpan=8 align=left>Found plug-in: Insteon, version: 1.5.5.0</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:05:29 AM </TD><TD class=LOGType1 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry1 colSpan=8 align=left>Found plug-in: HSTouch iPhone, version: 1.0.0.0</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:05:28 AM </TD><TD class=LOGType0 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry0 colSpan=8 align=left>Found plug-in: HSTouch Server, version: 1.0.0.10</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:05:24 AM </TD><TD class=LOGType1 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry1 colSpan=8 align=left>Found plug-in: X10 CM15AUSB, version: 1.0.0.3</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:05:22 AM </TD><TD class=LOGType0 colSpan=3 align=left>Plug-In </TD><TD class=LOGEntry0 colSpan=8 align=left>Found plug-in: X10 CM11A/CM12U, version: 1.0.1.0</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:05:19 AM </TD><TD class=LOGType1 colSpan=3 align=left>Startup </TD><TD class=LOGEntry1 colSpan=8 align=left>Checking for available plug-ins</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:50 AM </TD><TD class=LOGType0 colSpan=3 align=left>Startup </TD><TD class=LOGEntry0 colSpan=8 align=left>Restoring Device Status</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:48 AM </TD><TD class=LOGType1 colSpan=3 align=left>HSPhone </TD><TD class=LOGEntry1 colSpan=8 align=left>HomeSeer Phone Web Interface initializing.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:38 AM </TD><TD class=LOGType0 colSpan=3 align=left>Startup </TD><TD class=LOGEntry0 colSpan=8 align=left>Initializing phone interface...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:30 AM </TD><TD class=LOGType1 colSpan=3 align=left>Startup </TD><TD class=LOGEntry1 colSpan=8 align=left>Creating Speaker Client Interface Object...</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:30 AM </TD><TD class=LOGType0 colSpan=3 align=left>Startup </TD><TD class=LOGEntry0 colSpan=8 align=left>Starting remoting (Remote client connection monitor)</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:30 AM </TD><TD class=LOGType1 colSpan=3 align=left>Startup </TD><TD class=LOGEntry1 colSpan=8 align=left>HomeSeer version is: 2.4.0.1</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:25 AM </TD><TD class=LOGType0 colSpan=3 align=left>Database </TD><TD class=LOGEntry0 colSpan=8 align=left>HomeSeer configuration database C:\Program Files\HomeSeer HS2\Config\homeseer 091810.mdb has been closed.</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:25 AM </TD><TD class=LOGType1 colSpan=3 align=left>Load Config </TD><TD class=LOGEntry1 colSpan=8 align=left>259 total events loaded.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:23 AM </TD><TD class=LOGType0 colSpan=3 align=left>Load Config </TD><TD class=LOGEntry0 colSpan=8 align=left>Loading Events...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:23 AM </TD><TD class=LOGType1 colSpan=3 align=left>Load Config </TD><TD class=LOGEntry1 colSpan=8 align=left>Finished checking device type settings.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:23 AM </TD><TD class=LOGType0 colSpan=3 align=left>Load Config </TD><TD class=LOGEntry0 colSpan=8 align=left>Checking device type settings for all devices...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:23 AM </TD><TD class=LOGType1 colSpan=3 align=left>Load Config </TD><TD class=LOGEntry1 colSpan=8 align=left>231 total devices loaded.</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:16 AM </TD><TD class=LOGType0 colSpan=3 align=left>Database </TD><TD class=LOGEntry0 colSpan=8 align=left>Loading Devices...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:07 AM </TD><TD class=LOGType1 colSpan=3 align=left>Database </TD><TD class=LOGEntry1 colSpan=8 align=left>Opening (Mode=Read) up HomeSeer database: C:\Program Files\HomeSeer HS2\Config\homeseer 091810.mdb</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:07 AM </TD><TD class=LOGType0 colSpan=3 align=left>System </TD><TD class=LOGEntry0 colSpan=8 align=left>Loading device types file...</TD></TR><TR><TD class=LOGDateTime1 noWrap align=left>5/24/2011 9:04:07 AM </TD><TD class=LOGType1 colSpan=3 align=left>Startup </TD><TD class=LOGEntry1 colSpan=8 align=left>Loading configuration file ...</TD></TR><TR><TD class=LOGDateTime0 noWrap align=left>5/24/2011 9:04:07 AM </TD><TD class=LOGType0 colSpan=3 align=left>Startup </TD><TD class=LOGEntry0 colSpan=8 align=left>Settings Loaded.</TD></TR></TBODY></TABLE>


        HomeSeer starts, just no Insteon anymore.
        did you power cycle the plm as well?

        can you open hyperterminal to com7?
        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
          Interface

          did you power cycle the plm as well? Yes.

          can you open hyperterminal to com7? No idea how to do that (at least in those terms). I did view the ports from the hardware manager and when I would unplug the PLM port 7 would vanish from the device manager.

          The PLM seemed to be very warm.

          Comment


            #6
            Originally posted by gjtherk@comcast.net View Post
            did you power cycle the plm as well? Yes.

            can you open hyperterminal to com7? No idea how to do that (at least in those terms). I did view the ports from the hardware manager and when I would unplug the PLM port 7 would vanish from the device manager.

            The PLM seemed to be very warm.
            hyperterminal is a windows tool avail under programs/accessories/comm

            run the app and try to open com7 and see if you get an error or if the port opens successfully (without error)
            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


              #7
              Hyperterminal

              Set up is requiring telephone number and dialing access information. I do not have a phone line associated with the HomeSeer computer, cable modem only.

              Comment


                #8
                lets try this...download and install docklight. its a utility that will allow you to send cmds directly to the plm so we can see if it is still working. I think it may be dead since you said its hot and its not responding.

                http://www.docklight.de/download_en.htm V1.9

                you will need the attached docklight project file. unzip to your desktop and double click to open this project file with docklight.

                com7 should be configured to open automatically then just click on the ---> btn next to the Get Version on the left.

                if the PLM is working it should respond. please post a screen shot of the docklight window after you perform the above
                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


                  #9
                  Test

                  Thanks Mark:

                  I have to go to a meeting but will attempt this when I return. I too suspect the PLM is bad. I haven't had one last more than a year yet.

                  Will advise as soon as I perform the test.

                  Comment


                    #10
                    I tried to download the Docklight application but it just flashes constantly and doesn't download. Rebooted - retried same result.

                    But after restarting, the HomeSeer started normally with the Insteon Configuration button appearing.

                    That being said, most of the Insteon events are not working although I seem to be able to control every device I have tried from the GUI. Polling seems to work fine but most events are not triggering.

                    I noticed before shutting down that X-10 devices and triggers were working normally.

                    And finally, the 2413 is running cooler.

                    Comment


                      #11
                      Originally posted by gjtherk@comcast.net View Post
                      I tried to download the Docklight application but it just flashes constantly and doesn't download. Rebooted - retried same result.

                      But after restarting, the HomeSeer started normally with the Insteon Configuration button appearing.

                      That being said, most of the Insteon events are not working although I seem to be able to control every device I have tried from the GUI. Polling seems to work fine but most events are not triggering.

                      I noticed before shutting down that X-10 devices and triggers were working normally.

                      And finally, the 2413 is running cooler.
                      I've had a PLM to get to a state where it could control all devices, but wouldn't respond to any messages from the devices. The memory on the PLM was lost (all links gone). "Reprogram Interface" should bring it back, but if it works out like mine it will eventually fail again.

                      Comment


                        #12
                        guys, this is a little off topic, but do you have other deviced plugged into the back of your PLMs or run the plm in a hot environment? the extra heat from the other device could shorten the plm's life.
                        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


                          #13
                          Plm

                          My PLM is plugged into a duplex receptacle that is not shared with any other device. The only heat producing device nearby is an LCD monitor about 18 inches away. Room is set for 74 degrees in the AC months and 70 in the heating months. My PLM does not have a pass through receptacle.

                          I periodically unplug the PLM to reset it and have never found it to be as warm as it was this morning. But this afternoon it was much cooler (and working). I had to re-link all of my 2420s other than the ones that are linked to more than the PLM.

                          I ordered a new PLM. I've gone through 3 so far. This one lasted just over a year, longest yet. I don't trust this one anymore. I suspect a correlation between the high temp and the failure and subsequent failure to connect.

                          But the fact that the X10 side of the device continued to work is puzzling to me. I have very few X10 devices, a few EagleEyes and a 16 channel interface to an Ademco alarm panel.

                          I thank all of you for your response and input. I sincerely appreciate it.

                          Comment


                            #14
                            Originally posted by mnsandler View Post
                            guys, this is a little off topic, but do you have other deviced plugged into the back of your PLMs or run the plm in a hot environment? the extra heat from the other device could shorten the plm's life.
                            Mine in plugged into the pass-through outlet of a filterlinc. The UPS for the homeseer PC is plugged into the filter. The outlet is below the shelves that hold the UPS and the PC. I would say that the temperature there is not elevated from room temperature.

                            Smarthome uses PIC microcontrollers from MicroChip. The way that their IO ports work makes it possible for an instruction that changes the value of one bit to also expectantly change the value of another bit if there is electrical noise at the time the instruction is executed. (There is a way around this, but they don't seem to be following that practice.) I've seen this cause problems with the older X10 devices, and it might be part of the issue here.

                            Comment

                            Working...
                            X