OH2 Kodi: No binding found that supports creating a thing of type kodi:kodi

Kodi binding 2.2.0.201709032148
OH 2.2.0 snapshot #1003

I decided to upgrade to the v2 Kodi binding today. My first issue was that auto discovery failed until I enabled Settings> Services> UPnP/DLNA> Allow remote control via UPnP. I’m not sure what the default configuration is for Kodi, so I may have disabled it at some point. The documentation should probably include this.

After discovery, I get an error when trying to add the thing from the Inbox. Restarting the binding did not help. I have the logging for the binding in DEBUG, but there really is very little being logged. Any ideas?

2017-09-05 13:42:45.598 [DEBUG] [org.openhab.binding.kodi            ] - BundleEvent STARTING - org.openhab.binding.kodi
2017-09-05 13:42:45.598 [DEBUG] [org.openhab.binding.kodi            ] - BundleEvent STARTED - org.openhab.binding.kodi
2017-09-05 13:42:45.604 [DEBUG] [org.openhab.binding.kodi            ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.UpnpDiscoveryParticipant}={component.name=org.openhab.binding.kodi.internal.discovery.KodiDiscoveryParticipant, component.id=231, service.id=1083, service.bundleid=223, service.scope=bundle} - org.openhab.binding.kodi
2017-09-05 13:51:07.187 [DEBUG] [l.discovery.KodiDiscoveryParticipant] - Manufacturer matched: search: XBMC Foundation, device value: XBMC Foundation.
2017-09-05 13:51:07.188 [DEBUG] [l.discovery.KodiDiscoveryParticipant] - Device type matched: search: MediaRenderer, device value: MediaRenderer.
2017-09-05 13:51:07.193 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'kodi:kodi:846929b3-1e70-af41-06d2-6dcc5248648e' to inbox.
2017-09-05 13:51:41.417 [WARN ] [g.discovery.internal.PersistentInbox] - Cannot create thing. No binding found that supports creating a thing of type kodi:kodi.

Hi Scott,

Settings> Services> UPnP/DLNA> Allow remote control via UPnP. The documentation should probably include this.

Definitely. Good catch. I will take care of that.

[2017-09-05 13:51:41.417 [WARN ] [g.discovery.internal.PersistentInbox] - Cannot create thing. No binding found that supports creating a thing of type kodi:kodi.

That’s strange. I don’t see such an error if I try to add a discovered Kodi instance. What OS do you use? Which version?

Fedora 25

OK understood. Maybe I wasn’t specific enough. Which Kodi OS and Kodi version?

:slightly_smiling_face:
FireTV: Android 5.1.1 API level 22 (kernel: Linux 3.10.61+)
Kodi 17.3

And in case this helps track down the error, PaperUI displays this…

image

Another layer… when discovery didn’t work, I manually created things but they never initialized. I deleted them after discovery worked, but PaperUI couldn’t remove them so I deleted them through Habmin.

PaperUI shows this in the Inbox:

image

I just tested this on my Win10 laptop running Kodi 16.1 with the same result.

2017-09-05 16:44:00.829 [DEBUG] [l.discovery.KodiDiscoveryParticipant] - Manufacturer matched: search: XBMC Foundation, device value: XBMC Foundation.
2017-09-05 16:44:00.829 [DEBUG] [l.discovery.KodiDiscoveryParticipant] - Device type matched: search: MediaRenderer, device value: MediaRenderer.
2017-09-05 16:44:00.830 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'kodi:kodi:ec446fa3-4041-c5f3-b56c-ec3a1144b623' to inbox.
2017-09-05 16:45:08.943 [WARN ] [g.discovery.internal.PersistentInbox] - Cannot create thing. No binding found that supports creating a thing of type kodi:kodi.

You are using OH2 snapshot anyway. Do you mind to update to the latest build: openHAB 2.2.0 Build #1032?

1 Like

There were a few breaking changes that I was hoping to avoid for a bit longer. It may take a few days, but I’ll look into what changes I’ll need to make to do the upgrade. I’ll let you know the result.

Allright, now I see the problem. Let me guess, you downloaded the Kodi binding .jar file and installed it manually by putting it into the addons folder?

Kodi binding 2.2.0.201709032148
OH 2.2.0 snapshot #1003

Those two versions doesn’t match. There may be differences in the dependencies. Try to restart your OH2 service with DEBUG logging activated for the Kodi binding and you will see an error in the log files - the Kodi binding could not be installed.

// Edit: You don’t have to update if you don’t want to. Just try to install the older Kodi binding version first.

No… I installed through PaperUI. I thought about grabbing the latest and putting it in addons, but 20170903 looked recent enough for me! I’ll restart, but I did not see any issues in the logs when I restarted OH earlier today. The Kodi binding is installed and active:

openhab> bundle:list |grep -i kodi
223 | Active | 80 | 2.2.0.201709032148 | Kodi Binding

I’ll get to it sooner or later… might as well be sooner!

Here is the log after a restart of OH and then adding the Thing from the Inbox (same result):

2017-09-05 18:17:28.387 [DEBUG] [org.openhab.binding.kodi            ] - BundleEvent STARTING - org.openhab.binding.kodi
2017-09-05 18:17:28.454 [DEBUG] [org.openhab.binding.kodi            ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.UpnpDiscoveryParticipant}={component.name=org.openhab.binding.kodi.internal.discovery.KodiDiscoveryParticipant, component.id=226, service.id=1114, service.bundleid=223, service.scope=bundle} - org.openhab.binding.kodi
2017-09-05 18:17:28.484 [DEBUG] [org.openhab.binding.kodi            ] - BundleEvent STARTED - org.openhab.binding.kodi
2017-09-05 18:19:44.260 [DEBUG] [l.discovery.KodiDiscoveryParticipant] - Manufacturer matched: search: XBMC Foundation, device value: XBMC Foundation.
2017-09-05 18:19:44.264 [DEBUG] [l.discovery.KodiDiscoveryParticipant] - Device type matched: search: MediaRenderer, device value: MediaRenderer.
2017-09-05 18:19:44.267 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'kodi:kodi:846929b3-1e70-af41-06d2-6dcc5248648e' to inbox.
2017-09-05 18:20:06.425 [WARN ] [g.discovery.internal.PersistentInbox] - Cannot create thing. No binding found that supports creating a thing of type kodi:kodi.

Updating to the latest 2.2.0 snapshot (build #1033) corrected this (moving to jog4j2 wasn’t too hard). Thank you for your assistance! I have a backup of my old setup, if you would like to troubleshoot further. The error was coming out of ESH, so I have no idea what exactly could have been causing it.