Wake up NextPVR when Kodi plays Live TV

[fla]

Enhancement Request:

I do not know the architecture of the NextPVR Kodi addon but would it be possible to automatically wake up the NextPVR backend server when starting to play live TV on Kodi? Right now the Kodi screen will freeze for a minute or two if the NextPVR server has slept. When it comes back you can run a separate addon "Advanced Wake on LAN" or pretend to access pictures, videos, music on the server and Kodi will automatically wake up the server. It would be nice if the NextPVR backend would wake up and live TV just worked albeit with the wake up delay.

[fla]

Nobody? Does X-NEWA do this?

[2leftfeet]

I do this all the time. Here's how I do it:
I use a script (bat file) to send a WOL (wake on Lan) signal to the server, then enter a loop waiting for notification that npvr.db3 exists on the server. Once a response is received that npvr.db3 exists (indicating that the server is now awake and happy), a command to start Kodi is executed by the bat file.

That's it - works everytime.

[mvallevand]

Nobody? Does X-NEWA do this?

Yes it does.

Martin

[fla]

Yes it does.

Great. We'll try using X-NEWA instead of sub's plugin. We can't do what what 2leftfeet does since kodi is already running 24/7/365 on a SBC. The plugin really needs to ensure it won't freeze the system when called upon.

[fla]

Adding the following line to kodi's favourites.xml creates a favorite that will wake up the server then go to the guide. The problem and workaround are discussed in this thread.

Code:

<favourite name="Live TV" thumb="/storage/.kodi/addons/pvr.nextpvr/icon.png">RunScript(&quot;script.advanced.wol&quot;,ActivateWindow(TVGuide),True)</favourite>

It's an ugly hack that does what should be in the addon but it beats freezing for several minutes.

BTW X-NEWA was also freezing when the server was asleep.

[mvallevand]

You probably did not configure x-newa with the correct MAC address

Martin

[fla]

You probably did not configure x-newa with the correct MAC address

Martin

In the x-newa general settings where it asks for "Host IP or Name" we had the name. By putting the host IP instead, x-newa now pops up the message about sending the wol packet (bug with name???).

Also in the x-newa advanced settings where it asks for "Broadcast address" we had 255.255.255.55 (error in script.xbmc.x-newa/resources/settings.xml???). By putting 255.255.255.255 the nextpvr server wakes up.

[mvallevand]

True if you use the NetBIOS hostname the error is different since the system cannto resolve the hostname. I will consider sending WOL on this error too.

Yes and the .55 is a wrong, fixed for the next release. Glad you figured it out.

Martin

[fla]

The hostname resolution comes from a local dns so it should always work. This X-NEWA is running on linux in case that's relevant. X-NEWA'S WOL is a great feature btw.