Mark, I had a dirty shutdown last night. The log shows when HS restarted that the plugin did not have a COM port set. I set it, and the log shows it started communicating with the PLM. All devices showed up in HS, but no control was happening. I finally went into the plugin's devices page, and nothing was there! I checked the ini file and it was 1 KB. Well, that would explain why there was no COM port set. I disabled the plugin and restored from a backup ini. (I was scared because the "Insteon - Backup.ini" was from over three years ago. Good thing I have a daily backup of the HS directory via BLBackup, so I restored from yesterday's backup. Only after restoring from that did I see that backups are now called insteonN.ini. Obviously, I haven't had to revert to a backup ini in years.) I restarted the plugin, all devices showed up in the plugin's device's page. I let out a huge sigh of relief.
Anyway, I have had dirty shutdowns before and this has never happened. Is it just something that always has a risk of occurring when that happens? Without knowing what happened to the ini during system reboot and/or HS startup (was it deleted, was it saved with no data in it), should the plugin have automatically restored from the most recent backup, or is it always meant to be a manual operation?
Thanks,
Scott
Anyway, I have had dirty shutdowns before and this has never happened. Is it just something that always has a risk of occurring when that happens? Without knowing what happened to the ini during system reboot and/or HS startup (was it deleted, was it saved with no data in it), should the plugin have automatically restored from the most recent backup, or is it always meant to be a manual operation?
Thanks,
Scott
Comment