Python plugin: Kodi

[Dnpwwo]

Thread for all things related to the Python Kodi plugin.

Latest full versions is available here: https://github.com/dnpwwo/Domoticz-Kodi-Plugin

Latest Update: 2.6.4 - August 26th, 2018

• Handles Domoticz returning structured JSON messages

Update: v2.4.2 - February 22nd, 2018

• Bug fix: Changed handling for Play and Pause commands from scripts,
• Added initial Description that will appear in Hardware page

Update: v2.3.11 - February 17th, 2018

• Added Blockly support,
• Uplift error response handling
• Added 'Rewind' command

Update: v2.2.1 - February 11th, 2018

• Activates the screensaver using the proper "ActivateScreensaver" function via the UDP interface

Previous Update: v2.0.6 - December 12th, 2017

• Optionally highlights devices that can not be found on the network (red banner in web UI)
• Supports screensaver events (Kodi 17+) and shows Kodi as 'Sleeping' when screensaver is on

[zak45]

still not able to have it running in Windows.
I'm running on version 3.6591, python 3.5.3 (x86)
Got this error :

2017-02-04 00:42:00.091 (kodic) Initialized version 1.2.0, author 'dnpwwo'
2017-02-04 00:42:00.133 (kodic) Devices created.
2017-02-04 00:42:00.134 PluginSystem: Starting I/O service thread.
2017-02-04 00:42:00.185 Error: (kodic) 'onConnect' failed 'TypeError':'onConnect() missing 2 required positional arguments: 'Status' and 'Description''.
2017-02-04 00:42:05.030 (RFX433E) Energy (Compteur EDF)
2017-02-04 00:42:11.652 (RFX433E) Temp + Humidity (433-TempExt)
2017-02-04 00:42:14.929 (RFX433E) Temp + Humidity (433-TempSalon)
2017-02-04 00:42:19.344 (RFX433E) Temp + Humidity (433-TempSDBE)
2017-02-04 00:42:29.434 (RFX433E) Temp + Humidity (433-TempSDB)
2017-02-04 00:42:29.662 Error: PyDomoticz_Connect, connection request from 'kodic' ignored. Transport is already connected.
2017-02-04 00:42:50.641 (RFX433E) Temp + Humidity (433-TempExt)

[Dnpwwo]

@zak45,

Can you run the plugin in Debug mode and post the initial log. A recent beta added some logging that might help.

2017-02-04 09:49:04.525 (Test Kodi) Initialized version 1.2.0, author 'dnpwwo'
2017-02-04 09:49:04.529 (Test Kodi) Debug log level set to: 'true'.
2017-02-04 09:49:04.529 (Test Kodi) 'Port':'9090'
2017-02-04 09:49:04.530 (Test Kodi) 'Mode2':'Ignore'
2017-02-04 09:49:04.530 (Test Kodi) 'Address':'192.168.xxx.xxx'
2017-02-04 09:49:04.530 (Test Kodi) 'Version':'1.2.0'
2017-02-04 09:49:04.530 (Test Kodi) 'Author':'dnpwwo'
2017-02-04 09:49:04.530 (Test Kodi) 'Mode6':'Debug'
2017-02-04 09:49:04.530 (Test Kodi) 'HardwareID':'5'
2017-02-04 09:49:04.530 (Test Kodi) 'Mode3':'False'
2017-02-04 09:49:04.530 (Test Kodi) 'Key':'Kodi'
2017-02-04 09:49:04.531 (Test Kodi) 'HomeFolder':'plugins\Kodi\'
2017-02-04 09:49:04.531 (Test Kodi) 'Name':'Test Kodi'

Make sure that the HomeFolder setting matches where you think the plugin should be loading from.

This setting shows the folder name that is added to the start of the Python path list for the specific plugin immediately prior to the import and is the most reliable indication of where Python picked up the file.

[zak45]

Thanks Dnpwwo

here is the logfile output :

Spoiler: show

2017-02-04 10:55:15.115 (RFX433E) Temp + Humidity (433-TempSDBE)
2017-02-04 10:55:16.934 (kodic) Initialized version 1.2.0, author 'dnpwwo'
2017-02-04 10:55:16.935 (kodic) Debug log level set to: 'true'.
2017-02-04 10:55:16.935 (kodic) Creating device 'Status'.
2017-02-04 10:55:16.944 (kodic) Creating device 'Source'.
2017-02-04 10:55:16.955 (kodic) Creating device 'Volume'.
2017-02-04 10:55:16.964 (kodic) Creating device 'Playing'.
2017-02-04 10:55:16.974 (kodic) Devices created.
2017-02-04 10:55:16.975 (kodic) 'HomeFolder':'C:\Program Files (x86)\Domoticz\plugins\Kodi\'
2017-02-04 10:55:16.975 (kodic) 'HardwareID':'11'
2017-02-04 10:55:16.975 (kodic) 'Author':'dnpwwo'
2017-02-04 10:55:16.975 (kodic) 'Key':'Kodi'
2017-02-04 10:55:16.975 (kodic) 'Mode6':'Debug'
2017-02-04 10:55:16.975 (kodic) 'Port':'9090'
2017-02-04 10:55:16.975 (kodic) 'Address':'127.0.0.1'
2017-02-04 10:55:16.975 (kodic) 'Mode3':'False'
2017-02-04 10:55:16.975 (kodic) 'Name':'kodic'
2017-02-04 10:55:16.975 (kodic) 'Mode2':'Ignore'
2017-02-04 10:55:16.975 (kodic) 'Version':'1.2.0'
2017-02-04 10:55:16.975 (kodic) Device count: 4
2017-02-04 10:55:16.975 (kodic) Device: 1 - ID: 641, Name: 'kodic - Status', nValue: 0, sValue: ''
2017-02-04 10:55:16.975 (kodic) Device ID: '641'
2017-02-04 10:55:16.975 (kodic) Device Name: 'kodic - Status'
2017-02-04 10:55:16.975 (kodic) Device nValue: 0
2017-02-04 10:55:16.975 (kodic) Device sValue: ''
2017-02-04 10:55:16.975 (kodic) Device LastLevel: 0
2017-02-04 10:55:16.975 (kodic) Device: 2 - ID: 642, Name: 'kodic - Source', nValue: 0, sValue: ''
2017-02-04 10:55:16.975 (kodic) Device ID: '642'
2017-02-04 10:55:16.975 (kodic) Device Name: 'kodic - Source'
2017-02-04 10:55:16.975 (kodic) Device nValue: 0
2017-02-04 10:55:16.975 (kodic) Device sValue: ''
2017-02-04 10:55:16.975 (kodic) Device LastLevel: 0
2017-02-04 10:55:16.975 (kodic) Device: 3 - ID: 643, Name: 'kodic - Volume', nValue: 0, sValue: ''
2017-02-04 10:55:16.975 (kodic) Device ID: '643'
2017-02-04 10:55:16.976 (kodic) Device Name: 'kodic - Volume'
2017-02-04 10:55:16.976 (kodic) Device nValue: 0
2017-02-04 10:55:16.976 (kodic) Device sValue: ''
2017-02-04 10:55:16.976 (kodic) Device LastLevel: 0
2017-02-04 10:55:16.976 (kodic) Device: 4 - ID: 644, Name: 'kodic - Playing', nValue: 0, sValue: ''
2017-02-04 10:55:16.976 (kodic) Device ID: '644'
2017-02-04 10:55:16.976 (kodic) Device Name: 'kodic - Playing'
2017-02-04 10:55:16.976 (kodic) Device nValue: 0
2017-02-04 10:55:16.976 (kodic) Device sValue: ''
2017-02-04 10:55:16.976 (kodic) Device LastLevel: 0
2017-02-04 10:55:16.976 (kodic) Transport set to: 'TCP/IP', 127.0.0.1:9090.
2017-02-04 10:55:16.976 (kodic) Protocol set to: 'JSON'.
2017-02-04 10:55:16.976 (kodic) Heartbeat interval set to: 10.
2017-02-04 10:55:16.976 PluginSystem: Starting I/O service thread.
2017-02-04 10:55:16.976 (kodic) Connect directive received, transport connect initiated successfully.
2017-02-04 10:55:17.987 (kodic) Calling message handler 'onConnect'.
2017-02-04 10:55:17.987 Error: (kodic) 'onConnect' failed 'TypeError':'onConnect() missing 2 required positional arguments: 'Status' and 'Description''.
2017-02-04 10:55:23.831 (AeonStick) Lux (Z-WCLux)
2017-02-04 10:55:26.492 (kodic) Calling message handler 'onHeartbeat'.
2017-02-04 10:55:36.484 (kodic) Calling message handler 'onHeartbeat'.
2017-02-04 10:55:46.495 (kodic) Calling message handler 'onHeartbeat'.
2017-02-04 10:55:46.495 PluginSystem: Starting I/O service thread.
2017-02-04 10:55:46.495 (kodic) Connect directive received, transport connect initiated successfully.
2017-02-04 10:55:47.308 (RFX433E) Temp + Humidity (433-TempExt)
2017-02-04 10:55:47.500 (kodic) Calling message handler 'onConnect'.
2017-02-04 10:55:47.500 Error: (kodic) 'onConnect' failed 'TypeError':'onConnect() missing 2 required positional arguments: 'Status' and 'Description''.
2017-02-04 10:55:51.482 (RFX433E) Temp + Humidity (433-TempSalon)
2017-02-04 10:55:54.106 (RFX433E) Temp + Humidity (433-TempSDBE)
2017-02-04 10:55:55.576 (RFX433E) Temp + Humidity (433-TempSDB)
2017-02-04 10:55:56.505 (kodic) Calling message handler 'onHeartbeat'.
2017-02-04 10:56:04.084 (RFX433E) Energy (Compteur EDF)
2017-02-04 10:56:06.496 (kodic) Calling message handler 'onHeartbeat'.
2017-02-04 10:56:16.545 (kodic) Calling message handler 'onHeartbeat'.
2017-02-04 10:56:16.545 PluginSystem: Starting I/O service thread.
2017-02-04 10:56:16.545 (kodic) Connect directive received, transport connect initiated successfully.
2017-02-04 10:56:17.552 (kodic) Calling message handler 'onConnect'.
2017-02-04 10:56:17.552 Error: (kodic) 'onConnect' failed 'TypeError':'onConnect() missing 2 required positional arguments: 'Status' and 'Description''.
2017-02-04 10:56:26.315 (RFX433E) Temp + Humidity (433-TempExt)
2017-02-04 10:56:26.557 (kodic) Calling message handler 'onHeartbeat'.

Home folder is on the right place, version is the right one.
Just FYI: I do not compile Domoticz myself, I take the one from the Web download section.

Will be very nice to have it running. This version have all missing part for me from the built-in one.!!
If you need more test/debug, will be happy to try to help.

[jake]

I posted my test results originally in the Kodi Mediaserver Support topic, but it is better in place in this topic:

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.

[zak45]

Have tried the Yamaha plugin and got same error:

2017-02-07 21:28:43.249 (test) Initialized version 1.0.0, author 'thomasvillagers'
2017-02-07 21:28:43.300 (test) Debug log level set to: 'true'.
2017-02-07 21:28:43.300 (test) onStart called
2017-02-07 21:28:43.300 (test) Creating device 'Status'.
2017-02-07 21:28:43.311 (test) Creating device 'Volume'.
2017-02-07 21:28:43.320 (test) Creating device 'Source'.
2017-02-07 21:28:43.330 (test) Transport set to: 'TCP/IP', 127.0.0.1:50000.
2017-02-07 21:28:43.330 (test) Protocol set to: 'Line'.
2017-02-07 21:28:43.331 PluginSystem: Starting I/O service thread.
2017-02-07 21:28:43.331 (test) Connect directive received, transport connect initiated successfully.
2017-02-07 21:28:43.331 (test) Heartbeat interval set to: 20.
2017-02-07 21:28:44.340 (test) Calling message handler 'onConnect'.
2017-02-07 21:28:44.340 Error: (test) 'onConnect' failed 'TypeError':'onConnect() missing 2 required positional arguments: 'Status' and 'Description''.
2017-02-07 21:28:52.774 (test) Calling message handler 'onHeartbeat'.
2017-02-07 21:28:52.774 (test) onHeartbeat called. Connected: True
2017-02-07 21:28:52.774 Error: (test) Transport is not connected, write directive ignored.


So my problem is not related to Kodi plugin but to my python installation/settings.
Will switch back to the general thread
this is just FYI.

[jake]

Is it possible to have an additional status for Kodi? I have domoticz turning off my monitor after 5 minutes of kodi in status 'on'. However, sometimes I am playing with the interface while the screen turns off. Therefore it would be nice to have the status 'sleep' or 'doze' or whatever to indicate that the screensaver is active and nobody is using kodi.

[jake]

I see quite repetitive the following error in the log:

Code: Select all

2017-03-13 18:43:37.751 Error: (Kodi Woonkamer) 'onNotification' failed 'TypeError':'onNotification() takes 1 positional argument but 7 were given'.

2017-03-13 18:43:39.672 Error: (Kodi Woonkamer) 'onNotification' failed 'TypeError':'onNotification() takes 1 positional argument but 7 were given

Is there a planning to improve the kodi python plugin? Or was it just a proof of concept?

[Dnpwwo]

@jake,

I am planning on uplifting it again, just working on my amplifier plugin at the moment

[jake]

Thanks, good to hear it is not dead!

[Dnpwwo]

Updated version of the plugin, functionally similar but updated to remove onNotification error in log.

You can now choose from 3 custom icon sets from a drop down in the Hardware page.

Kodi 1.5.2.rar

(33.29 KiB) Downloaded 186 times

EDIT: You need to be on the latest beta to run this on a Raspberry Pi

[zak45]

Cool, thanks.
Will give it a try...

[jake]

I updated yesterday:
Copy paste files from the rar in the plugin/kodi folder
Disable / enable 'kodi players' in 'hardware'

Result: it knocked out Domoticz completely: all hardware and devices were gone. Luckily a restart of the service fixed it.

Today I tried the new feature of different icons: I chose the 'black' one. After 'update' of the hardware, I rightaway got a message 'error adding hardware' in a red window and white text. All hardware and devices were gone again. A reset fixed it and it shows then black icons now as well.

So far I didn't see the 'notification errors' in the log anymore, so thanks for that! If only you could fix the brutal results of changing/enabling the kodi players 'hardware' in the 'hardware' page, it scares the crap out of me, because only afterwards I think 'oops, should have made a copy of the domoticz.db file before I try somehing new'. Luckily everything is sill OK.

[Dnpwwo]

@jake,

Can you give this another try with the latest beta? Just go into the hardware page, select a Kodi and hit 'Update', that will force an unload/reload.

I added some handling to make the disconnection more graceful and it seems to work fine on my RPi B+ running Jessie.

Spoiler: show

2017-04-11 19:49:55.211 (Retreat Kodi) Device has disconnected
2017-04-11 19:50:05.290 (Retreat Kodi) Connected successfully to: 192.168.xxx.xxx:9090
2017-04-11 19:50:16.926 (Lounge Kodi) Exiting work loop...
2017-04-11 19:50:17.881 PyDomoticz_Send, send request from 'Lounge Kodi' ignored. Plugin is stopping.
2017-04-11 19:50:17.889 (Lounge Kodi) Device has disconnected
2017-04-11 19:50:17.894 (Lounge Kodi) onStop called
2017-04-11 19:50:18.221 (Lounge Kodi) Stopped.
2017-04-11 19:50:20.643 (Lounge Kodi) Initialized version 1.5.2, author 'dnpwwo'
2017-04-11 19:50:20.850 (Lounge Kodi) Connected successfully to: 192.168.xxx.xxx:9090
2017-04-11 19:50:21.375 (Lounge Kodi) Update 2:'100' (Lounge Kodi - Volume)
2017-04-11 19:51:25.575 (Retreat Kodi) Device has disconnected
2017-04-11 19:51:35.600 (Retreat Kodi) Connected successfully to: 192.168.xxx.xxx:9090
2017-04-11 19:51:44.358 (Family Kodi) Device has disconnected
2017-04-11 19:51:44.368 (Family Kodi) onStop called
2017-04-11 19:51:44.745 (Family Kodi) Exiting work loop...
2017-04-11 19:51:44.753 (Family Kodi) Stopped.
2017-04-11 19:51:45.690 (Family Kodi) Initialized version 1.5.2, author 'dnpwwo'
2017-04-11 19:51:45.841 (Family Kodi) Connected successfully to: 192.168.xxx.xxx:9090
2017-04-11 19:51:46.085 (Family Kodi) Update 2:'83' (Family Kodi - Volume)
2017-04-11 19:52:12.897 (Retreat Kodi) Device has disconnected
2017-04-11 19:52:12.905 (Retreat Kodi) onStop called
2017-04-11 19:52:13.070 (Retreat Kodi) Exiting work loop...
2017-04-11 19:52:13.410 (Retreat Kodi) Stopped.
2017-04-11 19:52:14.504 (Retreat Kodi) Initialized version 1.5.2, author 'dnpwwo'
2017-04-11 19:52:14.621 (Retreat Kodi) Connected successfully to: 192.168.xxx.xxx:9090
2017-04-11 19:53:34.156 (Retreat Kodi) Device has disconnected
2017-04-11 19:53:44.205 (Retreat Kodi) Connected successfully to: 192.168.xxx.xxx:9090
2017-04-11 19:55:04.261 (Retreat Kodi) Device has disconnected
2017-04-11 19:55:14.367 (Retreat Kodi) Connected successfully to: 192.168.xxx.xxx:9090

[jake]

@jake,

Can you give this another try with the latest beta? Just go into the hardware page, select a Kodi and hit 'Update', that will force an unload/reload.

I added some handling to make the disconnection more graceful and it seems to work fine on my RPi B+ running Jessie.

Thanks for your update. I now was able to change the icon set of the Kodi plugin and hit 'update' without crashes of Domoticz. I got similar log results as you showed in the spoiler. So far I don't dare to disable / enable the Kodi hardware, because that usually ends in a big crash as well and you didn't mention improvements in that direction

[Dnpwwo]

@jake,

Thanks for testing, glad it is working now.

Enabling/Disabling should also be fine now, they run through the same disconnect code. They worked fine for me.

[G3rard]

@jake,

Can you give this another try with the latest beta? Just go into the hardware page, select a Kodi and hit 'Update', that will force an unload/reload.

I added some handling to make the disconnection more graceful and it seems to work fine on my RPi B+ running Jessie.

Can confirm this is also working fine now on my server with Ubuntu. Tested again what I described in this post and that is working now.
Thanks for fixing this!

[Brutus]

Is it possible to use this plugin the same as the "Build In" plugin?

More specific the commands that can be used:
http://www.domoticz.com/wiki/Kodi#Event ... ifications

[jake]

Still looking forward to see the Kodi status 'screensaver' or 'sleep' added!

Verstuurd vanaf mijn GT-I9195 met Tapatalk

[Dnpwwo]

@Brutus,

Broadly speaking, yes it is. For example I replaced an existing Kodi device with a new plugin one and gave it the same name and all of my Lua scripts worked exactly as before.

Notifications the devices generate are slightly different however:

• There is now a volume device that can generate On/Off notifications
• A 'Playing' device that can generate Playing/Not Playing via On/Off notifications
• There is a selector switch that generates notifications based on source changes

Is there some specific functionality you are after?