Bugs in de IPPower plugin
Posted: Sun Nov 15, 2009 2:17 pm
Zou je het log level eens op debug kunnen zetten en doorgeven wat er in de log staat op het moment dat Homeseer crashed?
Rene.
Rene.
Domotica - Home Automation Forum
https://www.domoticaforum.eu/
Code: Select all
IP Power Log:
16-11-2009 9:05:08 IPPower DEBUG: Entering GetStatus for controller Controller1
16-11-2009 9:05:08 IPPower DEBUG: Query: http://192.46.150.212:80/info.xml
16-11-2009 9:05:09 IPPower DEBUG: Parsing info.xml
16-11-2009 9:05:09 IPPower DEBUG: IPPower firmware version: V1.15 2009/05/27
16-11-2009 9:05:09 IPPower DEBUG: Output mask: 00010111
16-11-2009 9:05:09 IPPower DEBUG: Input mask: 00010000
16-11-2009 9:05:09 IPPower INFO: Set appliance [5 to on
16-11-2009 9:05:13 IPPower DEBUG: Host Name: 192.46.150.212
16-11-2009 9:05:13 IPPower DEBUG: Query: http://192.46.150.212:80/info.xml
16-11-2009 9:05:13 IPPower DEBUG: IP Address: 192.46.150.212
16-11-2009 9:05:13 IPPower DEBUG: Entering GetStatus for controller Controller1
16-11-2009 9:05:13 IPPower DEBUG: Set credentials for controller Controller1
16-11-2009 9:05:14 IPPower DEBUG: Parsing info.xml
16-11-2009 9:05:14 IPPower DEBUG: IPPower firmware version: V1.15 2009/05/27
16-11-2009 9:05:14 IPPower DEBUG: Output mask: 00010111
16-11-2009 9:05:14 IPPower DEBUG: Input mask: 00010000
16-11-2009 9:05:18 IPPower DEBUG: Entering GetStatus for controller Controller1
16-11-2009 9:05:18 IPPower DEBUG: Host Name: 192.46.150.212
16-11-2009 9:05:18 IPPower DEBUG: IP Address: 192.46.150.212
16-11-2009 9:05:18 IPPower DEBUG: Set credentials for controller Controller1
16-11-2009 9:05:18 IPPower DEBUG: Query: http://192.46.150.212:80/info.xml
16-11-2009 9:05:19 IPPower DEBUG: Output mask: 00010111
16-11-2009 9:05:19 IPPower DEBUG: Input mask: 00010000
16-11-2009 9:05:19 IPPower DEBUG: Parsing info.xml
16-11-2009 9:05:19 IPPower DEBUG: IPPower firmware version: V1.15 2009/05/27
16-11-2009 9:05:23 IPPower DEBUG: IP Address: 192.46.150.212
16-11-2009 9:05:23 IPPower DEBUG: Set credentials for controller Controller1
16-11-2009 9:05:23 IPPower DEBUG: Query: http://192.46.150.212:80/info.xml
16-11-2009 9:05:23 IPPower DEBUG: Entering GetStatus for controller Controller1
16-11-2009 9:05:23 IPPower DEBUG: Host Name: 192.46.150.212
16-11-2009 9:05:24 IPPower DEBUG: Parsing info.xml
16-11-2009 9:05:24 IPPower DEBUG: IPPower firmware version: V1.15 2009/05/27
16-11-2009 9:05:24 IPPower DEBUG: Output mask: 00010111
16-11-2009 9:05:24 IPPower DEBUG: Input mask: 00010000
16-11-2009 9:05:28 IPPower DEBUG: Query: http://192.46.150.212:80/info.xml
16-11-2009 9:05:28 IPPower DEBUG: Entering GetStatus for controller Controller1
16-11-2009 9:05:28 IPPower DEBUG: Host Name: 192.46.150.212
16-11-2009 9:05:28 IPPower DEBUG: Set credentials for controller Controller1
16-11-2009 9:05:28 IPPower DEBUG: IP Address: 192.46.150.212
16-11-2009 9:05:29 IPPower DEBUG: Parsing info.xml
16-11-2009 9:05:29 IPPower DEBUG: IPPower firmware version: V1.15 2009/05/27
16-11-2009 9:05:29 IPPower DEBUG: Output mask: 00010111
16-11-2009 9:05:29 IPPower DEBUG: Input mask: 00010000
16-11-2009 9:05:29 IPPower DEBUG: Enter ReceiveSnmpCallback
16-11-2009 9:05:29 IPPower DEBUG: Received SNMP trap from 192.46.150.212
16-11-2009 9:05:29 Web Server Web Server stopped
16-11-2009 9:05:33 IPPower DEBUG: Entering GetStatus for controller Controller1
16-11-2009 9:05:33 IPPower DEBUG: Host Name: 192.46.150.212
16-11-2009 9:05:33 IPPower DEBUG: IP Address: 192.46.150.212
16-11-2009 9:05:33 IPPower DEBUG: Set credentials for controller Controller1
16-11-2009 9:05:33 IPPower DEBUG: Query: http://192.46.150.212:80/info.xml
16-11-2009 9:05:34 IPPower DEBUG: Input mask: 00010000
16-11-2009 9:05:34 IPPower DEBUG: Output mask: 00010111
16-11-2009 9:05:34 IPPower DEBUG: IPPower firmware version: V1.15 2009/05/27
16-11-2009 9:05:34 IPPower DEBUG: Parsing info.xml
16-11-2009 9:05:38 IPPower DEBUG: Entering GetStatus for controller Controller1
16-11-2009 9:05:38 IPPower DEBUG: Host Name: 192.46.150.212
16-11-2009 9:05:38 IPPower DEBUG: IP Address: 192.46.150.212
16-11-2009 9:05:38 IPPower DEBUG: Set credentials for controller Controller1
16-11-2009 9:05:38 IPPower DEBUG: Query: http://192.46.150.212:80/info.xml
16-11-2009 9:05:39 IPPower DEBUG: Input mask: 00010000
16-11-2009 9:05:39 IPPower DEBUG: Parsing info.xml
16-11-2009 9:05:39 IPPower DEBUG: IPPower firmware version: V1.15 2009/05/27
16-11-2009 9:05:39 IPPower DEBUG: Output mask: 00010111
16-11-2009 9:05:43 IPPower DEBUG: Query: http://192.46.150.212:80/info.xml
16-11-2009 9:05:43 IPPower DEBUG: Set credentials for controller Controller1
16-11-2009 9:05:43 IPPower DEBUG: IP Address: 192.46.150.212
16-11-2009 9:05:43 IPPower DEBUG: Entering GetStatus for controller Controller1
16-11-2009 9:05:43 IPPower DEBUG: Host Name: 192.46.150.212
16-11-2009 9:05:44 IPPower DEBUG: Parsing info.xml
16-11-2009 9:05:44 IPPower DEBUG: IPPower firmware version: V1.15 2009/05/27
16-11-2009 9:05:44 IPPower DEBUG: Output mask: 00010111
16-11-2009 9:05:44 IPPower DEBUG: Input mask: 10010000
16-11-2009 9:05:44 IPPower DEBUG: Set [16 to 2
Homeseer error in Windows:
16-11-2009 9:06:41
The Undo operation encountered a context that is different from what was applied in the corresponding Set operation. The possible cause is that a context was Set on the thread and not reverted(undone).
HomeSeer version: 2.4.0.1
Source: mscorlib
Target: Void Undo()
Stack trace:
at System.Threading.SynchronizationContextSwitcher.Undo()
at System.Threading.ExecutionContextSwitcher.Undo()
at System.Threading.ExecutionContext.runFinallyCode(Object userData, Boolean exceptionThrown)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteBackoutCodeHelper(Object backoutCode, Object userData, Boolean exceptionThrown)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.ContextAwareResult.Complete(IntPtr userToken)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
Vanwege deze opmerking dacht ik dat het misschien handig zou kunnen zijn om te zien wat er verder gebeurt na de crash van HS. Dat lukt met de methode die ik in de genoemde post beschrijf.rwitkamp wrote:Ik heb het nog steeds. Ik werk met Homeseer Pro 2.4.0.1. Nadeel van de Pro versie is dat HSEntry zorgt voor een restart, en ik amper tijd heb om de exacte foutmelding te noteren.