WebIf Remote Controller 'OK' 'OK' 'OK' 'OK' 'OK'

#1
I think the Webif Remote Controller is just brilliant, especially the mobile version. I can change channel for the kids whilst sitting reading in the kitchen :). But....... why oh why do I have to press 'OK' after every command to action it??? I don't on the actual remote. I suggest maybe an option in the setting or in the remote page that automatically adds the OK to every command that needs it or just do away with the need to 'OK' ok?
I also find the Mobile version does not always respond to changes in the main remote or the favourites pages and that trying to hit the tiny arrow in the favourites section can be a little difficult, is it possible to make the whole thing press-able?
 

Ezra Pound

Well-Known Member
#2
It's to do with timing, the O.K. completes a string of key presses, this would be done on the 'real' remote by adding (or not adding) a gap between key presses. So only you know if you want channel 123 you press these keys in quick succession and with gaps if you want Ch 1 followed by Ch2 followed by Ch 3. The auto O.K. sender would not know whether to send 1, 2, 3, O.K or 1, O.K., 2, O.K., 3, O.K.
 
OP
OP
S

steveharr

New Member
#4
Could the time of the press not be recorded and then depending on the time between presses the sender could then determine what to send? a little bit like what the remote does.
 
OP
OP
S

steveharr

New Member
#5
You don't, what makes you think that you do? It works just like the real remote in that regard. Each keypress is sent straight away.
Well on my Remote interface I do have to press 'ok'. If I just press '1' it does not do anything, each key press is not sent straight away. So in that regard it does not work like the remote I have, do you have to press 'ok' on your remote if you press '1'? I don't it just changes after a short pause.
 

Black Hole

May contain traces of nut
#6
There is something odd going on there then. You should see exactly the same on the TV screen as if you were using the real remote - press '1' say, and a "---1" appears at top right, and then changes to LCN 1 when it has timed out any further input (unless you press OK).

However: if you use the channel change drop-down list, or configure a set of favourites, or even set up your own macros (all these options are to the right of the remote control page, which I suspect you may be missing out on if you are using a narrow screen), the channel change including OK is sent as a string.
 

Brian

Administrator
Staff member
#7
Well on my Remote interface I do have to press 'ok'. If I just press '1' it does not do anything, each key press is not sent straight away. So in that regard it does not work like the remote I have, do you have to press 'ok' on your remote if you press '1'? I don't it just changes after a short pause.
It works properly for me, I don't need to press OK, the channel changes after a short pause. Pressing OK afterwards should speed up the channel change, but is not necessary.
 
OP
OP
S

steveharr

New Member
#8
It works properly for me, I don't need to press OK, the channel changes after a short pause. Pressing OK afterwards should speed up the channel change, but is not necessary.
OK, well it doesn't do that for me now!. I have tried it on Chrome first and it always needed the 'OK' (I waited over a minute), I tried it on IE, the same. So I tried it on Firefox and it worked yeahhh, I then tried on Chrome and IE again and Android stock browser and all works fine now :) Not sure why there was a problem, don't think it was network based because it always work pressing 'ok'. Thank you all for replying.

I must say I hack around with ALL my gadgets and this forum is just the best, with some great contributors. I am a .net developer I'd love to get into helping or submitting on here but really not sure where to start. Could anybody point me in a good direction to learn the ropes?
 

af123

Administrator
Staff member
#10
Most of the code for the web-based remote is in javascript and so executed within your browser. As far as that code is concerned, the only thing special about the OK button is that it forces a quick refresh of the status panel at the top of the screen as well as sending the key code. Glad it's working now but can't explain it.
 
#11
A brilliant idea, unfortunately I cannot get it to work! I have tried using Chrome, IE, and Firefox with the same result.
Could the cause be channel renumbering? Both button presses and the Channel Shortcuts for BBC2 show "TWO (0x4) OK (0x13)" but nothing happens!
Any help will be much appreciated.
Michael.h
 

Black Hole

May contain traces of nut
#12
I also have examples of the ir package not working (but fine on other machines), I don't think it is to do with the browser. You could try running the diagnostic fix-flash-packages, but no guarantees.
 

af123

Administrator
Staff member
#13
Are you using a non-standard remote control mode? If so, you need to set the same mode in the settings for the IR package.

Failing that, try turning debug on by running the ir3/debugon diagnostic, restarting and then look at the humaxtv.log log file for diagnostic output.
 
#14
Unfortunately fix-flash-packages made no difference.
I am using the remote supplied with the Humax.
I have run ir3/debugon and attach humaxtv.log log file renamed to .txt to allow for upload as its contents mean nothing to me.
Thank you for trying to help.
 

Attachments

af123

Administrator
Staff member
#15
Could you do some real remote keypresses and then some ones via the web interface and post the end of the log?
 

Black Hole

May contain traces of nut
#16
You need to check that the ir package is using the same RC channel as your handset. Chances are it is, but worth a check non-the-less.

On the handset, press and hold "OK" and then "0" together for a few seconds - the "PVR" button will go out and then turn on permanently, and the TV screen (displaying the Humax output) will put up a message "you can change the control channel... current control channel is Mode 1" (or something to that effect). Leave it alone and it will go away of its own accord.

Now in WebIF >> Settings >> Remote Control Settings check the Remote Control Mode selected is the same as was displayed on the TV screen - if not, change it.
 
#17
Reply to af123
Hope I ave included all you want.
Michael
-------------------------------------
Initialising Dustbin v1.0
Dustbin debug: 0
Dustbin media root: /mnt/hd2/My Video/
Dustbin path: /mnt/hd2/My Video/[Deleted Items]
-------------------------------------
route: SIOCADDRT: File exists
[RR] Thu Jan 1 19:56:27 1970: Ring going blue, full boot.
DRV_DSC_Init_Begin
SIOCDELRT failed , ret->-1

GALIO STARTING
./humaxtv --alt-config /usr/browser/config-ocontroller-si-rootfs.txt --config /var/lib/humaxtv/galio-config.txt
User opts: None
OCON | initialising controller
Restore reminders from file failed
Persist reminders to file failed

mq_receive: 04
Injecting 04

InjectCommand: Got mutex
get_inbuf: Popped existing.
get_inbuf: Popped existing.
InjectCommand: Buffers 0 014af7d0 1 014af7dc
InjectCommand: Input list 0
InjectCommand: setting signal (0x14af660)
GetQueueSize: 1
GetEvents(): faking key 04 (2)
Real IR code: 00000000 0xfb041000
GetQueueSize: 1
GetEvents(): faking key 04 (1)
Real IR code: 0x000001 0xfb041000

mq_receive: 13
Injecting 13

InjectCommand: Got mutex
get_inbuf: Popped existing.
get_inbuf: Popped existing.
InjectCommand: Buffers 0 014af7e8 1 014af7f4
InjectCommand: Input list 0
InjectCommand: setting signal (0x14af660)
GetQueueSize: 1
GetEvents(): faking key 13 (2)
Real IR code: 00000000 0xec131000
GetQueueSize: 1
GetEvents(): faking key 13 (1)
Real IR code: 0x000001 0xec131000

mq_receive: 07
Injecting 07

InjectCommand: Got mutex
get_inbuf: Popped existing.
get_inbuf: Popped existing.
InjectCommand: Buffers 0 014af800 1 014af80c
InjectCommand: Input list 0
InjectCommand: setting signal (0x14af660)
GetQueueSize: 1
GetEvents(): faking key 07 (2)
Real IR code: 00000000 0xf8071000
GetQueueSize: 1
GetEvents(): faking key 07 (1)
Real IR code: 0x000001 0xf8071000

mq_receive: 13
Injecting 13

InjectCommand: Got mutex
get_inbuf: Popped existing.
get_inbuf: Popped existing.
InjectCommand: Buffers 0 014af818 1 014af824
InjectCommand: Input list 0
InjectCommand: setting signal (0x14af660)
GetQueueSize: 1
GetEvents(): faking key 13 (2)
Real IR code: 00000000 0xec131000
GetQueueSize: 1
GetEvents(): faking key 13 (1)
Real IR code: 0x000001 0xec131000
MEM: used heap 4692992/4702200 flex 844712/25165824
MEM: used heap 4692992/4702200 flex 844712/25165824
MEM: used heap 4692992/4702200 flex 844712/25165824
MEM: used heap 4692992/4702200 flex 844712/25165824
MEM: used heap 4692992/4702200 flex 844712/25165824
MEM: used heap 4692992/4702200 flex 844712/25165824
MEM: used heap 4692992/4702200 flex 844712/25165824
MEM: used heap 4692992/4702200 flex 844712/25165824
MEM: used heap 4692992/4702200 flex 844712/25165824
MEM: used heap 4692992/4702200 flex 844712/25165824
MEM: used heap 4692992/4702200 flex 844712/25165824
MEM: used heap 4692992/4702200 flex 844712/25165824
Real IR code: 00000000 0xfb0410fe
Real IR code: 00000000 0xf80710fe
Real IR code: 0x000001 0xf80710fe
Real IR code: 0x000001 0xf80710fe
Real IR code: 0x000001 0xf80710fe
Real IR code: 0x000001 0xf80710fe

mq_receive: 03
Injecting 03

InjectCommand: Got mutex
get_inbuf: Popped existing.
get_inbuf: Popped existing.
InjectCommand: Buffers 0 014af830 1 014af83c
InjectCommand: Input list 0
InjectCommand: setting signal (0x14af660)
GetQueueSize: 1
GetEvents(): faking key 03 (2)
Real IR code: 00000000 0xfc031000
GetQueueSize: 1
GetEvents(): faking key 03 (1)
Real IR code: 0x000001 0xfc031000

mq_receive: 13
Injecting 13

InjectCommand: Got mutex
get_inbuf: Popped existing.
get_inbuf: Popped existing.
InjectCommand: Buffers 0 014af848 1 014af854
InjectCommand: Input list 0
InjectCommand: setting signal (0x14af660)
GetQueueSize: 1
GetEvents(): faking key 13 (2)
Real IR code: 00000000 0xec131000
GetQueueSize: 1
GetEvents(): faking key 13 (1)
Real IR code: 0x000001 0xec131000

mq_receive: 43
Injecting 43

InjectCommand: Got mutex
get_inbuf: Popped existing.
get_inbuf: Popped existing.
InjectCommand: Buffers 0 014af860 1 014af86c
InjectCommand: Input list 0
InjectCommand: setting signal (0x14af660)
GetQueueSize: 1
GetEvents(): faking key 43 (2)
Real IR code: 00000000 0xbc431000
GetQueueSize: 1
GetEvents(): faking key 43 (1)
Real IR code: 0x000001 0xbc431000

mq_receive: 13
Injecting 13

InjectCommand: Got mutex
get_inbuf: Popped existing.
get_inbuf: Popped existing.
InjectCommand: Buffers 0 014af878 1 014af884
InjectCommand: Input list 0
InjectCommand: setting signal (0x14af660)
GetQueueSize: 1
GetEvents(): faking key 13 (2)
Real IR code: 00000000 0xec131000
GetQueueSize: 1
GetEvents(): faking key 13 (1)
Real IR code: 0x000001 0xec131000
 
#18
Reply to Black Hole
I have followed your instructions and both are set to mode 1.
Should any of the options listed below be changed?
Block remote control mode change icons NO
Swap INFO and LIST commands? NO
Disable volume controls? NO
Use custom map file? NO
Michael
 

Black Hole

May contain traces of nut
#19
Those options are fine:

Block remote control change icons stops the graphics which pop up when you press an unallocated mode button (probably DVD or Audio) on the handset.

Swap Info and List exchanges the function of those buttons, for people who refuse to acclimatise to the Humax remote after getting used to a different one.

Disable volume controls prevents vol+/- and mute doing anything in PVR mode (forcing you to use the TV controls).

Use custom map file pulls in a user-defined mapping file enabling you to redefine the RC buttons, including macro sequences.​

With them all off, the handset should work normally.

If we can get to the bottom of why your ir package isn't working, it should help a number of users who have reported similar problems but not pursued it (including me).
 

af123

Administrator
Staff member
#20
According to that log, your remote control is set to mode 6. Try setting the ir mode to match in the web interface and then restart.
 
Top