default, 2 minute.
I've wondered what this actually means in practice. Doesn't the virtual device synchronize if/when there's an event on the physical device? And if so, why do I ever care about a full remote device sync?
ok, lets turn that off completely, also make sure its disabled on each device, they have individual overrides.
This setting is there just to make sure that nothing gets missed, but yes, events are sent as they are generated on the source hub.
So nothing should get missed in the first place, this is simply a test to see if its contributing and or the cause of these errors.
ouch that's going to take a few hours to go through all of them, to disable. I'll do it if need be, but is there a shortcut?
EDIT: Also, feel like I should mention that I switched from UDP to TCP when I saw probs with Hub Mesh, recognizing I have a hub router (Orbi). Didn't seem to improve my issues.
How many linked devices on the hub with issues?
And I can't think of any other way of testing this short or disabling hub link altogether...
By hub where the physical device is:
134 + 124 + 51 + 37 = 346
There's another ~200 devices (99% virtual) that are native to the hub in question.
Edit: also, noticed that one Motion Lighting rule (my only one) is generating errors. See log extract below. Look at the runtime--jeez. It's a very simple motion-flips-switch rule.
app:39722020-12-28 07:26:31.644 pm warnmethod motionInactive of child app Flag: Set Office Occupied vSwitch on .53 ran for 354,971ms
app:39722020-12-28 07:25:17.243 pm errorjava.lang.Exception: Unable to aquire lock to schedule run once for turnOff on line 1139 (motionInactive)
app:39722020-12-28 07:24:03.750 pm errorjava.lang.Exception: Unable to aquire lock to schedule run once for turnOff on line 1139 (motionInactive)
app:39722020-12-28 07:23:08.208 pm errorjava.lang.Exception: Unable to aquire lock to schedule run once for turnOff on line 1139 (motionInactive)
Yeah, like I said, let's turn off full remote device sync first and see where we sit.
Yeah, sorry, I wasn't clear. I did that when you first asked. Currently monitoring logging. Stay tuned.
1 Like
Bad news....getting same errors from same apps as before: (1) ZMC; (2) the one Motion Lighting app; and (3) an RM4 app. Details below
The ZMC errors are repeats of:
app:46662020-12-28 09:21:17.323 pm errorjava.lang.Exception: Unable to aquire lock to schedule run once for zoneOff on line 257 (inactiveHandler)
The MLA errors are repeats of:
app:39722020-12-28 09:24:24.806 pm warnmethod motionInactive of child app Flag: Set Office Occupied vSwitch on .53 ran for 324,765ms
app:39722020-12-28 09:22:05.205 pm errorjava.lang.Exception: Unable to aquire lock to schedule run once for turnOff on line 1139 (motionInactive)
This time I also noticed a RM app that notifies on door left open:
app:37302020-12-28 09:24:22.955 pm errorjava.lang.Exception: Unable to aquire lock to schedule run once for delayedActsCancel on line 7051 (allHandler)
Ok, going to move further work on this to the pm we have going...
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
