About 8:15PM last night I noticed Google Voice Command failed. The Omni Plugin has failed again. As usual, I restarted the plugin but, this time, that did NOT recover the plugin functionality. I resorted to reboot the Hometroller Zee which did bring everything back.
Unfortunately, the HS log file prior to the reboot was lost (lesson learned). The Omni log via PC Access is uneventful through the time period.
HomeSeer Log
Oct-14 8:17:14 PM Startup ************************************************************ ********************
Oct-14 8:17:14 PM Startup HomeSeer version 3.0.0.435 Edition: HS3 ZEE S2 Starting Now
Oct-14 8:17:14 PM Startup ************************************************************ ********************
...
Oct-14 8:40:38 PM Z-Wave ************************************************************ *******************
Oct-14 8:40:38 PM Z-Wave STARTUP COMPLETE: All configured interfaces were successfully initialized.
Oct-14 8:40:38 PM Z-Wave ************************************************************ *******************
OMNI Log
1 10/15 6:36 AM The system Master Code DISARM
2 10/14 10:58 PM QUICK ARM NIGHT
3 10/14 4:03 PM The system Master Code DISARM
4 10/14 4:03 PM Entry Doors TRIPPED
5 10/14 3:01 PM QUICK ARM AWAY
6 10/14 3:00 PM The system Master Code DISARM
7 10/14 3:00 PM Entry Doors TRIPPED
8 10/14 2:58 PM QUICK ARM AWAY
9 10/14 6:34 AM The system Master Code DISARM
The Omni Log file as presented in HS, for reasons I do not understand, have no data since the reboot but started collecting log data about 12 hours later.
10/15/2018 8:17:43 AM [2] [NOT READY]
10/15/2018 8:17:43 AM [2] [MapZoneStatus_V2: zoneId=[2] status=[1] zoneChanged=[False] annotation=[Z2] statusText=[NOT READY] zoneType=[3] zoneTypeText=[AwayInt] name=[InteriorMotion] area=[1] analogLoop=[254] isNamed=[True] lastStatus=[0] lastStatusText=[] statusLastChangeDate=[10/15/2018 8:17:43 AM] isSecurityZone=[True] isArmingZone=[True] hsDeviceRef=[19] hsParentRef=[7] temperature=[0] humidity=[0] currentCondition=[0] currentStatusText=[NOT READY] hsZoneStatus=[0] lowSetpoint=[0] highsetpoint=[0]]
10/15/2018 8:17:43 AM [2] [Zone [2] status=[1] [1]] <--- first log entry, reboot was 8:17PM on 10/14
Beginning data above
Unfortunately, the HS log file prior to the reboot was lost (lesson learned). The Omni log via PC Access is uneventful through the time period.
HomeSeer Log
Oct-14 8:17:14 PM Startup ************************************************************ ********************
Oct-14 8:17:14 PM Startup HomeSeer version 3.0.0.435 Edition: HS3 ZEE S2 Starting Now
Oct-14 8:17:14 PM Startup ************************************************************ ********************
...
Oct-14 8:40:38 PM Z-Wave ************************************************************ *******************
Oct-14 8:40:38 PM Z-Wave STARTUP COMPLETE: All configured interfaces were successfully initialized.
Oct-14 8:40:38 PM Z-Wave ************************************************************ *******************
OMNI Log
1 10/15 6:36 AM The system Master Code DISARM
2 10/14 10:58 PM QUICK ARM NIGHT
3 10/14 4:03 PM The system Master Code DISARM
4 10/14 4:03 PM Entry Doors TRIPPED
5 10/14 3:01 PM QUICK ARM AWAY
6 10/14 3:00 PM The system Master Code DISARM
7 10/14 3:00 PM Entry Doors TRIPPED
8 10/14 2:58 PM QUICK ARM AWAY
9 10/14 6:34 AM The system Master Code DISARM
The Omni Log file as presented in HS, for reasons I do not understand, have no data since the reboot but started collecting log data about 12 hours later.
10/15/2018 8:17:43 AM [2] [NOT READY]
10/15/2018 8:17:43 AM [2] [MapZoneStatus_V2: zoneId=[2] status=[1] zoneChanged=[False] annotation=[Z2] statusText=[NOT READY] zoneType=[3] zoneTypeText=[AwayInt] name=[InteriorMotion] area=[1] analogLoop=[254] isNamed=[True] lastStatus=[0] lastStatusText=[] statusLastChangeDate=[10/15/2018 8:17:43 AM] isSecurityZone=[True] isArmingZone=[True] hsDeviceRef=[19] hsParentRef=[7] temperature=[0] humidity=[0] currentCondition=[0] currentStatusText=[NOT READY] hsZoneStatus=[0] lowSetpoint=[0] highsetpoint=[0]]
10/15/2018 8:17:43 AM [2] [Zone [2] status=[1] [1]] <--- first log entry, reboot was 8:17PM on 10/14
Beginning data above
Comment