2021-08-25, 08:12
Thanks for your answer.
My tests are from 18.9 because i have other issues with 19.1 on my ATV's which prevent's me from migrating.
But, i have tested 19.1 a few weeks ago and the same issue occured, so matrix is not fixing this.
The "wait for network option" is no solution i think. Think of the scenario that the internet connection of the user is down (ex.: during storms),
and he can't watch local media from NAS...
So the only real solution is to fix the issue.
I dont know much about the code, but i think the following is happening (please correct me if i am wrong):
thx
My tests are from 18.9 because i have other issues with 19.1 on my ATV's which prevent's me from migrating.
But, i have tested 19.1 a few weeks ago and the same issue occured, so matrix is not fixing this.
The "wait for network option" is no solution i think. Think of the scenario that the internet connection of the user is down (ex.: during storms),
and he can't watch local media from NAS...
So the only real solution is to fix the issue.
I dont know much about the code, but i think the following is happening (please correct me if i am wrong):
- PVR clients are offline and deleting the channels from the tv.db
- When they online again they are adding the channels again (with different unique id's), and there get's something messed up in the map
- every channel has an unique channel id (ex.: hash of {pvr addon name + channel id})
- mapping is done with this unique id's
- when an pvr addon is offline, remove the channels from the channels table but not from the map
- when the addon is online again, readd the channels to the channels table with their unique id'
thx