Sam Widges
Active Member
You might be able to do something by setting reminders - not sure if you can do that via the webif, though.
You might be able to do something by setting reminders - not sure if you can do that via the webif, though.
I think you had some kind of glitch. The forced reboot would not normally leave it in standby, so anything might have happened.
Note that an OTA update is expected to clear the power on/off timers.
By the way, you do not need to reboot the box as long as the normal power cycles will take care of it before the programme you are trying to schedule, and actually you are better off doing schedule stuff via the RS web site because the Humax will check in and fetch anything that's been queued up for it whenever it boots (and periodically when on, even if only "half awake" recording).
I'm not saying not to have secure access to your WebIF, but I don't see the problem with using the RS service for setting up recordings rather than using the WebIF - would solve a lot of problems surely?
A reminder is a suitable alternative to a power timer - it brings the box properly out of standby for the duration of the reminedr period and updates the EPG (for padding recordings).
And yes, I do mean an OTA will (probably) clear the power on/off timers.
I think you had some kind of glitch. The forced reboot would not normally leave it in standby, so anything might have happened.
I think you misunderstand what RS is all about. The Remote Schedulling Service is an externally-hosted web site af123 has set up. Every now and again your Humax handshakes with the external service to update an externally held copy of your EPG, and download any commands than have been left for it. Seperately from that, you can log in to the RS web site to inspect the copy of your EPG and set up any new recordings; you can also have "watches" placed which can automatically schedule programmes which match certain criteria, or have email alerts if anything matches.
You do not access your Humax insecurely, you are only logging in to a web site that is not hosted on your home network. The web site does not attempt to access your Humax, your Humax has to visit the web site and is recognised by its MAC address.
The advantage of the RS service as opposed to using WebIF for schedulling either locally or by remote connection is that there are fall-back mechanisms - like in your example when the Humax failed to boot again after a restart, not a problem with the RS service because the Humax will check in again next time it boots for any reason at all. You can also set up wake-up times via the RS.
Unless there is a technical reason why this won't work for you, I recommend using RS for schedulling, and your secure access to WebIF for everything else.
Set up a series of manually scheduled reminders at intervals through the day (they must not conflict with your recording schedule of course). For example, if you set up 4-4.30pm, 9-10pm - then if the box fails to wake up in one you've a good chance of it waking up the next time (though frankly I've never known it to fail). Actually, being accessed from the other side of the world, middle-of-the-night access windows might be quite convenient.However that still leaves me with the problem which I started today's post with. The inability to be sure whether the box is on or on standby. Any type of remote comunication needs to know that.
sftp root@192.168.1.10
root@192.168.1.10's password:
Connected to 192.168.1.10.
sftp> ls
bin boot etc lib mediatomb
mipsel-linux mipsel-unknown-linux-uclibc mnt root sbin
share test tmp var
sftp> quit
It should just work - here's my Linux session
Code:sftp root@192.168.1.10 root@192.168.1.10's password: Connected to 192.168.1.10. sftp> ls bin boot etc lib mediatomb mipsel-linux mipsel-unknown-linux-uclibc mnt root sbin share test tmp var sftp> quit
What client are you using? WinSCP is good on Windows as it's built on PuTTY.
By the way, you're not thinking of copying programmes this way are you?
By all means, give it a go, and you've nothing to lose by trying it, but avoid HD recordings.
Also, you may fall foul of another issue in the Internet - a lot of ISPs give a low priority to traffic that's on port numbers above 1024 (with a few exceptions) because of psp and torrents. The upshot of this is that the tunnel will be fine for running webif, but may be unreliable to transfer programmes. However, certain traffic types, including the default SSH port of 22, are given a higher priority, so you will have to consider moving your SSH port back to 22 if you get bad throughput. The good news is that, because you have turned off username/password authentication, you should still be secure, it's just that you will have more naughty people checking the locks.
If you do move your SSH port back to 22, I strongly recommend changing the root password to something long and nasty that's not 'humax', just in case there is a problem with the config and you accidentally enable password login again. Unfortunately, the passwd and crypt commands seem to be missing - maybe we could page af123 and get them added to the dropbear package.
Go to one of the speed test web sites and measure your uplink speed - that will give you an idea how long a video file will take to transfer. Half hour of HiDef is about 2GBytes, half hour of StDef is about 700MBytes (roughly speaking).If you think it is a non-starter then ok, I will abandon the idea.