Where did my HS4 log go ?

[claude]

I shut down HS4. I renamed the current log and moved it to a different directory. I restarted HS4. I see no new HomeSeerLog.hsd in C:\Program Files (x86)\HomeSeer HS4\Logs. But I'm still able to view the log within the HS4 Web page: it even goes back to Feb 10th. That's when I installed HS4 4.2.17.2.

Totally confused ... help? Where's THE log ?

[randy]

I shut down HS4. I renamed the current log and moved it to a different directory. I restarted HS4. I see no new HomeSeerLog.hsd in C:\Program Files (x86)\HomeSeer HS4\Logs. But I'm still able to view the log within the HS4 Web page: it even goes back to Feb 10th. That's when I installed HS4 4.2.17.2.

Totally confused ... help? Where's THE log ?

That is a very good question. Looking at my HomeSeerLog.hsd it has a last date of 2/10/23 at 8:35AM. The log in HomeSeer starts at that time. Clearly the log is elsewhere. I’ve been digging, but haven’t found the location. Clearly it is no longer HomeSeerLog.hsd.

[Rupp]

If you are running Windows 11 and have the OneDrive Personal active then your log was most likely abducted by OneDrive.

[claude]

It's now in "C:\Logs", for me. When and why did this happen? I see no mention in the release notes of 4.2.17.2 on relocating the log file.

[racerfern]

Yup, it's there for me as well. Oopsy.

[randy]

If you are running Windows 11 and have the OneDrive Personal active then your log was most likely abducted by OneDrive.

No, HomeSeer started putting it in the server root under c:\logs instead of under C:\Program files (x86)\HomeSeer HS4\logs where it used to reside. That is why we lost all logging prior to 4.2.17.2. I don’t know why the change was made, but it has to be an error to move it out of the HS directory structure.

[randy]

It's now in "C:\Logs", for me. When and why did this happen? I see no mention in the release notes of 4.2.17.2 on relocating the log file.

I found that as well. I think it was a developer oops. Put it in the wrong root.

[spud]

The cause of this issue has been identified and will be fixed shortly.
Tracked as HS-1813.

[claude]

...
Tracked as HS-1813.

Thanks for confirming.