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?
- Forums
- → Viewing Profile: Posts: dinth
ATTENTION:
On June 2nd 2023, our hosting provider will have a maintenance window for our server infrastructure. During this window our servers will be moved to new SSD storage.This work will commence at 10:00 UTC and may last until 13:00 UTC. In this time window, there will be periods of unavailability to this forum, the downloads and other services.
Community Stats
- Group Member
- Active Posts 6 ( per day)
- Profile Views 1,426
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Not Telling
Contact Information
User Tools
Friends
dinth hasn't added any friends yet.
Latest Visitors
No latest visitors to show
Posts I've Made
In Topic: Bug: Kodi's Enigma2 client doesnt connect to OpenPLi 0.7-rc
30 December 2018 - 09:30
In Topic: Bug: Kodi's Enigma2 client doesnt connect to OpenPLi 0.7-rc
29 December 2018 - 23:34
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
In Topic: Bug: Kodi's Enigma2 client doesnt connect to OpenPLi 0.7-rc
29 December 2018 - 21:32
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
In Topic: Bug: Kodi's Enigma2 client doesnt connect to OpenPLi 0.7-rc
29 December 2018 - 09:57
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
In Topic: Bug: Kodi's Enigma2 client doesnt connect to OpenPLi 0.7-rc
28 December 2018 - 21:33
Will try to update the build to the latest one today and try again.
- Forums
- → Viewing Profile: Posts: dinth