2015-01-25, 14:29
Yesterday I upgraded xbmc to Kodi (2:14.0-1~wheezy) on my Raspberry Pi (running Raspbian). Now I cannot control Kodi anymore using my phone (Nexus 5 running Yatse). The problem seems to be that the necessary servers aren't launched: if I look at what ports my raspi is listening, it's just:
So 9090 is only listening on localhost and nothing is listening on 8080, so there is nothing for Yatse to connect to.
I have edited /home/kodi/.kodi/userdata/guisettings.xml (while Kodi was shut down) so it says:
but no dice (I edited the file, because I cannot control Kodi by keyboard either, although direct keyboard access to the raspi works fine otherwise).
Does anyone know what may be going on and how I can get Kodi to allow json-rpc control from Yatse again? Possibly re-enabling keyboard control so I can change the settings via the Kodi menus may be a way out.
The only WARNINGS in kodi.log are:
Code:
root@pi:/home/kodi/.kodi# netstat -tanp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:9090 0.0.0.0:* LISTEN 6531/kodi.bin
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2668/sshd
tcp 0 288 192.168.1.46:22 192.168.1.53:32965 ESTABLISHED 6441/sshd: pi [privSo 9090 is only listening on localhost and nothing is listening on 8080, so there is nothing for Yatse to connect to.
I have edited /home/kodi/.kodi/userdata/guisettings.xml (while Kodi was shut down) so it says:
Code:
<services>
<airplay default="true">false</airplay>
<airplayios8compat default="true">true</airplayios8compat>
<airplaypassword default="true"></airplaypassword>
<airplayvolumecontrol default="true">true</airplayvolumecontrol>
<devicename default="true">pi</devicename>
<esallinterfaces default="true">true</esallinterfaces>
<escontinuousdelay default="true">25</escontinuousdelay>
<esenabled default="true">true</esenabled>
<esinitialdelay default="true">750</esinitialdelay>
<esmaxclients default="true">20</esmaxclients>
<esport default="true">9777</esport>
<esportrange default="true">10</esportrange>
<upnpannounce default="true">true</upnpannounce>
<upnpcontroller default="true">false</upnpcontroller>
<upnprenderer default="true">false</upnprenderer>
<upnpserver default="true">true</upnpserver>
<useairplaypassword default="true">false</useairplaypassword>
<webserver default="true">true</webserver>
<webserverpassword default="true"></webserverpassword>
<webserverport default="true">8080</webserverport>
<webserverusername default="true">kodi</webserverusername>
<webskin default="true">webinterface.default</webskin>
<zeroconf default="true">true</zeroconf>
</services>but no dice (I edited the file, because I cannot control Kodi by keyboard either, although direct keyboard access to the raspi works fine otherwise).
Does anyone know what may be going on and how I can get Kodi to allow json-rpc control from Yatse again? Possibly re-enabling keyboard control so I can change the settings via the Kodi menus may be a way out.
The only WARNINGS in kodi.log are:
Code:
12:36:09 T:3035607040 NOTICE: start dvd mediatype detection
12:36:09 T:2958181392 NOTICE: Thread DetectDVDMedia start, auto delete: false
12:36:11 T:3035607040 WARNING: JSONRPC: Could not parse type "PVR.Details.Channel"
12:36:11 T:3035607040 WARNING: JSONRPC: Could not parse type "PVR.Details.ChannelGroup.Extended"
12:36:11 T:3035607040 WARNING: JSONRPC: Could not parse type "GUI.Property.Value"
12:36:11 T:3035607040 WARNING: JSONRPC: Could not parse type "Setting.Details.SettingList"
12:36:12 T:2918904848 NOTICE: Thread LanguageInvoker start, auto delete: false
12:36:12 T:3035607040 NOTICE: initialize done