Hey all.. could use some guidance on what to check first. realized later today that HS3.exe was crashing then rebooting via Sentry. not sure when/why it started today... the only change I made to the system was to bind the IP to my HS3 install (I run it on a Windows 10 VM machine).
has worked flawlessly for months.... the only reason I tried it was the extra virtual adapter that is created via VM sometimes screws with the Sonos PI. (to make it work I have to disable that adapter - helped me figure that out many months ago.)
I finally got it to stop the circular reboots by first shutting down Hssentry, then restarted HS3, then killing Hssentry while it all started back up. Seems stable at the moment.
any ideas what I could check first?
thanks!
has worked flawlessly for months.... the only reason I tried it was the extra virtual adapter that is created via VM sometimes screws with the Sonos PI. (to make it work I have to disable that adapter - helped me figure that out many months ago.)
I finally got it to stop the circular reboots by first shutting down Hssentry, then restarted HS3, then killing Hssentry while it all started back up. Seems stable at the moment.
any ideas what I could check first?
thanks!
Current Date/Time: | 4/12/2019 5:17:00 PM Pacific Daylight Time |
HomeSeer Version: | HS3 Standard Edition 3.0.0.500 (Windows) |
HomeSeer: | Is Registered |
Operating System: | Microsoft Windows 10 Pro - Work Station |
OS Version: | 10.0.17763 Service Pack: 0.0 |
Comment