Kodi Mediaserver Support

Calzor Suzay
Posts: 142
Joined: Tuesday 08 July 2014 15:10
Target OS: Raspberry Pi
Domoticz version: 3.9629
Location: UK
Contact:

Re: Kodi Mediaserver Support

Post by Calzor Suzay » Tuesday 24 January 2017 14:23

Should this just 'work' on Kodi 17?
I have a Raspberry Pi running OSMC/Kodi & Domoticz on the same box.

I configured the hardware in Domoticz to use port 9090 but nothing, if I use 8080 I get the usual cycle.
I can confirm the web page is running on 8080 but when I port query 9090 it says not listening .
I've been through the Kodi gui and can't see anything obvious to turn on, do I need put something in the advancedsettings file?

When I set the hardware to 9090 the log shows...
2017-01-24 12:20:39.304 Kodi: (Kodi) Exiting work loop.
2017-01-24 12:20:39.356 Kodi: (Kodi) Removing device.
2017-01-24 12:20:39.857 Kodi: (Kodi) Starting thread.
2017-01-24 12:20:39.958 Kodi: Starting I/O service thread.

then nothing else and in switches it just says Off.

Calzor Suzay
Posts: 142
Joined: Tuesday 08 July 2014 15:10
Target OS: Raspberry Pi
Domoticz version: 3.9629
Location: UK
Contact:

Re: Kodi Mediaserver Support

Post by Calzor Suzay » Tuesday 24 January 2017 14:44

Ok got it working, looked at the kodi wiki http://kodi.wiki/view/JSON-RPC_API and found the line "TCP: In System/Settings/Network/Services activate Allow programs on this system to control Kodi for localhost access only and Allow programs on other systems to control Kodi for access from other computers as well"

As I have a funky skin it was buried in some options but got to it in the end and looks good now :)

Melotron
Posts: 50
Joined: Tuesday 22 November 2016 22:04
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Kodi Mediaserver Support

Post by Melotron » Tuesday 24 January 2017 17:00

@Dnpwwo

I've done that but Kodi are still in ON mode.

Here are the logs from Domoticz :

Code: Select all

2017-01-24 15:42:25.966 Error: Kodi: (Kodi Storarum) Async Read Exception: 125, Operation canceled
2017-01-24 15:42:25.970 Kodi: (Kodi Storarum) Event: 'Off'.
2017-01-24 15:42:26.867 Kodi: (Kodi Storarum) Sending data: '{"jsonrpc":"2.0","method":"JSONRPC.Ping","id":1001}'
2017-01-24 15:42:36.869 Kodi: (Kodi Storarum) Sending data: '{"jsonrpc":"2.0","method":"JSONRPC.Ping","id":1001}'
2017-01-24 15:42:46.871 Kodi: (Kodi Storarum) Missed 1 pings, assumed off.
2017-01-24 15:42:46.878 Kodi: (Kodi Storarum) Event: 'Off'.
2017-01-24 15:42:46.904 Kodi: (Kodi Storarum) Disonnected.
2017-01-24 15:42:47.875 Kodi: (Kodi Storarum) Connected to '192.168.0.126:8080'.
2017-01-24 15:42:47.879 Kodi: Restarting I/O service thread.
2017-01-24 15:42:47.880 Kodi: (Kodi Storarum) Event: 'On'.
2017-01-24 15:42:47.906 Kodi: (Kodi Storarum) Sending data: '{"jsonrpc":"2.0","method":"System.GetProperties","params":{"properties":["canhibernate","cansuspend","canshutdown"]},"id":1007}'
2017-01-24 15:42:48.908 Kodi: (Kodi Storarum) Sending data: '{"jsonrpc":"2.0","method":"JSONRPC.Ping","id":1001}'
2017-01-24 15:42:58.383 Kodi: Restarting I/O service thread.
2017-01-24 15:43:08.912 Kodi: (Kodi Storarum) Missed 1 pings, assumed off.
2017-01-24 15:43:08.917 Kodi: (Kodi Storarum) Event: 'Off'.
2017-01-24 15:43:08.941 Kodi: (Kodi Storarum) Disonnected.
2017-01-24 15:43:09.915 Kodi: (Kodi Storarum) Connected to '192.168.0.126:8080'.
2017-01-24 15:43:09.927 Kodi: (Kodi Storarum) Event: 'On'.
2017-01-24 15:43:09.952 Kodi: (Kodi Storarum) Sending data: '{"jsonrpc":"2.0","method":"System.GetProperties","params":{"properties":["canhibernate","cansuspend","canshutdown"]},"id":1007}'
2017-01-24 15:43:10.953 Kodi: (Kodi Storarum) Sending data: '{"jsonrpc":"2.0","method":"JSONRPC.Ping","id":1001}'
2017-01-24 15:43:19.390 Kodi: Restarting I/O service thread.
2017-01-24 15:43:20.955 Kodi: (Kodi Storarum) Sending data: '{"jsonrpc":"2.0","method":"JSONRPC.Ping","id":1001}'
2017-01-24 15:43:30.958 Kodi: (Kodi Storarum) Missed 1 pings, assumed off.
2017-01-24 15:43:30.963 Kodi: (Kodi Storarum) Event: 'Off'.
2017-01-24 15:43:30.988 Kodi: (Kodi Storarum) Disonnected.
2017-01-24 15:43:31.960 Kodi: (Kodi Storarum) Connected to '192.168.0.126:8080'.
2017-01-24 15:43:31.964 Kodi: (Kodi Storarum) Event: 'On'.
2017-01-24 15:43:31.988 Kodi: (Kodi Storarum) Sending data: '{"jsonrpc":"2.0","method":"System.GetProperties","params":{"properties":["canhibernate","cansuspend","canshutdown"]},"id":1007}'
2017-01-24 15:43:32.989 Kodi: (Kodi Storarum) Sending data: '{"jsonrpc":"2.0","method":"JSONRPC.Ping","id":1001}'
2017-01-24 15:43:40.397 Kodi: Restarting I/O service thread.
2017-01-24 15:43:42.991 Kodi: (Kodi Storarum) Sending data: '{"jsonrpc":"2.0","method":"JSONRPC.Ping","id":1001}'
2017-01-24 15:43:52.994 Kodi: (Kodi Storarum) Missed 1 pings, assumed off.
2017-01-24 15:43:52.999 Kodi: (Kodi Storarum) Event: 'Off'.
2017-01-24 15:43:53.040 Kodi: (Kodi Storarum) Disonnected.
2017-01-24 15:43:53.996 Kodi: (Kodi Storarum) Connected to '192.168.0.126:8080'.
2017-01-24 15:43:54.001 Kodi: (Kodi Storarum) Event: 'On'.
2017-01-24 15:43:54.024 Kodi: (Kodi Storarum) Sending data: '{"jsonrpc":"2.0","method":"System.GetProperties","params":{"properties":["canhibernate","cansuspend","canshutdown"]},"id":1007}'
2017-01-24 15:43:55.025 Kodi: (Kodi Storarum) Sending data: '{"jsonrpc":"2.0","method":"JSONRPC.Ping","id":1001}'
2017-01-24 15:44:01.404 Kodi: Restarting I/O service thread.
On the error tab so do I have the following error :

Code: Select all

2017-01-24 15:42:25.966 Error: Kodi: (Kodi Storarum) Async Read Exception: 125, Operation canceled
My Kodi player are an Android box RK3229 if that's whats causing it to not being able to talk with it.

//Magnus

User avatar
sincze
Posts: 977
Joined: Monday 02 June 2014 22:46
Target OS: Raspberry Pi
Domoticz version: 4.9700
Location: Netherlands
Contact:

Re: Kodi Mediaserver Support

Post by sincze » Tuesday 24 January 2017 21:16

I had to add the following line to the advancedsettings.xml to get it working.

Code: Select all

<advancedsettings>
  <jsonrpc>
    <tcpport>9090</tcpport>
  </jsonrpc>
</advancedsettings>
Using Pass2php since 2016-12
LAN: RFLink, P1-Port, OTGW, MySensors
USB: RFXCom, ZWave
WIFI: Mi-light Wifi-Bridge, Sonoff, ESP8266, Xiaomi Gateway
Solar: Omnik Inverter, PVOutput
Video: Kodi clients with Harmony HUB
Sensors: You name it I probably got 1.

User avatar
Dnpwwo
Posts: 749
Joined: Sunday 23 March 2014 10:00
Target OS: Raspberry Pi
Domoticz version: Beta
Location: Melbourne, Australia
Contact:

Re: Kodi Mediaserver Support

Post by Dnpwwo » Tuesday 24 January 2017 22:24

@Melotron,

This line in the log shows that you are still telling Domoticz to use the Kodi web server which is why you are getting the same result:

Code: Select all

2017-01-24 15:42:47.875 Kodi: (Kodi Storarum) Connected to '192.168.0.126:8080'.
you need to set it up as shown here: http://www.domoticz.com/wiki/Kodi#Kodi_in_Domoticz so that the log line shows 9090. There are also links to the Kodi website showing the settings for that end as well.
The reasonable man adapts himself to the world; the unreasonable one persists to adapt the world to himself. Therefore all progress depends on the unreasonable man. George Bernard Shaw

pvklink
Posts: 111
Joined: Wednesday 12 November 2014 16:01
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Kodi Mediaserver Support

Post by pvklink » Tuesday 24 January 2017 23:43

Hi, i added my raspberry libreelec kodi device with ip and port with no username pwd.
It seems to be recognize in the log:
2017-01-24 22:32:44.046 Kodi: (Kodiserver) Connected to '192.168.178.18:8080'.
2017-01-24 22:32:44.050 Kodi: (Kodiserver) Event: 'On'.

And there is one an extra switch added...
In the devices tab i see an lightning2 device with hardware=kodi

When i push the switch i get: Fout bij verzenden van schakelaar opdracht, controleer apparaat/hardware!

i am missing something

pvklink
Posts: 111
Joined: Wednesday 12 November 2014 16:01
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Kodi Mediaserver Support

Post by pvklink » Wednesday 25 January 2017 0:23

It works, i changed the domoticz kodi device to 9090.
Strange my kodi webserver uses port 8080

Melotron
Posts: 50
Joined: Tuesday 22 November 2016 22:04
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Kodi Mediaserver Support

Post by Melotron » Wednesday 25 January 2017 12:34

@Dnpwwo
I've tryed that but it gives me the following line in the log :

Code: Select all

2017-01-25 11:21:00.439 Error: Kodi: (Kodi Storarum) Async Read Exception: 125, Operation canceled
2017-01-25 11:21:00.443 Kodi: (Kodi Storarum) Event: 'Off'.
Edit : Forgot to add the spam from my log with -9090 in the settings.

Code: Select all

2017-01-25 13:12:02.649 Kodi: (Kodi Storarum) Connect to '192.168.0.126:9090' failed: (111) Connection refused

@sincze
I've tried that file too. But it's giving me the old error in the log file.
It feels as whatever I'am trying so won't Kodi allow anny communications with anything.
I'am suspecting that it's the box that aren't allowing Kodi to talk to any programs.

Edit : I'm going to put the advancedsettings.xml file back when I get home and see what happens then.
As it looks as the port aren't open at all.
Scanned port 1 to 9999 and its only port 8080 in the upper that's open.

//Magnus

jake
Posts: 459
Joined: Saturday 30 May 2015 22:40
Target OS: Raspberry Pi
Domoticz version: beta
Contact:

Re: Kodi Mediaserver Support

Post by jake » Wednesday 25 January 2017 17:09

Dnpwwo wrote:@jake,

Can you turn debug on in the Hardware page and reproduce these? If you post the logging output I maybe able to work out the issue.
Unfortunately, now also with the 1.00 the log started to give errors, even without touching anything (debug on):

Code: Select all

2017-01-25 16:04:08.926 (Kodi Woonkamer) initialized
2017-01-25 16:04:08.931 (Kodi Woonkamer) Debug log level set to: 'true'.
2017-01-25 16:04:08.931 (Kodi Woonkamer) 'Mode2':'Ignore'
2017-01-25 16:04:08.932 (Kodi Woonkamer) 'Key':'Kodi'
2017-01-25 16:04:08.932 (Kodi Woonkamer) 'Address':'192.168.1.31'
2017-01-25 16:04:08.932 (Kodi Woonkamer) 'HardwareID':'16'
2017-01-25 16:04:08.933 (Kodi Woonkamer) 'Name':'Kodi Woonkamer'
2017-01-25 16:04:08.933 (Kodi Woonkamer) 'Port':'9090'
2017-01-25 16:04:08.933 (Kodi Woonkamer) 'Mode3':'False'
2017-01-25 16:04:08.934 (Kodi Woonkamer) 'Mode6':'Debug'
2017-01-25 16:04:08.934 (Kodi Woonkamer) Device count: 4
2017-01-25 16:04:08.934 (Kodi Woonkamer) Device: 1 - ID: 146, Name: 'Kodi Woonkamer - Status', nValue: 0, sValue: ''
2017-01-25 16:04:08.935 (Kodi Woonkamer) Device ID: '146'
2017-01-25 16:04:08.935 (Kodi Woonkamer) Device Name: 'Kodi Woonkamer - Status'
2017-01-25 16:04:08.935 (Kodi Woonkamer) Device nValue: 0
2017-01-25 16:04:08.936 (Kodi Woonkamer) Device sValue: ''
2017-01-25 16:04:08.936 (Kodi Woonkamer) Device LastLevel: 0
2017-01-25 16:04:08.936 (Kodi Woonkamer) Device: 2 - ID: 147, Name: 'Kodi Woonkamer - Source', nValue: 0, sValue: '10'
2017-01-25 16:04:08.936 (Kodi Woonkamer) Device ID: '147'
2017-01-25 16:04:08.937 (Kodi Woonkamer) Device Name: 'Kodi Woonkamer - Source'
2017-01-25 16:04:08.937 (Kodi Woonkamer) Device nValue: 0
2017-01-25 16:04:08.937 (Kodi Woonkamer) Device sValue: '10'
2017-01-25 16:04:08.938 (Kodi Woonkamer) Device LastLevel: 0
2017-01-25 16:04:08.938 (Kodi Woonkamer) Device: 3 - ID: 148, Name: 'Kodi Woonkamer - Volume', nValue: 0, sValue: '100'
2017-01-25 16:04:08.939 (Kodi Woonkamer) Device ID: '148'
2017-01-25 16:04:08.939 (Kodi Woonkamer) Device Name: 'Kodi Woonkamer - Volume'
2017-01-25 16:04:08.939 (Kodi Woonkamer) Device nValue: 0
2017-01-25 16:04:08.940 (Kodi Woonkamer) Device sValue: '100'
2017-01-25 16:04:08.940 (Kodi Woonkamer) Device LastLevel: 100
2017-01-25 16:04:08.940 (Kodi Woonkamer) Device: 4 - ID: 149, Name: 'Kodi Woonkamer - Playing', nValue: 0, sValue: '0'
2017-01-25 16:04:08.941 (Kodi Woonkamer) Device ID: '149'
2017-01-25 16:04:08.941 (Kodi Woonkamer) Device Name: 'Kodi Woonkamer - Playing'
2017-01-25 16:04:08.941 (Kodi Woonkamer) Device nValue: 0
2017-01-25 16:04:08.941 (Kodi Woonkamer) Device sValue: '0'
2017-01-25 16:04:08.942 (Kodi Woonkamer) Device LastLevel: 95
2017-01-25 16:04:08.942 (Kodi Woonkamer) Transport set to: 'TCP/IP', 192.168.1.31:9090.
2017-01-25 16:04:08.942 (Kodi Woonkamer) Protocol set to: 'JSON'.
2017-01-25 16:04:08.943 (Kodi Woonkamer) Heartbeat interval set to: 10.
2017-01-25 16:04:08.944 PluginSystem: Starting I/O service thread.
2017-01-25 16:04:08.944 (Kodi Woonkamer) Connect directive received, transport connect initiated successfully.
2017-01-25 16:04:08.995 (Kodi Woonkamer) Calling message handler 'onConnect'.
2017-01-25 16:04:08.995 (Kodi Woonkamer) Connected successfully to: 192.168.1.31:9090
2017-01-25 16:04:08.996 (Kodi Woonkamer) Sending data: '{"jsonrpc":"2.0","method":"System.GetProperties","params":{"properties":["canhibernate","cansuspend","canshutdown"]},"id":1007}'.
2017-01-25 16:04:08.996 (Kodi Woonkamer) Sending data: '{"jsonrpc":"2.0","method":"Application.GetProperties","id":1011,"params":{"properties":["volume","muted"]}}'.
2017-01-25 16:04:08.997 (Kodi Woonkamer) Sending data: '{"jsonrpc":"2.0","method":"Player.GetActivePlayers","id":1001}'.
2017-01-25 16:04:09.049 (Kodi Woonkamer) Calling message handler 'onMessage'.
2017-01-25 16:04:09.049 Error: (Kodi Woonkamer) 'onMessage' failed 'TypeError':'onMessage() takes 1 positional argument but 3 were given'.
2017-01-25 16:04:09.049 (Kodi Woonkamer) Calling message handler 'onMessage'.
2017-01-25 16:04:09.050 Error: (Kodi Woonkamer) 'onMessage' failed 'TypeError':'onMessage() takes 1 positional argument but 3 were given'.
2017-01-25 16:04:09.050 (Kodi Woonkamer) Calling message handler 'onMessage'.
2017-01-25 16:04:09.050 Error: (Kodi Woonkamer) 'onMessage' failed 'TypeError':'onMessage() takes 1 positional argument but 3 were given'.
2017-01-25 16:04:16.321 (P1 Smart Meter) P1 Smart Meter (Electricity)
2017-01-25 16:04:18.481 (Kodi Woonkamer) Calling message handler 'onHeartbeat'.
2017-01-25 16:04:18.482 (Kodi Woonkamer) Sending data: '{"jsonrpc":"2.0","method":"Player.GetActivePlayers","id":1001}'.
2017-01-25 16:04:18.532 (Kodi Woonkamer) Calling message handler 'onMessage'.
2017-01-25 16:04:18.533 Error: (Kodi Woonkamer) 'onMessage' failed 'TypeError':'onMessage() takes 1 positional argument but 3 were given

krizzz
Posts: 171
Joined: Wednesday 20 November 2013 21:36
Target OS: Linux
Domoticz version:
Location: The Netherlands
Contact:

Re: Kodi Mediaserver Support

Post by krizzz » Thursday 26 January 2017 0:05

Just posting this for the guys out there with an Openelec installation and trying to add there Openelec setup to Kodi.

I can confirm that i am using the internal Kodi webserver (to be handled through Kodi self settings>>services>>webserver) on port 80 and I removed the standard username. So the field for username and password are empty.

In Domoticz self, i added the Pi with Openelec to the hardware section. And added the Pi to the "kodi"hardware section. It connects with port 9090.

This did not yet work within Kodi, i kept getting "could not connect"messages. There was 1 step extra to do before connecting properly. I added the advancedsettings.xml to the Openelec/Kodi pi within the folder .kodi/userdata/ with the following code included. And voila, it worked!

Code: Select all

<advancedsettings>
  <jsonrpc>
    <tcpport>9090</tcpport>
  </jsonrpc>
</advancedsettings>

Calzor Suzay
Posts: 142
Joined: Tuesday 08 July 2014 15:10
Target OS: Raspberry Pi
Domoticz version: 3.9629
Location: UK
Contact:

Re: Kodi Mediaserver Support

Post by Calzor Suzay » Saturday 28 January 2017 21:03

Out of interest is there a way to not make it a 'switch' as I added it to a floorplan you can click it and it'll turn off Kodi aka shut down my Raspberry Pi with Domoticz on it! :)

jake
Posts: 459
Joined: Saturday 30 May 2015 22:40
Target OS: Raspberry Pi
Domoticz version: beta
Contact:

Re: RE: Re: Kodi Mediaserver Support

Post by jake » Saturday 28 January 2017 21:44

Calzor Suzay wrote:Out of interest is there a way to not make it a 'switch' as I added it to a floorplan you can click it and it'll turn off Kodi aka shut down my Raspberry Pi with Domoticz on it! :)
I have protected the switch. An effective way to prevent accidental shutdown.

Calzor Suzay
Posts: 142
Joined: Tuesday 08 July 2014 15:10
Target OS: Raspberry Pi
Domoticz version: 3.9629
Location: UK
Contact:

Re: RE: Re: Kodi Mediaserver Support

Post by Calzor Suzay » Sunday 29 January 2017 2:10

jake wrote:I have protected the switch. An effective way to prevent accidental shutdown.
Didn't even know what that was for till now :)

User avatar
Dnpwwo
Posts: 749
Joined: Sunday 23 March 2014 10:00
Target OS: Raspberry Pi
Domoticz version: Beta
Location: Melbourne, Australia
Contact:

Re: Kodi Mediaserver Support

Post by Dnpwwo » Sunday 29 January 2017 3:04

@jake,

There is an updated version of the Python plugin here: http://www.domoticz.com/forum/viewtopic ... 51#p116951.

Should fix your problem, add support for the media remote and might make the mute issues better.

You need to be on the latest beta to get all those things though.
The reasonable man adapts himself to the world; the unreasonable one persists to adapt the world to himself. Therefore all progress depends on the unreasonable man. George Bernard Shaw

jake
Posts: 459
Joined: Saturday 30 May 2015 22:40
Target OS: Raspberry Pi
Domoticz version: beta
Contact:

Re: RE: Re: Kodi Mediaserver Support

Post by jake » Monday 30 January 2017 23:01

Dnpwwo wrote:@jake,

There is an updated version of the Python plugin here: http://www.domoticz.com/forum/viewtopic ... 51#p116951.

Should fix your problem, add support for the media remote and might make the mute issues better.

You need to be on the latest beta to get all those things though.
Thanks for working on it. I gave it a try:

Stop the 'Kodi Media Center' by disabling it.
Stop Domoticz service
remove the __pycache__ folder in the kodi plugin folder (as I saw in the plugin beta forum)
replace the plugin.py file (the line 79 is matching the one you mentioned in the plugin beta forum as well)
restart Domoticz service
in the browser go to hardware
enable the Kodi Players.... all hardware gone and domoticz went offline
Restarted the Domoticz service and everything was up and running again. pfew

The folder __pychache__ is automatically recreated again.

Kodi plugin works as it did when I started with the 1.00 beta (might have to do with the mentioned __pycache__ file)
Still the menu buttons are funny:
Click on Domoticz button -> Happens in Kodi:
Video -> Music menu
Music -> Video menu
TV Shows -> Video menu
Live TV -> Pictures menu

The Domoticz 'Kodi Source' buttons don't take Kodi out of the screen saver mode, when it is enabled.
When Kodi moves to the next song, the Source jumped to 'Music' so that was fine. It seems to be one way, kind of.

When I click on the loudspeaker, the sounds mutes, as expected, but the volume slider stays at original 'loundess' and icons stay in same color, therefore no indication of 'mute'. I can't get it out of 'mute' with the loudspeaker icon, but I can with changing the volume level slider the one or other way.

Trigun
Posts: 187
Joined: Wednesday 30 November 2016 12:58
Target OS: Raspberry Pi
Domoticz version: 4.9700
Contact:

Re: Kodi Mediaserver Support

Post by Trigun » Friday 03 February 2017 22:41

jake wrote:Thanks, you're welcome. This finally was within my scope of reach, so, happy to help :)
Hi Jake,

I've been using the script a while now but at some point it seems to stop my kodi device while it is playing.
could it be that there might be a mistake in the script compilation.
with my limited knowledge line 23 might give issues.

is there chance you can help me out here?

Thanks for you help!

jake
Posts: 459
Joined: Saturday 30 May 2015 22:40
Target OS: Raspberry Pi
Domoticz version: beta
Contact:

Re: Kodi Mediaserver Support

Post by jake » Monday 06 February 2017 23:09

Trigun wrote:
jake wrote:Thanks, you're welcome. This finally was within my scope of reach, so, happy to help :)
Hi Jake,

I've been using the script a while now but at some point it seems to stop my kodi device while it is playing.
could it be that there might be a mistake in the script compilation.
with my limited knowledge line 23 might give issues.

is there chance you can help me out here?

Thanks for you help!
Can you make a match in your log's of the selector switch and the Kodi switch to see at what point in time it happened? Could it be that the Kodi switch changes it's status at that time?

User avatar
gielie
Posts: 225
Joined: Tuesday 12 January 2016 12:40
Target OS: Raspberry Pi
Domoticz version: latest β
Location: The Netherlands (Alkmaar)
Contact:

Re: Kodi Mediaserver Support

Post by gielie » Tuesday 07 February 2017 23:31

I've always used Kodi within Domoticz without any problems but now it doesn't work anymore.

Code: Select all

2017-02-07 22:28:15.286 Kodi: (Huiskamer) Missed 1 pings, assumed off.
2017-02-07 22:28:15.288 Kodi: (Huiskamer) Event: 'Off'.
2017-02-07 22:28:15.304 Kodi: (Huiskamer) Disonnected.
2017-02-07 22:28:16.287 Kodi: (Huiskamer) Connected to '192.168.1.115:8080'.
2017-02-07 22:28:16.289 Kodi: (Huiskamer) Event: 'On'.
2017-02-07 22:28:16.306 Kodi: (Huiskamer) Sending data: '{"jsonrpc":"2.0","method":"System.GetProperties","params":{"properties":["canhibernate","cansuspend","canshutdown"]},"id":1007}'
2017-02-07 22:28:17.306 Kodi: (Huiskamer) Sending data: '{"jsonrpc":"2.0","method":"JSONRPC.Ping","id":1001}'
2017-02-07 22:28:19.861 Kodi: Restarting I/O service thread.
I've seen a lot of people with this problem but no solutions so far, anyone else with a bright idea?
- Vision ZU1401 USB Stick
- Aeotec MultiSensor 6
- FIBARO FGS222
- FIBARO FGWPE Wall Plug
- Everspring AN157
- Neo CoolCam Power plug
- Neo CoolCam PIR Sensor
- Popp Smoke Detector
- Toon
- Kodi Media Server

markjgabb
Posts: 128
Joined: Wednesday 25 January 2017 0:00
Target OS: Raspberry Pi
Domoticz version: 3.8153
Location: Australia
Contact:

Re: Kodi Mediaserver Support

Post by markjgabb » Wednesday 08 February 2017 0:13

giele, what platform are you using your kodi on?
V 3.8153 RPI 3
RFlink 334 mhz
mysensors
broadlink
wemo

User avatar
gielie
Posts: 225
Joined: Tuesday 12 January 2016 12:40
Target OS: Raspberry Pi
Domoticz version: latest β
Location: The Netherlands (Alkmaar)
Contact:

Re: Kodi Mediaserver Support

Post by gielie » Wednesday 08 February 2017 9:11

markjgabb wrote:giele, what platform are you using your kodi on?
Raspberry pi 2 with libreelec, latest stable version.
- Vision ZU1401 USB Stick
- Aeotec MultiSensor 6
- FIBARO FGS222
- FIBARO FGWPE Wall Plug
- Everspring AN157
- Neo CoolCam Power plug
- Neo CoolCam PIR Sensor
- Popp Smoke Detector
- Toon
- Kodi Media Server

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest