←  [EN] Enduser support

Forums

»

Bug: Kodi's Enigma2 client doesnt conn...

dinth's Photo dinth 28 Dec 2018

Since i updated my sat box to OpenPLi 0.7-rc (build 20181220) few days ago, it's not possible to enable Enigma2 client in Kodi anymore. Whenever i restart Kodi or manually go to addons list and disable/re-enable Enigma2 addon im getting "Add-on couldn't be loaded. An unknown error has occured" error. I filled a bug report on Kodi forums, but the devs out there advised me that this is OpenPLi bug/regression.

Here's the log in Kodi:

20:06:47.836 T:139678803232512 NOTICE: AddOnLog: Enigma2 Client: pvr.vuplus - Open - VU+ Addon Configuration options
20:06:47.836 T:139678803232512 NOTICE: AddOnLog: Enigma2 Client: pvr.vuplus - Open - Hostname: '192.168.1.175'
20:06:47.836 T:139678803232512 NOTICE: AddOnLog: Enigma2 Client: pvr.vuplus - Open - WebPort: '80'
20:06:47.836 T:139678803232512 NOTICE: AddOnLog: Enigma2 Client: pvr.vuplus - Open - StreamPort: '8001'
20:06:47.836 T:139678803232512 NOTICE: AddOnLog: Enigma2 Client: pvr.vuplus - Open Use HTTPS: 'false'
20:06:47.989 T:139678803232512 NOTICE: AddOnLog: Enigma2 Client: pvr.vuplus - LoadDeviceInfo - DeviceInfo
20:06:47.989 T:139678803232512 NOTICE: AddOnLog: Enigma2 Client: pvr.vuplus - LoadDeviceInfo - E2EnigmaVersion: 2018-12-19-rc
20:06:47.989 T:139678803232512 NOTICE: AddOnLog: Enigma2 Client: pvr.vuplus - LoadDeviceInfo - E2ImageVersion: 7.0-rc
20:06:47.989 T:139678803232512 NOTICE: AddOnLog: Enigma2 Client: pvr.vuplus - LoadDeviceInfo - E2DistroVersion: openpli
20:06:47.989 T:139678803232512 NOTICE: AddOnLog: Enigma2 Client: pvr.vuplus - LoadDeviceInfo - E2WebIfVersion: OWIF 1.3.5
20:06:47.989 T:139678803232512 NOTICE: AddOnLog: Enigma2 Client: pvr.vuplus - LoadDeviceInfo - E2DeviceName: 1
20:06:48.473 T:139678803232512 ERROR: ADDON: Dll Enigma2 Client - Client returned bad status (1) from Create and is not usable
20:06:49.959 T:139678803232512 ERROR: UpdateAddons: Failed to create add-on Enigma2 Client, status = 1

For some reason, OpenPLi 0.7-rc returns "1" as its DeviceName, and apparently this value is not valid. 


Edited by dinth, 28 December 2018 - 09:55.
Quote

littlesat's Photo littlesat 28 Dec 2018


Kodi forums, but the devs out there advised me that this is OpenPLi bug/regression.\

Easy statement... ;) Sounds more like it is caused due to a change in OWIF...

Quote

Trial's Photo Trial 28 Dec 2018

Hi,

have you enabled password in OWIF? If yes disable it for a test.

 

ciao


Edited by Trial, 28 December 2018 - 11:37.
Quote

foxbob's Photo foxbob 28 Dec 2018

Addons are compiled with kodi, otherwise they do not work.For me this is:
 
17:59:17.162 T:3014695984  NOTICE: AddOnLog: VU+ / Enigma2 Client: Open - VU+ Addon Configuration options
17:59:17.162 T:3014695984  NOTICE: AddOnLog: VU+ / Enigma2 Client: Open - Hostname: '127.0.0.1'
17:59:17.162 T:3014695984  NOTICE: AddOnLog: VU+ / Enigma2 Client: Open - WebPort: '80'
17:59:17.162 T:3014695984  NOTICE: AddOnLog: VU+ / Enigma2 Client: Open - StreamPort: '8001'
17:59:17.162 T:3014695984  NOTICE: AddOnLog: VU+ / Enigma2 Client: Open Use HTTPS: 'false'
17:59:17.258 T:3014695984  NOTICE: AddOnLog: VU+ / Enigma2 Client: GetDeviceInfo - DeviceInfo
17:59:17.262 T:3014695984  NOTICE: AddOnLog: VU+ / Enigma2 Client: GetDeviceInfo - E2EnigmaVersion: 2018-12-25-develop
17:59:17.262 T:3014695984  NOTICE: AddOnLog: VU+ / Enigma2 Client: GetDeviceInfo - E2ImageVersion: develop
17:59:17.262 T:3014695984  NOTICE: AddOnLog: VU+ / Enigma2 Client: GetDeviceInfo - E2WebIfVersion: OWIF 1.3.5
17:59:17.262 T:3014695984  NOTICE: AddOnLog: VU+ / Enigma2 Client: GetDeviceInfo - E2DeviceName: ET-11000
Quote

dinth's Photo dinth 28 Dec 2018

Will try to update the build to the latest one today and try again. 

Quote

dinth's Photo dinth 29 Dec 2018

Hi,

have you enabled password in OWIF? If yes disable it for a test.

 

ciao

No, authentication is disabled.

 

 

 

Addons are compiled with kodi, otherwise they do not work.For me this is:
 
17:59:17.262 T:3014695984  NOTICE: AddOnLog: VU+ / Enigma2 Client: GetDeviceInfo - E2DeviceName: ET-11000

 

I updated my OpenPLi to 28-12-18 revision and im still getting same problem. I tried changing "Custom device name" in web interface configuration, but apparently it's a different "device name". The problem seems to be with Forumler1 build

Quote

foxbob's Photo foxbob 29 Dec 2018

Try this file.

Attached Files

Quote

dinth's Photo dinth 29 Dec 2018

Try this file

 

 

Thanks for this, unfortunately i cannot install it - "dependency on xbmc.pvr version 5.2.1 could not be resolved".

Anyhow, i highly doubt if this is a Kodi plugin problem.  

 

Here your OpenPLi box is sending a correct E2DeviceName over OWIF:

 

17:59:17.262 T:3014695984  NOTICE: AddOnLog: VU+ / Enigma2 Client: GetDeviceInfo - E2DeviceName: ET-11000

My Formuler 1 box doesnt send a correct E2DeviceName though:

20:06:47.989 T:139678803232512 NOTICE: AddOnLog: Enigma2 Client: pvr.vuplus - LoadDeviceInfo - E2DeviceName: 1
20:06:48.473 T:139678803232512 ERROR: ADDON: Dll Enigma2 Client - Client returned bad status (1) from Create and is not usable
Quote

WanWizard's Photo WanWizard 29 Dec 2018

The generic OWIF API hasn't changed in dogs years. Kodi calls http://<ip>/web/deviceinfo.
 
it returns an XML file, which can be parsed only one way, and e2devicename is a value on the XML. It also lists the OWIF version. So what does that URL return when you call it in your browser? 

Quote

dinth's Photo dinth 29 Dec 2018

The generic OWIF API hasn't changed in dogs years. Kodi calls http://<ip>/web/deviceinfo.
 
it returns an XML file, which can be parsed only one way, and e2devicename is a value on the XML. It also lists the OWIF version. So what does that URL return when you call it in your browser? 

 

<e2deviceinfo>
<e2oeversion>PLi-OE</e2oeversion>
<e2enigmaversion>2018-12-27-rc</e2enigmaversion>
<e2distroversion>openpli</e2distroversion>
<e2imageversion>7.0-rc</e2imageversion>
<e2driverdate>4.10.6+20170413-r0.0</e2driverdate>
<e2webifversion>OWIF 1.3.5</e2webifversion>
<e2fpversion>None</e2fpversion>
<e2devicename>1</e2devicename>
<e2frontends>
<e2frontend>
<e2name>Tuner A</e2name>
<e2model>BCM7346 (internal) (DVB-S2)</e2model>
</e2frontend>
<e2frontend>
<e2name>Tuner B</e2name>
<e2model>BCM7346 (internal) (DVB-S2)</e2model>
</e2frontend>
<e2frontend>
<e2name>Tuner C</e2name>
<e2model>Si2168 (DVB-T2)</e2model>
</e2frontend>
</e2frontends>
<e2network>
<e2interface>
<e2name>eth0</e2name>
<e2mac>xx:xx:xx:xx:43:ed</e2mac>
<e2dhcp>False</e2dhcp>
<e2ip>192.168.1.175</e2ip>
<e2gateway>192.168.1.1</e2gateway>
<e2netmask>255.255.0.0</e2netmask>
</e2interface>
</e2network>
<e2hdds>
<e2hdd>
<e2model>ATA(G-DRIVE)</e2model>
<e2capacity>5.5 TB</e2capacity>
<e2free>5080.0 GB</e2free>
<e2mount>/media/hdd</e2mount>
</e2hdd>
</e2hdds>
</e2deviceinfo>

Same Kodi plugin used to work perfectly fine with 6.2 before i upgraded my tuner to 7.0-rc

Quote

WanWizard's Photo WanWizard 30 Dec 2018

The "1" comes from https://github.com/E...randing.py#L237. But that is a cosmetic thing, otherwise this output is fine.

 

7.0 is different from 6.2, that doesn't say anything. Wordperfect worked fine on my 8088 DOS PC. Not so good on later versions.

 

It is up to this Kodi plugin to maintain compatibility, so I suggest you should ask this on a Kodi forum? If you google that error message, you'll find lots of hits. I find this one interesting: https://forum.kodi.t....php?tid=309775, about the lack of maintenance of this plugin. So a year and a half ago there were already questions about its compatibility...

Quote

WanWizard's Photo WanWizard 30 Dec 2018

The "1" comes from https://github.com/E...randing.py#L237. But that is a cosmetic thing, otherwise this output is fine.

 

Fixed: https://github.com/E...27d526f854355c5

Quote

dinth's Photo dinth 30 Dec 2018

Thanks for fixing this WanWizard. Will your change be included in OpenPLi nightly automatically or i need to wait for next plugin release to test it? 

Quote

WanWizard's Photo WanWizard 30 Dec 2018

It will be in today's rc build.

Quote