HS3 Insteon Plug-In Version 3.0.4.8 Release

[mnsandler]

Has there been any further revelations on the date format issue experienced in earlier v.3 plugin versions? I am in the midst of manually reentering all my Insteon devices in HS3 (thanks HS ) and upon startup, am getting the date format error discussed in this thread. http://board.homeseer.com/showpost.p...3&postcount=88

Bill,
can you post one [device] section from your insteon.ini

[Bill Grant]

[Device 1]
DeviceName=Ceiling Light
DeviceID=12.50.DF
DeviceLocation=Eating Nook
DeviceType=0101
FirmwareVer=37
EEValues=LEDBrightness=0,DefaultRampRate=28,OpFlags1=32
DatabaseDelta=0
RecentDatabaseDelta=0
PollingInterval=0
LastContact=10 27 2014 2:01:16
HopData=25,5,20,0
Protocol=2
TotalInteractions=19
FailedInteractions=0
LinksDownloaded=1
NumLinks=2
Link 1=E2 01 1E 47 19 FE 1F 01 1
Link 2=A2 FE 1E 47 19 FF 1F 01 2

[mnsandler]

[Device 1]
DeviceName=Ceiling Light
DeviceID=12.50.DF
DeviceLocation=Eating Nook
DeviceType=0101
FirmwareVer=37
EEValues=LEDBrightness=0,DefaultRampRate=28,OpFlags1=32
DatabaseDelta=0
RecentDatabaseDelta=0
PollingInterval=0
LastContact=10 27 2014 2:01:16
HopData=25,5,20,0
Protocol=2
TotalInteractions=19
FailedInteractions=0
LinksDownloaded=1
NumLinks=2
Link 1=E2 01 1E 47 19 FE 1F 01 1
Link 2=A2 FE 1E 47 19 FF 1F 01 2

Bill,
to resolve this issue i standardized the format I use when writing to the ini file:

"M/d/yyyy h:mm:ss tt" (tt is AM or PM)

so my code looks for this format when reading the ini as well.

your entry doesn't look correct:
LastContact=10 27 2014 2:01:16

as a test, can you manually update the ini entries and retest.

this shouldn't affect anything displayed in homeseer

[Bill Grant]

I manually edited the date to the format you suggested for device 1. I'm still getting errors on startup though. Below are error strings from the error report.log for the first three devices. Note the difference in the error between device 1 and the other two.




2014 11 03 10:02:13 - ***:GetDateSetting reported an String was not recognized as a valid DateTime. exception trying to get Device 1, LastContact. The INI value was 10/30/2014 10:04:39 AM and we will return the default of 11 3 2014 10:02:13
2014 11 03 10:02:13 - ***:GetDateSetting reported an String was not recognized as a valid DateTime. exception trying to get Device 2, LastContact. The INI value was 10 30 2014 10:04:39 and we will return the default of 11 3 2014 10:02:13
2014 11 03 10:02:13 - ***:GetDateSetting reported an String was not recognized as a valid DateTime. exception trying to get Device 3, LastContact. The INI value was 10 30 2014 10:04:39 and we will return the default of 11 3 2014 10:02:13

[mnsandler]

I manually edited the date to the format you suggested for device 1. I'm still getting errors on startup though. Below are error strings from the error report.log for the first three devices. Note the difference in the error between device 1 and the other two.




2014 11 03 10:02:13 - ***:GetDateSetting reported an String was not recognized as a valid DateTime. exception trying to get Device 1, LastContact. The INI value was 10/30/2014 10:04:39 AM and we will return the default of 11 3 2014 10:02:13
2014 11 03 10:02:13 - ***:GetDateSetting reported an String was not recognized as a valid DateTime. exception trying to get Device 2, LastContact. The INI value was 10 30 2014 10:04:39 and we will return the default of 11 3 2014 10:02:13
2014 11 03 10:02:13 - ***:GetDateSetting reported an String was not recognized as a valid DateTime. exception trying to get Device 3, LastContact. The INI value was 10 30 2014 10:04:39 and we will return the default of 11 3 2014 10:02:13

can you post these sections from your insteon.ini [device 1] & [device 2]

[mnsandler]

I manually edited the date to the format you suggested for device 1. I'm still getting errors on startup though. Below are error strings from the error report.log for the first three devices. Note the difference in the error between device 1 and the other two.




2014 11 03 10:02:13 - ***:GetDateSetting reported an String was not recognized as a valid DateTime. exception trying to get Device 1, LastContact. The INI value was 10/30/2014 10:04:39 AM and we will return the default of 11 3 2014 10:02:13
2014 11 03 10:02:13 - ***:GetDateSetting reported an String was not recognized as a valid DateTime. exception trying to get Device 2, LastContact. The INI value was 10 30 2014 10:04:39 and we will return the default of 11 3 2014 10:02:13
2014 11 03 10:02:13 - ***:GetDateSetting reported an String was not recognized as a valid DateTime. exception trying to get Device 3, LastContact. The INI value was 10 30 2014 10:04:39 and we will return the default of 11 3 2014 10:02:13

Bill,

i posted 3.0.5.7 (at the top) with a small change that should fix the date issue. Please try it and report back.

[Bill Grant]

[Device 1]
DeviceName=Ceiling Light
DeviceID=12.50.DF
DeviceLocation=Eating Nook
DeviceType=0101
FirmwareVer=37
EEValues=LEDBrightness=0,DefaultRampRate=28,OpFlags1=32
DatabaseDelta=0
RecentDatabaseDelta=0
PollingInterval=0
LastContact=11 3 2014 10:02:13
HopData=29,5,24,0
Protocol=2
TotalInteractions=23
FailedInteractions=0
LinksDownloaded=1
NumLinks=2
Link 1=E2 01 1E 47 19 FE 1F 01 1
Link 2=A2 FE 1E 47 19 FF 1F 01 2
[Device 2]
DeviceID=0B.81.5F
DeviceName=Ceiling Light
DeviceLocation=Master Bedroom
DeviceType=0101
FirmwareVer=27
EEValues=DefaultRampRate=25,ResumeDim=136,DefaultOnLevel=255
DatabaseDelta=0
RecentDatabaseDelta=0
PollingInterval=0
LastContact=11 3 2014 10:02:13
HopData=37,0,37,0
Protocol=1
TotalInteractions=37
FailedInteractions=0
LinksDownloaded=1
NumLinks=2
Link 1=A2 FE 1E 47 19 FF 1F 01 1
Link 2=E2 01 1E 47 19 FE 1F 01 2

[mnsandler]

Bill,
please try v3.0.5.7 posted here:
http://board.homeseer.com/showthread.php?t=169303

again, please shutdown hs, update the date/time entry of [device 1] to the format we discussed before and then restart hs. if this works, you will need to update the lastcontact formats for the other devices while hs is shutdown, and then restart hs.

[Bill Grant]

I followed your instructions for Device 1 and I did not get an error message for Device 1 in the log file. Then I shut down and restarted HS3 and the entry in the .ini file returned to its prior date format state, thus reproducing the error.

[Device 1]
DeviceName=Ceiling Light
DeviceID=12.50.DF
DeviceLocation=Eating Nook
DeviceType=0101
FirmwareVer=37
EEValues=LEDBrightness=0,DefaultRampRate=28,OpFlags1=32
DatabaseDelta=0
RecentDatabaseDelta=0
PollingInterval=0
LastContact=11 8 2014 4:26:55
HopData=29,5,24,0
Protocol=2
TotalInteractions=23
FailedInteractions=0
LinksDownloaded=1
NumLinks=2
Link 1=E2 01 1E 47 19 FE 1F 01 1
Link 2=A2 FE 1E 47 19 FF 1F 01 2


Before restarting HS3, I had edited the date format to read:
LastContact=11/8/2014 4:21:04 PM

[Bill Grant]

Okay, so I changed the Windows regional settings for the date format from YYYY MM DD to YYYY/MM/DD and now I get no startup errors!

Is this something in the plugin code that should be addressed in future versions? I'm happy with the way it works now that I found the problem; I'm just trying to save others some agro down the road.

[mnsandler]

Okay, so I changed the Windows regional settings for the date format from YYYY MM DD to YYYY/MM/DD and now I get no startup errors!

Is this something in the plugin code that should be addressed in future versions? I'm happy with the way it works now that I found the problem; I'm just trying to save others some agro down the road.

I should be able to fix this.

[mnsandler]

Okay, so I changed the Windows regional settings for the date format from YYYY MM DD to YYYY/MM/DD and now I get no startup errors!

Is this something in the plugin code that should be addressed in future versions? I'm happy with the way it works now that I found the problem; I'm just trying to save others some agro down the road.

I posted 3.0.5.9 with another changed related to the date format issue. can you give it a try and report back. please change your regional settings back to the way you had it, but leave the ini settings as-is

[Bill Grant]

Thanks Mark, that works. No errors in the HS startup log and no Insteon errors generated.

[djbeam]

how to upgrade Plug-in

I have your plugin 3.0.4.4 and want to update to 3.0.4.8 ..

I have downloaded the zipped file, but it does not see to load and run on my W7 64bit machine ..

What is the process to update this plugin?

Don

[mnsandler]

I have your plugin 3.0.4.4 and want to update to 3.0.4.8 ..

I have downloaded the zipped file, but it does not see to load and run on my W7 64bit machine ..

What is the process to update this plugin?

Don

To Install:
1. Shutdown HS
2. Backup your current hs database and insteon.ini
3. Copy all the DLLs in the zip to the homeseer folder
4. Restart HS