No Entries in Program Guide after Reboot

[pkscout]

In my experience, sometimes Linux decides the network is ready even when it isn't really ready, especially WiFi, so I'm wondering if Kodi is starting before the network is fully available. The network not being available could cause that error regarding the remote communications server not being available. I'm catching up a little on this thread, but it looks like you have Kodi set to automatically start when the device is started. As a test, I would turn that off, reboot connecting to WiFi, wait a full minute, and then start Kodi. If the issue doesn't repeat, then you need to figure out how to add some additional wait time to the process that starts Kodi.

[RocketDestroyer]

Thanks for the reply.  I believe that you are on the correct track.  I did a search and found this page
https://wiki.libreelec.tv/configuration/...p-shutdown that describes how to delay Kodi starting.

https://wiki.libreelec.tv/configuration/...p-shutdown

I was all excited and added the autostart.sh shell and that's as far as I got.   I tried to switch back from wired internet to the wireless internet and got an invalid-key error.   I know that I typed in the key correctly.  Another search turned up this...

https://forum.libreelec.tv/thread/25409-.../?pageNo=1

It sounds like the wireless software is broken so I will have to wait for that to be fixed before I can do anything else.

And this was supposed to be easy!?!?

[pkscout]

Sorry you're having this struggle.  If you want to go down a completely different rabbit hole, you could run OSMC on the pi instead on LibreElec.  It's an entirely different Linux distro basically but built specifically to run Kodi.

https://osmc.tv

I've run this both on a Raspberry Pi and using hardware they sell (Vero 4K+) and always been happy with it.  As long as you're not trying to do anything super specific with LibreElec besides running Kodi, it should work fine.

[mvallevand]

There are multiple issues involved here and the logs are not complete so it makes it difficult to diagnose. Running the server and client together is causing a weird issue introduced by Kodi in Nexus which I will be addressing but I cannot explain why Kodi core is not simply getting guide data on its own. In my testing the guide simply is reloaded.

I am thinking there could be server issues related to obtaining two IP addresses or delays in getting network after the server starts but we don't have system logs or nextpvr logs.

Two tests to see if networking is the issue would be to

Reset PVR to get the guide populated

1. Restart Kodi from the power button with the server running. This should keep the guide.

2. Disable the nextpvr and PVR.nextpvr from settings and renable them

OSMC doesn't provide an easy way to install NextPVR server so it would not be a useful test

Martin

[pkscout]

Oooo, I didn't realize the OP was trying to run NextPVR and Kodi on the same device. My bad. Agreed that if that's a need in this case, OSMC is not a good choice.

[RocketDestroyer]

Martin, I would be happy to do the tests that you mentioned but I can't because I am unable to log in to my network. I am experiencing the LibreElec Invalid-key error mentioned above. Until that is fixed I'm stuck.

I chose LibreElec because I could easily install NextPVR and connect to my HDHomeRun to watch and record local TV shows. It was easy to get it running with Schedules Direct. When it works is works well. I'm running NextPVR and Kodi on another LInux system for my HTPC and it works great. None of the issues I'm having with the Raspberry Pi system.

[mvallevand]

My suggestion would be to try and connect with wifi and then after it fails plug in the lan cable. Then you can ssh into the RPi and use the pastekodi command to get a url to the system and Kodi logs.

Martin

[RocketDestroyer]

Okay, here is the link to the results of the pastkodi command.  I did a reboot to LAN and then tried to switch to WiFi.

http://ix.io/4qG8

Here is a second capture.  This time the program guide did load when started with the LAN.  This has worked in the past.   I had to manually start the server to get the program guide to load.   Then I tried to switch to the 5 GHz Wifi and finally tired to switch 2.5 GHz wifi.  Both failed with the invalid-key error.

http://ix.io/4qGi

The WiFi is a TP link Deko x60 dual band mesh network and LAN is plugged into one of the Deko units.

[mvallevand]

Ok I am back home from vacation and can look at this in a little more detail. Do things change if you disable the VPN?

Martin

[mvallevand]

Could you try this on RPi4 and let me know how it works out.  It should solve the original connection problem.

Martin