Jim Star
Jim Star
Same issue, with RLN8-410 NVR and four RLC-822A cameras (all four connected through this NVR). It constantly loses sensors to "Unavailable" state, and then back to "Clear" again, then all...
Nope, no grey parts on the timeline, neither in Android nor in PC app (see the screenshot). And I have 24/7 recording enabled for all four cameras, so they record...
The log is full of errors from reolink_dev. This is the top-most one of this list for example, Python traceback. Let me know if you'd need logs in a text-form...
... and the log is just full of those:
I'm not sure so far (just a first quick look at this), but the tracebacks look like some Python errors on `reolink_dev` side, not on the NVR side...
I see a lot of those: Looks like some empty or broken Json response is returned by Reolink NVR to the calling Reolink-Python code. And the Reolink code just blindly...
Another thought: I see that in the previous logs I posted here, the period of `reolink_dev` flooding the Reolink NVR with requests is like 40 milliseconds, at least this is...
It looks like in the Reolink-API's **separate** `get_motion_state()` call it is done **properly** in contrast to `get_all_motion_states()`: it first checks if the response is **empty** before passing it to `json.loads(response)`....
...and I see there is no proper exit with return value in the `get_all_motion_states()` **and no call to `clear_token()`** in the exception case... Could possibly the lack of `clear_token()` be...