Difference between revisions of "Remote Scheduling Portal"

From hummy.tv Wiki
Jump to: navigation, search
 
(69 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
This page contains documentation and demos for the tabs extension.
+
<tabs>
−
Paste this text on a wiki article with the tabs extension installed
+
<tab name="Overview">
−
to view these demos.
+
==== What is the Remote Scheduling Portal? ====
 +
 
 +
Remote Scheduling is a web site which enables you to manage your list of scheduled recordings while you're out and about, from anywhere with a web browser and Internet connection, without having to expose your Humax device to the Internet or leave it powered on.
 +
 
 +
As long as your Humax has Internet access and wakes up occasionally to check for updates or make a recording, it will work.
 +
 
 +
It allows you to perform the following:
 +
* Schedule recording of a single/series/split/manual TV or radio event.
 +
* Automatically schedule recording of a single/series event based on keywords/channel/time etc.
 +
* Remove recording schedule.
 +
* See disk contents.
 +
* Delete a recorded program, useful when the box is running low on free space.
 +
* Get warnings about failed recordings.
 +
* See disk statistics (total/used/free space).
 +
* See warnings about recording conflicts, eg when more than two concurrent recordings have been scheduled within the same time window.
 +
 
 +
==== HD/HDR-Fox T2 ====
 +
 
 +
All commands are queued on the server and the box polls the server for commands every 8-12 minutes.
  
−
-----
+
This means that it's a secure solution because you don't need to open up your firewall at home in order to use this (many similar systems are "push" instead of "pull").
  
−
{{TOC|limit=4}}
+
At each startup the program waits a random time, up to 2 minutes, spreading out server communication in order to avoid that all boxes contact the server at the exact same time.
  
−
= Installation =
+
Most commands require a powercycle to take effect, except for "delete" and "reboot".
−
{{ExtensionInstall|Tabs}}
 
  
−
= Configuration =
+
The "reboot" command is not carried out if the box is currently recording.  Instead, the processing is stopped and not resumed until the box is no longer busy.
  
−
This extension has no configuration options in <code>LocalSettings.php</code>, but it does have the ''MediaWiki:tabs-dropdown-bgcolor'' message associated with it, which is not meant to be translated. This message contains the default value for the <code>background-color</code> style for dropdown menus. This needs to be a [https://developer.mozilla.org/en-US/docs/Web/CSS/color_value valid <code>background-color</code> value].
+
==== Foxsat-HDR ====
  
−
It also has the following internationalisation messages associated with it:
+
All commands are queued on the server and the box polls the server for commands every 10 minutes when the box isn't already busy, eg recording (the rs package depends on the crond package).
  
−
*''MediaWiki:tabs-tab-label'' - The default label for a tab. The <code>$1</code> stands for the index of the tab.
+
This means that it's a secure solution because you don't need to open up your firewall at home in order to use this (many similar systems are "push" instead of "pull").
−
*''MediaWiki:tabs-toggle-open'' - The default opening label for toggle boxes.
 
−
*''MediaWiki:tabs-toggle-close'' - The default closing label for toggle boxes.
 
−
*''MediaWiki:tabs-dropdown-label'' - The default label for a dropdown menu.
 
  
−
= Usage =
+
At each startup the program waits a random time, up to 2 minutes, spreading out server communication in order to avoid that all boxes contact the server at the exact same time.
  
−
== General usage information ==
+
Most commands require a powercycle to take effect, except for "delete" and "reboot".
  
−
'''Note:''' - This extension uses the <code>bgcolor</code> attribute for dropdown menus. This is in no way meant as encouragement for the use of this deprecated attribute anywhere other than this tag.
+
During the Housekeeper boot at 03:00 the box is supposed to do as little as possible so queued commands are not received and executed during this boot.
  
−
For both the <code>&lt;tab&gt;</code> and <code>&lt;tabs&gt;</code> tags, parser functions ''can'' be used within the content of the tag, but ''not'' in the attributes. To use parser functions within the attributes, the <code>#tag:tabs</code> or <code>#tag:tab</code> parser functions should be used. The [[#Parser function|<code>#tab</code> parser function]] will also work, but since the only attributes it can define are the <code>index</code> and <code>name</code> attributes, these don't allow complete support.
+
The "reboot" command is not carried out if the box is currently recording or converting (convertfiles).
 +
Instead, the processing is stopped and not resumed until the box is no longer busy.
  
−
For example, this will not work:
+
If the system is currently running a convertfiles process when the disk contents is pushed to the server the .ts file size is taken from the .tmp file (the original) and the .tmp file is not sent to the server as the current .ts/.tmp files are transient.
  
−
<pre>
+
==== Comparision of Features Available to Supported PVRs ====
−
<tabs style="color:{{#if:{{{1|}}}|green|red}}">
+
 
−
<tab name="{{{1|}}}">Foo</tab>
+
Humax models supported are:
−
<tab name="{{{2|}}}">Bar</tab>
+
# HD-Fox T2
−
</tabs>
+
# HDR-Fox T2
−
</pre>
+
# Foxsat-HDR
−
But this will work:
+
 
−
<pre>
+
The following table compares the various features available to each model:
−
{{#tag:tabs|
+
 
−
{{#tag:tab|Foo|name={{{1|}}}}}
+
{| class="wikitable" style="margin: auto;"
−
{{#tab:{{{2|}}}|Bar}}
+
! Feature !! HD-Fox T2 !! HDR-Fox T2 !! Foxsat-HDR !! Notes
−
|style=color:{{#if:{{{1|}}}|green|red}} }}
+
|-
−
</pre>
+
| colspan="5"|'''Home:'''
 +
|-
 +
| Pending Schedule - Delete || Enabled || Enabled || Enabled
 +
|-
 +
| Pending Schedule - Enable/Disable AR || Enabled || Enabled || Disabled
 +
|-
 +
| Pending Schedule - Refresh Events || Enabled || Enabled || Disabled
 +
|-
 +
| Pending Schedule - Change Folder || Enabled || Enabled || Enabled
 +
|-
 +
| Active Schedule - Delete || Enabled || Enabled || Enabled
 +
|-
 +
| Active Schedule - Enable/Disable AR || Enabled || Enabled || Disabled
 +
|-
 +
| Active Schedule - Refresh Events || Enabled || Enabled || Disabled
 +
|-
 +
| Active Schedule - Change Folder || Enabled || Enabled || Enabled
 +
|-
 +
| colspan="5"|'''EPG:'''
 +
|-
 +
| EPG - Now/Next || Enabled || Enabled || Enabled
 +
|-
 +
| EPG - Grid Style || Enabled || Enabled || Enabled
 +
|-
 +
| EPG Searches || Enabled || Enabled || Enabled
 +
|-
 +
| Record Series || Enabled || Enabled || Enabled
 +
|-
 +
| Record Programme || Enabled || Enabled || Enabled
 +
|-
 +
| Set Reminder || Enabled || Enabled || Disabled
 +
|-
 +
| Recording Conflict Detection || Enabled || Enabled || Enabled
 +
|-
 +
| colspan="5"|'''Automatic Scheduling Feature:'''
 +
|-
 +
| Email Matching Events || Enabled || Enabled || Enabled
 +
|-
 +
| Email Matching Series || Enabled || Enabled || Enabled
 +
|-
 +
| Schedule Matching Events || Enabled || Enabled || Enabled
 +
|-
 +
| Schedule Matching Series || Enabled || Enabled || Enabled
 +
|-
 +
| Schedule Reminders for Matching Events || Enabled || Enabled || Disabled
 +
|-
 +
| colspan="5"|'''Visual page provides an alternative view of:'''
 +
|-
 +
| Scheduled Events || Enabled || Enabled || Enabled
 +
|-
 +
| Pending Events || Enabled || Enabled || Enabled
 +
|-
 +
| Conflicts || Enabled || Enabled || Enabled
 +
|-
 +
| colspan="5"|'''Recordings:'''
 +
|-
 +
| Display Recording Details || Enabled || Enabled || Enabled
 +
|-
 +
| Delete Recordings || Enabled || Enabled || Enabled
 +
|-
 +
| colspan="5"|'''Email Warnings:'''
 +
|-
 +
| Hard Disk Problem || Enabled || Enabled || Disabled
 +
|-
 +
| Upcoming Conflict(s) || Enabled || Enabled || Enabled
 +
|-
 +
| Failed Recording(s) || Enabled || Enabled || Enabled
 +
|-
 +
| colspan="5"|'''WebIf Packages:'''
 +
|-
 +
| recmon (Recording monitor) || Enabled || Enabled || Built in || Simplified recmon that'll report recorded programs<br />after a few hours (instead of immediately when they finish<br />recording as the T2 recmon package does)
 +
|-
 +
| Smartmontools (S.M.A.R.T. Status) || Enabled || Enabled || Disabled
 +
|}
 +
 
 +
==== Foxsat-HDR Port Differences ====
 +
Most of the features have been ported with the following variations owing to differences in the two platforms (hardware or TV platform, ie Freeview vs Freesat):
 +
* The custom channel names are used instead of default channel names.
 +
* The server's conflict management has been extended to warn about conflicts for concurrent recordings on incompatible channels when only one satellite feed is available and tuner 1 is looped to tuner 2.
 +
* Often the Housekeeper job removes scheduled split events so a method of converting these to one single manual event has been implemented. This currently only works on split events with two parts. Enabling this feature is controlled by the user.
 +
* The Freesat guide is flaky and often single events don't have an ECRID, eg Click and The Film Review on BBC NEWS, which means that it can be difficult to schedule them for recording. Instead, scheduled single events missing an ECRID are converted to manual single events.
 +
* Refresh of series events, skipping a series event, scheduling of reminders and changing scheduled events to use Accurate Recording are not supported by the Foxsat-HDR, hence these features are not provided on the RS server.
 +
* Foxsat-HDR doesn't have a concept of pending schedules. These are instead simulated by taking a snapshot of the schedules at boot time and comparing actual schedules against this. This method isn't foolproof (eg a recording scheduled directly on the box using the remote control handset is regarded as pending and if the aforementioned recording is removed through WebIf or Remote Scheduling this will not take effect until after a reboot and in this case we create a dummy reboot pending record), however it hasn't been possible to find another way of handling pending schedules.
 +
* Foxsat-HDR doesn't support the inotify interface in the Linux kernel so recmon hasn't been implemented. On the HDR-Fox T2 recmon is used to log a message on the box and the server as soon as a recording has finished, notifying that the given programme was recorded. Instead, a lazy recorded log mechanism has been implemented: Every few hours the recordings completed since the last reporting are logged on the box and the server, for instance:
 +
: <code>16/02/2017 07:11:56 - Recorded: BBC2 HD 15 Feb 2017 19:55:00-21:04:48 Trust Me, I'm a Doctor (69 minutes, 2.30 GiB)</code>
 +
: This means that recordings removed before the next reporting window will not be logged.
 +
* rs_process is not a Jim/TCL program as the original but has instead been rewritten entirely in C++ owing to Jim file name clashes, major platform differences and also differences in the Jim language support.
 +
* rs_process and rs binaries are installed in /opt/bin.
 +
* Multi-mode Recording isn't supported.
 +
* The Foxsat-HDR CFW doesn't have a S.M.A.R.T. interface, so no S.M.A.R.T. status is sent to/displayed by the RS server.
 +
* The Foxsat-HDR CPU is quite slow compared to the HDR-Fox T2, so the rs_process program (the main controller) detects whether the system is too busy to carry out any commands. Specifically, the program terminates almost instantly when it starts up and detects that the number of currently playing/recording programs is larger than the user-configurable '''Max. Running Playbacks+Recordings''' value (default set to 0), regarding the system as being too busy. This means that the server is only queried for queued commands if the system is non-busy. No efforts are made towards detecting playbacks over DLNA and/or SMB, only directly on the box.
 +
* For the same reason, only non-hidden channels are pushed to the server, in order to keep CPU/disk usage to a minimum. You control which channels are hidden in the WebIf Channel Editor.
 +
* Non-Freesat channels aren't supported with Remote Scheduling as most of the channels don't have EPG entries.
 +
* Foxsat-HDR doesn't show any actual padding assignment to the schedule so the pre/post padding shown by the RS server is a guestimate.
 +
* The BBC region is determined based on the name of channel 101 using the following mappings, no other channels are used for determining the region:
 +
 
 +
{| class="wikitable" style="margin: auto;"
 +
|-
 +
! Channel !! BBC Region !! Net
 +
|-
 +
| BBC One CI || Channel Islands || 501
 +
|-
 +
| BBC One East E || East (East) || 502
 +
|-
 +
| BBC One East W || East (West) || 503
 +
|-
 +
| BBC One E Mid || East Midlands || 504
 +
|-
 +
| BBC One Lon || London || 505
 +
|-
 +
| BBC One NE&C || North East & Cumbria || 506
 +
|-
 +
| BBC One N West || North West || 507
 +
|-
 +
| BBC One NI HD || Northern Ireland || 508
 +
|-
 +
| BBC One ScotHD || Scotland || 509
 +
|-
 +
| BBC One South || South || 510
 +
|-
 +
| BBC One S East || South (East) || 511
 +
|-
 +
| BBC One Oxford || South (Oxford) || 512
 +
|-
 +
| BBC One S West || South West || 513
 +
|-
 +
| BBC One Wal HD || Wales || 514
 +
|-
 +
| BBC One West || West || 515
 +
|-
 +
| BBC One W Mid || West Midlands || 516
 +
|-
 +
| BBC One Yorks || Yorkshire || 517
 +
|-
 +
| Other || Unknown || 518
 +
|}
 +
 
 +
{{#tag:tab|==== Known Issues ====
 +
===== HD/HDR-Fox T2 =====
 +
None.
 +
===== Foxsat-HDR =====
 +
* If you rename files to include special characters directly on the box with the remote control handset these characters are ASCII 8-bit, which means that the files will not be visible via WebIf, Samba and DLNA (although MediaTomb can be configured for this). Furthermore, they will disrupt the upload of disk content metadata to the RS server, which means that file names containing UTF-8 characters will not be handled correctly, eg you won't be able to delete them through the RS server.
 +
* Gives incorrect boot reason if booted from WebIf version 2.88. Perhaps a future version of WebIf will fix this.
 +
|collapsed=true|name="Known Issues"}}
 +
 
 +
==== New Terms ====
 +
;rs package
 +
: The Remote Scheduling program that runs on your Humax (which needs to be running the Customised Firmware including the Web Interface package).
 +
;https://rs.hpkg.tv/
 +
: The Remote Scheduling website that captures your schedule requirements and synchronises them to your Humax at home.
 +
 
 +
</tab><tab name="Getting Started">
 +
{{#tag:tab|== Getting Started on the HD/HDR-Fox T2 ==
 +
If you are not already running the Customised Firmware then please have a look at the Wiki and Black Hole's threads at the top of the https://hummy.tv/forum/forums/hd-hdr-fox-t2-customised-firmware.28/ Forum which covers how to get started and ready to move on.
 +
* Make sure you're running at least version 1.11 of the Customised Firmware (see Firmware Downloads).
 +
* Install the latest WebIf and rs packages.
 +
* See Wireless Users Notes below if you are connected via Wi-Fi.
 +
* Go to the Settings page in your device's local web interface and register with the remote scheduling service.
 +
* Wait for your initial password to arrive via email.
 +
* Access https://rs.hpkg.tv/ and accept the Terms & Conditions to get started.
 +
When you first log in there is some important information regarding what the site will and won't do and general Terms &amp; Conditions to agree to before you can proceed.
 +
This gets you to the Home page which, to begin with, will show you the existing schedule details from your Hummy.
 +
 
 +
===== Wireless Users Notes =====
 +
If your HD/HDR-Fox T2 is usually connected to your network via wireless, then it will not connect to the wireless network when it wakes up to make a recording.
 +
You can install the wireless-helper package to change this behaviour and increase the opportunities for your Humax to check for new recordings.
 +
The wireless-helper package currently only supports wireless networks using WPA or WPA2. It is planned to extend support to at least WEP in a future release.
 +
 
 +
===== Scheduling Sequence of Events =====
 +
If your Humax is in standby when a new recording is '''Queued''' using Remote Scheduling, your Humax will not be aware of the new request until it is taken out of stand-by,
 +
when your Humax awakes the recording's status will move to '''Pending''' and a further stand-by >> awake cycle is required in order to make the new recording request move to '''Active'''.
 +
It is possible to remove the need for a further stand-by >> awake cycle by requesting a 'Scheduled Reboot' in the RS Home page so that the Humax will perform two reboots in one.
 +
 
 +
===== Frequency of Wake-up =====
 +
To have the best chance of being able to successfully schedule a recording, you should set your HD/HDR-Fox T2 to wake up for 30 minutes at least once a day which is most easily done through the on-screen menus at Settings->Preferences->Time:
 +
 
 +
[[File:RS_Fox-T2-PowerOnTimer.png]]
 +
 
 +
In conjunction with the overnight update check, this ensures that your device checks for new recordings at least twice a day. Any recordings that you have set will also enable the Humax to check for updates.
 +
It is also possible to schedule additional wake-up/sleep periods via the RS portal using the Additional Commands option which is below the list of scheduled recordings.
 +
You may wish to do this when going away from home for an extended period for example.
 +
|collapsed=true|name="Getting Started on the HD/HDR-Fox T2"}}
 +
 
 +
{{#tag:tab|== Getting Started on the Foxsat-HDR ==
 +
If you are not already running the Customised Firmware then please have a look at https://www.avforums.com/threads/media-file-server-bundle-for-the-foxsat-hdr-release-4-part-6.2024876/ Forum which covers how to get started and ready to move on.
 +
* Make sure you're running at least version 4.1.3 of the Customised Firmware and at least version 2.88 of the WebIf.
 +
* Install the rs package.
 +
* Go to the Settings page in your device's local web interface and register with the remote scheduling service.
 +
* Wait for your initial password to arrive via email.
 +
* Access https://rs.hpkg.tv/ and accept the Terms & Conditions to get started.
 +
When you first log in there is some important information regarding what the site will and won't do and general Terms & Conditions to agree to before you can proceed.
 +
This gets you to the Home page which, to begin with, will show you the existing schedule details from your Hummy.
 +
The initial upload of your Hummy's channels, EPG and recording schedule can take several minutes, up to 10-15 minutes.
 +
You can limit the amount of data your Hummy sends by hiding the channels you don't need/use in the WebIf Channel Editor.
 +
 
 +
===== Scheduling Sequence of Events =====
 +
If your Humax is in standby when a new recording is '''Queued''' using Remote Scheduling, your Humax will not be aware of the new request until it is taken out of stand-by,
 +
when your Humax awakes the recording's status will move to '''Pending''' and a further stand-by >> awake cycle is required in order to make the new recording request move to '''Active'''.
 +
It is possible to remove the need for a further stand-by >> awake cycle by requesting a 'Scheduled Reboot' in the RS Home page so that the Humax will perform two reboots in one.
 +
 
 +
===== Frequency of Wake-up =====
 +
To have the best chance of being able to successfully schedule a recording, you should set your Humax to wake up for 30 minutes at least once a day which is most easily done through the on-screen menus at Menu->Settings->Time:
 +
 
 +
[[File:RS_Foxsat-HDR-PowerOnTimer.png]]
 +
 
 +
It is also possible to schedule additional wake-up/sleep periods through the on-screen menus at Schedule->Manual Watch reservation:
 +
 
 +
[[File:RS_Foxsat-HDR-WatchReservation.png]]
 +
 
 +
You may wish to do this when going away from home for an extended period for example.
 +
{{Note|Once again, please keep in mind how RS queries queued server commands in relation to the setting of '''Max. Running Playbacks+Recordings''' (default set to 0).  Specifically, if you expect RS to query and process queued server commands when the box is recording this doesn't happen unless '''Max. Running Playbacks+Recordings''' is set to a value larger than or equal to the number of recordings (plus playbacks) currently running on the box.}}
 +
 
 +
|collapsed=true|name="Getting Started on the Foxsat-HDR"}}
 +
 
 +
The Remote Scheduling server, which can be accessed from https://rs.hpkg.tv/ has a menu bar that remains on all pages:
 +
 
 +
[[File:RS_Menu.png]]
 +
 
 +
The various buttons are explained via the tabs at the top of this page.
 +
</tab><tab name="Home">
 +
This page describes the [[File:RS_Home-Button.png]] button on the [https://rs.hpkg.tv/ Remote Scheduling Web Site]
 +
----
 +
The following appear on the 'Home' page:
 +
 
 +
== Queued commands ==
 +
These are the things you have done on the web site. Set recordings, deleted schedules.
 +
At this stage they are only held on the website until the next 10 minute 'sweep' or your Hummy wakes up and check the site.
 +
 
 +
[[File:RS_Home-Queued.png]]
 +
 
 +
=== Deleting Queued Items ===
 +
You'll notice the Queued items list has a dustbin icon at the end of each line and this will remove the item from the queue and therefore won't sync with your Hummy.
 +
 
 +
== Pending Events ==
 +
 
 +
The Humax knows about these items, but it needs a reboot in order to save them into the schedule list on the Humax so that they actually work as expected.
 +
 
 +
[[File:RS_Home-Pending.png]]
 +
 
 +
=== Deleting Pending Events ===
 +
Click on the item in the Pending list and choose the <code>Cancel Event</code> option. This will create a cancellation line in the Queued commands list for each event to be deleted and will wait for the next sync between the site and your Humax.
 +
 
 +
Just like setting a recording the cancellation item will then sit in the Pending queue on your Humax until a restart takes place hence you can also send along a reboot action with the cancellation just like you can with a new recording. BUT like setting a recording, if your Humax is in standby it needs to wake up in order to sync in the first place. Less of a worry when deleting items as it's no problem to record something you now don't want any more (unless it conflicts with other recordings you want).
 +
 
 +
=== More Context Menu ===
 +
 
 +
===== HD/HDR Fox T2 =====
 +
Each event has the following items on the more context menu:
 +
 
 +
[[File:RS_Home-Active-More-T2.png]]
 +
 
 +
{| class="wikitable"
 +
|-
 +
| '''Delete''' || Delete the selected event.
 +
|-
 +
| '''Disable AR''' || Disable Accurate Recording (AR) for the selected event. See "Multi-mode Recording" below.
 +
|-
 +
| '''Refresh Events''' || The Fox T2 schedule database contains a binary field aulEventToRecordInfo.
 +
Refresh just blanks that field out on the next reboot which makes the Humax software re-populate it based on events in the current EPG.
 +
It's really a troubleshooting/diagnostic thing but can also be used to re-add any episodes which have been set up for skip.
 +
|-
 +
| '''Change Folder''' || Change the folder name to be used for series recodings.
 +
|}
 +
 
 +
===== Foxsat-HDR =====
 +
Each event has the following items on the more context menu:
 +
 
 +
[[File:RS_Home-Active-More-Foxsat.png]]
 +
{| class="wikitable"
 +
| '''Delete''' || Delete the selected event.
 +
|-
 +
| '''Change Folder''' || Change the folder name to be used for series recodings.
 +
|}
 +
 
 +
== Active Events ==
 +
These are all the items the Humax knows about AND will carry them out in full.
 +
 
 +
[[File:RS_Home-Active.png]]
 +
 
 +
=== Deleting Active Events ===
 +
Click on the item(s) in the Active list and then choose the [Delete Selected] button, or another option is to click [Delete] on the event's context menu.
 +
 
 +
To delete all finished events select the [Select Finished] button and then the [Delete Selected] button.
 +
 
 +
This will create a cancellation line in the Queued commands list for each event to be deleted and will wait for the next sync between the site and your Humax.
 +
 
 +
Just like setting a recording the cancellation item will then sit in the Pending queue on the Humax until a restart takes place hence you can also send along a reboot action with the cancellation just like you can with a new recording.  BUT like setting a recording, if your Humax is in standby it needs to wake up in order to sync in the first place. Less of a worry when deleting items as it's no problem to record something you now don't want any more (unless it conflicts with other recordings you want).
 +
 
 +
=== More Context Menu ===
 +
 
 +
===== HD/HDR-Fox-T2 =====
 +
See "Pending Events", "More Context Menu", "HD/HDR-Fox T2" which is the same.
 +
 
 +
===== Foxsat-HDR =====
 +
See "Pending Events", "More Context Menu", "Foxsat-HDR" which is the same.
 +
 
 +
== Additional Commands ==
 +
 
 +
===== HD/HDR-Fox T2 =====
 +
At the end of the Active list there are the following buttons:
 +
 
 +
[[File:RS_Home-Active-ScheduleReboot.png]] - Schedule a Reboot.
 +
 
 +
[[File:RS_Home-Active-ManualEvent.png]] - Create a Manual Event (a recording or reminder).
 +
 
 +
[[File:RS_Home-Active-RawDatabase.png]] - View the Raw Database.
 +
 
 +
===== Foxsat-HDR =====
 +
At the end of the Active list there are the following buttons:
 +
 
 +
[[File:RS_Home-Active-ScheduleReboot.png]] - Schedule a Reboot.
 +
 
 +
[[File:RS_Home-Active-ManualEvent.png]] - Create a Manual Event (recording only).
 +
 
 +
[[File:RS_Home-Active-RawDatabase.png]] - View the Raw Database.
 +
 
 +
== Recent Activity ==
 +
This is a simple view of an event log - it's not meant to be an exhaustive audit trail but it does confirm that things are happening and when they happened.
 +
 
 +
[[File:RS_Home-RecentActivity.png]]
 +
 
 +
You can see a more detailed list of every event tracked by clicking the <code>More</code> button and then even more detail via the <code>Show diagnostic entries</code> button.
 +
You can also delete the contents of the log file via the [Delete log entries] button.
 +
 
 +
== Top 10/500 list ==
 +
Clicking on a programme in the Top 10/500 list will display all broadcast times for that programme with the ability to set up a recording from there.
 +
 
 +
[[File:RS_Home-Top10500List.png]]
 +
 
 +
</tab><tab name="EPG">
 +
This page describes the [[File:RS_EPG-Button.png]] button on the [https://rs.hpkg.tv/ Remote Scheduling Web Site]
 +
--
 +
{{Note|Remote Scheduling doesn't automatically detect changes in the channel lineup or the WebIf Favourite lists.
 +
With any change to these you will have to run the following from a command line on the box in order to push the changes to the server.
 +
This applies to the HD/HDR-Fox T2 and Foxsat-HDR:
 +
 
 +
rs push channels
 +
}}
 +
 
 +
The following appear on the 'EPG' page:
 +
 
 +
== EPG - Now/Next ==
 +
 
 +
Clicking a specific programme displays a pop-up with details from the EPG (Electronic Programme Guide).
 +
Clicking the Channel name hyperlink will display all EPG entries for that channel.
 +
 
 +
[[File:RS_EPG-Guide-NowNext.png]]
 +
 
 +
You can switch to the grid display by clicking on the <code>Grid  EPG</code> button.
 +
 
 +
== EPG - Grid Style ==
 +
 
 +
Where programs are of a duration too short to display in the grid, the title hyperlink is truncated,
 +
which can be clicked to see the full programme EPG information in the same way as the Now/Next EPG function.
 +
Clicking the Channel name hyperlink will display all EPG entries for that channel.
 +
 
 +
[[File:RS_EPG-Guide-Grid.png]]
 +
 
 +
You can switch to the Now/Next display by clicking on the <code>Now/Next</code> button.
 +
 
 +
The cell width is adjustable to avoid left to right scrolling.
 +
 
 +
Note that the narrower settings for cell width will result in more programme titles not being displayed in full on the EPG 7-day page.
 +
But if you hover over the programme a pop-up window will display the full title and start/end times.
 +
Set a value that works best for you.  See the <code>Settings</code> button below.
 +
 
 +
The Navigation bar enables:
 +
* Selecting the time range displayed.
 +
* Selecting 'Now', the current day & time.
 +
* Selecting the required day.
 +
 
 +
[[File:RS_EPG-Navication.png|950px]]
  
−
=== Hotlinking tabs ===
+
== EPG Searches ==
 +
The EPG page provides 2 methods of searching for programs which covers the full 7 days.
  
−
It is possible to hotlink tabs the same way as hotlinking sections on pages. Simply put the tab label in the URL, and the page will automatically scroll to the top of the tab, and open the selected tab. This will always open only the very first tab that has the specified tab label (for example, if there are two tab boxes that both have a tab labelled "Tab 1", putting <code>#Tab_1</code> in the URL will scroll to the first one on the page). If there is already another element on the page that could be scrolled to, such as a page section, that other element will have priority, and the tab will not be focused.
+
==== 1. EPG Search ====
 +
Will search the EPG data for specific text in the programme title
 +
(and optionally the programme description).
 +
By default, results are filtered by the standard Channel List mechanism
 +
although this can be over-ridden in the case of a search.
  
−
== Toggle box ==
+
[[File:RS_EPG-Search.png|950px]]
  
−
=== Documentation ===
+
You can use the following operators and rules to refine/enhance the search results:
−
You can create a simple collapsible box by enclosing some content between <code><nowiki><tab> ... </tab></nowiki></code>. All content within the tags will be displayed within the toggle box.
+
{| class=wikitable
 +
| + || stands for AND
 +
|-
 +
| - || stands for NOT
 +
|-
 +
| no operator || implies OR
 +
|-
 +
| "two words" || in quotes must appear together
 +
|-
 +
| +doctor +(amy tardis) || containing 'doctor' and one of 'amy' or 'tardis'
 +
|}
 +
 
 +
==== 2. Content Type Searches ====
  
−
==== Available attributes: ====
+
Will search the EPG data on the content type (genre).
−
*<code>collapsed</code> - If this attribute is set, the toggle box will appear collapsed when the page loads. Otherwise it will be opened.
+
The results are filtered by the standard Channel List mechanism.
−
*<code>inline</code> - If this attribute is set, the toggle box can be placed within text without interrupting the flow of the text.
 
−
*<code>dropdown</code> - See [[#Dropdown menus]].
 
−
*Name attributes:
 
−
**<code>openname</code> - The label for the toggle box that indicates that clicking it will close the box. Default value is stored in the ''MediaWiki:tabs-toggle-open'' page.
 
−
**<code>closename</code> - Same as <code>openname</code>, but for closing the toggle box. Default is stored in ''MediaWiki:tabs-toggle-close''.
 
−
**<code>name</code> - If neither the <code>openname</code> and <code>closename</code> is defined, this value will be used for both states.
 
−
**If only one of the <code>openname</code> or <code>closename</code> attributes is defined, the other will take its value. If neither is defined, and the <code>name</code> attribute is also not defined, the default values are taken from the respective MediaWiki pages.
 
−
*<code>container</code> - Use this attribute to define any styles for the toggle box container. Styles defined here will only affect the content of the toggle box, not the label.
 
−
*Default HTML attributes:
 
−
**[https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes#title <code>title</code>] - Determines the tooltip shown when hovering over the box.
 
−
**[https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes#style <code>style</code>] - Use this attribute to define any styles for the box. This can also affect the box's label.
 
−
**[https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes#class <code>class</code>] - Adds classes to the box.
 
−
**[https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes#id <code>id</code>] - Adds an id to the box. This id must be unique on the page, as with any id.
 
  
−
=== Toggle box demos ===
+
[[File:RS_EPG-Search-Content.png|950px]]
  
−
==== Plain toggle box ====
+
== Scheduling a Recording ==
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
 
−
&lt;tab&gt;This toggle box has no attributes assigned to it.&lt;/tab&gt;
 
−
</pre></tab>
 
−
<tab>This toggle box has no attributes assigned to it.</tab>
 
  
−
==== Toggle box attributes ====
+
==== HD/HDR-Fox T2 ====
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
 
−
&lt;tab collapsed openname="Toggle" style="font-weight:bold;width:500px;" container="font-style:italic;" title="Example tooltip"&gt;
 
−
This toggle box has the following attributes defined:
 
−
*<code>collapsed</code> - By default, it is closed.
 
−
*<code>openname="Toggle"</code> - The label will show "Toggle" when it can be clicked to open the box. Since no <code>closename</code> attribute is defined, it defaults to "Toggle" too.
 
−
*<code>style="font-weight:bold;width:500px;"</code> - The whole toggle box will be bold, and have a width of 500px.
 
−
*<code>container="font-style:italic;"</code> - Only the contents of the toggle box will be italic.
 
−
*<code>title="Example tooltip"</code> - The tooltip that shows when hovering over this tab is defined via the <code>title</code> attribute.
 
−
&lt;/tab&gt;
 
−
</pre></tab>
 
  
−
<tab collapsed openname="Toggle" style="font-weight:bold;width:500px;" container="font-style:italic;" title="Example tooltip">
+
Click on the programme name that you want to schedule and you will get a dialogue box with more detailed programme info, plus buttons at the bottom to record the series, just the program, set a reminder or cancel.
−
This toggle box has the following attributes defined:
 
−
*<code>collapsed</code> - By default, it is closed.
 
−
*<code>openname="Toggle"</code> - The label will show "Toggle" when it can be clicked to open the box. Since no <code>closename</code> attribute is defined, it defaults to "Toggle" too.
 
−
*<code>style="font-weight:bold;width:500px;"</code> - The whole toggle box will be bold, and have a width of 500px.
 
−
*<code>container="font-style:italic;"</code> - Only the contents of the toggle box will be italic.
 
−
*<code>title="Example tooltip"</code> - The tooltip that shows when hovering over this tab is defined via the <code>title</code> attribute.
 
−
</tab>
 
  
−
==== Inline toggle boxes ====
+
[[File:RS_EPG-ProgDetails-T2.png]]
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
 
−
&lt;tab inline collapsed openname="Show" closename="Hide"&gt;
 
−
</pre></tab>
 
  
−
Here is an example of an inline toggle box. <tab inline collapsed openname="Show" closename="Hide">This togglebox is <code>inline</code> and <code>collapsed</code></tab> This toggle box has the attributes <code>openname="Show"</code> and <code>closename="Hide"</code> to change the default label text.
+
No recording option buttons will be displayed for programmes already scheduled for recording.
  
−
== Dropdown menus ==
+
Confirmation of the successful or otherwise setting of the recording will be shown in a banner at the top of the page:
−
=== Documentation ===
 
  
−
Dropdown menus are made by simply defining the <code>dropdown</code> attribute on a toggle box. They can be opened by either hovering over the label, or by clicking on the label to keep it opened even after moving away the cursor. Dropdown menus have an opening delay of 0.2 seconds built in to prevent accidental opening when hovering over the label, and to prevent accidental closing when accidentally moving the cursor off the dropdown. This delay is enough to prevent accidents like those, but is not enough to be bothersome.
+
[[File:RS_EPG-Confirmation.png]]
  
−
Dropdown menus are heavily based on the code for toggle boxes, so will also resemble them in many ways. There are a couple of quite distinct differences though.
+
Once this is done the Home page will now show a section at the top called Queued commands - at this stage these are only stored on the website awaiting a sync with your HD/HDR-Fox T2.
 +
Every 10-12 minutes or so (or on next reboot if the HD/HDR-Fox T2 is on standby) your HD/HDR-Fox T2 will contact the site to see if there is anything to sync and if there are items in Queued commands they will be picked up and copied over to your HD/HDR-Fox T2, and then they will appear in a Pending list.
 +
There is a 'last seen' time/date stamp at the top of the Home Page so you know if the site is seeing your Humax.
  
−
Since dropdown menus use the <code>&lt;menu&gt;</code> tag for their content, it is permitted to use <code>&lt;li&gt;</code> tags directly within the dropdown menu's contents. Any other content is also allowed.
+
Please note that due to the way the core HD/HDR-Fox T2 software works a restart of the HD/HDR-Fox T2 is then required in order for Pending items to actually take place.
 +
This is why items in the Queued commands list also have a button for <code>Schedule Reboot</code> - if you click this a reboot command is also sent to the HD/HDR-Fox T2 along with your recordings, and the HD/HDR-Fox T2 will restart itself shortly after synchronising the Queued commands thus ensuring your recordings/changes take place.
  
−
Dropdown menus will convert all list items and links placed within to specially styled list items. The only exception is that links ''only'' show as they normally do when placed within unordered lists ([http://www.mediawiki.org/wiki/Help:Lists any line starting with <code>*</code>]). In ordered lists, or outside list items, they take up the full list item. This is also the only difference between ordered and unordered lists.
+
[[File:RS_EPG-QueuedCommands.png]]
  
−
Any nested lists will be rendered as sub-menus in the dropdown menu. Nested lists are created by starting a line with [http://www.mediawiki.org/wiki/Help:Lists multiple <code>*</code> or <code>#</code> characters]. There is one limitation with this however: Individual nested lists can not alternate between ordered and unordered lists. Seperate levels can, however. For example, this is not allowed:
+
All HD/HDR-Fox T2 have an auto update task at 4:30 am every morning so at worst case they wake up every morning and any Pending Items already on the Humax will become active. Otherwise if you have the HD/HDR-Fox T2 on standby when you are not there you may want to schedule a power cycle or two so that the HD/HDR-Fox T2 wakes up and can pick up any Queued and/or Pending items and incorporate them fully into the schedule (there is a function for this under Additional Commands).
−
<pre>
 
−
*Menu item 1
 
−
*Menu item 2
 
−
**Sub-menu item 1
 
−
*#Sub-menu item 2
 
−
</pre>
 
−
But this is:
 
−
<pre>
 
−
*Menu item 1
 
−
#Menu item 2
 
−
#*Sub-menu item 1
 
−
#*Sub-menu item 2
 
−
#*#Sub-sub-menu item 1
 
−
</pre>
 
  
−
==== Available attributes: ====
+
You can force a sync from the command line with:
 +
/mod/sbin/rs_process now
 +
To push the schedule from the command line use:
 +
rs push
 +
Don't forget that if you have the HD/HDR-Fox T2 on standby when you make the schedule then it'll need one wake up to pick up the scheduled item(s), then another in order to successfully incorporate them into the schedule on the HD/HDR-Fox T2. You can send the second reboot along with the schedule but the first has to already be defined on the HD/HDR-Fox T2 (either the built in daily 4:30am auto update or wake up/sleep cycles you can program yourself).
  
−
*All attributes that are available for toggle boxes
+
==== Foxsat-HDR ====
−
*<code>dropdown</code> - Must be defined for the toggle box to become a dropdown menu.
 
−
*<code>openname</code> and <code>closename</code> - These attributes are identical to the <code>name</code> attribute in dropdown menus. It is not possible to let the dropdown switch between 2 values. If the <code>openname</code> attribute is set, that value will be used as label, otherwise the <code>closename</code> value is used, and if neither of those values is set, the <code>name</code> value is used.
 
−
*<code>bgcolor</code> - Because of how the background-color styling for dropdown works (background styles are applied to all items within dropdowns, otherwise they would become transparent), background colors need to be defined seperately. This must be done in the <code>bgcolor</code> attribute. This attribute works exactly the same as the <code>background-color</code> style in CSS. This defaults to the value defined in ''MediaWiki:tabs-dropdown-bgcolor''.
 
  
−
=== Dropdown demos ===
+
Click on the programme name that you want to schedule and you will get a dialogue box with more detailed programme info, plus buttons at the bottom to record the series, just the programme or cancel.
  
−
==== Dropdown without lists ====
+
[[File:RS_EPG-ProgDetails-Foxsat.png]]
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
 
−
&lt;tab dropdown style="width:300pt" openname="Click/hover to show" closename="Showing..."&gt;
 
−
This dropdown contains no lists, so it will not have any of the styling designed for dropdowns. It does work as it normally would though.
 
  
−
This dropdown also has its <code>style</code> attribute set to <code>style="width:300pt"</code>. It also has different <code>openname</code> and <code>closename</code> attributes, so it defaults to the <code>openname</code> value.
+
No recording option buttons will be displayed for programmes already scheduled for recording.
−
&lt;/tab&gt;
 
−
</pre></tab>
 
  
−
<tab dropdown style="width:300pt" openname="Click/hover to show" closename="Showing...">
+
Confirmation of the successful or otherwise setting of the recording will be shown in a banner at the top of the page:
−
This dropdown contains no lists, so it will not have any of the styling designed for dropdowns. It does work as it normally would though.
 
  
−
This dropdown also has its <code>style</code> attribute set to <code>style="width:300pt"</code>. It also has different <code>openname</code> and <code>closename</code> attributes, so it defaults to the <code>openname</code> value.
+
[[File:RS_EPG-Confirmation.png]]
−
</tab>
 
  
−
==== Background-color for dropdowns ====
+
Once this is done the Home page will now show a section at the top called Queued commands - at this stage these are only stored on the website awaiting a sync with your Foxsat-HDR.
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
+
Every 10-12 minutes or so (or on next reboot if the Foxsat-HDR is on standby) your Foxsat-HDR will contact the site to see if there is anything to sync and if there are items in Queued commands they will be picked up and copied over to your Foxsat-HDR, and then they will appear in a Pending list.
−
&lt;tab dropdown bgcolor="salmon}body{font-weight:bold;"&gt;
+
There is a 'last seen' time/date stamp at the top of the Home Page so you know if the site is seeing your Humax.
−
This tab has a its <code>bgcolor</code> attribute set to <code>bgcolor="salmon"</code>.
 
−
Just defining a <code>background-color</code> style would not work.
 
−
&lt;/tab&gt;
 
−
</pre></tab>
 
  
−
<tab dropdown bgcolor="salmon}body{font-weight:bold;">
+
Please note that due to the way the core Foxsat-HDR software works a restart of the Humax is then required in order for Pending items to actually take place.
−
This tab has a its <code>bgcolor</code> attribute set to <code>bgcolor="salmon"</code>.
+
This is why items in the Queued commands list also have a button for <code>Schedule Reboot</code> - if you click this a reboot command is also sent to the Humax along with your recordings, and the Foxsat-HDR will restart itself shortly after synchronising the Queued commands thus ensuring your recordings/changes take place.
−
Just defining a <code>background-color</code> style would not work.
 
−
</tab>
 
  
−
==== Lists and links ====
+
[[File:RS_EPG-QueuedCommands.png]]
−
Here you can see the difference between unordered and ordered lists within dropdowns. The appearance of both does not change, but the behaviour of links within them does.
 
  
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
+
You need to have set up at least one daily wake up/sleep cycle and any Pending Items already on the Foxsat-HDR will become active. Otherwise if you have the Foxsat-HDR on standby when you are not there you may want to schedule a power cycle or two so that the Foxsat-HDR wakes up and can pick up any Queued and/or Pending items and incorporate them fully into the schedule.
−
&lt;tab dropdown&gt;
 
−
#The first 2 items use ordered lists, which will show links as list items too.
 
−
#[[#Dropdown demos|Example link]]
 
−
*From here on this dropdown uses ordered lists, so links are shown within text.
 
−
*See this [[#Dropdown demos|example link]].
 
−
*Any links in dropdown menus placed outside lists will also be rendered as list items, like the following link:
 
−
[[#Dropdown demos|Example link]]
 
−
&lt;/tab&gt;
 
−
</pre></tab>
 
  
−
<tab dropdown>
+
You can force a sync from the command line with:
−
#The first 2 items use ordered lists, which will show links as list items too.
+
rs_process now
−
#[[#Dropdown demos|Example link]]
+
To push the schedule from the command line use:
−
*From here on this dropdown uses ordered lists, so links are shown within text.
+
rs push
−
*See this [[#Dropdown demos|example link]].
+
Don't forget that if you have the Foxsat-HDR on standby when you make the schedule then it'll need one wake up to pick up the scheduled item(s), then another in order to successfully incorporate them into the schedule on the Foxsat-HDR. You can send the second reboot along with the schedule but the first has to already be defined on the Foxsat-HDR, see 'Getting Started'-> 'Frequency of Wake-up'-> 'Foxsat-HDR' above.
−
*Any links in dropdown menus placed outside lists will also be rendered as list items, like the following link:
 
−
[[#Dropdown demos|Example link]]
 
−
</tab>
 
  
−
==== Inline dropdowns ====
+
====== Reminder ======
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
+
* Queued commands are not received and executed when the number of currently playing/recording programs is larger than the user-configurable '''Max. Running Playbacks+Recordings''' value (default set to 0), regarding the system as being too busy.
−
&lt;tab dropdown inline&gt;
+
* During the Housekeeper boot at 03:00 the box is supposed to do as little as possible so Queued commands are not received and executed during this boot.
−
*You can do anything you'd normally do in a dropdown
 
−
*This box will fit in with the text.
 
−
&lt;/tab&gt;
 
−
</pre></tab>
 
  
−
It is also possible to create inline dropdowns: <tab dropdown inline>
+
== Recording Conflict Detection ==
−
*You can do anything you'd normally do in a dropdown
 
−
*This box will fit in with the text.
 
−
</tab>. This will also not interrupt the flow of the text.
 
  
−
==== Nested lists ====
+
The scheduling mechanism will check for recording conflicts each time a new recording is scheduled.
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
 
−
&lt;tab dropdown&gt;
 
−
*This dropdown menu demonstrates dropdown menus with multiple levels.
 
−
*Hovering over a list item with further lists nested within it will cause the next level to show up
 
−
*Hover over this item to see
 
−
**This list now shows up.
 
−
**Nested lists can also contain even more lists
 
−
**See this item for example
 
−
***This is a third level menu
 
−
**This can go on for any amount of levels.
 
−
*Multiple sub-menus are also allowed
 
−
**Such as this one.
 
−
&lt;/tab&gt;
 
−
</pre></tab>
 
  
−
<tab dropdown>
+
If a schedule conflict is detected, all conflicting recordings will be displayed in the pop-up window:
−
*This dropdown menu demonstrates dropdown menus with multiple levels.
 
−
*Hovering over a list item with further lists nested within it will cause the next level to show up
 
−
*Hover over this item to see
 
−
**This list now shows up.
 
−
**Nested lists can also contain even more lists
 
−
**See this item for example
 
−
***This is a third level menu
 
−
**This can go on for any amount of levels.
 
−
*Multiple sub-menus are also allowed
 
−
**Such as this one.
 
−
</tab>
 
  
−
==== Alternating ordered and unordered lists ====
+
[[File:RS_EPG-ConflictDetection.png]]
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
 
−
&lt;tab dropdown&gt;
 
−
*It is possible to alternate between ordered and unordered lists, but not within sub-menus.
 
−
*The first 2 items are unordered list items
 
−
#And this is an ordered list item
 
−
#*This is an unordered list item again
 
−
#*This also ''has'' to be an unordered list item
 
−
#*#This can be an ordered list item again though
 
−
#*#But then this also has to be ordered.
 
−
#*Within an individual sub-menu, it is not possible to change between ordered and unordered list items
 
−
&lt;/tab&gt;
 
−
</pre></tab>
 
  
−
<tab dropdown>
+
{{Note|For this to work correctly on the '''Foxsat-HDR''' you must first set the number of satellite feeds available to your Foxsat-HDR in the 'RemoteScheduling Plug-in Settings' section on the 'Settings' page of the Web Interface.}}
−
*It is possible to alternate between ordered and unordered lists, but not within sub-menus.
 
−
*The first 2 items are unordered list items
 
−
#And this is an ordered list item
 
−
#*This is an unordered list item again
 
−
#*This also ''has'' to be an unordered list item
 
−
#*#This can be an ordered list item again though
 
−
#*#But then this also has to be ordered.
 
−
#*Within an individual sub-menu, it is not possible to change between ordered and unordered list items
 
−
</tab>
 
  
 +
</tab><tab name="Auto">
 +
This page describes the [[File:RS_Auto-Button.png]] button on the [https://rs.hpkg.tv/ Remote Scheduling Web Site]
 
----
 
----
 +
The Remote Scheduling Portal includes an automatic scheduling feature.
 +
This allows you to set up rules which are matched against the EPG data as it comes in eight days ahead.
 +
When a match is found, it's possible to either have it send you an email message, or to attempt to automatically schedule the recording on your behalf.
 +
 +
There are 2 types of rules:
 +
 +
== Standard Rules ==
 +
 +
[[File:RS_Auto-StandardRules.png|950px]]
 +
 +
==== Add New Rule ====
 +
[[File:RS_Auto-Standard-Add.png]]
 +
;Type
 +
: The type of rule, either Email which causes emails to be sent when matches are found or Schedule which attempts to schedule any events found and also emails notification of the schedule.
 +
;Subtype
 +
: Whether to treat matches as single events or, if possible, series.
 +
;Date
 +
: If specified, only match events which occur on this date.
 +
;Day
 +
: If specified, only match events which occur on this day or set of days (e.g. weekdays). Note that if you use this to only schedule events occurring on particular days then you should most likely be using the Schedule Events option rather than Schedule Series. If you schedule the series then the day restriction will only apply to the original matching event - you will get the rest of the series regardless of the day.
 +
;Start Time
 +
: If specified, only match events which start between the times provided.
 +
;Channel
 +
: If specified, only match events shown on this channel.
 +
;Content Type
 +
: If specified, only match events with this content type (as set by the content provider).
 +
;Name
 +
: Part of the EPG name to match. This supports wild cards, '*' for 0 or more characters, '?' for exactly one character. It is matched against the EPG as a substring.
 +
;Synopsis
 +
: Part of the EPG synopsis. This supports the same wild cards as name.
 +
 +
==== More Context Menu ====
 +
Each rule has the following items on the more context menu:
 +
[[File:RS_Auto-Standard-More.png]]
 +
{| class=wikitable
 +
| '''Edit''' || Allows changes to an existing Auto search.
 +
|-
 +
| '''Delete''' || Removes a single standard rule.
 +
|-
 +
| '''Disable/Enable Rule''' || Allows the rule to be disabled/enabled.
 +
|-
 +
| '''Convert to Advanced''' || Converts standard to advanced rule.
 +
|-
 +
| '''Show Matching Events''' || Displays a current search results for the current 'Auto' search.
 +
|-
 +
| '''Reset Matched Events''' || Enables all previously found CRID's for the current search to be emailed / scheduled again.
 +
|}
 +
 +
=== Examples ===
 +
 +
'''Example 1'''
 +
:[[File:RS_Auto-Standard-Example1.png]]
 +
:Record all Harry Potter films that pop up in the EPG and email notification.
 +
 +
''' Example 2'''
 +
:[[File:RS_Auto-Standard-Example2.png]]
 +
:Record any episodes of Doctor Who showing on Christmas Day 2017 on BBC ONE HD and email notification.
 +
 +
'''Example 3'''
 +
:[[File:RS_Auto-Standard-Example3.png]]
 +
:Record the Formula 1 highlights from Channel 4 HD and email notification.
 +
:Series link doesn't work reliably for this and often pulls in practice sessions, qualifying and the race. It rarely records subsequent races.
 +
 +
'''Example 4'''
 +
:[[File:RS_Auto-Standard-Example4.png]]
 +
:Send an email alert when any James Bond films, not featuring Pierce Brosnan are found in the EPG.
 +
:NOTE:- the use of '+' and '-' forces a whole word search, with '*' as a wild card e.g. -bros*
 +
 +
'''Notes:'''
 +
:* In example 4 above the -brosnan MUST follow a +keyword, a stand alone -keyword will always find zero matches.
 +
:* If Type = Schedule the item will be scheduled and an email notification will be sent with a link to the RS EPG entry.
 +
:* If Type = Email you will only be sent an email notification with an RS EPG link, so that a manual recording can be selected.
 +
 +
== Advanced Rules ==
 +
: [[File:RS_Auto-AdvancedRules.png]]
 +
 +
==== Add Rule or Add New Entry ====
 +
 +
;Add Description
 +
: [[File:RS_Auto-Advanced-Add1.png]]
 +
: Enter description for rule and after you click on the [Create Rule] button the following will be created:
 +
: [[File:RS_Auto-Advanced-Add2.png]]
 +
 +
;Add Condition(s)
 +
: At the left hand end of the rule there is a [+] icon which allows a new condition to be added:
 +
: [[File:RS_Auto-Advanced-Add3.png]]
 +
: The "Negate?" tick box negates the condition so that if you selected 'Channel name is' and then tick the 'negate' box, you end up with 'Channel name is NOT'.
 +
: Select the condition required and after you click on the [Add Condition] button the following will be created:
 +
: [[File:RS_Auto-Advanced-Add4.png]]
 +
: At the end of the "If/And" part of the condition there is an edit icon which allows the value(s) to be changed:
 +
: [[File:RS_Auto-Advanced-Add5.png]]
 +
 +
==== HD/HDR-Fox T2 ====
 +
At the end of the "Then" part of the condition there is an edit icon which allows the value to be changed:
  
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
+
: [[File:RS_Auto-Advanced-Add6-T2.png]]
−
&lt;tab dropdown&gt;
 
−
*This item is in an unordered list, so it allows [[#Dropdown demos|in-line linking]].
 
−
#This item and the next one are in an ordered list, so they turn links into list-items
 
−
#[[#Dropdown demos|List-item links]]
 
−
#*...with a sub-menu that uses unordered lists again, so allows [[#Dropdown demos|in-line linking]] again.
 
−
#*#And this sub-menu again creates...
 
−
#*#[[#Dropdown demos|...list-item links]]
 
−
&lt;/tab&gt;
 
−
</pre></tab>
 
  
−
<tab dropdown>
+
==== Foxsat-HDR ====
−
*This item is in an unordered list, so it allows [[#Dropdown demos|in-line linking]].
+
At the end of the "Then" part of the condition there is an edit icon which allows the value to be changed:
−
#This item and the next one are in an ordered list, so they turn links into list-items
+
 
−
#[[#Dropdown demos|List-item links]]
+
: [[File:RS_Auto-Advanced-Add6-Foxsat.png]]
−
#*...with a sub-menu that uses unordered lists again, so allows [[#Dropdown demos|in-line linking]] again.
+
 
−
#*#And this sub-menu again creates...
+
You can add more condition(s) as required.
−
#*#[[#Dropdown demos|...list-item links]]
 
−
</tab>
 
  
−
== Tab menus ==
+
==== Quick Add ====
−
=== Documentation ===
+
: [[File:RS_Auto-Advanced-QuickAdd.png]]
  
−
Tab menus can be used to make it possible to switch between different layouts. Anything within <code><nowiki><tabs> ... </tabs></nowiki></code> tags is rendered as a tab menu. Individual tabs are then defined via a <code>&lt;tab&gt;</code> tag.
+
==== Save Changes ====
 +
To save the rule(s) after they have been created, edited or deleted click on the <code>Save changes</code> button.
  
−
==== Available attributes ====
+
==== Discard Changes ====
−
;<code>&lt;tabs&gt;</code>
+
To discard changes to rule(s) after they have been created, edited or deleted click on the <code>Discard changes</code> button.
−
*<code>container</code> - Use this attribute to define any styles for the tabs container. Styles defined here will only affect the container of the tabs, not the labels.
+
{{Note|This only applies to changes made since the last 'Save changes' was carried out.}}
−
*<code>plain</code> - If this attribute is set, the tab interface will be a much more plain layout, without a border around the container, and with the tab labels just being buttons above it, instead of the typical tab layout. This can be used to get more freedom in styling the interface.
 
−
;<code>&lt;tab&gt;</code>
 
−
*<code>inline</code> - If this attribute is set, the tab's contents can be placed within text without interrupting the flow of the text. The difference between this and the default state of <code>display:inline-block</code> is that with <code>inline-block</code>, the tab's contents are forced to a new line when placed at the end of a new line, when not the whole of the tab's contents fit on the same line. <code>inline</code> tabs however will use up any space that's left at the end of the line, and fit in with the normal flow of the text just like normal text.
 
−
*<code>block</code> - Converts the tab's contents to a block element. This can be used to assure the tab's contents will be displayed as a block instead of an inline-block, in cases where the tab's contents should not be placed within a line of text. When both the <code>block</code> and <code>inline</code> attributes are available, the <code>inline</code> attribute will be ignored.
 
−
*Name attributes:
 
−
**<code>index</code> - This will determine the index of the tab. This only works if the entered index is already the index of a defined tab. Otherwise, this attribute is ignored. If no valid index or matching name attributes are defined, the index is automatically set to be the next in the list of tabs.
 
−
**<code>name</code> - This attribute is used to define the text the label shows for the tab. If the entered name already exists within the tab, the contents of the <code>&lt;tab&gt;</code> tag are automatically assigned to the existing tab. This also means no two tabs can have an identical label. This attribute will be ignored if the <code>index</code> attribute already refers to an existing tab. Whitespace is automatically removed from the start and end of this attribute's value.
 
−
;Both
 
−
*Default HTML attributes:
 
−
**[https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes#title <code>title</code>] - Determines the tooltip shown when hovering over the box.
 
−
**[https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes#style <code>style</code>] - Use this attribute to define any styles for the box. This can also affect the box's label.
 
−
**[https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes#class <code>class</code>] - Adds classes to the box.
 
−
**[https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes#id <code>id</code>] - Adds an id to the box. This id must be unique on the page, as with any id.
 
  
−
==== Self-closing tabs ====
+
==== Matching Events ====
 +
: [[File:RS_Auto-Advanced-MatchingEvents.png]]
  
−
Self-closing tabs can be used to define a list of tabs at the top of the tab menu, for later use via the <code>index</code> attribute. Self-closing tabs only have an effect when a name is defined, and no (valid) index is defined. The syntax for self-closing tabs is <code>&lt;tab name="name" /&gt;</code>
+
At the end of each rule there is the [Matching Events] button which will display any matching events found.
  
−
==== Parser function ====
+
==== Options ====
 +
At the end of each rule there are the following icons:
  
−
As an alternative for the tab tag, the <code><nowiki>{{#tab:}}</nowiki></code> parser function can also be used to simplify the syntax for tabs. The syntax for this parser function allows the following syntaxes:
+
: [[File:RS_Auto-Advanced-Options.png]]
  
−
{|class="wikitable"
+
{| class=wikitable
−
!style="width: 50%"|Code
+
| [[File:RS_Auto-Advanced-Options-Refresh.png]] || '''Refresh Rule''' || Enables all previously found CRID's for the current search to be emailed / scheduled again.
−
!style="width: 50%"|Description
 
−
|-
 
−
|<code style="color: green;"><nowiki>{{#tab:name1/#1, name2/#2, etc|content 1|content 2|etc}}</nowiki></code>
 
−
|Each of the defined names will be set as <code>name</code> or <code>index</code> attributes, respectively.
 
−
*All values that are prefixed with <code>#</code>, and are numbers only will be recognised as indices. For indices, surrounding whitespace is allowed, but internal whitespace or any non-number characters such as decimal points aren't.
 
−
*If these condtions are not met, the entered value is interpreted as a name.
 
−
*If the entered value contains only whitespace or is left empty, the index of that tab is automatically calculated.
 
 
|-
 
|-
−
|<code style="color: green;"><nowiki>{{#tab:|content 1|content 2|etc}}</nowiki></code>
+
| [[File:RS_Auto-Advanced-Options-Edit.png]] || '''Edit Rule Text''' || Allows changes to the selected rule text.
−
|No indices or names are defined here, so the indices of the tabs within the parser functions are automatically assigned as index.
 
 
|-
 
|-
−
|<code style="color: green;"><nowiki>{{#tab:name1/#1, , name3/#3, name4/#4|content 1|content 2| |content 4}}</nowiki></code>
+
| [[File:RS_Auto-Advanced-Options-Enable.png]] || '''Enable/Disable Rule''' || Allows the rule to be enabled/disabled.
−
|The second tab will automatically get <code>index="2"</code>, and the third tab will have no content:
 
−
*If the third tab has a name defined in the list of names, then it becomes a [[#Self-closing tabs|self-closing tag]].
 
−
*If the third tab has an index defined, this tab is skipped, and no output is generated for this tab.
 
 
|-
 
|-
−
|<code style="color: green;"><nowiki>{{#tab:name1, name2, name3...}}</nowiki></code>
+
| [[File:RS_Auto-Advanced-Options-Delete.png]] || '''Delete Rule''' || Removes the selected advanced rule.
−
|This will define three tabs, "name1", "name2" and "name3" using the [[#Self-closing tabs|self-closing syntax]].
 
 
|-
 
|-
−
|<code style="color: green;"><nowiki>{{#tab:#3, #5|content 3|content 5}}</nowiki></code>
+
| [[File:RS_Auto-Advanced-Options-Duplicate.png]] || '''Duplicate Rule''' || Duplicates an existing search that can then be modified.
−
|This will add "content 3" to the rest of the contents of tab 3, and "content 5" to the rest of the content of tab 5.
 
 
|-
 
|-
−
|<code style="color: green;"><nowiki>{{#tab:name1/#1, etc|content 1|$1}}</nowiki></code>
+
| [[File:RS_Auto-Advanced-Options-MoveUp.png]] || '''Move Rule Up''' || Moves the selected rule up in the list.
−
|When the content of a tab is <code>$n</code> (where <code>n</code> is the place of the tab in the parser function), the contents of that tab are copied over to the tab that has <code>$n</code> in it. For this to work, the following conditions must be met:
 
−
*The tab must contain nothing other than a dollar sign and a number directly after it. Surrounding whitespace is allowed.
 
−
*The parser function's <code>n</code>th parameter must be defined. <code>n</code> may also be bigger than the current tab index (so, <code><nowiki>{{#tab:#3,#5|$2|Hi}}</nowiki></code> would put "Hi" in both tab 3 and 5).
 
−
*The parser function's <code>n</code>th parameter must contain something other than just whitespace. Recursive references won't work, so <code><nowiki>{{#tab:|Hi|$1|$2}}</nowiki></code> will put "Hi" in tabs 1 and 2, and the literal text "$1" in tab 3.
 
 
|-
 
|-
−
|<code style="color: green;"><nowiki>{{#tab:|3=content 3| 5 = content 5}}</nowiki></code>
+
| [[File:RS_Auto-Advanced-Options-MoveDown.png]] || '''Move Rule Down''' || Moves the selected rule down in the list.
−
|You can also refer to the tab '''index''' (so not the tab name) by putting the tab index before an equals sign (<code>=</code>) in the parameter. This will not work for tab names, to prevent unwanted effects caused by equals signs inside the tab (which then would cause all of the preceding text to be interpreted as a tab name). This syntax will override an index or name specified using the syntax of the above code examples.
 
 
|}
 
|}
  
−
=== Demos ===
+
==== Examples ====
 +
 
 +
'''Example 1'''
 +
:[[File:RS_Auto-Advanced-Example1.png]]
 +
:
 +
:Record all Harry Potter films that pop up in the EPG and email notification.
  
−
==== Naming and reusing tabs, and default text ====
+
'''Example 2'''
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
+
:[[File:RS_Auto-Advanced-Example2.png]]
−
&lt;tabs&gt;
+
:
−
&lt;tab name="First" style="border:1px solid black;"&gt;This tab has a defined <code>name</code>. It also has a <code>style</code> attribute set to <code>style="border:1px solid black;"</code>.&lt;/tab&gt;
+
:Record any episodes of Doctor Who showing on Christmas Day 2017 on BBC ONE HD and email notification.
−
&lt;tab name="Second" style="background:salmon;"&gt;This tab also has a defined <code>name</code> attribute, and its <code>style</code> attribute set to <code>style="background:salmon;"</code>.&lt;/tab&gt;
+
 
−
&lt;tab&gt;This tab has no attributes defined. Its name is automatically generated based on its position.&lt;/tab&gt;
+
'''Example 3'''
−
&lt;tab index="1"&gt;This is a seperate tab. It has a defined <code>index</code> attribute with value "1". This makes it also show when the first tab is selected.&lt;/tab&gt;
+
:[[File:RS_Auto-Advanced-Example3.png]]
−
&lt;tab name="Second"&gt;This is a seperate tab. It has a defined <code>name</code> attribute, with a value equal to that of the second tab ("Second"). It therefore also shows when the second tab is opened.&lt;/tab&gt;
+
:
 +
:Record the Formula 1 highlights from Channel 4 HD and email notification.
 +
:Series link doesn't work reliably for this and often pulls in practice sessions, qualifying and the race. It rarely records subsequent races.
 +
 
 +
'''Example 4'''
 +
:[[File:RS_Auto-Advanced-Example4.png]]
 +
:
 +
:Send an email alert when any James Bond films, not featuring Pierce Brosnan are found in the EPG.
 +
:NOTE:- the use of '+' and '-' forces a whole word search, with '*' as a wild card e.g. -bros*
 +
 
 +
</tab><tab name="Visual">
 +
This page describes the [[File:RS_Visual-Button.png]] button on the [https://rs.hpkg.tv/ Remote Scheduling Web Site]
 
----
 
----
−
This line of text will show for every tab you view. It is not placed within <code>&lt;tab&gt; tags, and can be used as default content for the tab menu.
+
The Remote Scheduling Visual page provides an alternative view of scheduled and pending events, it also clearly displays any outstanding conflicts:
−
&lt;/tabs&gt;
+
 
−
</pre></tab>
+
[[File:RS_Visual.png|950px]]
  
−
<tabs>
+
</tab><tab name="Disk">
−
<tab name="First" style="border:1px solid black;">This tab has a defined <code>name</code>. It also has a <code>style</code> attribute set to <code>style="border:1px solid black;"</code>.</tab>
+
This page describes the [[File:RS_Disk-Button.png]] button on the [https://rs.hpkg.tv/ Remote Scheduling Web Site]
−
<tab name="Second" style="background:salmon;">This tab also has a defined <code>name</code> attribute, and its <code>style</code> attribute set to <code>style="background:salmon;"</code>.</tab>
 
−
<tab>This tab has no attributes defined. Its name is automatically generated based on its position.</tab>
 
−
<tab index="1">This is a seperate tab. It has a defined <code>index</code> attribute with value "1". This makes it also show when the first tab is selected.</tab>
 
−
<tab name="Second">This is a seperate tab. It has a defined <code>name</code> attribute, with a value equal to that of the second tab ("Second"). It therefore also shows when the second tab is opened.</tab>
 
 
----
 
----
−
This line of text will show for every tab you view. It is not placed within <code>&lt;tab&gt; tags, and can be used as default content for the tab menu.
+
== HD/HDR-Fox T2 ==
−
</tabs>
 
  
−
==== <code>block</code> and <code>inline</code> tabs ====
+
Clicking in the 'Pie Chart' symbol on any page will pull up a page showing your recordings.
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
+
From here it is possible to set up a delete command that will be carried out the next time your Humax is in contact with the RS server.
−
&lt;tabs&gt;
 
−
&lt;tab name="Default 1" style="background:lightgreen;"&gt;First tab.&lt;/tab&gt;
 
−
&lt;tab name="Default 2" style="background:lightgreen;"&gt;Second tab.&lt;/tab&gt;
 
−
&lt;tab name="Inline" style="background:salmon;"&gt;Third tab.&lt;/tab&gt;
 
−
&lt;tab name="Block" style="background:royalblue;"&gt;Fourth tab.&lt;/tab&gt;
 
−
&lt;tab index="1"&gt;This is a seperate tab. It demonstrates what happens if a tab has no <code>inline</code> or <code>block</code> attributes defined. If the tab contains a lot of text, it will automatically be forced to a new line, despite extra space being available at the end of the previous line.&lt;/tab&gt;
 
−
&lt;tab index="2"&gt;This seperate tab isn't forced to a new line, since it's short enough.&lt;/tab&gt;
 
−
&lt;tab index="3" inline&gt;This is a seperate tab that has an <code>inline</code> attribute defined. It will fit in with the text as normal text would, and it fills up any space that is left available after the previous line. This makes tabs with <code>inline</code> attributes a bit better at fitting in with the flow of text.&lt;/tab&gt;
 
−
&lt;tab index="4" block&gt;Despite fitting on the previous line, the <code>block</code> attribute forces this seperate tab to a new line&lt;/tab&gt;
 
−
&lt;/tabs&gt;
 
−
</pre></tab>
 
  
−
<tabs>
+
[[File:RS_Disk-Details-T2.png]]
−
<tab name="Default 1" style="background:lightgreen;">First tab.</tab>
 
−
<tab name="Default 2" style="background:lightgreen;">Second tab.</tab>
 
−
<tab name="Inline" style="background:salmon;">Third tab.</tab>
 
−
<tab name="Block" style="background:royalblue;">Fourth tab.</tab>
 
−
<tab index="1">This is a seperate tab. It demonstrates what happens if a tab has no <code>inline</code> or <code>block</code> attributes defined. If the tab contains a lot of text, it will automatically be forced to a new line, despite extra space being available at the end of the previous line.</tab>
 
−
<tab index="2">This seperate tab isn't forced to a new line, since it's short enough.</tab>
 
−
<tab index="3" inline>This is a seperate tab that has an <code>inline</code> attribute defined. It will fit in with the text as normal text would, and it fills up any space that is left available after the previous line. This makes tabs with <code>inline</code> attributes a bit better at fitting in with the flow of text.</tab>
 
−
<tab index="4" block>Despite fitting on the previous line, the <code>block</code> attribute forces this seperate tab to a new line</tab>
 
−
</tabs>
 
  
−
==== <code>plain</code> tab interfaces ====
+
[[File:RS_Disk-DirectoryDetails-T2.png]]
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
 
−
&lt;tabs plain style="width:250px;"&gt;
 
−
&lt;tab&gt;This tab interface doesn't have a box surrounding it, but just has buttons above it.&lt;/tab&gt;
 
−
&lt;tab&gt;This makes it a bit easier to customise the box&lt;/tab&gt;
 
−
&lt;tab&gt;It is also more useful for storing tabbed tables in&lt;/tab&gt;
 
−
&lt;/tabs&gt;
 
−
</pre></tab>
 
  
−
<tabs plain style="width:250px;">
+
The various icons that can be displayed are detailed below:
−
<tab>This tab interface doesn't have a box surrounding it, but just has buttons above it.</tab>
+
{| class=wikitable
−
<tab>This makes it a bit easier to customise the box</tab>
+
| [[File:RS_Disk-FolderParent.png]] || The parent folder, move up a level.
−
<tab>It is also more useful for storing tabbed tables in</tab>
+
|-
−
</tabs>
+
| [[File:RS_Disk-FolderNew.png]] || The folder contains unwatched recordings, the number will be displayed.
 +
|-
 +
| [[File:RS_Disk-FolderWatched.png]] || The folder contains only watched recordings or is empty.
 +
|-
 +
| [[File:RS_Disk-RecordingNew.png]] || The recording is unwatched.
 +
|-
 +
| [[File:RS_Disk-RecordingWatched.png]] || The recording has been watched.
 +
|-
 +
| [[File:RS_Disk-SD.png]] || The recording is in standard definition.
 +
|-
 +
| [[File:RS_Disk-HD.png]] || The recording is in high definition.
 +
|}
 +
 
 +
==== Deletion of Disk Contents ====
  
−
==== Inline switching parts ====
+
There are 2 methods of deleting the disk contents:
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
+
* Recordings and folders can be deleted individually by using the appropriate [Opt+] button:
−
&lt;tabs&gt;
 
−
This line of text contains &lt;tab name="Exaggerating"&gt;over 9000&lt;/tab&gt;&lt;tab name="Truth"&gt;a couple of&lt;/tab&gt; switching parts. The &lt;tab index="1"&gt;biggest by far&lt;/tab&gt;&lt;tab index="2"&gt;main&lt;/tab&gt; part of this tab's contents is placed outside any &lt;tab index="1"&gt;awesome&lt;/tab&gt; <code>&lt;tab&gt;</code> tags.
 
  
−
The switching &lt;tab index="1"&gt;epicness&lt;/tab&gt;&lt;tab index="2"&gt;parts&lt;/tab&gt; are made by putting <code>&lt;tab&gt;</code> tags within the flow of the text.
+
[[File:RS_Disk-Opt.png]]
−
&lt;/tabs&gt;
 
−
</pre></tab>
 
  
−
This tab menu uses the regular syntax using the <code>&lt;tab&gt;</code> tag.
+
* Recordings and folders can be deleted by selecting individual recordings and folders and using the following buttons:
−
<tabs>
 
−
This line of text contains <tab name="Exaggerating">over 9000</tab><tab name="Truth">a couple of</tab> switching parts. The <tab index="1">biggest by far</tab><tab index="2">main</tab> part of this tab's contents is placed outside any <tab index="1">awesome</tab> <code>&lt;tab&gt;</code> tags.
 
  
−
The switching <tab index="1">epicness</tab><tab index="2">parts</tab> are made by putting <code>&lt;tab&gt;</code> tags within the flow of the text.
+
[[File:RS_Disk-Selection.png]]
−
</tabs>
 
−
----
 
−
This tab menu looks exactly the same, but uses the parser function <code><nowiki>{{#tab:name1, name2|content1|content2}}</nowiki></code> or <code><nowiki>{{#tab: #1, #2|content1|content2}}</nowiki></code>. This makes the code a bit shorter.
 
  
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
+
As a safety measure, in order to delete a folder through the RS server the folder needs to contain no .ts files.
−
&lt;tabs&gt;
+
If you want to delete the folder including all the .ts files you need to delete the .ts files first, then the folder.
−
This line of text contains {{#tab:Exagerrating,Truth|over 9000|a couple of}} switching parts. The {{#tab:|very biggest|main}} part of this tab's contents is placed outside any {{#tab:|awesome}} <code>&lt;tab&gt;</code> tags.
 
  
−
The switching {{#tab:|epicness|parts}} are made by putting <code>&lt;tab&gt;</code> tags within the flow of the text.
+
== Foxsat-HDR ==
−
&lt;/tabs&gt;
+
Clicking in the 'Pie Chart' symbol on any page will pull up a page showing your recordings.
−
</pre></tab>
+
From here it is possible to set up a delete command that will be carried out the next time your Humax is in contact with the RS server.
  
 +
[[File:RS_Disk-Details-Foxsat.png]]
  
−
<tabs>
+
[[File:RS_Disk-DirectoryDetails-Foxsat.png]]
−
This line of text contains {{#tab:Exagerrating,Truth|over 9000|a couple of}} switching parts. The {{#tab:|very biggest|main}} part of this tab's contents is placed outside any {{#tab:|awesome}} <code>&lt;tab&gt;</code> tags.
 
  
−
The switching {{#tab:|epicness|parts}} are made by putting <code>&lt;tab&gt;</code> tags within the flow of the text.
+
The various icons that can be displayed are detailed below:
−
</tabs>
+
{| class=wikitable
 +
| [[File:RS_Disk-FolderParent.png]] || The parent folder, move up a level.
 +
|-
 +
| [[File:RS_Disk-FolderNew.png]] || The folder contains unwatched recordings, the number will be displayed.
 +
|-
 +
| [[File:RS_Disk-FolderWatched.png]] || The folder contains only watched recordings or is empty.
 +
|-
 +
| [[File:RS_Disk-RecordingNew.png]] || The recording is unwatched.
 +
|-
 +
| [[File:RS_Disk-RecordingWatched.png]] || The recording has been watched.
 +
|-
 +
| [[File:RS_Disk-SD.png]] || The recording is in standard definition.
 +
|-
 +
| [[File:RS_Disk-HD.png]] || The recording is in high definition.
 +
|-
 +
| [[File:RS_Disk-Locked.png]] || The recording is locked and/or protected and requires the PIN to watch/delete.
 +
|-
 +
| [[File:RS_Disk-DLNA.png]] || The recording has been modified by the Convert Files Plug-in and is now more 'DLNA-friendly'.
 +
|}
  
−
==== Predefining tabs and reference syntax ====
+
==== Deletion of Disk Contents ====
  
−
Tabs can be predefined via either [[#Self-closing tabs|self-closing tabs]] or the [[#Parser function|parser function]]. This tab menu's third tab also uses the reference syntax for the parser function.
+
There are 2 methods of deleting the disk contents:
  
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
+
* Recordings and folders can be deleted individually by using the appropriate [Opt+] button:
−
&lt;tabs&gt;
 
−
&lt;tab name="First"/&gt;{{#tab:Second,Third}}
 
−
The {{#tab:|first|second|third}} tab is predefined via ''{{#tab:|a self-closing <code>&lt;tab /&gt;</code> tag|the parser-function syntax|$2}}''.
 
  
−
&lt;tab index="3"&gt;The italic text in the above line is defined via a <code>$2</code> reference. This automatically inserts the contents for the second value entered into the third tab too.
+
[[File:RS_Disk-Opt.png]]
−
&lt;/tab&gt;
 
−
&lt;/tabs&gt;
 
−
</pre></tab>
 
  
−
<tabs>
+
* Recordings and folders can be deleted by selecting individual recordings and folders and using the following buttons:
−
<tab name="First"/>{{#tab:Second,Third}}
 
−
The {{#tab:|first|second|third}} tab is predefined via ''{{#tab:|a self-closing <code>&lt;tab /&gt;</code> tag|the parser-function syntax|$2}}''.
 
  
−
<tab index="3">The italic text in the above line is defined via a <code>$2</code> reference. This automatically inserts the contents for the second value entered into the third tab too.
+
[[File:RS_Disk-Selection.png]]
−
</tab>
 
−
</tabs>
 
  
−
== Nested combinations ==
+
As a safety measure, in order to delete a folder through the RS server the folder needs to contain no .ts files.
 +
If you want to delete the folder including all the .ts files you need to delete the .ts files first, then the folder.
  
−
In some cases, it is possible to put multiple of these boxes inside each other. For this to work however, the <code>#tag:tabs</code>, <code>#tag:tab</code> or <code>#tab:</code> parser functions will have to be used whenever two of the same tags are used anywhere within each other. This is required because otherwise the wikicode parser will recognise the closing tag for the nested tag as the closing tag for the outer tag, and skip the rest of the content, which could cause problems.
+
'''This differs from the Foxsat-HDR WebIf but this is the way Remote Scheduling for the HD/HDR-Fox T2 works.'''
  
−
For the <code>#tag:</code> parser function, even boolean attributes (such as <code>dropdown</code> or <code>inline</code>) need to have a value defined for them, otherwise they are not recognised as attributes. For example, <code><nowiki>{{#tag:tab|Dropdown contents|dropdown}}</nowiki></code> will not work (it will show a toggle box instead of a dropdown), while <code><nowiki>{{#tag:tab|Dropdown contents|dropdown=true}}</nowiki></code> will show a dropdown box.
+
==== Server Representation of Disk Contents ====
 +
The server representation of disk contents focuses on non-transient state so if the Foxsat-HDR runs convertfiles while the box pushes the contents to the server this will not include the .tmp file (the original recording) and the size of the .ts file (the current progress of convertfiles) will be the size of the .tmp file.
  
−
All combinations of nesting multiple tags will work, except for nesting ''any'' tab menus inside other tab menus.
+
</tab><tab name="Settings">
 +
This page describes the [[File:RS_Settings-Button.png]] button on the [https://rs.hpkg.tv/ Remote Scheduling Web Site]
 +
----
 +
== HD/HDR-Fox T2 ==
 +
The following appears on the 'Settings' page:
  
−
=== Nested tab menus ===
+
==== Account Settings ====
 +
[[File:RS_Settings-Account-HDR-T2.png]]
  
−
==== Inside toggle boxes ====
+
{| class=wikitable
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
+
| '''Registered Email Address''' || Your registered email address will be displayed here.
−
&lt;tab&gt;
+
|-
−
This tab contains a tab menu:
+
| '''Hard Disk Problem Emails''' || Warning emails will be sent depending on:
 +
|-
 +
|  || On = Email notification of problems that arise will be sent daily at 7:15am.
 +
|-
 +
|  || Off = No email notifications will be sent.
 +
|-
 +
| '''Upcoming Conflict Warning Emails''' || Warning emails will be sent depending on:
 +
|-
 +
|  || On = Email notification of conflicts that arise will be sent daily at 7:15am.
 +
|-
 +
|  || Off = No email notifications will be sent.
 +
|-
 +
| '''Failed Recording Warning Emails''' || Email notification of failed recordings will be sent depending on:
 +
|-
 +
|  || On = Email notification of conflicts that arise will be sent.
 +
|-
 +
|  || Off = No email notifications will be sent.
 +
|-
 +
| '''Hide OTA from Visual View''' || There is a daily event in the schedule for the OTA update.
 +
|-
 +
|  || On = OTA event is not displayed in the Visual view.
 +
|-
 +
|  || Off = OTA event is displayed in the Visual view.
 +
|}
  
−
&lt;tabs&gt;
+
From here you can also change your password:
−
{{#tab:First, Second|These tabs use the <code>#tab:</code> parser function to create the nested tabs.|Placing <code>&lt;tab&gt;</code> tags inside another <code>&lt;tab&gt;</code> tag will cause the parser to recognise the inner closing tag as the closing tag for the outer tag, which messes it up.}}
 
−
&lt;/tabs&gt;
 
−
&lt;/tab&gt;
 
−
</pre></tab>
 
  
−
<tab>
+
[[File:RS_Settings-ChangePassword.png]]
−
This tab contains a tab menu:
 
  
−
<tabs>
+
==== EPG Settings ====
−
{{#tab:First, Second|These tabs use the <code>#tab:</code> parser function to create the nested tabs.|Placing <code>&lt;tab&gt;</code> tags inside another <code>&lt;tab&gt;</code> tag will cause the parser to recognise the inner closing tag as the closing tag for the outer tag, which messes it up.}}
 
−
</tabs>
 
−
</tab>
 
  
−
==== Inside dropdowns ====
+
The EPG settings are:
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
 
−
&lt;tab dropdown&gt;
 
−
And here is another tab menu:
 
−
&lt;tabs&gt;
 
−
{{#tag:tab|These tabs are generated via the <code>#tag:tab</code> parser function|name="First"}}
 
−
{{#tag:tab|This is required, for the same reason as explained in the Second tab in the toggle box example above.|name="Second"}}
 
−
&lt;/tabs&gt;
 
−
&lt;/tab&gt;
 
−
</pre></tab>
 
  
−
<tab dropdown>
+
[[File:RS_Settings-EPG.png]]
−
And here is another tab menu:
 
−
<tabs>
 
−
{{#tag:tab|These tabs are generated via the <code>#tag:tab</code> parser function|name="First"}}
 
−
{{#tag:tab|This is required, for the same reason as explained in the Second tab in the toggle box example above.|name="Second"}}
 
−
</tabs>
 
−
</tab>
 
  
−
=== Nested toggle/dropdown boxes ===
+
{| class=wikitable
 +
| '''EPG Quick Access''' || Sets the default EPG access:
 +
|-
 +
|  || On = Sets the EPG button to display the EPG.
 +
|-
 +
|  || Off = Sets the EPG button to display an EPG/search pop-up.
 +
|-
 +
| '''Grid-style EPG''' || Sets the default EPG display:
 +
|-
 +
|  || On = Sets the grid-style display.
 +
|-
 +
|  || Off = Sets the standard now/next display.
 +
|-
 +
| '''Grid-style EPG Hours''' || Sets the number of hours displayed (grid-style only).
 +
|-
 +
| '''Grid EPG Fixed Scrolling''' || Sets the EPG scrolling:
 +
|-
 +
|  || On = Scrolls the EPG within a fixed window.
 +
|-
 +
|  || Off = Scrolls the whole page.
 +
|-
 +
| '''De-duplicate genre search results?''' || De-duplicate the search results depends on:
 +
|-
 +
|  || On = Removes duplicate search results.
 +
|-
 +
|  || Off = Leaves duplicate search results.
 +
|}
  
−
==== Toggle boxes in toggle boxes ====
+
==== Devices ====
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
 
−
&lt;tab&gt;
 
−
This toggle box has another toggle box nested inside it.
 
  
−
{{#tag:tab|This tab is generated by the <code>#tag:tab</code> parser function.|openname=Show|closename="Hide"}}
+
The Device settings are:
−
&lt;/tab&gt;
 
−
</pre></tab>
 
  
−
<tab>
+
[[File:RS_Settings-Devices-HDR-T2.png]]
−
This toggle box has another toggle box nested inside it.
 
  
−
{{#tag:tab|This tab is generated by the <code>#tag:tab</code> parser function.|openname=Show|closename="Hide"}}
+
{| class=wikitable
−
</tab>
+
| '''Unique Identifier''' || Your unique identifier will be displayed here.
 +
|-
 +
| '''MAC Address''' || Your Humax's MAC will be displayed here.
 +
|-
 +
| '''Description''' || If description is preceded with a '!' e.g. !My-Humax, then only the text after the '!' will be displayed in the Device page header, e.g. the host name and unit type will be omitted.
 +
|-
 +
| '''Model''' || Displays the Humax model.
 +
|-
 +
| '''HX/CFW/RS Versions''' || Displays the Humax Firmware/Custom Firmware/Remote Scheduling versions.
 +
|-
 +
| '''Disk Size''' || Displays the size of your hard disk drive &amp; percentage used.
 +
|-
 +
| '''S.M.A.R.T. Status''' || Reports the status of the S.M.A.R.T. hard disk drive, if the Smartmontools package is installed.
 +
|-
 +
| '''EPG Region''' || Displays your region.
 +
|-
 +
| '''EPG Favourites Group''' || Which of the favorites set up in WebIf on the Humax itself you would like to use for channels on the server.
 +
|-
 +
| '''Order''' || Use this for ordering multiple devices on the server in the Humax list selectors.
 +
|-
 +
| '''Last Seen''' || Displays the time and date when your Humax last contacted the RS server.
 +
|-
 +
| '''Warn if not seen for''' || Send an email warning if the Humax hasn't been in contact with the server for x number of hours, specify x.
 +
|}
  
−
==== Toggle boxes in dropdowns ====
+
== Foxsat-HDR ==
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
+
The following appears on the 'Settings' page:
−
{{#tag:tab|
 
−
It is also possible to use the <code>#tag:tab</code> parser function for the outer tab.
 
−
&lt;tab collapsed&gt;
 
−
This inner toggle box is made via the <code>&lt;tag&gt;</code> syntax.
 
−
&lt;/tab&gt;
 
−
|dropdown=true}}
 
−
</pre></tab>
 
  
−
{{#tag:tab|
+
==== Account Settings ====
−
It is also possible to use the <code>#tag:tab</code> parser function for the outer tab.
 
−
<tab collapsed>
 
−
This inner toggle box is made via the <code>&lt;tag&gt;</code> syntax.
 
−
</tab>
 
−
|dropdown=true}}
 
  
−
==== Toggle boxes and dropdowns in tab boxes ====
+
The Account settings are:
  
−
If you want to place a toggle box or a dropdown inside a tab navigation, and want the toggle box to show up for every tab as opposed to just the tab it's nested in, first a parent <code>&lt;tab&gt;</code> tab must be made, with <code>index="*"</code>, so that the toggle box won't be recognised as a seperate tab content.
+
[[File:RS_Settings-Account-Foxsat.png]]
  
−
If you want to place a toggle box or dropdown menu inside a tab menu, you can simply place a <code>&lt;tab&gt;</code> tag inside the <code>&lt;tab&gt;</code> tag that functions as a tab. This will restrict toggle boxes and dropdowns to visibility in just one tab though. So, if you want to have a toggle box or dropdown that's visible in every tab, encase it in a <code>&lt;tab&gt;</code> tag with an <code>index="*"</code> set to it.
+
{| class=wikitable
 +
| '''Registered Email Address''' || Your registered email address will be displayed here.
 +
|-
 +
| '''Upcoming Conflict Warning Emails''' || Warning emails will be sent depending on:
 +
|-
 +
|  || On = Email notification of conflicts that arise will be sent daily at 7:15am.
 +
|-
 +
|  || Off = No email notifications will be sent.
 +
|-
 +
| '''Failed Recording Warning Emails''' || Email notification of failed recordings will be sent depending on:
 +
|-
 +
|  || On = Email notification of conflicts that arise will be sent.
 +
|-
 +
|  || Off = No email notifications will be sent.
 +
|-
 +
| '''Hide OTA from Visual View''' || HD/HDR-Fox T2 setting which is not required for the Foxsat-HDR
 +
|-
 +
|  || On = Default setting. Has little effect if On or Off.
 +
|}
 +
From here you can also change your password:
  
−
That way, the outer <code>&lt;tab&gt;</code> tag will be recognised as a tab container, and the inner one will be recognised as a toggle box or dropdown menu, as desired. The toggle box or dropdown must then also use the [[#Nested combinations|parser function syntax]].
+
[[File:RS_Settings-ChangePassword.png]]
 +
==== EPG Settings ====
 +
The EPG settings are:
  
−
If you want the contents of the toggle box inside the tab menu to be able to change depending on the selected tab, you should use the <code>nested="true"</code> attribute on the tag. This can be done by setting the very last argument of the <code>#tab:</code> parser function or the <code>#tag:tab</code> parser function to <code>nested=true</code>.
+
[[File:RS_Settings-EPG.png]]
  
−
See this demo for an example of how to make this work:
+
{| class=wikitable
 +
| '''EPG Quick Access''' || Sets the default EPG access:
 +
|-
 +
|  || On = Sets the EPG button to display the EPG.
 +
|-
 +
|  || Off = Sets the EPG button to display an EPG/search pop-up.
 +
|-
 +
| '''Grid-style EPG''' || Sets the default EPG display:
 +
|-
 +
|  || On = Sets the grid-style display.
 +
|-
 +
|  || Off = Sets the standard now/next display.
 +
|-
 +
| '''Grid-style EPG Hours''' || Sets the number of hours displayed (grid-style only).
 +
|-
 +
| '''Grid EPG Fixed Scrolling''' || Sets the EPG scrolling:
 +
|-
 +
|  || On = Scrolls the EPG within a fixed window.
 +
|-
 +
|  || Off = Scrolls the whole page.
 +
|-
 +
| '''De-duplicate genre search results?''' || De-duplicate the search results depends on:
 +
|-
 +
|  || On = Removes duplicate search results.
 +
|-
 +
|  || Off = Leaves duplicate search results.
 +
|}
  
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
+
==== Devices ====
−
&lt;tabs&gt;
+
The Device settings are:
−
&lt;tab name="Toggle box"&gt;
 
−
This first tab has a toggle box nested inside it
 
−
{{#tab:Toggle|This toggle box is made via the <code>#tab:</code> parser function.}}
 
−
&lt;/tab&gt;
 
−
&lt;tab name="Dropdown"&gt;
 
−
This second tab has a dropdown nested inside it
 
−
{{#tag:tab|This dropdown is created via the <code>#tag:tab</code> parser function, since it's not possible to define attributes such as <code>dropdown</code> via the <code>#tab:</code> parser function.|dropdown=true}}
 
−
&lt;/tab&gt;
 
−
&lt;tab index="*" block&gt;
 
−
{{#tag:tab|This toggle box shows up inside {{#tab:|every|each of the|nested=true}} tab{{#tag:tab|s|index=2|nested=true}}, because the containing tab tag has got its index attribute set to <code>index="*"</code>. It also has a <code>block</code> attribute.|openname=Open|closename=Close}}
 
−
&lt;/tab&gt;
 
−
&lt;/tabs&gt;
 
−
</pre></tab>
 
  
−
<tabs>
+
[[File:RS_Settings-Devices-Foxsat.png]]
−
<tab name="Toggle box">
 
−
This first tab has a toggle box nested inside it
 
−
{{#tab:Toggle|This toggle box is made via the <code>#tab:</code> parser function.}}
 
−
</tab>
 
−
<tab name="Dropdown">
 
−
This second tab has a dropdown nested inside it
 
−
{{#tag:tab|This dropdown is created via the <code>#tag:tab</code> parser function, since it's not possible to define attributes such as <code>dropdown</code> via the <code>#tab:</code> parser function.|dropdown=true}}
 
−
</tab>
 
−
<tab index="*" block>
 
−
{{#tag:tab|This toggle box shows up inside {{#tab:|every|each of the|nested=true}} tab{{#tag:tab|s|index=2|nested=true}}, because the containing tab tag has got its index attribute set to <code>index="*"</code>. It also has a <code>block</code> attribute.|openname=Open|closename=Close}}
 
−
</tab>
 
−
</tabs>
 
  
−
==== Toggle boxes in dropdowns ====
+
{| class=wikitable
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
+
| '''Unique Identifier''' || Your unique identifier will be displayed here.
−
&lt;tab dropdown name="nested toggle boxes" style="width:250px"&gt;
+
|-
−
This dropdown has a nested toggle box that has <code>inline</code> and <code>collapsed</code> attributes filled in: {{#tag:tab|You can do the same things with nested boxes as you'd normally do outside other tags.|inline=true|collapsed=true}}
+
| '''MAC Address''' || Your Humax's MAC will be displayed here.
−
&lt;/tab&gt;
+
|-
−
</pre></tab>
+
| '''Description''' || If description is preceded with a '!' e.g. !My-Humax, then only the text after the '!' will be displayed in the Device page header, e.g. the host name and unit type will be omitted.
 +
|-
 +
| '''Model''' || Displays the Humax model.
 +
|-
 +
| '''HX/CFW/RS Versions''' || Displays the Humax Firmware/Custom Firmware/Remote Scheduling versions.
 +
|-
 +
| '''Disk Size''' || Displays the size of your hard disk drive &amp; percentage used.
 +
|-
 +
| '''Satellite Feeds''' || Displays the number of satellite feeds:
 +
|-
 +
|  || 1 - One feed available, only one recording at any given time is possible.
 +
|-
 +
|  || 1.5 - Only one feed available but tuner 2 is looped with a cable from tuner 1 output, such that two compatible channels can be recorded at any given time.
 +
|- Two channels are compatible if they're in the same frequency band (low/high, cutoff is at 11700 MHz, less than or equal to 11700 is Low Band, above 11700 is High Band) and have the same polarization (horizontal/vertical).  Eg BBC1 HD, BBC2 HD, ITV1 HD, Channel 4 HD, More4 and E4 are all compatible with each other (Low Band Vertical), BBC4 HD, BBC News HD, Channel 5 HD, 5+1, 5+24, BBC Radio 5 Live and BBC Radio 5 Live Sports Extra are all compatible with each other (Low Band Horizontal).
 +
|  || 2 - Two independent feeds are available.
 +
|-
 +
| '''EPG Region''' || Displays your region.
 +
|-
 +
| '''EPG Favourites Group''' || Which of the favorites set up in WebIf on the Humax itself you would like to use for channels on the server.
 +
|-
 +
| '''Order''' || Use this for ordering multiple devices on the server in the Humax list selectors.
 +
|-
 +
| '''Last Seen''' || Displays the time and date when your Humax last contacted the RS server.
 +
|-
 +
| '''Warn if not seen for''' || Send an email warning if the Humax hasn't been in contact with the server for x number of hours, specify x.
 +
|}
  
−
<tab dropdown name="nested toggle boxes" style="width:250px">
+
</tab><tab name="Logout">
−
This dropdown has a nested toggle box that has <code>inline</code> and <code>collapsed</code> attributes filled in: {{#tag:tab|You can do the same things with nested boxes as you'd normally do outside other tags.|inline=true|collapsed=true}}
+
This page describes the [[File:RS_Logout-Button.png]] button on the [https://rs.hpkg.tv/ Remote Scheduling Web Site]
−
</tab>
+
----
 +
When you click on the <code>Logout</code> button you will be logged out, without further confirmation and then the following page will be displayed:
  
−
==== Dropdowns in dropdowns ====
+
[[File:RS_Logout.png|Logout Page]]
−
<tab openname="Show code" closename="Hide code" collapsed block style="max-width:100%;"><pre style="overflow:auto;">
 
−
&lt;tab dropdown name="nested dropdowns"&gt;
 
−
*It is even possible to have a dropdown inside a list item in another dropdown box
 
−
*{{#tag:tab|This a dropdown inside a list in the outer dropdown menu|dropdown=true}}
 
−
*And it is even possible to have a dropdown inside sub-menus in the dropdown...
 
−
**{{#tag:tab|It also works normally in sub-menus, although <code>style="width:186px;"</code> would be recommended. Although making the encasing <code>&lt;tab&gt;</code> wider using <code>style="width:214px;"</code> would work just as well.|dropdown=true|style=width:186px;}}
 
−
Or if you want, you can place it outside lists too.
 
−
{{#tag:tab|Here's a dropdown inside a dropdown, but not in any list|dropdown=true}}
 
−
&lt;/tab&gt;
 
−
</pre></tab>
 
  
−
<tab dropdown name="nested dropdowns">
+
</tab><tab name="Terms/Privacy Policy">
−
*It is even possible to have a dropdown inside a list item in another dropdown box
+
This page describes the [[File:RS_Terms-Button.png]] button on the [https://rs.hpkg.tv/ Remote Scheduling Web Site]
−
*{{#tag:tab|This a dropdown inside a list in the outer dropdown menu|dropdown=true}}
+
----
−
*And it is even possible to have a dropdown inside sub-menus in the dropdown...
+
When you click on the <code>Terms & Privacy Policy</code> button the Terms &amp; Privacy Policy will be displayed.
−
**{{#tag:tab|It also works normally in sub-menus, although <code>style="width:186px;"</code> would be recommended. Although making the encasing <code>&lt;tab&gt;</code> wider using <code>style="width:214px;"</code> would work just as well.|dropdown=true|style=width:186px;}}
 
−
Or if you want, you can place it outside lists too.
 
−
{{#tag:tab|Here's a dropdown inside a dropdown, but not in any list|dropdown=true}}
 
 
</tab>
 
</tab>
 +
</tabs>

Latest revision as of 20:39, 31 August 2017

What is the Remote Scheduling Portal?

Remote Scheduling is a web site which enables you to manage your list of scheduled recordings while you're out and about, from anywhere with a web browser and Internet connection, without having to expose your Humax device to the Internet or leave it powered on.

As long as your Humax has Internet access and wakes up occasionally to check for updates or make a recording, it will work.

It allows you to perform the following:

  • Schedule recording of a single/series/split/manual TV or radio event.
  • Automatically schedule recording of a single/series event based on keywords/channel/time etc.
  • Remove recording schedule.
  • See disk contents.
  • Delete a recorded program, useful when the box is running low on free space.
  • Get warnings about failed recordings.
  • See disk statistics (total/used/free space).
  • See warnings about recording conflicts, eg when more than two concurrent recordings have been scheduled within the same time window.

HD/HDR-Fox T2

All commands are queued on the server and the box polls the server for commands every 8-12 minutes.

This means that it's a secure solution because you don't need to open up your firewall at home in order to use this (many similar systems are "push" instead of "pull").

At each startup the program waits a random time, up to 2 minutes, spreading out server communication in order to avoid that all boxes contact the server at the exact same time.

Most commands require a powercycle to take effect, except for "delete" and "reboot".

The "reboot" command is not carried out if the box is currently recording. Instead, the processing is stopped and not resumed until the box is no longer busy.

Foxsat-HDR

All commands are queued on the server and the box polls the server for commands every 10 minutes when the box isn't already busy, eg recording (the rs package depends on the crond package).

This means that it's a secure solution because you don't need to open up your firewall at home in order to use this (many similar systems are "push" instead of "pull").

At each startup the program waits a random time, up to 2 minutes, spreading out server communication in order to avoid that all boxes contact the server at the exact same time.

Most commands require a powercycle to take effect, except for "delete" and "reboot".

During the Housekeeper boot at 03:00 the box is supposed to do as little as possible so queued commands are not received and executed during this boot.

The "reboot" command is not carried out if the box is currently recording or converting (convertfiles). Instead, the processing is stopped and not resumed until the box is no longer busy.

If the system is currently running a convertfiles process when the disk contents is pushed to the server the .ts file size is taken from the .tmp file (the original) and the .tmp file is not sent to the server as the current .ts/.tmp files are transient.

Comparision of Features Available to Supported PVRs

Humax models supported are:

  1. HD-Fox T2
  2. HDR-Fox T2
  3. Foxsat-HDR

The following table compares the various features available to each model:

Feature HD-Fox T2 HDR-Fox T2 Foxsat-HDR Notes
Home:
Pending Schedule - Delete Enabled Enabled Enabled
Pending Schedule - Enable/Disable AR Enabled Enabled Disabled
Pending Schedule - Refresh Events Enabled Enabled Disabled
Pending Schedule - Change Folder Enabled Enabled Enabled
Active Schedule - Delete Enabled Enabled Enabled
Active Schedule - Enable/Disable AR Enabled Enabled Disabled
Active Schedule - Refresh Events Enabled Enabled Disabled
Active Schedule - Change Folder Enabled Enabled Enabled
EPG:
EPG - Now/Next Enabled Enabled Enabled
EPG - Grid Style Enabled Enabled Enabled
EPG Searches Enabled Enabled Enabled
Record Series Enabled Enabled Enabled
Record Programme Enabled Enabled Enabled
Set Reminder Enabled Enabled Disabled
Recording Conflict Detection Enabled Enabled Enabled
Automatic Scheduling Feature:
Email Matching Events Enabled Enabled Enabled
Email Matching Series Enabled Enabled Enabled
Schedule Matching Events Enabled Enabled Enabled
Schedule Matching Series Enabled Enabled Enabled
Schedule Reminders for Matching Events Enabled Enabled Disabled
Visual page provides an alternative view of:
Scheduled Events Enabled Enabled Enabled
Pending Events Enabled Enabled Enabled
Conflicts Enabled Enabled Enabled
Recordings:
Display Recording Details Enabled Enabled Enabled
Delete Recordings Enabled Enabled Enabled
Email Warnings:
Hard Disk Problem Enabled Enabled Disabled
Upcoming Conflict(s) Enabled Enabled Enabled
Failed Recording(s) Enabled Enabled Enabled
WebIf Packages:
recmon (Recording monitor) Enabled Enabled Built in Simplified recmon that'll report recorded programs
after a few hours (instead of immediately when they finish
recording as the T2 recmon package does)
Smartmontools (S.M.A.R.T. Status) Enabled Enabled Disabled

Foxsat-HDR Port Differences

Most of the features have been ported with the following variations owing to differences in the two platforms (hardware or TV platform, ie Freeview vs Freesat):

  • The custom channel names are used instead of default channel names.
  • The server's conflict management has been extended to warn about conflicts for concurrent recordings on incompatible channels when only one satellite feed is available and tuner 1 is looped to tuner 2.
  • Often the Housekeeper job removes scheduled split events so a method of converting these to one single manual event has been implemented. This currently only works on split events with two parts. Enabling this feature is controlled by the user.
  • The Freesat guide is flaky and often single events don't have an ECRID, eg Click and The Film Review on BBC NEWS, which means that it can be difficult to schedule them for recording. Instead, scheduled single events missing an ECRID are converted to manual single events.
  • Refresh of series events, skipping a series event, scheduling of reminders and changing scheduled events to use Accurate Recording are not supported by the Foxsat-HDR, hence these features are not provided on the RS server.
  • Foxsat-HDR doesn't have a concept of pending schedules. These are instead simulated by taking a snapshot of the schedules at boot time and comparing actual schedules against this. This method isn't foolproof (eg a recording scheduled directly on the box using the remote control handset is regarded as pending and if the aforementioned recording is removed through WebIf or Remote Scheduling this will not take effect until after a reboot and in this case we create a dummy reboot pending record), however it hasn't been possible to find another way of handling pending schedules.
  • Foxsat-HDR doesn't support the inotify interface in the Linux kernel so recmon hasn't been implemented. On the HDR-Fox T2 recmon is used to log a message on the box and the server as soon as a recording has finished, notifying that the given programme was recorded. Instead, a lazy recorded log mechanism has been implemented: Every few hours the recordings completed since the last reporting are logged on the box and the server, for instance:
16/02/2017 07:11:56 - Recorded: BBC2 HD 15 Feb 2017 19:55:00-21:04:48 Trust Me, I'm a Doctor (69 minutes, 2.30 GiB)
This means that recordings removed before the next reporting window will not be logged.
  • rs_process is not a Jim/TCL program as the original but has instead been rewritten entirely in C++ owing to Jim file name clashes, major platform differences and also differences in the Jim language support.
  • rs_process and rs binaries are installed in /opt/bin.
  • Multi-mode Recording isn't supported.
  • The Foxsat-HDR CFW doesn't have a S.M.A.R.T. interface, so no S.M.A.R.T. status is sent to/displayed by the RS server.
  • The Foxsat-HDR CPU is quite slow compared to the HDR-Fox T2, so the rs_process program (the main controller) detects whether the system is too busy to carry out any commands. Specifically, the program terminates almost instantly when it starts up and detects that the number of currently playing/recording programs is larger than the user-configurable Max. Running Playbacks+Recordings value (default set to 0), regarding the system as being too busy. This means that the server is only queried for queued commands if the system is non-busy. No efforts are made towards detecting playbacks over DLNA and/or SMB, only directly on the box.
  • For the same reason, only non-hidden channels are pushed to the server, in order to keep CPU/disk usage to a minimum. You control which channels are hidden in the WebIf Channel Editor.
  • Non-Freesat channels aren't supported with Remote Scheduling as most of the channels don't have EPG entries.
  • Foxsat-HDR doesn't show any actual padding assignment to the schedule so the pre/post padding shown by the RS server is a guestimate.
  • The BBC region is determined based on the name of channel 101 using the following mappings, no other channels are used for determining the region:
Channel BBC Region Net
BBC One CI Channel Islands 501
BBC One East E East (East) 502
BBC One East W East (West) 503
BBC One E Mid East Midlands 504
BBC One Lon London 505
BBC One NE&C North East & Cumbria 506
BBC One N West North West 507
BBC One NI HD Northern Ireland 508
BBC One ScotHD Scotland 509
BBC One South South 510
BBC One S East South (East) 511
BBC One Oxford South (Oxford) 512
BBC One S West South West 513
BBC One Wal HD Wales 514
BBC One West West 515
BBC One W Mid West Midlands 516
BBC One Yorks Yorkshire 517
Other Unknown 518

Known Issues

HD/HDR-Fox T2

None.

Foxsat-HDR
  • If you rename files to include special characters directly on the box with the remote control handset these characters are ASCII 8-bit, which means that the files will not be visible via WebIf, Samba and DLNA (although MediaTomb can be configured for this). Furthermore, they will disrupt the upload of disk content metadata to the RS server, which means that file names containing UTF-8 characters will not be handled correctly, eg you won't be able to delete them through the RS server.
  • Gives incorrect boot reason if booted from WebIf version 2.88. Perhaps a future version of WebIf will fix this.

New Terms

rs package
The Remote Scheduling program that runs on your Humax (which needs to be running the Customised Firmware including the Web Interface package).
https://rs.hpkg.tv/
The Remote Scheduling website that captures your schedule requirements and synchronises them to your Humax at home.

Getting Started on the HD/HDR-Fox T2

If you are not already running the Customised Firmware then please have a look at the Wiki and Black Hole's threads at the top of the https://hummy.tv/forum/forums/hd-hdr-fox-t2-customised-firmware.28/ Forum which covers how to get started and ready to move on.

  • Make sure you're running at least version 1.11 of the Customised Firmware (see Firmware Downloads).
  • Install the latest WebIf and rs packages.
  • See Wireless Users Notes below if you are connected via Wi-Fi.
  • Go to the Settings page in your device's local web interface and register with the remote scheduling service.
  • Wait for your initial password to arrive via email.
  • Access https://rs.hpkg.tv/ and accept the Terms & Conditions to get started.

When you first log in there is some important information regarding what the site will and won't do and general Terms & Conditions to agree to before you can proceed. This gets you to the Home page which, to begin with, will show you the existing schedule details from your Hummy.

Wireless Users Notes

If your HD/HDR-Fox T2 is usually connected to your network via wireless, then it will not connect to the wireless network when it wakes up to make a recording. You can install the wireless-helper package to change this behaviour and increase the opportunities for your Humax to check for new recordings. The wireless-helper package currently only supports wireless networks using WPA or WPA2. It is planned to extend support to at least WEP in a future release.

Scheduling Sequence of Events

If your Humax is in standby when a new recording is Queued using Remote Scheduling, your Humax will not be aware of the new request until it is taken out of stand-by, when your Humax awakes the recording's status will move to Pending and a further stand-by >> awake cycle is required in order to make the new recording request move to Active. It is possible to remove the need for a further stand-by >> awake cycle by requesting a 'Scheduled Reboot' in the RS Home page so that the Humax will perform two reboots in one.

Frequency of Wake-up

To have the best chance of being able to successfully schedule a recording, you should set your HD/HDR-Fox T2 to wake up for 30 minutes at least once a day which is most easily done through the on-screen menus at Settings->Preferences->Time:

RS Fox-T2-PowerOnTimer.png

In conjunction with the overnight update check, this ensures that your device checks for new recordings at least twice a day. Any recordings that you have set will also enable the Humax to check for updates. It is also possible to schedule additional wake-up/sleep periods via the RS portal using the Additional Commands option which is below the list of scheduled recordings. You may wish to do this when going away from home for an extended period for example.

Getting Started on the Foxsat-HDR

If you are not already running the Customised Firmware then please have a look at https://www.avforums.com/threads/media-file-server-bundle-for-the-foxsat-hdr-release-4-part-6.2024876/ Forum which covers how to get started and ready to move on.

  • Make sure you're running at least version 4.1.3 of the Customised Firmware and at least version 2.88 of the WebIf.
  • Install the rs package.
  • Go to the Settings page in your device's local web interface and register with the remote scheduling service.
  • Wait for your initial password to arrive via email.
  • Access https://rs.hpkg.tv/ and accept the Terms & Conditions to get started.

When you first log in there is some important information regarding what the site will and won't do and general Terms & Conditions to agree to before you can proceed. This gets you to the Home page which, to begin with, will show you the existing schedule details from your Hummy. The initial upload of your Hummy's channels, EPG and recording schedule can take several minutes, up to 10-15 minutes. You can limit the amount of data your Hummy sends by hiding the channels you don't need/use in the WebIf Channel Editor.

Scheduling Sequence of Events

If your Humax is in standby when a new recording is Queued using Remote Scheduling, your Humax will not be aware of the new request until it is taken out of stand-by, when your Humax awakes the recording's status will move to Pending and a further stand-by >> awake cycle is required in order to make the new recording request move to Active. It is possible to remove the need for a further stand-by >> awake cycle by requesting a 'Scheduled Reboot' in the RS Home page so that the Humax will perform two reboots in one.

Frequency of Wake-up

To have the best chance of being able to successfully schedule a recording, you should set your Humax to wake up for 30 minutes at least once a day which is most easily done through the on-screen menus at Menu->Settings->Time:

RS Foxsat-HDR-PowerOnTimer.png

It is also possible to schedule additional wake-up/sleep periods through the on-screen menus at Schedule->Manual Watch reservation:

RS Foxsat-HDR-WatchReservation.png

You may wish to do this when going away from home for an extended period for example.

Note Note: Once again, please keep in mind how RS queries queued server commands in relation to the setting of Max. Running Playbacks+Recordings (default set to 0). Specifically, if you expect RS to query and process queued server commands when the box is recording this doesn't happen unless Max. Running Playbacks+Recordings is set to a value larger than or equal to the number of recordings (plus playbacks) currently running on the box.

The Remote Scheduling server, which can be accessed from https://rs.hpkg.tv/ has a menu bar that remains on all pages:

RS Menu.png

The various buttons are explained via the tabs at the top of this page.

This page describes the RS Home-Button.png button on the Remote Scheduling Web Site

The following appear on the 'Home' page:

Queued commands

These are the things you have done on the web site. Set recordings, deleted schedules. At this stage they are only held on the website until the next 10 minute 'sweep' or your Hummy wakes up and check the site.

RS Home-Queued.png

Deleting Queued Items

You'll notice the Queued items list has a dustbin icon at the end of each line and this will remove the item from the queue and therefore won't sync with your Hummy.

Pending Events

The Humax knows about these items, but it needs a reboot in order to save them into the schedule list on the Humax so that they actually work as expected.

RS Home-Pending.png

Deleting Pending Events

Click on the item in the Pending list and choose the Cancel Event option. This will create a cancellation line in the Queued commands list for each event to be deleted and will wait for the next sync between the site and your Humax.

Just like setting a recording the cancellation item will then sit in the Pending queue on your Humax until a restart takes place hence you can also send along a reboot action with the cancellation just like you can with a new recording. BUT like setting a recording, if your Humax is in standby it needs to wake up in order to sync in the first place. Less of a worry when deleting items as it's no problem to record something you now don't want any more (unless it conflicts with other recordings you want).

More Context Menu

HD/HDR Fox T2

Each event has the following items on the more context menu:

RS Home-Active-More-T2.png

Delete Delete the selected event.
Disable AR Disable Accurate Recording (AR) for the selected event. See "Multi-mode Recording" below.
Refresh Events The Fox T2 schedule database contains a binary field aulEventToRecordInfo.

Refresh just blanks that field out on the next reboot which makes the Humax software re-populate it based on events in the current EPG. It's really a troubleshooting/diagnostic thing but can also be used to re-add any episodes which have been set up for skip.

Change Folder Change the folder name to be used for series recodings.
Foxsat-HDR

Each event has the following items on the more context menu:

RS Home-Active-More-Foxsat.png

Delete Delete the selected event.
Change Folder Change the folder name to be used for series recodings.

Active Events

These are all the items the Humax knows about AND will carry them out in full.

RS Home-Active.png

Deleting Active Events

Click on the item(s) in the Active list and then choose the [Delete Selected] button, or another option is to click [Delete] on the event's context menu.

To delete all finished events select the [Select Finished] button and then the [Delete Selected] button.

This will create a cancellation line in the Queued commands list for each event to be deleted and will wait for the next sync between the site and your Humax.

Just like setting a recording the cancellation item will then sit in the Pending queue on the Humax until a restart takes place hence you can also send along a reboot action with the cancellation just like you can with a new recording. BUT like setting a recording, if your Humax is in standby it needs to wake up in order to sync in the first place. Less of a worry when deleting items as it's no problem to record something you now don't want any more (unless it conflicts with other recordings you want).

More Context Menu

HD/HDR-Fox-T2

See "Pending Events", "More Context Menu", "HD/HDR-Fox T2" which is the same.

Foxsat-HDR

See "Pending Events", "More Context Menu", "Foxsat-HDR" which is the same.

Additional Commands

HD/HDR-Fox T2

At the end of the Active list there are the following buttons:

RS Home-Active-ScheduleReboot.png - Schedule a Reboot.

RS Home-Active-ManualEvent.png - Create a Manual Event (a recording or reminder).

RS Home-Active-RawDatabase.png - View the Raw Database.

Foxsat-HDR

At the end of the Active list there are the following buttons:

RS Home-Active-ScheduleReboot.png - Schedule a Reboot.

RS Home-Active-ManualEvent.png - Create a Manual Event (recording only).

RS Home-Active-RawDatabase.png - View the Raw Database.

Recent Activity

This is a simple view of an event log - it's not meant to be an exhaustive audit trail but it does confirm that things are happening and when they happened.

RS Home-RecentActivity.png

You can see a more detailed list of every event tracked by clicking the More button and then even more detail via the Show diagnostic entries button. You can also delete the contents of the log file via the [Delete log entries] button.

Top 10/500 list

Clicking on a programme in the Top 10/500 list will display all broadcast times for that programme with the ability to set up a recording from there.

RS Home-Top10500List.png

This page describes the RS EPG-Button.png button on the Remote Scheduling Web Site --

Note Note: Remote Scheduling doesn't automatically detect changes in the channel lineup or the WebIf Favourite lists. With any change to these you will have to run the following from a command line on the box in order to push the changes to the server. This applies to the HD/HDR-Fox T2 and Foxsat-HDR: 

rs push channels

The following appear on the 'EPG' page:

EPG - Now/Next

Clicking a specific programme displays a pop-up with details from the EPG (Electronic Programme Guide). Clicking the Channel name hyperlink will display all EPG entries for that channel.

RS EPG-Guide-NowNext.png

You can switch to the grid display by clicking on the Grid EPG button.

EPG - Grid Style

Where programs are of a duration too short to display in the grid, the title hyperlink is truncated, which can be clicked to see the full programme EPG information in the same way as the Now/Next EPG function. Clicking the Channel name hyperlink will display all EPG entries for that channel.

RS EPG-Guide-Grid.png

You can switch to the Now/Next display by clicking on the Now/Next button.

The cell width is adjustable to avoid left to right scrolling.

Note that the narrower settings for cell width will result in more programme titles not being displayed in full on the EPG 7-day page. But if you hover over the programme a pop-up window will display the full title and start/end times. Set a value that works best for you. See the Settings button below.

The Navigation bar enables:

  • Selecting the time range displayed.
  • Selecting 'Now', the current day & time.
  • Selecting the required day.

RS EPG-Navication.png

EPG Searches

The EPG page provides 2 methods of searching for programs which covers the full 7 days.

1. EPG Search

Will search the EPG data for specific text in the programme title (and optionally the programme description). By default, results are filtered by the standard Channel List mechanism although this can be over-ridden in the case of a search.

RS EPG-Search.png

You can use the following operators and rules to refine/enhance the search results:

+ stands for AND
- stands for NOT
no operator implies OR
"two words" in quotes must appear together
+doctor +(amy tardis) containing 'doctor' and one of 'amy' or 'tardis'

2. Content Type Searches

Will search the EPG data on the content type (genre). The results are filtered by the standard Channel List mechanism.

RS EPG-Search-Content.png

Scheduling a Recording

HD/HDR-Fox T2

Click on the programme name that you want to schedule and you will get a dialogue box with more detailed programme info, plus buttons at the bottom to record the series, just the program, set a reminder or cancel.

RS EPG-ProgDetails-T2.png

No recording option buttons will be displayed for programmes already scheduled for recording.

Confirmation of the successful or otherwise setting of the recording will be shown in a banner at the top of the page:

RS EPG-Confirmation.png

Once this is done the Home page will now show a section at the top called Queued commands - at this stage these are only stored on the website awaiting a sync with your HD/HDR-Fox T2. Every 10-12 minutes or so (or on next reboot if the HD/HDR-Fox T2 is on standby) your HD/HDR-Fox T2 will contact the site to see if there is anything to sync and if there are items in Queued commands they will be picked up and copied over to your HD/HDR-Fox T2, and then they will appear in a Pending list. There is a 'last seen' time/date stamp at the top of the Home Page so you know if the site is seeing your Humax.

Please note that due to the way the core HD/HDR-Fox T2 software works a restart of the HD/HDR-Fox T2 is then required in order for Pending items to actually take place. This is why items in the Queued commands list also have a button for Schedule Reboot - if you click this a reboot command is also sent to the HD/HDR-Fox T2 along with your recordings, and the HD/HDR-Fox T2 will restart itself shortly after synchronising the Queued commands thus ensuring your recordings/changes take place.

RS EPG-QueuedCommands.png

All HD/HDR-Fox T2 have an auto update task at 4:30 am every morning so at worst case they wake up every morning and any Pending Items already on the Humax will become active. Otherwise if you have the HD/HDR-Fox T2 on standby when you are not there you may want to schedule a power cycle or two so that the HD/HDR-Fox T2 wakes up and can pick up any Queued and/or Pending items and incorporate them fully into the schedule (there is a function for this under Additional Commands).

You can force a sync from the command line with: 

/mod/sbin/rs_process now

To push the schedule from the command line use: 

rs push

Don't forget that if you have the HD/HDR-Fox T2 on standby when you make the schedule then it'll need one wake up to pick up the scheduled item(s), then another in order to successfully incorporate them into the schedule on the HD/HDR-Fox T2. You can send the second reboot along with the schedule but the first has to already be defined on the HD/HDR-Fox T2 (either the built in daily 4:30am auto update or wake up/sleep cycles you can program yourself).

Foxsat-HDR

Click on the programme name that you want to schedule and you will get a dialogue box with more detailed programme info, plus buttons at the bottom to record the series, just the programme or cancel.

RS EPG-ProgDetails-Foxsat.png

No recording option buttons will be displayed for programmes already scheduled for recording.

Confirmation of the successful or otherwise setting of the recording will be shown in a banner at the top of the page:

RS EPG-Confirmation.png

Once this is done the Home page will now show a section at the top called Queued commands - at this stage these are only stored on the website awaiting a sync with your Foxsat-HDR. Every 10-12 minutes or so (or on next reboot if the Foxsat-HDR is on standby) your Foxsat-HDR will contact the site to see if there is anything to sync and if there are items in Queued commands they will be picked up and copied over to your Foxsat-HDR, and then they will appear in a Pending list. There is a 'last seen' time/date stamp at the top of the Home Page so you know if the site is seeing your Humax.

Please note that due to the way the core Foxsat-HDR software works a restart of the Humax is then required in order for Pending items to actually take place. This is why items in the Queued commands list also have a button for Schedule Reboot - if you click this a reboot command is also sent to the Humax along with your recordings, and the Foxsat-HDR will restart itself shortly after synchronising the Queued commands thus ensuring your recordings/changes take place.

RS EPG-QueuedCommands.png

You need to have set up at least one daily wake up/sleep cycle and any Pending Items already on the Foxsat-HDR will become active. Otherwise if you have the Foxsat-HDR on standby when you are not there you may want to schedule a power cycle or two so that the Foxsat-HDR wakes up and can pick up any Queued and/or Pending items and incorporate them fully into the schedule.

You can force a sync from the command line with: 

rs_process now

To push the schedule from the command line use: 

rs push

Don't forget that if you have the Foxsat-HDR on standby when you make the schedule then it'll need one wake up to pick up the scheduled item(s), then another in order to successfully incorporate them into the schedule on the Foxsat-HDR. You can send the second reboot along with the schedule but the first has to already be defined on the Foxsat-HDR, see 'Getting Started'-> 'Frequency of Wake-up'-> 'Foxsat-HDR' above.

Reminder
  • Queued commands are not received and executed when the number of currently playing/recording programs is larger than the user-configurable Max. Running Playbacks+Recordings value (default set to 0), regarding the system as being too busy.
  • During the Housekeeper boot at 03:00 the box is supposed to do as little as possible so Queued commands are not received and executed during this boot.

Recording Conflict Detection

The scheduling mechanism will check for recording conflicts each time a new recording is scheduled.

If a schedule conflict is detected, all conflicting recordings will be displayed in the pop-up window:

RS EPG-ConflictDetection.png

Note Note: For this to work correctly on the Foxsat-HDR you must first set the number of satellite feeds available to your Foxsat-HDR in the 'RemoteScheduling Plug-in Settings' section on the 'Settings' page of the Web Interface.

This page describes the RS Auto-Button.png button on the Remote Scheduling Web Site

The Remote Scheduling Portal includes an automatic scheduling feature. This allows you to set up rules which are matched against the EPG data as it comes in eight days ahead. When a match is found, it's possible to either have it send you an email message, or to attempt to automatically schedule the recording on your behalf.

There are 2 types of rules:

Standard Rules

RS Auto-StandardRules.png

Add New Rule

RS Auto-Standard-Add.png

Type
The type of rule, either Email which causes emails to be sent when matches are found or Schedule which attempts to schedule any events found and also emails notification of the schedule.
Subtype
Whether to treat matches as single events or, if possible, series.
Date
If specified, only match events which occur on this date.
Day
If specified, only match events which occur on this day or set of days (e.g. weekdays). Note that if you use this to only schedule events occurring on particular days then you should most likely be using the Schedule Events option rather than Schedule Series. If you schedule the series then the day restriction will only apply to the original matching event - you will get the rest of the series regardless of the day.
Start Time
If specified, only match events which start between the times provided.
Channel
If specified, only match events shown on this channel.
Content Type
If specified, only match events with this content type (as set by the content provider).
Name
Part of the EPG name to match. This supports wild cards, '*' for 0 or more characters, '?' for exactly one character. It is matched against the EPG as a substring.
Synopsis
Part of the EPG synopsis. This supports the same wild cards as name.

More Context Menu

Each rule has the following items on the more context menu: RS Auto-Standard-More.png

Edit Allows changes to an existing Auto search.
Delete Removes a single standard rule.
Disable/Enable Rule Allows the rule to be disabled/enabled.
Convert to Advanced Converts standard to advanced rule.
Show Matching Events Displays a current search results for the current 'Auto' search.
Reset Matched Events Enables all previously found CRID's for the current search to be emailed / scheduled again.

Examples

Example 1

RS Auto-Standard-Example1.png
Record all Harry Potter films that pop up in the EPG and email notification.

Example 2

RS Auto-Standard-Example2.png
Record any episodes of Doctor Who showing on Christmas Day 2017 on BBC ONE HD and email notification.

Example 3

RS Auto-Standard-Example3.png
Record the Formula 1 highlights from Channel 4 HD and email notification.
Series link doesn't work reliably for this and often pulls in practice sessions, qualifying and the race. It rarely records subsequent races.

Example 4

RS Auto-Standard-Example4.png
Send an email alert when any James Bond films, not featuring Pierce Brosnan are found in the EPG.
NOTE:- the use of '+' and '-' forces a whole word search, with '*' as a wild card e.g. -bros*

Notes:

  • In example 4 above the -brosnan MUST follow a +keyword, a stand alone -keyword will always find zero matches.
  • If Type = Schedule the item will be scheduled and an email notification will be sent with a link to the RS EPG entry.
  • If Type = Email you will only be sent an email notification with an RS EPG link, so that a manual recording can be selected.

Advanced Rules

RS Auto-AdvancedRules.png

Add Rule or Add New Entry

Add Description
RS Auto-Advanced-Add1.png
Enter description for rule and after you click on the [Create Rule] button the following will be created:
RS Auto-Advanced-Add2.png
Add Condition(s)
At the left hand end of the rule there is a [+] icon which allows a new condition to be added:
RS Auto-Advanced-Add3.png
The "Negate?" tick box negates the condition so that if you selected 'Channel name is' and then tick the 'negate' box, you end up with 'Channel name is NOT'.
Select the condition required and after you click on the [Add Condition] button the following will be created:
RS Auto-Advanced-Add4.png
At the end of the "If/And" part of the condition there is an edit icon which allows the value(s) to be changed:
RS Auto-Advanced-Add5.png

HD/HDR-Fox T2

At the end of the "Then" part of the condition there is an edit icon which allows the value to be changed:

RS Auto-Advanced-Add6-T2.png

Foxsat-HDR

At the end of the "Then" part of the condition there is an edit icon which allows the value to be changed:

RS Auto-Advanced-Add6-Foxsat.png

You can add more condition(s) as required.

Quick Add

RS Auto-Advanced-QuickAdd.png

Save Changes

To save the rule(s) after they have been created, edited or deleted click on the Save changes button.

Discard Changes

To discard changes to rule(s) after they have been created, edited or deleted click on the Discard changes button.

Note Note: This only applies to changes made since the last 'Save changes' was carried out.

Matching Events

RS Auto-Advanced-MatchingEvents.png

At the end of each rule there is the [Matching Events] button which will display any matching events found.

Options

At the end of each rule there are the following icons:

RS Auto-Advanced-Options.png
RS Auto-Advanced-Options-Refresh.png Refresh Rule Enables all previously found CRID's for the current search to be emailed / scheduled again.
RS Auto-Advanced-Options-Edit.png Edit Rule Text Allows changes to the selected rule text.
RS Auto-Advanced-Options-Enable.png Enable/Disable Rule Allows the rule to be enabled/disabled.
RS Auto-Advanced-Options-Delete.png Delete Rule Removes the selected advanced rule.
RS Auto-Advanced-Options-Duplicate.png Duplicate Rule Duplicates an existing search that can then be modified.
RS Auto-Advanced-Options-MoveUp.png Move Rule Up Moves the selected rule up in the list.
RS Auto-Advanced-Options-MoveDown.png Move Rule Down Moves the selected rule down in the list.

Examples

Example 1

RS Auto-Advanced-Example1.png
Record all Harry Potter films that pop up in the EPG and email notification.

Example 2

RS Auto-Advanced-Example2.png
Record any episodes of Doctor Who showing on Christmas Day 2017 on BBC ONE HD and email notification.

Example 3

RS Auto-Advanced-Example3.png
Record the Formula 1 highlights from Channel 4 HD and email notification.
Series link doesn't work reliably for this and often pulls in practice sessions, qualifying and the race. It rarely records subsequent races.

Example 4

RS Auto-Advanced-Example4.png
Send an email alert when any James Bond films, not featuring Pierce Brosnan are found in the EPG.
NOTE:- the use of '+' and '-' forces a whole word search, with '*' as a wild card e.g. -bros*

This page describes the RS Visual-Button.png button on the Remote Scheduling Web Site

The Remote Scheduling Visual page provides an alternative view of scheduled and pending events, it also clearly displays any outstanding conflicts:

RS Visual.png

This page describes the RS Disk-Button.png button on the Remote Scheduling Web Site

HD/HDR-Fox T2

Clicking in the 'Pie Chart' symbol on any page will pull up a page showing your recordings. From here it is possible to set up a delete command that will be carried out the next time your Humax is in contact with the RS server.

RS Disk-Details-T2.png

RS Disk-DirectoryDetails-T2.png

The various icons that can be displayed are detailed below:

RS Disk-FolderParent.png The parent folder, move up a level.
RS Disk-FolderNew.png The folder contains unwatched recordings, the number will be displayed.
RS Disk-FolderWatched.png The folder contains only watched recordings or is empty.
RS Disk-RecordingNew.png The recording is unwatched.
RS Disk-RecordingWatched.png The recording has been watched.
RS Disk-SD.png The recording is in standard definition.
RS Disk-HD.png The recording is in high definition.

Deletion of Disk Contents

There are 2 methods of deleting the disk contents:

  • Recordings and folders can be deleted individually by using the appropriate [Opt+] button:

RS Disk-Opt.png

  • Recordings and folders can be deleted by selecting individual recordings and folders and using the following buttons:

RS Disk-Selection.png

As a safety measure, in order to delete a folder through the RS server the folder needs to contain no .ts files. If you want to delete the folder including all the .ts files you need to delete the .ts files first, then the folder.

Foxsat-HDR

Clicking in the 'Pie Chart' symbol on any page will pull up a page showing your recordings. From here it is possible to set up a delete command that will be carried out the next time your Humax is in contact with the RS server.

RS Disk-Details-Foxsat.png

RS Disk-DirectoryDetails-Foxsat.png

The various icons that can be displayed are detailed below:

RS Disk-FolderParent.png The parent folder, move up a level.
RS Disk-FolderNew.png The folder contains unwatched recordings, the number will be displayed.
RS Disk-FolderWatched.png The folder contains only watched recordings or is empty.
RS Disk-RecordingNew.png The recording is unwatched.
RS Disk-RecordingWatched.png The recording has been watched.
RS Disk-SD.png The recording is in standard definition.
RS Disk-HD.png The recording is in high definition.
RS Disk-Locked.png The recording is locked and/or protected and requires the PIN to watch/delete.
RS Disk-DLNA.png The recording has been modified by the Convert Files Plug-in and is now more 'DLNA-friendly'.

Deletion of Disk Contents

There are 2 methods of deleting the disk contents:

  • Recordings and folders can be deleted individually by using the appropriate [Opt+] button:

RS Disk-Opt.png

  • Recordings and folders can be deleted by selecting individual recordings and folders and using the following buttons:

RS Disk-Selection.png

As a safety measure, in order to delete a folder through the RS server the folder needs to contain no .ts files. If you want to delete the folder including all the .ts files you need to delete the .ts files first, then the folder.

This differs from the Foxsat-HDR WebIf but this is the way Remote Scheduling for the HD/HDR-Fox T2 works.

Server Representation of Disk Contents

The server representation of disk contents focuses on non-transient state so if the Foxsat-HDR runs convertfiles while the box pushes the contents to the server this will not include the .tmp file (the original recording) and the size of the .ts file (the current progress of convertfiles) will be the size of the .tmp file.

This page describes the RS Settings-Button.png button on the Remote Scheduling Web Site

HD/HDR-Fox T2

The following appears on the 'Settings' page:

Account Settings

RS Settings-Account-HDR-T2.png

Registered Email Address Your registered email address will be displayed here.
Hard Disk Problem Emails Warning emails will be sent depending on:
On = Email notification of problems that arise will be sent daily at 7:15am.
Off = No email notifications will be sent.
Upcoming Conflict Warning Emails Warning emails will be sent depending on:
On = Email notification of conflicts that arise will be sent daily at 7:15am.
Off = No email notifications will be sent.
Failed Recording Warning Emails Email notification of failed recordings will be sent depending on:
On = Email notification of conflicts that arise will be sent.
Off = No email notifications will be sent.
Hide OTA from Visual View There is a daily event in the schedule for the OTA update.
On = OTA event is not displayed in the Visual view.
Off = OTA event is displayed in the Visual view.

From here you can also change your password:

RS Settings-ChangePassword.png

EPG Settings

The EPG settings are:

RS Settings-EPG.png

EPG Quick Access Sets the default EPG access:
On = Sets the EPG button to display the EPG.
Off = Sets the EPG button to display an EPG/search pop-up.
Grid-style EPG Sets the default EPG display:
On = Sets the grid-style display.
Off = Sets the standard now/next display.
Grid-style EPG Hours Sets the number of hours displayed (grid-style only).
Grid EPG Fixed Scrolling Sets the EPG scrolling:
On = Scrolls the EPG within a fixed window.
Off = Scrolls the whole page.
De-duplicate genre search results? De-duplicate the search results depends on:
On = Removes duplicate search results.
Off = Leaves duplicate search results.

Devices

The Device settings are:

RS Settings-Devices-HDR-T2.png

Unique Identifier Your unique identifier will be displayed here.
MAC Address Your Humax's MAC will be displayed here.
Description If description is preceded with a '!' e.g. !My-Humax, then only the text after the '!' will be displayed in the Device page header, e.g. the host name and unit type will be omitted.
Model Displays the Humax model.
HX/CFW/RS Versions Displays the Humax Firmware/Custom Firmware/Remote Scheduling versions.
Disk Size Displays the size of your hard disk drive & percentage used.
S.M.A.R.T. Status Reports the status of the S.M.A.R.T. hard disk drive, if the Smartmontools package is installed.
EPG Region Displays your region.
EPG Favourites Group Which of the favorites set up in WebIf on the Humax itself you would like to use for channels on the server.
Order Use this for ordering multiple devices on the server in the Humax list selectors.
Last Seen Displays the time and date when your Humax last contacted the RS server.
Warn if not seen for Send an email warning if the Humax hasn't been in contact with the server for x number of hours, specify x.

Foxsat-HDR

The following appears on the 'Settings' page:

Account Settings

The Account settings are:

RS Settings-Account-Foxsat.png

Registered Email Address Your registered email address will be displayed here.
Upcoming Conflict Warning Emails Warning emails will be sent depending on:
On = Email notification of conflicts that arise will be sent daily at 7:15am.
Off = No email notifications will be sent.
Failed Recording Warning Emails Email notification of failed recordings will be sent depending on:
On = Email notification of conflicts that arise will be sent.
Off = No email notifications will be sent.
Hide OTA from Visual View HD/HDR-Fox T2 setting which is not required for the Foxsat-HDR
On = Default setting. Has little effect if On or Off.

From here you can also change your password:

RS Settings-ChangePassword.png

EPG Settings

The EPG settings are:

RS Settings-EPG.png

EPG Quick Access Sets the default EPG access:
On = Sets the EPG button to display the EPG.
Off = Sets the EPG button to display an EPG/search pop-up.
Grid-style EPG Sets the default EPG display:
On = Sets the grid-style display.
Off = Sets the standard now/next display.
Grid-style EPG Hours Sets the number of hours displayed (grid-style only).
Grid EPG Fixed Scrolling Sets the EPG scrolling:
On = Scrolls the EPG within a fixed window.
Off = Scrolls the whole page.
De-duplicate genre search results? De-duplicate the search results depends on:
On = Removes duplicate search results.
Off = Leaves duplicate search results.

Devices

The Device settings are:

RS Settings-Devices-Foxsat.png

Unique Identifier Your unique identifier will be displayed here.
MAC Address Your Humax's MAC will be displayed here.
Description If description is preceded with a '!' e.g. !My-Humax, then only the text after the '!' will be displayed in the Device page header, e.g. the host name and unit type will be omitted.
Model Displays the Humax model.
HX/CFW/RS Versions Displays the Humax Firmware/Custom Firmware/Remote Scheduling versions.
Disk Size Displays the size of your hard disk drive & percentage used.
Satellite Feeds Displays the number of satellite feeds:
1 - One feed available, only one recording at any given time is possible.
1.5 - Only one feed available but tuner 2 is looped with a cable from tuner 1 output, such that two compatible channels can be recorded at any given time.
2 - Two independent feeds are available.
EPG Region Displays your region.
EPG Favourites Group Which of the favorites set up in WebIf on the Humax itself you would like to use for channels on the server.
Order Use this for ordering multiple devices on the server in the Humax list selectors.
Last Seen Displays the time and date when your Humax last contacted the RS server.
Warn if not seen for Send an email warning if the Humax hasn't been in contact with the server for x number of hours, specify x.

This page describes the RS Logout-Button.png button on the Remote Scheduling Web Site

When you click on the Logout button you will be logged out, without further confirmation and then the following page will be displayed:

Logout Page

This page describes the RS Terms-Button.png button on the Remote Scheduling Web Site

When you click on the Terms & Privacy Policy button the Terms & Privacy Policy will be displayed.

Retrieved from "https://wiki.hummy.tv/w/index.php?title=Remote_Scheduling_Portal&oldid=4989"