As I left to catch my plane this morning, I realized that my morning light event had not executed. Remoting in from the cab I panicked as I saw that I had only 17 devices (counters, timers and DSC alarm only) of a usual population of almost 300. The log revealed a 3 AM system restart for some unknown reason and that the config file it loaded had no devices in it. Setup showed that the config file loaded was homeseer6.hsd. I looked in the HS3 data directory and found that there are dozens of hsd files that have file dates and times indicating that several are created or used daily. I changed setup to an earlier data file, rebooted and I seemed to be back to normal.
When it rebooted, the new log file indicated that it had to re-establish virtually all of my Z wave devices. The log showed this for each device:
Sep-28 7:07:40 AM
Z-Wave Warning
HomeSeer device Light Gst S Floor Lamp indicates it is owned by this plug-in but no device exists in this plug-in to match it - attempting to create it from the HomeSeer device information.
Creation of Z-Wave plug-in object from HomeSeer data was successful.
Sep-28 7:07:40 AM
Questions:
Any idea what happened?
Should I have so many hsd files? Doesn't HS3 use a consistent hsd file?
Why would I suddenly get a new hsd file with no devices?
When it rebooted, the new log file indicated that it had to re-establish virtually all of my Z wave devices. The log showed this for each device:
Sep-28 7:07:40 AM
Z-Wave Warning
HomeSeer device Light Gst S Floor Lamp indicates it is owned by this plug-in but no device exists in this plug-in to match it - attempting to create it from the HomeSeer device information.
Creation of Z-Wave plug-in object from HomeSeer data was successful.
Sep-28 7:07:40 AM
Questions:
Any idea what happened?
Should I have so many hsd files? Doesn't HS3 use a consistent hsd file?
Why would I suddenly get a new hsd file with no devices?
Comment