Sure I can send you the logs when I get home tonight but just to be clear your addon is working fine on my chromebook. I just saw your 24 hour comment and wondered what you meant as I ran into another problem that may or may not be related:djp952 wrote: ↑Sun Jul 14, 2019 9:31 pmThe discovery data in the cloud (HTTP) has no means of knowing if you turned something off and will continue to report the device as available for around 24 hours.fletchb1 wrote: ↑Sun Jul 14, 2019 6:22 pmWhat do you mean that it will show up in the list for 24 hours? I did noticed that my main TV no longer has the program guide and can't record anything like it lost the record engine.djp952 wrote: ↑Sun Jul 14, 2019 5:40 pm
Fixed before I even saw the post! Nice. HTTP used to be the default but I recently switched it over to use UDP broadcast by default by popular demand HTTP discovery works perfectly well, the only problem with it is that if you turn something off it will still show up in the list for up to 24 hours. If you aren't in the habit of turning things on and off, there should be no problem at all!
Glad you like it, have a great remainder of your weekend.
The guide data and the ability to add/manipulate tuners depends on the information reported from your tuners. The RECORD engine, ironically enough has nothing to do with those. If the discovery data about the tuners is out of date the PVR may be sending stale authorization strings to the could backend and cause this. Can you provide a Kodi log from this system? I pretty much log everything useful at this point it should be pretty easy to identify the root cause from that
Moments after I got Kodi working on the chromebook , I just happen to notice that the guild stopped working on our main tv (Android running on Shield) and could not record any shows.
I was too tired to fool with it last night but noticed it was working again this morning so not sure if they were related or not. Tonight when I get home from work, I will fire up the chromebook and see if the issue returns.