Kodi Community Forum

Hello,

I have a problem regarding Kodi + Yatse (remote control for Android). Firstly I thought it will be a problem of Yatse, here is the description of bug report I filed on Yatse pages:

Quote:Hello,

I use Kodi (well, actually OSMC which is just a Kodi “wrapper”) on Raspberry Pi 3 and your great remote control, Yatse, on Android device.
When eveyrthing works, it works great. However, for past months I have been experiencing remote control malfunctioning irregularly once in a day or two.
Basically it keeps turning off (showing me that the device is offline and not responding to controls) after some up-time.
The most extreme scenario that happened to me and demonstrates the case is that I played an episode of a series with Yatse, it played for 20 minutes, I wanted to play next but the remote was not working anymore.
The more common case is simply watching a movie and coming to Kodi the next day with not anymore functioning Yatse.

I can’t figure out what is making the remote suddenly not working.
What I know is:

• there is a workaround for remote not stopping working - if I leave Kodi in any kind of plugin screen (e.g. YouTube search screen) - it becomes immune to stopping working
  
• I have feeling that most of the “stops working” times are around the mid-day, however it is merely a feeling
  
• when the Yatse remote problem happens and I connect external USB keyboard, I can control Kodi with it without any problem, Yatse however remains non-functioning - therefore it seems that the problem is not in global controls mechanism, but specifically in the way Yatse communicates with Kodi
  
• when the problem happens, I can access Kodi web interface from one of my local computers and control Kodi from it as well - therefore the network communication seems to be OK as well
  
• the only thing that solves it is plugging off and on RPi or simply connecting to the Pi by SSH and restarting mediacenter service - after restart, Yatse works again
  

I hope I haven’t forgot anything important.
Also attaching Yatse and Kodi logs.
Please, can you help me with the issue?

Thank you,
Regards,
Martin      

And after a few minutes, there was following reply from Yatse developer:

Quote:The fact that rebooting OMSC and not touching Yatse gives a big hint at where the problem relies
[662] HTTP FAILED: java.net.ConnectException: Failed to connect to /192.168.0.19:8080Your OSMC stop responding for an unknown reason  
I guess some thread gets locked on Kodi due to a bug on Kodi or OSMC
And if the remote buttons does not work too then issue is maybe network related on your phone as it use another protocol. 

Then I continued by opening a support thread on OSMC forum.
I got a response that OSMC is an operating system running Kodi but the service mediacenter is a Kodi service and if restarting it helps, then the problem seems to be in Kodi.

So here I am and I'd like to ask all of you if you can help me with the issue.
Here are the logs: https://paste.osmc.tv/renanenuva

Thank you,
Martin

(2017-11-18, 19:47)mardu Wrote: [ -> ]https://paste.osmc.tv/renanenuva2

"Document not found."

I think he means:  https://paste.osmc.tv/renanenuva

It's not a debug log though -- so can't advise much.

I've replied on your original post, with some instructions on how to try 17.6. I believe there were some improvements to web server lockups in that release.

(2017-11-19, 09:14)Sam.Nazarko Wrote: [ -> ]I think he means:  https://paste.osmc.tv/renanenuva

It's not a debug log though -- so can't advise much.

I've replied on your original post, with some instructions on how to try 17.6. I believe there were some improvements to web server lockups in that release.

Thank you Sam for correcting the link. I copied it without noticing also copying '2' badge. I have updated my first post to contain the right link.

To keep forum threads synced: I will now try 17.6 release as advised and will let you know about the outcome.

The problem is now solved. For anyone else experiencing the issue and stumbling upon this thread, it looks like the newest (January) OSMC update has fixed the issue: https://discourse.osmc.tv/t/remote-contr...11?u=mardu.

Martin