Announcement

Collapse
No announcement yet.

HS3 Insteon Plug-In Version 3.0.3.17 Release

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

    #76
    Still having date format issues once in a while

    Originally posted by claude View Post
    I should have looked more closely at the Insteon error log and not focus on your reply

    I first modified all the Lastcontact's to dd/mm/yyyy, but still got errors. I then modified them to mm/dd/yyy and all is well. This seems to be what the plug-in's error message is suggesting:
    Error: GetDateSetting reported an String was not recognized as a valid DateTime. exception trying to get Device 37, LastContact. The INI value was 15/01/2014 7:16:25 PM and we will return the default of 1/16/2014 2:31:53 PM -- 1/16/2014 2:31:53 PM

    Can you see what is the contents of the return from HS.clid ?
    Just to keep you busy...

    Many time when I start up HS3 I get a few of those date errors, so I've started looking into it.

    I have one instance where I had a copy of the insteon.ini file after a particular shutdown of HS3. When HS3 started up, the Insteon plug-in mentioned a date format error in the HS3 log. The error indicated an invalid date format (dd/mm/yyyy) and replaced it with (mm/dd/yyy). When I looked in the saved insteon.ini from before the startup, the date format was correct for that device (mm/dd/yyy).

    I've tried to reproduce the action resulting in that invalid date format on LastContact: polling, local On/Off, On/Off from HS3. Nothing triggered the error.

    The fact remains that I cleaned up all the LastContact date formats to (mm/dd/yyy), I don't mess with the insteon.ini and have not changed regional settings. And I do get these date format errors periodically.

    I started looking into Insteon.error.report.log's and this caught my attention:
    Insteon Plug-in Error Log Generated 2/1/2014 3:17:26 PM
    -----------*Error Message*----------------
    Error: GetDateSetting reported an String was not recognized as a valid DateTime. exception trying to get Device 20, LastContact. The INI value was 31/01/2014 1:03:26 PM and we will return the default of 2/1/2014 3:17:26 PM -- 2/1/2014 3:17:26 PM
    --------*Initialization Log*--------------
    2/1/2014 3:17:22 PM - Host System: () 3.0.0.55
    2/1/2014 3:17:22 PM - Plugin: HSPI_Insteon.DLL - v3.0.3.16
    2/1/2014 3:17:22 PM - RegisterCallback Completed
    2/1/2014 3:17:22 PM - Enter InitIO
    2/1/2014 3:17:22 PM - Enter InitPlugin
    2/1/2014 3:17:22 PM - Global initialization of plug-in required, starting up.
    2/1/2014 3:17:22 PM - Initializing Insteon hardware interface...
    01/02/2014 3:17:22 PM - In ProcessRawReceiveThread
    01/02/2014 3:17:22 PM - In PLMBuffer_ProcessBufferThread
    01/02/2014 3:17:22 PM - Clearing buffer...
    01/02/2014 3:17:22 PM - Sending
    http://192.168.1.15:25105/1?XB=M=1
    2/1/2014 3:17:22 PM - Sending command 02 60 to Interface, (Expecting 6 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
    2/1/2014 3:17:22 PM - ..waiting 495ms
    01/02/2014 3:17:22 PM - ..Time to send http request (ms): 11
    01/02/2014 3:17:22 PM - Finished sending command.
    01/02/2014 3:17:22 PM - finished clearing buffer.
    2/1/2014 3:17:22 PM - Sending
    http://192.168.1.15:25105/3?0260=I=3
    2/1/2014 3:17:22 PM - ..Time to send http request (ms): 0
    2/1/2014 3:17:22 PM - Finished sending command.
    01/02/2014 3:17:23 PM - ..My XML buffer begins with: 02601E9ECF03379C06
    01/02/2014 3:17:23 PM - Clearing buffer...
    01/02/2014 3:17:23 PM - Sending
    http://192.168.1.15:25105/1?XB=M=1
    01/02/2014 3:17:23 PM - ..Time to send http request (ms): 0
    01/02/2014 3:17:23 PM - Finished sending command.
    01/02/2014 3:17:23 PM - finished clearing buffer.


    Could it be that different sections of code in the plug-in handle dates differently?

    Comment


      #77
      Originally posted by claude View Post
      Just to keep you busy...

      Many time when I start up HS3 I get a few of those date errors, so I've started looking into it.

      I have one instance where I had a copy of the insteon.ini file after a particular shutdown of HS3. When HS3 started up, the Insteon plug-in mentioned a date format error in the HS3 log. The error indicated an invalid date format (dd/mm/yyyy) and replaced it with (mm/dd/yyy). When I looked in the saved insteon.ini from before the startup, the date format was correct for that device (mm/dd/yyy).

      I've tried to reproduce the action resulting in that invalid date format on LastContact: polling, local On/Off, On/Off from HS3. Nothing triggered the error.

      The fact remains that I cleaned up all the LastContact date formats to (mm/dd/yyy), I don't mess with the insteon.ini and have not changed regional settings. And I do get these date format errors periodically.

      I started looking into Insteon.error.report.log's and this caught my attention:
      Insteon Plug-in Error Log Generated 2/1/2014 3:17:26 PM
      -----------*Error Message*----------------
      Error: GetDateSetting reported an String was not recognized as a valid DateTime. exception trying to get Device 20, LastContact. The INI value was 31/01/2014 1:03:26 PM and we will return the default of 2/1/2014 3:17:26 PM -- 2/1/2014 3:17:26 PM
      --------*Initialization Log*--------------
      2/1/2014 3:17:22 PM - Host System: () 3.0.0.55
      2/1/2014 3:17:22 PM - Plugin: HSPI_Insteon.DLL - v3.0.3.16
      2/1/2014 3:17:22 PM - RegisterCallback Completed
      2/1/2014 3:17:22 PM - Enter InitIO
      2/1/2014 3:17:22 PM - Enter InitPlugin
      2/1/2014 3:17:22 PM - Global initialization of plug-in required, starting up.
      2/1/2014 3:17:22 PM - Initializing Insteon hardware interface...
      01/02/2014 3:17:22 PM - In ProcessRawReceiveThread
      01/02/2014 3:17:22 PM - In PLMBuffer_ProcessBufferThread
      01/02/2014 3:17:22 PM - Clearing buffer...
      01/02/2014 3:17:22 PM - Sending
      http://192.168.1.15:25105/1?XB=M=1
      2/1/2014 3:17:22 PM - Sending command 02 60 to Interface, (Expecting 6 bytes extra back) Pre-Payload ACK:False, NAK is ok:False
      2/1/2014 3:17:22 PM - ..waiting 495ms
      01/02/2014 3:17:22 PM - ..Time to send http request (ms): 11
      01/02/2014 3:17:22 PM - Finished sending command.
      01/02/2014 3:17:22 PM - finished clearing buffer.
      2/1/2014 3:17:22 PM - Sending
      http://192.168.1.15:25105/3?0260=I=3
      2/1/2014 3:17:22 PM - ..Time to send http request (ms): 0
      2/1/2014 3:17:22 PM - Finished sending command.
      01/02/2014 3:17:23 PM - ..My XML buffer begins with: 02601E9ECF03379C06
      01/02/2014 3:17:23 PM - Clearing buffer...
      01/02/2014 3:17:23 PM - Sending
      http://192.168.1.15:25105/1?XB=M=1
      01/02/2014 3:17:23 PM - ..Time to send http request (ms): 0
      01/02/2014 3:17:23 PM - Finished sending command.
      01/02/2014 3:17:23 PM - finished clearing buffer.


      Could it be that different sections of code in the plug-in handle dates differently?
      claude,
      did you happen to delete a device from your system since you noticed this problem?

      also did you set your regional settings in the xml back to the defaults
      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


        #78
        Originally posted by mnsandler View Post
        ... did you happen to delete a device from your system since you noticed this problem? ...
        I did a 'replace' yesterday (bad SwitchLinc replaced)

        Originally posted by mnsandler View Post
        ... also did you set your regional settings in the xml back to the defaults
        Here it is, no change since Jan 9th.


        <msLocale:dateFormatLengthtype="long"><O></O>
        <msLocale:default type="2"/><O></O>
        <msLocale:dateFormattype="0"><O></O>
        <msLocaleattern>dddd, MMMM dd, yyyy<O></O>
        </< font>msLocaleattern><O></O>
        </< font>msLocale:dateFormat></SPAN><O></O>
        <msLocale:dateFormattype="1"><O></O>
        <msLocaleattern>MMMM dd, yyyy<O></O>
        </< font>msLocaleattern><O></O>
        </< font>msLocale:dateFormat></SPAN><O></O>
        <msLocale:dateFormattype="2"><O></O>
        <msLocaleattern>dddd, dd MMMM, yyyy<O></O>
        </< font>msLocaleattern><O></O>
        </< font>msLocale:dateFormat></SPAN><O></O>
        <msLocale:dateFormattype="3"><O></O>
        <msLocaleattern>dd MMMM, yyyy<O></O>
        </< font>msLocaleattern><O></O>
        </< font>msLocale:dateFormat><O></O></SPAN>
        </< font>msLocale:dateFormatLength></SPAN><O></O>
        <msLocale:dateFormatLengthtype="short"><O></O>
        <msLocale:default type="5"/><O></O>
        <msLocale:dateFormattype="0"><O></O>
        <msLocaleattern>M/d/yyyy<O></O>
        </< font>msLocaleattern><O></O>
        </< font>msLocale:dateFormat></SPAN><O></O>
        <msLocale:dateFormattype="1"><O></O>
        <msLocaleattern>M/d/yy<O></O>
        </< font>msLocaleattern><O></O>
        </< font>msLocale:dateFormat></SPAN><O></O>
        <msLocale:dateFormattype="2"><O></O>
        <msLocaleattern>MM/dd/yy<O></O>
        </< font>msLocaleattern><O></O>
        </< font>msLocale:dateFormat></SPAN><O></O>
        <msLocale:dateFormattype="3"><O></O>
        <msLocaleattern>MM/dd/yyyy<O></O>
        </< font>msLocaleattern><O></O>
        </< font>msLocale:dateFormat></SPAN><O></O>
        <msLocale:dateFormattype="4"><O></O>
        <msLocaleattern>yy/MM/dd<O></O>
        </< font>msLocaleattern><O></O>
        </< font>msLocale:dateFormat></SPAN><O></O>
        <msLocale:dateFormattype="5"><O></O>
        <msLocaleattern>yyyy-MM-dd<O></O>
        </< font>msLocaleattern><O></O>
        </< font>msLocale:dateFormat></SPAN><O></O>
        <msLocale:dateFormattype="6"><O></O>
        <msLocaleattern>dd-MMM-yy<O></O>
        </< font>msLocaleattern><O></O>
        </< font>msLocale:dateFormat></SPAN><O></O>


        As you see. default type="5" on the short date

        Comment


          #79
          isn't the format for "5" yyyy-MM-dd. this isn't even a format we have discussed.

          the default in my xml is "0" which seems to be inline with what we want
          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


            #80
            Originally posted by mnsandler View Post
            isn't the format for "5" yyyy-MM-dd. this isn't even a format we have discussed.

            the default in my xml is "0" which seems to be inline with what we want
            My target, especially for the HS3 interface is to display short dates as yyyy-mm-dd, which I get by specifying "5" and it works great.

            If I set it back to "0", then everything displays as m/d/yyyy.

            It seems the plug-in writes back to the insteon.ini as mm/dd/yyyy, but the next time it reads that same entry, it's served as dd/mm/yyyy while it's obviously physically mm/dd/yyyy in the .ini.

            Under what circumstances is the LastContact updated?

            Comment


              #81
              Originally posted by claude View Post
              My target, especially for the HS3 interface is to display short dates as yyyy-mm-dd, which I get by specifying "5" and it works great.

              If I set it back to "0", then everything displays as m/d/yyyy.

              It seems the plug-in writes back to the insteon.ini as mm/dd/yyyy, but the next time it reads that same entry, it's served as dd/mm/yyyy while it's obviously physically mm/dd/yyyy in the .ini.

              Under what circumstances is the LastContact updated?
              LastContact is updated during polling when the device responds.

              do you know if there is a way to get the user date format from hs directly?
              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


                #82
                Originally posted by mnsandler View Post
                LastContact is updated during polling when the device responds.

                do you know if there is a way to get the user date format from hs directly?
                Not that I know of, based on the general user help; maybe in the developer help?

                Comment


                  #83
                  insteon question

                  I am a new user and had the insteon plugin working with a new standard HS2.

                  I had to reimage because of a corrupt windows file and was sent the HS3 version. I upgraded both the HS3 and the insteon and am unable to get the insteon plugin to work. My insteon plugin is version .16 and when I select plugin manage the insteon status tells me to enter the interface port on the config page and restart HS. This never says ok, Only reminds me to go to the config page. I have a USB interface, I am using HS3 standard 3.0.0.55 windows and your version .16 from this link. Ant ideas? Thanks John

                  Comment


                    #84
                    Originally posted by Johnwmaq View Post
                    I am a new user and had the insteon plugin working with a new standard HS2.

                    I had to reimage because of a corrupt windows file and was sent the HS3 version. I upgraded both the HS3 and the insteon and am unable to get the insteon plugin to work. My insteon plugin is version .16 and when I select plugin manage the insteon status tells me to enter the interface port on the config page and restart HS. This never says ok, Only reminds me to go to the config page. I have a USB interface, I am using HS3 standard 3.0.0.55 windows and your version .16 from this link. Ant ideas? Thanks John
                    Welcome to HS3 John.

                    are you able to click on the Insteon link on the Plugin Manage page? this should take you to the config page.

                    the workaround might be to add InterfacePort=COMx to the [config] section of your insteon.ini and then restart hs
                    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


                      #85
                      Originally posted by claude View Post
                      Not that I know of, based on the general user help; maybe in the developer help?
                      Nothing in the dev help? I'll have to ask HST about this. if the regional settings are accessible to the plugin than i can't resolve this for you?

                      You know, since the lastcontact info is never actually displayed on the screen, the format I use to save/retrieve it from the ini should matter to the plugin

                      I'll drop HST a note on this, and report back
                      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


                        #86
                        Originally posted by claude View Post
                        Not that I know of, based on the general user help; maybe in the developer help?
                        claude,
                        HST said that the regional settings xml file should not be changed manually. it is derived from the windows settings at first startup of hs3 (or hs2).

                        so you might need to delete the xml file, make your changes in windows, and let hs3 recreate it. but that doesn't really fix/change anything for me.

                        I still don't think there is any good reason to change the date format of the lastcontact entries on the insteon.ini file. Its an internal value. I can modify the plugin to ensure it reads and writes mm/dd/yyyy regardless of any custom settings in windows or hs3 which should resolve this issue.
                        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


                          #87
                          Originally posted by mnsandler View Post
                          claude,
                          HST said that the regional settings xml file should not be changed manually. it is derived from the windows settings at first startup of hs3 (or hs2) ...
                          I believe HST is not handling regional settings properly. If interested, see last comment on Bugzilla http://www.homeseer.com/bugzilla/show_bug.cgi?id=1306

                          Originally posted by mnsandler View Post
                          ... I still don't think there is any good reason to change the date format of the lastcontact entries on the insteon.ini file. Its an internal value ...
                          I agree with you. I am not asking you to change the format. If you recall my initial post on this, I'm getting errors from the plug-in around LastContact date format. But only the plug-in writes and reads from the insteon.ini. If I knew that the error was about LastContact date format, I would simply ignore it as it has no incidence.

                          So, why is this important? When I check the HS3 log, the Insteon error message only mentions "an error", so I need to get to the "Insteon Error Report.Log" and scan it all to make sure they are only "LastContact date format" errors and nothing else more serious.

                          Originally posted by mnsandler View Post
                          ... I can modify the plugin to ensure it reads and writes mm/dd/yyyy regardless of any custom settings in windows or hs3 which should resolve this issue. ...
                          I think that would make my life simpler. Just curious, why does the plug-in need to validate the previous LastContact date before writing the new one, or is that an uncontrollable artifact of reading the entry?

                          Comment


                            #88
                            Originally posted by claude View Post
                            I believe HST is not handling regional settings properly. If interested, see last comment on Bugzilla http://www.homeseer.com/bugzilla/show_bug.cgi?id=1306



                            I agree with you. I am not asking you to change the format. If you recall my initial post on this, I'm getting errors from the plug-in around LastContact date format. But only the plug-in writes and reads from the insteon.ini. If I knew that the error was about LastContact date format, I would simply ignore it as it has no incidence.

                            So, why is this important? When I check the HS3 log, the Insteon error message only mentions "an error", so I need to get to the "Insteon Error Report.Log" and scan it all to make sure they are only "LastContact date format" errors and nothing else more serious.



                            I think that would make my life simpler. Just curious, why does the plug-in need to validate the previous LastContact date before writing the new one, or is that an uncontrollable artifact of reading the entry?
                            Claude,

                            i posted 3.0.3.17 (at the top). it now reads & writes the LastContact with the following explicit date format: "M/d/yyyy h:mm:ss tt". I hope this resolves this issue for the both of us

                            Please shutdown hs, update your values accordingly, upgrade, and everything should be fine.

                            i haven't changed the display format that occurs in some log entries. But it might be displayed with your local format
                            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


                              #89
                              Originally posted by mnsandler View Post
                              Claude,

                              i posted 3.0.3.17 (at the top). it now reads & writes the LastContact with the following explicit date format: "M/d/yyyy h:mm:ss tt". I hope this resolves this issue for the both of us

                              Please shutdown hs, update your values accordingly, upgrade, and everything should be fine.

                              i haven't changed the display format that occurs in some log entries. But it might be displayed with your local format
                              Thanks. Loaded and did 1 general poll. No errors so far.

                              Comment


                                #90
                                Originally posted by claude View Post
                                Thanks. Loaded and did 1 general poll. No errors so far.
                                thanks. also, you should not see any more x10event errors since you aren't using x10 i think. x10 is not disabled by default
                                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