[rs] Remote Scheduling v1

[Black Hole]

"Deprecated: Invalid characters..."??

 

[prpr]

See https://www.php.net/manual/en/migra...ion74.deprecated.core.invalid-base-characters

 

[/df]

Example: if a string contained some HTML entity like &#f6; (lowercase o umlaut), the affected PHP code would formerly convert the hex value to int with no need to extract the hex digits first. Since it's PHP, no-one can tell what attempting to convert the equivalent HTML5 entity ö would do, error or 0 or .... In 7.4 or later, if you previously got an int, you get the warning as well. Presumably some later version will raise an error.

 

[Black Hole]

So an update to PHP on the server has stopped RS working properly? @af123

 

[MymsMan]

So an update to PHP on the server has stopped RS working properly? @af123

RS still working for me, including schedule
Were you trying to schedule something with a weird name?

 

[Black Hole]

Were you trying to schedule something with a weird name?

Nope, that's just the landing page. Still happening here.

 

[prpr]

It works OK for me, on a real computer.

 

[MymsMan]

It works OK for me, on a real computer.

It also works for me on an Android phone though I thought they were server generated error messages rather than browser error messages so device likely to be irrelevant.

Nope, that's just the landing page. Still happening here.

Do other RS pages work?
Does it fail with your other Humax boxes?
What recordings do you have scheduled?
Have you tried from another device?

 

[prpr]

I thought they were server generated error messages

They are.

rather than browser error messages so device likely to be irrelevant.

Possibly, given we have no idea what the code is actually doing.

 

[Black Hole]

So...

It works OK for me, on a real computer.

I get the same thing whether on my iPad (with out of date software) or on Firefox (Linux Mint). However, as the deprecated warnings are being inserted at the server, and the browser is not sending anything for the server to react to (except URL query strings), it has to be a result of data being retrieved from the HD/HDR and then processed by the server to generate the web page, and nothing to do with the browser or device the browser is running on.

Have you tried from another device?

See above.

Does it fail with your other Humax boxes?

Same, with variations which might be indicative: all three HDRs give the same two deprecated lines under the banner and then two in the Active list, whereas the HD-FOX produces three lines in each case.

What recordings do you have scheduled?

It's difficult to understand why all four of my RS-connected units are producing this but nobody else is seeing it. They have some duplication of schedule entries, but not duplicated across all four. Two of the units are on WiFi and two on HomePlug, so there's not even commonality there. The only thing left common to my units but nobody else's is my broadband connection!

Do other RS pages work?

The Auto and Settings pages work, EPG and Visual show similar effects.

 

[prpr]

the browser is not sending anything for the server to react to (except URL query strings),

And stuff like the User-Agent header, which can have a significant bearing. It probably doesn't in this case as you get the same result from a real computer.

it has to be a result of data being retrieved from the HD/HDR and then processed by the server to generate the web page

Probably correct.

The only thing left common to my units but nobody else's is my broadband connection!

Or your tuning database - I can't think network is significant to anything.
Are these on English, Welsh or a mixture of transmitters? As a test, you could just try the Mendip services, like my one which doesn't exhibit the fault. I could try a spare on Wenvoe too.

 

[MymsMan]

Or your tuning database - I can't think network is significant to anything.
Are these on English, Welsh or a mixture of transmitters? As a test, you could just try the Mendip services, like my one which doesn't exhibit the fault. I could try a spare on Wenvoe too.

Another way to test via the epg page would be to set up favourites lists which contain a subset of channels and see which channels cause problems on the epg pages and which don't

Also try deleting all scheduled recordings, see if that resolves problem and then reschedule one by one

It must be one of these special characters in a programme name type problems that have affected the webif over the years but have now (touch wood) been eliminated

 

[Black Hole]

Perhaps we don't! Why isn't this working?:

View attachment 6664
The first rule works (although I recently tweaked it to pick up the Monday broadcast specifically), and I added the second rule to try to catch the Sunday repeats even though they have the same S- and P-CRIDs. Here are the "matching events":

View attachment 6666

There is no sign of these being pushed as schedule events in rs.log, and I'm not getting emails to say they have triggered a schedule operation. Is that because they are being filtered by CRID? Yes, I have tried resetting the rule.

I have successfully scheduled these events through the WebIF EPG, so why not RS?

Baton now taken up in a new thread (yes, this still isn't working): https://hummy.tv/forum/threads/rs-scheduled-event-not-working.11472

 

[riku2]

Is it possible to configure how far in advance rs will schedule a programme? I have rs working ok but it will schedule my hummy as soon as epg data is received for a particular channel (about 8 days in advance). The problem I have is that some channels change their schedules between the uploading and the day of broadcast and my scheduled recording does not update to match the new time and stays based on the original published epg data.
I am not in the UK but Finland and AR does not work. I thought that changing the way rs uploads the epg and making it only upload epg data for the next two days in advance (not 8 days) would solve the problem, but is that configurable in the code somewhere?

 

[Owen Smith]

The problem I have is that some channels change their schedules between the uploading and the day of broadcast and my scheduled recording does not update to match the new time and stays based on the original published epg data.

That works for me, the recording changes to match EPG data when it updates even without AR in use. But I'm in the UK.

 

[Black Hole]

I am not in the UK but Finland and AR does not work.

It's hard to say what will or won't work in Finland, and frankly I'm amazed RS caters for Finland at all. I guess somebody (ie you!) is contributing their local EPG to it, and standards are sufficiently similar that it sort-of works.

You say AR doesn't work. AR relies on broadcast data containing a code representing the current programme, which matches the relevant code obtained from the EPG when scheduling a recording. I presume you have turned off AR (ie set up auto-padding) because without the AR codes the unit would wait to see the code and then time out.

However, even without AR, schedule changes in the EPG should track. RS won't have been designed to do anything other than ping out a schedule, or an alert email, as soon as a matching entry appears in the EPG.

I don't auto-schedule many things, mostly I just get an email and I decide what to do about it. You could take that approach.