Messages

[Would IceTV consider adding a feature that allows IceBox users to customise the format their own EPG content?]

Would IceTV consider adding a feature that allows IceBox users to customise the format their own EPG content?

The IceTV Kodi addon is written in the Python programming language.  It should be possible to call an external Python module from within the existing addon.

In its default configuration, the existing Kodi addon would remain relatively unchanged.  However, at startup, it would look for a user-defined Python module and set some flags if that module is found and is valid.

In the 'output_xmltv()' function, if the flags are true, service.icetv would then call those pre-defined external functions after the XMLTV object has been created, but before that object is converted to XML and sent to TVH.

This will allow the user to intercept and modify the XMLTV data before it is sent to TVH.

Because some data is critical, such as start/end times, these fields should not be customisable.

I suggest 3 functions in the external module for formatting 3 XMLTV elements:  'title', 'sub-title' and 'desc'.  Each of these modules would accept a single 'show' object as input and return a string containing the user-defined content for that field.

Once the module is initially loaded, each of the 3 functions can be tested for individually and flags set accordingly.

There would also need to be some try-except-else protection against syntax errors and the like within the user-defined module.

The existing Kodi addon would remain read-only in '/usr/share/kodi/addons/service.icetv'.  However, the external module would be located in '/storage/.kodi/userdata/addon_data/service.icetv/epg_formatter.py' (or similar) where it can be modified by the user.

I can post some code samples if this is of interest.

Under the hood, IceTV does not use the LCN to schedule recordings, it uses a string of characters (called a couplet?) to identify individual services within the transmission steam. It is only a problem if the couplet changes rather than the LCNs it is associated with, which does not appear to be the case here.

This is only partially true.

IceTV assigns a unique ID to each channel.  When a recording is sent to a PVR, it is sent referencing that unique ChannelID.

In the channels list, IceTV has a definition for each ChannelID, and part of that definition includes the DVB triplets (ONID, TSID & SID) as well as the LCN.

Code Select Expand

        }, {
            "id": "3",
            "name": "7 Digital",
            "name_short": "Seven",
            "network_id": "9",
            "region_id": "1",
            "is_hd": 0,
            "lcns": "7,71",
            "region_name": "NSW - Sydney",
            "network_name": "Seven",
            "is_hidden": 0,
            "icon_src": "https://images.icetv.com.au/channels/seven-v2.png",
            "icon_width": 0,
            "icon_height": 0,
            "is_capital_channel": false,
            "dvbt_info": [{
                    "original_network_id": "4115",
                    "transport_stream_id": "1282",
                    "service_id": "1312",
                    "lcn": "7",
                    "frequency": "0"
                }, {
                    "original_network_id": "4115",
                    "transport_stream_id": "1282",
                    "service_id": "1313",
                    "lcn": "71",
                    "frequency": "0"
                }
            ]
        }, {
When determining which actual channel to record, the PVR needs to look at the ChannelID provided, find the DVB triplets or LCN for that channel and then perform a match.

If the PVR matches on the DVB triplets, there is not a problem, because they have not changed.  However, if the PVR matches on the LCN, then an error may occur.  Perhaps the PVR does neither and tries to match on the channel name.

This issue will come down to how the PVR firmware matches IceTV channels to the DVB Services that it receives.

This analysis is based on the newer JSON API.  I did reverse engineer the old binary API that Topfield PVRs use a long time ago, but I don't remember what matching criteria are provided for channels, it may be LCN-based.

I compared a re-scanned TVHeadend with an old copy that has not been re-scanned yet, here are my results from Sydney:



The Name/SID mapping has stayed the same, but the LCNs were swapped.

A logged-in user could report a problem with the EPG directly from within the 'tv-guide.icetv.com.au' web page.

When the EPG details are visible, in addition to the 'Recording Options' operations, a 'Report Error' operation could be added.  This could present the user with a screen containing a list of error types like 'Repeat status', 'Missing episode number', 'Wrong start time', etc, with maybe a free form text field for extra comments.

Once the error has been reported, the EPG will be flagged with a message that an error has been reported with a timestamp and error type.  'This entry was flagged as having a <type> error at <timestamp>'.

This could initiate a workflow within ICE TV to investigate/resolve the error.  Once the error has been resolved, the error displayed in the EPG could either be removed or shown with the resolved timestamp.

The XML / JSON feeds could also carry a flag indicating that an error may be present.

The Kodi interface appears not to show these details, however, the TVH WebUI shows the error count on completed recordings.  Also, if you have any failed recordings, there is normally a status message.

http://icebox_ip:9981/

Thanks for the update.

How about an update on your IceBox plans for 2026?

Any new features or bug fixes scheduled?

For example, it could be handy to be able to manage keywords and series directly from within your Kodi addon.

Kodi v22 is on the horizon.  It is still in the release Alpha stage, but worth keeping an eye on.

I can confirm that a soft reset is needed in order for the icebox to recognise any additional tuners plugged in after initial set up.
A simple re boot will not get the new tuner recognised as such by the system.
In tvheadend it will show under tuners but in a grey font, any active / recognised tuners will be in bold font and be numbered #0 to #3 only after a soft reset.

I suspect that enabling the new (grey) adaptors and possibly assigning them to the existing DVB-T Network in within TVH is all that would have been required to make them operational.

My advice to to only use IceTV's app or website to set recordings.

What about adding that functionality to the IceTV Kodi addon?

The user could see new series or manage their keyword searches from within the IceBox UI without having to logon to the Web portal or use the App.

The reason I use this method to record Escape to the Country is that the episode information is very inconsistent.

@MD has also suggesting using the IceTV App or Web portal.

There is also the option of using a time-based 'Recording: Timer rule' [not (Guide based)] approach.  You could setup a 'Timer rule' the required times on 7TWO on those days.  The system will just keep making recordings at that time.  It will not adjust the times if they change (you will need lots of padding) and no EPG metadata will be stored.  You could create the time-based approach as a backup with low priority.

However, I reiterate, my first approach would be the Web portal or App.

I assumed the start and end time would restrict the recordings based on that.

I agree with you.

I tried the same thing on my system and got 19 scheduled recordings.  Almost all of those recordings started outside of the time range provided.

You may have found a bug in TVH (The back-end software).

I tried with the IceBox Kodi connected to the latest version of TVH on my test system and I only matched the expected programmes.  However, my test system used FTA EPG which carries a CRID whereas the IceTV EPG does not have a CRID (There is a recent TVH XMLTV/XPath PR that addresses this).  I can see that my OTA test system used the 'Series link' were my IceBox did not.

I manually created an Autorec on my test system providing the time parameters and it only found 2 programmes (this Sat and next Fri).  I created the same manual entry on my IceBox and again got 19 matches.

You could consider deleting what you have done locally on the IceBox, logon to the Ice TV Web portal and then create a series recording there.

I set the timer using the EPG on the IceBox.

Did you select 'Record' or 'Add timer'?



'Record' will just record this programme.  'Add timer' will create a local 'Autorec' that does a local keyword search that will match any programme matching the selected title.

ANy suggestions?

That depends on how technical you are.  I do this:

Code Select Expand

SSH to the IceBox.
systemctl stop kodi.service
nano ~/.kodi/userdata/addon_data/service.icetv/settings.xml
Set 'last_run' to 0.
Save and exit.
systemctl start kodi.service
This will tell the IceBox to reload ALL of the EPG.

Use with caution.  This method may void your warranty.

BTW can I screenshot from the IceBox.

Yes, but you will probably need to connect a USB keyboard to your IceBox to do so.  Ctrl+S.

https://kodi.wiki/view/Keyboard_controls

I have set a timer rule using the EPG to record Escape to the Country on Friday and Saturday with a start time of 8:30 pm and end time of 9:30 pm.

Where exactly did you set this?

Reflecting the inclusion of Series (Season) and episode number

I suspect that this 'feature' was always there, it's just that the series and episode numbers weren't being fed into TVH correctly.  From the update email I received:

Episode numbering is now correctly visible in the programme guide

Also, from the WebUI, you can go into Configuration/General/Base and set your default 'Items per page' so that you don't need to change it every time you change pages in the WebUI.