[ir] Web-based Remote Control

You never needed the git folder anyway. That was just a bit of laxness in the previous postings. You should have used /tmp instead.
 
Sorry for any confusion, humax /mnt/hd2/mod/git # is my command prompt (and a different colour) and mod/git is just my default working directory and included in the prompt so I don't get too confused about where I am.
 
...I've removed the 1.20 version from the repository - it isn't crashing any of my three boxes though so I don't know what's going on yet.
With beta packages enabled, diag fix-flash-packages removes and then fails to re-install ir.
Code:
...
Re-installing ir
Removing package ir from root...
Installing ir (1.20) to root...
Downloading http://hpkg.tv/hdrfoxt2/beta/ir_1.20_mipsel.opk.
Collected errors:
 * opkg_download: Failed to download http://hpkg.tv/hdrfoxt2/beta/ir_1.20_mipsel.opk, wget returned 8.
 * opkg_install_pkg: Failed to download ir. Perhaps you need to run 'opkg update'?
 * opkg_install_cmd: Cannot install package ir.
...
The package can be re-installed directly after downloading it; installing directly from its URL, as commenters above suggested, didn't work, as opkg ignored the package version in the URL and went directly for what it thought was most recent, as above:
Code:
wget -U '' http://hpkg.tv/hdrfoxt2/beta/ir_1.19_mipsel.opk
opkg install ir_1.19_mipsel.opk
# or, reverting beta,
wget -U '' http://hpkg.tv/hdrfoxt2/base/ir_1.17_mipsel.opk
opkg install ir_1.17_mipsel.opk
 
Last edited:
With beta packages enabled, diag fix-flash-packages removes and then fails to re-install ir.
Because /mod/var/opkg/beta still refers to 1.20 even though it's been removed. The file needs to be rebuilt when packages are removed, but it hasn't been.
I guess we can hope for 1.21 sometime, as alluded to back in July.
 
Because /mod/var/opkg/beta still refers to 1.20 even though it's been removed. The file needs to be rebuilt when packages are removed, but it hasn't been.
I guess we can hope for 1.21 sometime, as alluded to back in July.
Unfortunately we are dependent on @af123 for updates and he has been largely out of action since July
 
I've made my own extra repository, with just the old ir_1.19 package and a couple of my private/test packages in it, and added it like opkg-beta does on the Humax.
Works nicely. :)
 
With beta packages enabled, diag fix-flash-packages removes and then fails to re-install ir.
Oh shit. I thought I would see what happens if I remove the opkg-beta package and then run fix-flash-packages... bad move. It stripped out my beta WebIF and didn't reinstall.

I think the fix-flash-packages diagnostic needs some safeguards!
 
I'm trying to disable the power button by putting 00:: in the map file. The humaxtv.log file says:
Code:
Initialising IR3 v1.19
IR3 debug: 1
IR3 Mode: 1 (0x1000)
IR3 Options: 0x18
IR3 - Loading custom keymap.
Read 152 bytes from map file.
IR3 map line: [00::]
Parsed [00] []
Not mapping [0].
Is there something inhibiting the power button from being mapped out?
 
did you edit both '00' entries in the /mod/boot/ir3.map file ?

Code:
Humax3# cd /mod/boot
Humax3# cat ir3.map
00:00:POWER        <<<<<<<<<<  THIS ONE
00:00:STANDBY      <<<<<<<<<< AND THIS ONE
02:02:SOURCE  
03:03:ONE
04:04:TWO
05:05:THREE
06:06:FOUR

EDIT
Maybe the fact that there are two entries for '00' in the ir3.map file prevents any alterations, I guess that is why af123 built-in this power off option (not sure about power on), see General Notes # 3 here :-

https://wiki.hummy.tv/wiki/WebIf_Remote_Controller#General_Notes
 
Last edited:
Code:
00:00:POWER <<<<<<<<<< THIS ONE
00:00:STANDBY <<<<<<<<<< AND THIS ONE
So far as I can see, those are just duplicate entries.

wiki said:
When 'Ir' is installed, it is possible to 'lock out' the power off function by creating a file called /tmp/.irhold, then it won't be possible to power off the Humax using the remote
Thanks for that.
 
Is /tmp/.irhold only a temporary file? It stopped working, and when I investigated (today) I found it isn't there any more. If it needs recreating each boot, I'll have to put it in the boot scripts.

...It seems that it is, I checked before and after a reboot. To make it auto-recreate each boot, see https://hummy.tv/forum/threads/symbolic-link.3926/#post-47862.

Thus, /mod/etc/init.d/S99irhold:
Code:
#!/bin/sh

touch /tmp/.irhold
 
Last edited:
Pardon me for being stupid. But isn't every file in /tmp temporary and could be deleted on next reboot?
I think the issue here is that /tmp is in RAM (and recreated fresh each boot), as opposed to /tmp just being a parking space on HDD. Other parts of the file system are in Flash and read-only.
 
Last edited:
There appears to be a bug on the ir WebIF page, as reported here:
Thanks once again. Because the Humax remembers where it last was, the button will only work first time around. So I thought to add it as a start-up sequence, which would mean that Media would default to that after reboot. I could not implement/test that, as one has to name the macro "root" and I cannot use 'r' as a character in the filename; 'r' clicks the blue button on the virtual remote instead. I could not figure out how to rename a macro.

Edit: Windows 10; tried on Firefox and on Edge.

Keyboard keys are mapped to virtual remote button presses (when did that happen? If it was announced I don't remember it, but that's nothing unusual...), so trying to type into the name box for the macro recorder is a comedy with the key presses recording remote codes instead of entering in the name box.

I tried copy-and-paste to enter a name, that worked but still did not enable the "save" button.

According to the wiki (the only reference I can find), recorded macros (as opposed to button redefinitions in /mod/boot/ir3.map) are held in /mod/etc/webif/db, so are not amenable to direct hacking.

Therefore, macro recording is broken with no work-around.
 
Back
Top