Still having date format issues once in a while
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:
Originally posted by claude
View Post
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?
-----------*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