Remote scheduling failing - "!Error, cannot find event to schedule"

AJones

Member
I've been having a problem recently where my remote scheduling isn't completing. I get the email to say the programme has been successfully scheduled, but it doesn't appear in the schedule on the Humax, and the log in the RS website shows "!Error, cannot find event to schedule". The guide is fully populated in the RS website, on my Humax and on the web interface and the programme in question is visible in all three.

For instance, today it correctly picked up The Sky At Night as being on BBC Four HD on Monday the 11th of May at 10pm and emailed me to tell me it had been scheduled, but didn't actually do so due to the above error. I can see it in all three EPGs and have manually scheduled it instead.

I don't know if this is relevant, but I ran the EPG range diagnostic and it shows this:

Wed Apr 23 06:00:00 BST 2025
Tue May 12 00:59:59 BST 2026

The second date looks correct but the first is over a year in the past. Is that normal? Has something got corrupted that needs resetting?

Thanks.

Web Interface Version: 1.5.4-4
Custom Firmware Version: 3.14 (build 1757805000)
Humax Version: 1.03.12 (kernel HDR_CFW_3.14)
Loader Version: a7.33

rs 1.5.1-5
 
the log in the RS website shows "!Error, cannot find event to schedule".
Can you post the relevant section of the rs.log file from the unit itself?
The guide is fully populated in the RS website, on my Humax and on the web interface and the programme in question is visible in all three.
Have you got multiple regions tuned by any chance?
I ran the EPG range diagnostic and it shows this...

Is that normal? Has something got corrupted that needs resetting?
Yes it's normal, but unhelpful, as the Humax software is cr@p at maintaining it properly. You can (should) go in to Maintenance Mode where there's an option to clear it.
 
Here's what I could find in rs.log:

7248 04/05/2026 10:08:39 - !Error, cannot find event to schedule.
7247 04/05/2026 10:08:38 - *Trying event at the same time on service 18048.
7246 04/05/2026 10:08:38 - *Trying events at the original event time @18048
7245 04/05/2026 10:08:38 - *LATEST: 1778542200, TIME: 1778533200
7244 04/05/2026 10:08:37 - *Trying source service/event ID.
7243 04/05/2026 10:08:36 - *Schedule 18048/2503/1/106/BBC FOUR HD/1778533200/The Sky at Night
7242 04/05/2026 10:08:35 - Processing command 'schedule auto'

And in the log on rs.hpkg.tv:

04/05/2026 13:50:03System booted (Remote control handset).
04/05/2026 10:08:00!Error, cannot find event to schedule.
04/05/2026 10:07:57Processing command 'schedule auto'
04/05/2026 10:07:48System booted (Scheduled event).
04/05/2026 07:42:16Updated disk contents.
04/05/2026 07:38:02System booted (Remote control handset).

The email was received at 09:10 this morning:

BBC FOUR HD
[Mon, 11 May 2026 22:00:00 +0100 / 00:30]
The Sky at Night
The team explore the remarkable story of Jodrell Bank Observatory and its towering Lovell Telescope, which scientists have used to listen to the cosmos for almost 70 years. [S ] [HD]
= Scheduled successfully (event). (The Sky at Night / ) =


--

This message is sent from an unmonitored account and replies will not be read. For help and support, please join the community at hummy.tv and search the forums to see if your question has been asked before. If not, then post a new thread in the customised firmware section and someone will be along to help you.

Only one region (Sandy Heath) is tuned in and there are no reception issues. I'll give the maintenance mode option a try and report back, thanks!
 
If you are familiar with command line operations, can you try the following commands:
Code:
humax# sqlite3 /var/lib/humaxtv/channel.db "select * from tbl_svc where ussvcid=18048"
humax# sqlite3 /mnt/hd1/epg.db "select * from epg where service_id=18048 and event_id=2503"
and report the output.
 
humax# sqlite3 /var/lib/humaxtv/channel.db "select * from tbl_svc where ussvcid=18048"

158|106|^UBBC FOUR HD|18048|1|2|1|2|7|6700|6701|6702|6701|8192|6|1|0|2|0|0|255|0|393374|8192|0|0|0|8192|0|0|9018|16525|0|0|1|1|0|1|4294967295|16|1|2|0|fp.bbc.co.uk|50332417|255|0|''|''

humax# sqlite3 /mnt/hd1/epg.db "select * from epg where service_id=18048 and event_id=2503"

18048|2503|1778533200|1778535000|1800|The Sky at Night|The team explore the remarkable story of Jodrell Bank Observatory and its towering Lovell Telescope, which scientists have used to listen to the cosmos for almost 70 years. [S ] [HD]|||2|News & Factual|1|/m/1L1S8|/b/3N93G|

I added the space in "[S ]" in the above output to avoid strikethrough for all of the text following it. Does any of it give a clue as to what might have happened?

After running those commands I ran the epg option in maintenance mode. The guide seems to have repopulated now and the epprange diagnostic shows:

Mon May 4 01:00:00 BST 2026
Tue May 12 00:59:59 BST 2026

When I get chance I'll try adding a search in the remote scheduling site that I know will be found and see if it gets scheduled correctly.
 
Does any of it give a clue as to what might have happened?
No. Mine's the same apart from site specific stuff, and my RS scheduled it OK.
After running those commands I ran the epg option in maintenance mode. The guide seems to have repopulated now
That all looks good.
If you can bear another test, issue these commands such that output looks something like this:
Code:
humax# jimsh
Welcome to Jim version 0.83
. source /mod/webif/lib/setup
jscss
. require epg.class
. epg dbfetch dump -service 18048 -event 2503
::<reference.<epg____>.00000000000000000000>
. exit
and report if no response to the "epg dbfetch..." command.
 
I've received my email for this today:

BBC FOUR
[Mon, 11 May 2026 22:00:00 +0100 / 00:30]
The Sky at Night
The team explore the remarkable story of Jodrell Bank Observatory and its towering Lovell Telescope, which scientists have used to listen to the cosmos for almost 70 years. Also in HD.
= Scheduled successfully (event). (+sky +night / ) =

It strikes me yours might have jumped the gun. The RS EPG is pooled from multiple registered HDR-FOXes, and perhaps one of them registered an EPG update before it went live in your region (just guessing).

PS: Bloody Markdown interpretation, I've had to protect some of it in plain tags to avoid Markdown inserting unwanted strike outs!
 
The RS EPG is pooled from multiple registered HDR-FOXes, and perhaps one of them registered an EPG update before it went live in your region (just guessing).
It doesn't work like that. All regions update at the same time - this stuff is done centrally. Even if it wasn't, your box/RS will only get stuff pertaining to your region.
There is something else going on, but quite what is not yet known.
 
Hi, just catching up.
and report if no response to the "epg dbfetch..." command.
My output looks identical to yours:

humax# jimsh
Welcome to Jim version 0.83
. source /mod/webif/lib/setup
jscss
. require epg.class
. epg dbfetch dump -service 18048 -event 2503
::<reference.<epg____>.00000000000000000000>
. exit
humax#

I've received my email for this today:
I got that email too yesterday. Did yours successfully schedule?

I've added a search rule for the Silence of the Lambs, which is on next Tuesday on BBC One HD. Matching events shows the correct programme, as does my previous entry for the Sky at Night. I'll see what happens!
 
Oops, I was mistaken about Silence of the Lambs, I was looking at the wrong day in the EPG. It's on tonight, not next Tuesday. I've left it, but set another rule to find The Theory of Everything, Which is on BBC2 next Tuesday.

I also tried scheduling a couple of programmes directly in the remote scheduling EPG, one of them for Tuesday the 12th. They were transferred to the Humax schedule without issue on the next boot.
 
My output looks identical to yours:
That would indicate that if you were to re-schedule TSaN it would now work as expected on RS. It's difficult to know what the problem was, but it seems to have gone away with clearing the old EPG data.
 
Thanks! I regret not doing those schedule tests before clearing the EPG data now, but it does look like that may have fixed the problem.

By the way, when you add a new search rule, does it only get picked up when a new match first appears in the EPG data, or will matches that already exist in the EPG be found too? I assume the ones I added today will get processed tomorrow.
 
I got that email too yesterday. Did yours successfully schedule?
Yes

By the way, when you add a new search rule, does it only get picked up when a new match first appears in the EPG data, or will matches that already exist in the EPG be found too? I assume the ones I added today will get processed tomorrow.
Not certain, but you could try More... Show Matching Events, and Reset Matched Events. The former lists events which currently match the rule, and the latter resets any "already processed" flags so matching events get processed again.
 
Fix confirmed. I received the email for The Theory of Everything this morning, and the next time I booted the Humax it was added to the schedule. Looks like clearing the EPG data did the trick. Thanks both for your help!
 
If you now do a Reset Matched Events on your Sky At Night search term, RS should re-attempt the scheduling.
 
I'd scheduled it manually since, but I've deleted the schedule on the Humax and reset matched events on the RS search as a test. I'm confident at this point that it will get picked up and scheduled again tomorrow.
 
I regret not doing those schedule tests before clearing the EPG data now, but it does look like that may have fixed the problem.
For future reference, if this ever happens again, preserving copies of /mnt/hd1/dvbepg/epg.dat , /mnt/hd1/epg.db and /var/lib/humaxtv/channel.db is a good idea (HDR only; HD EPG files are in /media/drive1/ ). This would then allow off-line analysis.
I'm confident at this point that it will get picked up and scheduled again tomorrow.
Me too.
 
The Sky at Night was scheduled successfully this morning. All is good, thanks again.

Before I cleared the EPG data, the EPG range diagnostic was showing the earliest date as Wed Apr 23 06:00:00 BST 2025. It occurs to me that if really was retaining all the EPG data since April last year, then it would have contained two 11th of Mays. Could my Humax have been looking at the first one, from 2025, which wouldn't have contained a match?
 
Back
Top