How to throttle or stop plug-in from cluttering LuaPnP Log?
-
I use the ROKU plug-in from Vera's app repository. It seems to constantly add Log entries every 5 seconds or so, to the point where my LuaPnP log is just littered with page-long reports about the status of my Roku TV. My Log is 75% "Roku" status!
The only pertinent setting I see under Advanced > Variables is "PollingEnabled" (default:
true
) which when set tofalse
does indeed stop the logging altogether. But I fear this also completely stops the plug-in from checking TV status which otherwise would update variables that happen to trigger some of my MSR routines. (More testing needed here...)But do you guys know of any way -- up to and including editing the D_, I_ or L_ files of the plug-in itself! -- to simply stop or slow a running plug-in from writing to the Log??
Also, is there any harm (other than mild annoyance when I have to review the Log for unrelated things) in allowing Vera to write so vigorously to the Log all day long??
THANKS!
-
On a separate note, should I be at all concerned about these lines in my Vera Plus LuaPnP log?
02 03/31/21 0:56:28.105 ZWaveNode::AddPollingCommand light/switch node 27 doesn't support any COMMAND_CLASS_BASIC <0x75f53520> 02 03/31/21 0:56:38.100 ZWaveJobHandler::AlarmCallback skipping check because of jobs <0x76553520> 01 03/31/21 0:59:50.162 LuaInterface::CallFunction_Timer device 336 refreshCache took 10 seconds <0x73353520>
They repeat quite often, though I can't pinpoint what they denote. I do know that "Node 27" refers to "altID=27" which is my Fibaro RGBW LED controller (this is precisely why I foolishly clicked "Configure Node Now" on it the other day, to my eternal embarrassment!).
Should I ignore? Do something? The Log is just the Amazon jungle to me. Thanks!
-
On a separate note, should I be at all concerned about these lines in my Vera Plus LuaPnP log?
02 03/31/21 0:56:28.105 ZWaveNode::AddPollingCommand light/switch node 27 doesn't support any COMMAND_CLASS_BASIC <0x75f53520> 02 03/31/21 0:56:38.100 ZWaveJobHandler::AlarmCallback skipping check because of jobs <0x76553520> 01 03/31/21 0:59:50.162 LuaInterface::CallFunction_Timer device 336 refreshCache took 10 seconds <0x73353520>
They repeat quite often, though I can't pinpoint what they denote. I do know that "Node 27" refers to "altID=27" which is my Fibaro RGBW LED controller (this is precisely why I foolishly clicked "Configure Node Now" on it the other day, to my eternal embarrassment!).
Should I ignore? Do something? The Log is just the Amazon jungle to me. Thanks!
-
@rafale77 said in How to throttle or stop plug-in from cluttering LuaPnP Log?:
You should really disable polling on the vera...
I actually thought I had...? I'll dredge up the old "Polling" thread and follow up. Thanks again!
-
Care to comment on this particular line, which (a) occurred during my most recent unplanned Luup Engine restart, and (b) is the only instance of this I've seen:
01 03/31/21 12:17:43.489 Main WatchDogRoutine: blocked - terminating 1 <0x6b31e520> 02 03/31/21 12:17:43.491 Dumping 28 locks <0x6b31e520> ... 2021-03-31 12:17:43 - LuaUPnP Terminated with Exit Code: 137
Sounds scary to me, esp. cuz the first line was shown all in RED in Vera's Log.
(Much) earlier threads about this situation on MCV suggest it's the result of plug-ins fighting each other, in essence. I may have to remove plug-ins one by one to see which one's the worst offender.
UPDATE:
I've since deleted these plug-ins from my Vera Plus...
Reactor
,GCal3
,AutoVera
(none of which were in use)
...then power cycled her in case there were memory leaks.