1459 replies to this topic

[theparasol]

Now fetched all files from github, replaced the files on my box with these and removed all *.pyo...

Infoscreen remains the same.... so too bad: would be nice to assist you for a change

[hemertje]

 

Ok, fixed it.

 

Output from as many different boxes as possible please

 

You got a picture on Github. You can't post pictures here

 

 

 

yes you can

 

More Reply Options on the right left corner!

Select and upload the picture

[ims]

Please, rebuild size in info.py:

size = "%d GB" % (size / float(1024))

f.eg. to:

size = "%.2f GB" % (size / 1024.)

Why size / float() and then %d ?  And why using float and not . only ?

[SpaceRat]

I'll have to check that rounding out ...

 

I have some idea what it happens at the 1023 MB <> 1024 MB = 1GB boundary, but not really about the 2 GB vs. 3 GB thing.

[Priskvark]

 

 

 

 

You got a picture on Github. You can't post pictures here

 

 

yes you can

 

More Reply Options on the right left corner!

Select and upload the picture

 

 

Thank you hemertje!

After the error message I got when pasting the picture and trying to post I wrongly thought picture posting was disabled .

But you are right, now I can after you showed me how.

Edited by Priskvark, 16 December 2014 - 00:33.

[Gerr]

in the process of re-implementing a replacement module for oe-a's "boxbranding" module I had to add quite some logic, i.e. to gather the OE version (Should return "PLi-OE" on OpenPLi, OE 1.6 on some older other images, "OE 2.2" on DM7080/DM820 running original images, "OpenVuplus 2.1" for newer VTI/BH/original Vu+ images ...)

I don't know if it's already possible or not, but it would be useful to be able to retrieve this type of info via api, something like:

http://127.0.0.1/web/info/getOEVersion

 

If that would return "PLi-OE"  (as an example according to your quote), and preferably only that string in plaintext and not enclosed in xml tags, that would be perfect for use in shellscripts.

 

I use shellscripts for a lot of stuff, and I already use other api commands via wget in scripts and also directly from browser bookmarks.

Examples:

/web/powerstate?newstate=0

/web/servicelistreload?mode=2

 

Or similar commands provided by plugins, like:

/epgrefresh/refresh

 

I find these and other such commands very useful, and I'm sure there are many more I don't know about, so it would also be cool and IMHO logical if you could visit something like:

http://myboxip/web in your browser and get a list of available api commands and parameters, rather than a 404. Maybe they could even be clickable.

 

Or, taking it one step further, if a subdir "info" is one of those listed items like I used in my suggestion for getOEVersion api, then http://myboxip/web/info could list all the api commands in the (box)info category. Just a thought. 

 

Speaking of those api commands, I found a cosmetic issue with /web/servicelistreload

If you supply an invalid parameter, like 9 in this example /web/servicelistreload?mode=9

the error message seems cut off, missing some valid options and a closing square bracket. See this comparison with DMM's webif:

OpenWebif:  missing or wrong parameter mode [0=both, 1=lamedb only, 2=userbouqets only

DMM Webif: missing or wrong parameter mode [0=both, 1=lamedb only, 2=userbouqets only, 3=transponders, 4=parentalcontrol white-/blacklist]

[system]

Hello everyone,

report the version OpenWebif 4.xx and following on decoder Dreambox 800se, remote control mode full,  the buttons
do not work except for a few button; in full mode the remote control is shown correctly.
The numeric keys work, the function keys and colorful keys no;
for example, by clicking the "OK" button to open the channel list and clicking again "ok" channels rushing down.

You can verify?

Thanks in advance

[ims]

All buttons work well for me...

[SpaceRat]

Hm, he reported the same issue on the oe-a fork of OpenWebif ...

So I told him it's a boxbranding issue then, as OpenWebif on oe-a doesn't even have a full remote but just takes the one boxbranding provides.

 

Now he's reporting here ....

Argls.

 

@system:

Which image (OpenPLi, OpenATV, VTI, ...) do you use?

[system]

Thanks for the answers, I thought it was the right place here.
Use the ItalySat, which from what I know and based OpenPLi, I apologize if my information is not correct.
I tried with different browsers and computers but reflected the same problem.
This anomaly with version 0.2.9 does not occur, the feedback from the subsequent.
Can you help?

[SpaceRat]

API

None of my businesses ...

I created an issue https://github.com/E...ebif/issues/228 for you.

[SpaceRat]

As ims reports all keys to work on the same box, I assume the problem to be inside your image.

 

The remote control inside the OpenWebif (regardless of if it comes from oe-a's boxbranding or is provided by OpenWebif itselt) just sends key codes to E2 which has to interpret them.

If you have a borked keymap.xml inside your E2, keys aren't properly handled.

[system]

As ims reports all keys to work on the same box, I assume the problem to be inside your image.

 

The remote control inside the OpenWebif (regardless of if it comes from oe-a's boxbranding or is provided by OpenWebif itselt) just sends key codes to E2 which has to interpret them.

If you have a borked keymap.xml inside your E2, keys aren't properly handled.

It could depend on the image, but I do not understand why loading the version 0.2.9 does work.
Sorry if I insist but I would like to understand where and when I can act autonomously.

[Dimitrij]

Please add this patch:

--- plugin/controllers/web.py
+++ plugin/controllers/web.py
@@ -434,6 +434,9 @@
 		description = ""
 		if "description" in request.args.keys():
 			description = request.args["description"][0]
+		eit = 0
+		if "eit" in request.args.keys():
+			eit = int(request.args["eit"][0])
 
 		return addTimer(
 			self.session,
@@ -448,6 +451,7 @@
 			dirname,
 			tags,
 			repeated,
+			eit,
 			self.vpsparams(request)
 		)

[SpaceRat]

It would be much easier if you would just provide pull requests ...

[Dimitrij]

It would be much easier if you would just provide pull requests ...

I do not know how to do it.
The problem is my English.

[SpaceRat]

Just edit the file on https://github.com/E...lugin-OpenWebif as if you would have write access to it.
That will create your own fork of OpenWebif where you can apply all the changes you like.

After you are done, you can create a pull request of it.

See here: https://github.com/E...nWebif/pull/232
Priskvark did it for you

[Dimitrij]

SpaceRat

thanks again

[Dimitrij]

Sorri,my mistake

Please add new patch:

--- plugin/controllers/web.py
+++ plugin/controllers/web.py
@@ -434,6 +434,9 @@
 		description = ""
 		if "description" in request.args.keys():
 			description = request.args["description"][0]
+		eventid = 0
+		if "eit" in request.args.keys():
+			eventid = int(request.args["eit"][0])
 
 		return addTimer(
 			self.session,
@@ -448,6 +451,7 @@
 			dirname,
 			tags,
 			repeated,
+			eit=eventid,
 			self.vpsparams(request)
 		)

[gabrielinio_39]

vusolose with beta image openpli 4 openwebif not stream with my pc in vlc player i need a plugin?