Joe_90
Moderator
@abu - what does the option to toggle the custom mode actually do?
I updated my dev version to 6.8.4.018 last night (8th March). I set the Custom Mode toggle to yes. (assuming it would retain the existing provider).
This morning's scheduled run of ABM failed with the following:
The sdcustom provider has been deleted from the system as per your post #32. My bouquets would no longer be updated and I wouldn't notice unless I ran ABM manually.
Is this the intended consequence of the change?
I've reverted to the standard Sky London HD provider in the meantime and ABM runs normally.
I updated my dev version to 6.8.4.018 last night (8th March). I set the Custom Mode toggle to yes. (assuming it would retain the existing provider).
This morning's scheduled run of ABM failed with the following:
Code:
< 584.515868> 04:30:00.7136 [eDVBChannel] OURSTATE: ok
< 584.680909> 04:30:00.8787 [ABM-main][checkTunerLock] ACQUIRING TSID/ONID
< 584.792957> 04:30:00.9907 [ABM-Manager][read] Reading sat_282_sky_uk (sdcustom_london)...
< 584.793447> 04:30:00.9912 [ABM-Manager][read] sat_282_sky_uk, Done
< 584.793736> 04:30:00.9915 [ABM-main][doScan] Cannot read data
< 584.804728> 04:30:01.0025 [ABM-Scheduler][runscheduleditemCallback] inStandby <class 'Screens.Standby.Standby'>
< 584.922038> 04:30:01.1198 [eDVBFrontend0] set dynamic current limiting
< 587.795948> 04:30:03.9937 [eDVBFrontend0] close frontend
The sdcustom provider has been deleted from the system as per your post #32. My bouquets would no longer be updated and I wouldn't notice unless I ran ABM manually.
Is this the intended consequence of the change?
I've reverted to the standard Sky London HD provider in the meantime and ABM runs normally.
