Any chance of an early release of the IceTV plugin version 20190308?

[Grumpy_Geoff]

Is there any chance of the new version (20190308) of the IceTV plugin being made as an early availability so we so we can download and install it independent of the future 19.3-series that contains it?
I ask because a few of us are seeing the "duplicate" IceTV timers issue in greater numbers (of timers and users) than previously seen.
I believe the fix we're mainly after is this -
"There appears to be a further bug associated with this issue in that sometimes the timer being updated has its ice_timer_id set to None, but it is not deleted."
which was part of the fix for Issue 710 - [IceTV] Unnecessary updates on unchanged timers.

See this and subsequent posts on the IceTV forum.


Cheers,
Geoff

[Paul_oz53]

+1. I'd be happy to patch it in manually.

PS We have too many shows to replicate to ever swap to autotimers.

PPS Noticed the duplication last night - two recordings of The Voice.

[adoxa]

Here's the latest from the V2 beta feed, changed to "all".

[Grumpy_Geoff]

Here's the latest from the V2 beta feed, changed to "all".

Cheers.
I was guessing you'd be the man, given prl is away and peteru normally gets on late.

I'll chuck it on. Ta.

[Grumpy_Geoff]

That .ipk didn't successfully install

[adoxa]

Sorry 'bout that. Updated the previous attachment (verified it installs, but didn't check it actually works).

[Grumpy_Geoff]

Executive summary -
You probably don't need to update to this new plugin version just yet.


I've been running the new 20190327 version on our T4 since yesterday.
Until about an hour ago, I wasn't having much luck with it - I didn't think this was a plugin issue, but wanted to wait until the issue was resolved before posting.

I could get the plugin to fetch the EPG okay, and timers set on the T4 would update the IceTV server; but timers initiated from IceTV weren't being fetched.
I tried an IceTV disable/enable, a server login, even a setup wizard - nothing seemed to fix it, so I logged an issue with IceTV support.
The reply from IceTV support indicated I had a new T4 device appear in the IceTV servers. This then took me along some false steps to removing the "new" device and keep attempting to get the "old" one to fetch.
I updated the support ticket with info that I seemed to be in a rinse-repeat "new device" cycle every time I logged in.

Eventually I gave up on waiting on IceTV support after about 2 hours (I'm not complaining about the timing), I ran the wizard again to generate a "new#2" device, used the "copy series timers" function to copy the timers to it, followed by a resend all for "new#2". I set some one-off timers and, Bob's your uncle, they're being fetched.

It turns out the issue stems back from when I had the T4 tuner regulator heatsink cement issues back on 31-Mar and Mark/warkus swapped T4s with me. Even though prl warned me that IceTV wouldn't work on the swapped unit, I found it did work okay after the settings restore and thought no more about it.
About an hour after I copied the timers to the "new#2" device, I heard back again from IceTV support who stated the MAC address had changed and thus the new device.
I'm guessing that even though the MAC address had changed, having the same plugin version, device ID, and token allowed the plugin to fetch timers since 31-Mar until I changed the plugin yesterday.
Yesterday the IceTV server must have decided the new plugin version (or whatever else it reports to the IceTV server) was enough for "server says no".

Now, to finish up, I was also having a bunch of -
Can not retrieve channel map: HTTPConnectionPool(host='api.icetv.com.au', port=80): Read timed out. (read timeout=10.0) errors. It turns out others were too. I had 100 of them last month, and 49 this month. It's believed that this gives rise to the "duplicate" IceTV timer issue when the updated timer is accepted and then the plugin can't get back to the IceTV server to ack the old timer deletion.
IceTV support have nuked the cause (full table) and thus this issue shouldn't occur, and the reason for updating to the new IceTV plugin isn't as urgent as once thought. phew...

[raymondjpg]

...Even though prl warned me that IceTV wouldn't work on the swapped unit, I found it did work okay after the settings restore and thought no more about it....

There is probably history for this but I'm curious as to why IceTV might not work on the swapped unit (?)

Now, to finish up, I was also having a bunch of -
Can not retrieve channel map: HTTPConnectionPool(host='api.icetv.com.au', port=80): Read timed out. (read timeout=10.0) errors. It turns out others were too.

So happens that I am "others" and I can confirm that IceTV fetches appear to be working normally today after a full table was cleared at the IceTV end yesterday.

[MrQuade]

There is probably history for this but I'm curious as to why IceTV might not work on the swapped unit (?)

Because the hardware swap meant that the T4 appears to IceTV to be a different box, therefore it would show up as a different PVR in IceTV. As-per GG's post though, there were some complicating factors.

[Grumpy_Geoff]

There is probably history for this but I'm curious as to why IceTV might not work on the swapped unit (?)

Because the hardware swap meant that the T4 appears to IceTV to be a different box, therefore it would show up as a different PVR in IceTV. As-per GG's post though, there were some complicating factors.

Yep, that's it.
I should have more precisely written 'Even though prl warned me that IceTV wouldn't immediately work on the swapped unit, I found it did work okay after the settings restore and thought no more about it.'
See Whingepool post and my reply to it, and also prl's follow up.

The settings have an IceTV token and device ID amongst other IceTV values. The changed MAC ID should've meant the IceTV server wouldn't recognise the swapped in T4 as being on my account, but I'm guessing that the token and device ID restored from settings, combined with using the same IceTV plugin version, created a perfect match and everything worked for two and a bit months. I think the introduction of the new plugin version upset the apple cart (as the plugin version is sent to the IceTV server along with the token and user name/email address), and the T4 no longer had that perfect match.
There were enough details such that when I used the plugin to login to the Ice server, it would create a new device ID (unbeknownst to me).

[raymondjpg]

Thanks for the explanation. Makes sense to me now.

Regards

[prl]

Don't copy settings files from one box to another if you use IceTV. Like gravity, it's not just a good idea, it's the law.

[Grumpy_Geoff]

Don't copy settings files from one box to another if you use IceTV. Like gravity, it's not just a good idea, it's the law.

Yeah, I don't really have a defence, except "it worked at the time". But two months later...

[peteru]

I don't really have a defence, except "it worked at the time".

It not so much worked as it exploited a security hole in IceTV's service.

[Grumpy_Geoff]

I don't really have a defence, except "it worked at the time".

It not so much worked as it exploited a security hole in IceTV's service.

shhh

[prl]

I don't really have a defence, except "it worked at the time".

It not so much worked as it exploited a security hole in IceTV's service.

While that's true, it's an exploit that tends to bite the exploiter back.

[Paul_oz53]

Here's the latest from the V2 beta feed, changed to "all".

Just a quick update to say no duplicated recordings since running the plugin as updated (should I call it an alpha? Maybe not).

[Grumpy_Geoff]

Just a quick update to say no duplicated recordings since running the plugin as updated (should I call it an alpha? Maybe not).

Same same me

[prl]

Here's the latest from the V2 beta feed, changed to "all".

Just a quick update to say no duplicated recordings since running the plugin as updated (should I call it an alpha? Maybe not).

I think its status is "escapee"

[Paul_oz53]

Here's the latest from the V2 beta feed, changed to "all".

Just a quick update to say no duplicated recordings since running the plugin as updated (should I call it an alpha? Maybe not).

I think its status is "escapee"