2022-05-21, 15:34
2022-05-21, 16:17
(2022-05-21, 15:34)phunkyfish Wrote: @sus67 if you visit this URL in a browser what happens?This: https://paste.kodi.tv/kiguyaciza
http://192.168.178.30/web/settings
2022-05-21, 18:15
(2022-05-21, 16:17)sus67 Wrote:(2022-05-21, 15:34)phunkyfish Wrote: @sus67 if you visit this URL in a browser what happens?This: https://paste.kodi.tv/kiguyaciza
http://192.168.178.30/web/settings
Hmmm, very strange. It’s should print a message after reading settings and it does not. I wonder if it’s your version of OpenWebIf. 1.2.8 is very old.
@phunkyfish
with newer OWIF 1.5.0 on backend (VU+ box) the same with Kodi Nexus & VU+ PVR Addon -> Kodi crashed after restart with Hostname: https://paste.kodi.tv/ehiniwixaq.kodi
Other facts:
- Same settings in VU+ PVR Addon with Kodi Matrix 19.4 results no problems.
- It was possible to add video-sources (Movies) from backend (VU+ box) to Kodi Nexus
- Under Kodi Nexus in 'System info' the PVR service is inactive:
Let me know what you mean, please.
with newer OWIF 1.5.0 on backend (VU+ box) the same with Kodi Nexus & VU+ PVR Addon -> Kodi crashed after restart with Hostname: https://paste.kodi.tv/ehiniwixaq.kodi
Other facts:
- Same settings in VU+ PVR Addon with Kodi Matrix 19.4 results no problems.
- It was possible to add video-sources (Movies) from backend (VU+ box) to Kodi Nexus
- Under Kodi Nexus in 'System info' the PVR service is inactive:
Let me know what you mean, please.
2022-05-22, 09:11
(2022-05-22, 07:15)sus67 Wrote: @phunkyfish
with newer OWIF 1.5.0 on backend (VU+ box) the same with Kodi Nexus & VU+ PVR Addon -> Kodi crashed after restart with Hostname: https://paste.kodi.tv/ehiniwixaq.kodi
Other facts:
- Same settings in VU+ PVR Addon with Kodi Matrix 19.4 results no problems.
- It was possible to add video-sources (Movies) from backend (VU+ box) to Kodi Nexus
- Under Kodi Nexus in 'System info' the PVR service is inactive:
Let me know what you mean, please.
Ok, that helps. So it appears the addon is crashing and is never started correctly.
As you have an Amazon device can you run ADB and supply a stack trace from the crash?
2022-05-22, 11:32
2022-05-22, 12:31
(2022-05-22, 11:32)sus67 Wrote:(2022-05-22, 09:11)phunkyfish Wrote: As you have an Amazon device can you run ADB and supply a stack trace from the crash?This tool working fine with Fire-TV, but I dont know to create stack traces; sorry.
If you run an ADB shell before starting kodi and then a logcat when it crashes that should give us a starting point.
2022-05-22, 13:45
(2022-05-22, 12:31)phunkyfish Wrote: If you run an ADB shell before starting kodi and then a logcat when it crashes that should give us a starting point.
Found in logcat (adbLink): https://paste.kodi.tv/atufugilug.kodi
Not sure what to do with ADB Shell: https://youtu.be/TVGmC1-UHs8
2022-05-23, 23:07
(2022-05-22, 13:45)sus67 Wrote:(2022-05-22, 12:31)phunkyfish Wrote: If you run an ADB shell before starting kodi and then a logcat when it crashes that should give us a starting point.
Found in logcat (adbLink): https://paste.kodi.tv/atufugilug.kodi
Not sure what to do with ADB Shell: https://youtu.be/TVGmC1-UHs8
So for the backtrace that you get I was hoping it would point to the line of code that causes the crash. Unfortunately it just shows that the addon library causes it but nothing else.
2022-05-26, 10:20
@sus67 any chance I can connect to you VU+ device remotely? If you are ok with that I could likely fix the issue quite quickly. Ping on me gitter.im if that's possible. Same username.
2022-05-26, 11:18
(2022-05-26, 10:20)phunkyfish Wrote: @sus67 any chance I can connect to you VU+ device remotely? If you are ok with that I could likely fix the issue quite quickly. Ping me gitter.im if that's possible. Same username.Unfortunately I have non experience with this kind of remote control. Are there other ways for the fix? e.g. I send you download-link of select "rootfs" folder of VU+device ?
2022-05-27, 06:29
(2022-05-26, 10:20)phunkyfish Wrote: @sus67 any chance I can connect to you VU+ device remotely? If you are ok with that I could likely fix the issue quite quickly. Ping on me gitter.im if that's possible. Same username.Okay, let's try the VU+ fix ->Gitter ping done.
2022-06-14, 18:16
I recently switched to a new VU+ receiver (running OpenPLi) and at first Kodi seemed to work fine. However, after a some hours (or usage) the PVR functionality starts to fail and it displays an empty folder instead of the recordings. The only way to get it to work again is to reboot server. And there's another issue as well: when I delete a recording this always seems to fail the first time and it works the second time.
I've created a debug log (full log available via PM) and you can see that suddenly all commands start failing with server errors. I suspect that this is caused because I set my receiver to deep sleep but I always did the same thing with my previous receiver so I don't understand why this would suddenly be a problem where the PVR component can't seem to recover from. Anyway, when the receiver is turned on at a later time, the server error's keep on appearing in the log. I've manually checked the results of the http://192.168.1.37:80/web/currenttime command and it returns the current time as expected. However, according to the log it's still not working:
AddOnLog: pvr.vuplus: pvr.vuplus - Check Unable to open url: http://192.168.1.37:80/web/currenttime
AddOnLog: pvr.vuplus: pvr.vuplus - CheckHttp - Could not open webAPI.
thanks!
I've created a debug log (full log available via PM) and you can see that suddenly all commands start failing with server errors. I suspect that this is caused because I set my receiver to deep sleep but I always did the same thing with my previous receiver so I don't understand why this would suddenly be a problem where the PVR component can't seem to recover from. Anyway, when the receiver is turned on at a later time, the server error's keep on appearing in the log. I've manually checked the results of the http://192.168.1.37:80/web/currenttime command and it returns the current time as expected. However, according to the log it's still not working:
AddOnLog: pvr.vuplus: pvr.vuplus - Check Unable to open url: http://192.168.1.37:80/web/currenttime
AddOnLog: pvr.vuplus: pvr.vuplus - CheckHttp - Could not open webAPI.
thanks!
2022-06-14, 21:53
(2022-06-14, 18:16)Peekstra Wrote: I recently switched to a new VU+ receiver (running OpenPLi) and at first Kodi seemed to work fine. However, after a some hours (or usage) the PVR functionality starts to fail and it displays an empty folder instead of the recordings. The only way to get it to work again is to reboot server. And there's another issue as well: when I delete a recording this always seems to fail the first time and it works the second time.
I've created a debug log (full log available via PM) and you can see that suddenly all commands start failing with server errors. I suspect that this is caused because I set my receiver to deep sleep but I always did the same thing with my previous receiver so I don't understand why this would suddenly be a problem where the PVR component can't seem to recover from. Anyway, when the receiver is turned on at a later time, the server error's keep on appearing in the log. I've manually checked the results of the http://192.168.1.37:80/web/currenttime command and it returns the current time as expected. However, according to the log it's still not working:
AddOnLog: pvr.vuplus: pvr.vuplus - Check Unable to open url: http://192.168.1.37:80/web/currenttime
AddOnLog: pvr.vuplus: pvr.vuplus - CheckHttp - Could not open webAPI.
thanks!
You don’t mention what platform you run Kodi on, the version of kodi you are running or if your old E2 device was a VU+ or what model your new device is so it’s very hard to help.
It might also be that your device has a memory leak. What version of OpenPli and OpenWebIf do you have?
Also, I have an E2 device and deep standby kills the network. However when it comes out of standby it is picked up by by my kodi device without issue. Does it work if you use regular standby instead?
I use OpenVix though.
2022-06-15, 09:27
The KODI box is a Vero 4K unit running on the latest OSMC build. And on the Enigma side, that's a VU+ UNO 4K SE with OpenPLi and the latest updates which includes webif 1.5.1.
I don't suspect that my Kodi box has a memory leak as it was working without any problems with the previous box and hasn't received an update since that time. I do suspect some kind of a timing issue the new receiver is connected to my NAS and doesn't have an internal harddisk. Although the NAS is always on, maybe some commands take a bit longer and there's a timeout? The NAS is always on so no long wakeup procedure is happening there plus it has a SSD cache as well.
Until now, I've always used the deep standby feature and just as with your receiver, Kodi will reconnect with the box when it becomes available again. However I could disable deep standby for now check if Kodi keeps working. This will take some time as the PVR connection can be stable for over a day in the current situation.
Is there a way to see the results of the openwebif commands which Kodi sends?
I don't suspect that my Kodi box has a memory leak as it was working without any problems with the previous box and hasn't received an update since that time. I do suspect some kind of a timing issue the new receiver is connected to my NAS and doesn't have an internal harddisk. Although the NAS is always on, maybe some commands take a bit longer and there's a timeout? The NAS is always on so no long wakeup procedure is happening there plus it has a SSD cache as well.
Until now, I've always used the deep standby feature and just as with your receiver, Kodi will reconnect with the box when it becomes available again. However I could disable deep standby for now check if Kodi keeps working. This will take some time as the PVR connection can be stable for over a day in the current situation.
Is there a way to see the results of the openwebif commands which Kodi sends?
