(2020-06-17, 19:47)phunkyfish Wrote: Can you explain why you would want to block the requests?
The main reason is the authentication may have lapsed. This logic needs to wait for the client system wake to flow from
PVR_CONNECTION_STATE_DISCONNECTED
PVR_CONNECTION_STATE_CONNECTING
PVR_CONNECTION_STATE_CONNECTED
However there is more to it then this because those triggers are happening while the original PVR Manager is stopping which I suspect causes the notifications the user doesn't want and causes channels and groups to be deleted
2020-06-17 16:56:35.650 T:8928 NOTICE: PVR Manager: Stopping
...
2020-06-17 16:56:35.698 T:1048 ERROR: PVR::CPVRClients::GetChannels: PVR client 'NextPVR (127.0.0.1):connected' returned an error: server error
2020-06-17 16:56:35.711 T:1048 ERROR: PVR::CPVRClients::GetChannelGroups: PVR client 'NextPVR (127.0.0.1):connected' returned an error: server error
2020-06-17 16:56:35.711 T:1048 ERROR: PVR::CPVRClients::GetChannels: PVR client 'NextPVR (127.0.0.1):connected' returned an error: server error
2020-06-17 16:56:35.725 T:1048 ERROR: PVR::CPVRClients::GetChannels: PVR client 'NextPVR (127.0.0.1):connected' returned an error: server error
2020-06-17 16:56:35.731 T:1048 ERROR: PVR::CPVRClients::GetChannels: PVR client 'NextPVR (127.0.0.1):connected' returned an error: server error
2020-06-17 16:56:35.735 T:1048 ERROR: PVR::CPVRClients::GetRecordings: PVR client 'NextPVR (127.0.0.1):connected' returned an error: server error
2020-06-17 16:56:35.735 T:1048 ERROR: PVR::CPVRClients::GetTimers: PVR client 'NextPVR (127.0.0.1):connected' returned an error: server error
until eventually
2020-06-17 16:56:35.735 T:1048 DEBUG: Thread PVRManager 1048 terminating
2020-06-17 16:56:37.605 T:9264 DEBUG: Thread EPGUpdater 9264 terminating
2020-06-17 16:56:37.770 T:9836 DEBUG: Thread PVRGUIInfo 9836 terminating
2020-06-17 16:56:37.793 T:8928 NOTICE: PVR Manager: Stopped
2020-06-17 16:56:37.793 T:8928 NOTICE: PVR Manager: Starting
when things go back to normal.
Martin