Login at Kodi Home

robweber · 2017-01-04, 05:08

What is your goal with that, to run like every 4 hours between and 9am and 11pm? How about:

Code:
0 9,13,17,21 * * *

That would run every four hours between 9am and 11pm (actually stopping at 9 since there is only 2 hrs between). Yours might work but generally the first column is for digits between 0-60.

SliceOfPi · 2017-01-04, 19:14

Hi Rob. Yes, that's exactly what I was trying to do albeit more complicated than it needed to be! I'll try that cron expression and see how it goes.

robweber · 2017-01-04, 19:35

(2017-01-04, 19:14)SliceOfPi Wrote: Hi Rob. Yes, that's exactly what I was trying to do albeit more complicated than it needed to be! I'll try that cron expression and see how it goes.

Hope it works, that should at least stop the error.

robweber · 2017-01-31, 20:00

I'm making some changes to how custom paths are setup. The current version has 3 custom paths plus the ability to add more via a "custom.xml" file in the addon_data folder. I thought this was a bit messy.

I've added a custom paths setup tool to add "unlimited" custom paths with cron expressions right from within the settings. Anyone willing please take a look and see if this works for you. Be aware - any custom paths you had setup under the old system will disappear with this update so you'll have to add them with the new Custom Paths button in the settings.

https://github.com/robweber/xbmclibrarya...stom_paths

robweber · 2017-02-11, 20:30

It should work, no reason I can think of that it wouldn't. Post a log ASAP if you can with the error.

Anyone with the same issue? I have Krypton on a dev machine but not my main system yet.

Sent from my SM-G930V

DeadlyKnapsack · 2017-02-20, 09:10

(2017-02-11, 20:30)robweber Wrote: It should work, no reason I can think of that it wouldn't. Post a log ASAP if you can with the error.

Anyone with the same issue? I have Krypton on a dev machine but not my main system yet.

Sent from my SM-G930V (typie typie)

Where can I find the log?

robweber · 2017-02-20, 18:10

http://kodi.wiki/view/Log_file

The log file uploader add-on may or may not exist. I remember reading it is defunct somewhere.

Sent from my SM-G930V

voochi · (This post was last modified: 2017-02-28, 18:25 by voochi.)

In a future version would you consider adding finer granularity to the startup delay? Like perhaps a 10s startup delay?

On one system I find that update at 0s tends to bog down...system is busy or network not ready etc. But 1m delay is much longer than I need in this case. Something in between would be very nice.

MidKnight · 2017-03-21, 01:31

anyone else having an issue that this plugin has stopped working, using Milhouses Libreelec on a raspberry pi?

just noticed its no longer running a few days ago (could be longer), even when doing a manual run, it does nothing

DeadlyKnapsack · 2017-03-21, 11:14

(2017-02-20, 18:10)robweber Wrote: http://kodi.wiki/view/Log_file

The log file uploader add-on may or may not exist. I remember reading it is defunct somewhere.

Sent from my SM-G930V (typie typie)

Bit of a late reply, but I started with a fresh install of Kodi (OSMC) and reinstalled your amazing add-on and it works perfectly fine. I guess something went wrong while updating from previous version of Kodi.

robweber · 2017-04-05, 21:46

(2017-02-28, 18:23)voochi Wrote: In a future version would you consider adding finer granularity to the startup delay? Like perhaps a 10s startup delay?

On one system I find that update at 0s tends to bog down...system is busy or network not ready etc. But 1m delay is much longer than I need in this case. Something in between would be very nice.

Not a bad idea but from a practical perspective hard to implement. The current timing system is all based on checking if an update should be started every X minutes. The delay just adds an offset to the expected run time. I could very easily add the options but it would require some drastic changes to the timer system to check more often than once a minute. Technically possible but it would be a lot more checks (say once every 10 seconds) for something that would only really happen during system startup. For all other library checks you'd be waiting at least a minute.

If I'm every tinkering with the timer code I'll give this some thought.

SanderBroek · 2017-07-11, 20:42

Wat is thuis add-on no more in the kodi repo?

**pagali** · 2017-07-11, 22:42

It's still there. Just do a search in add-ons for "library" It's a script, actually.

JockeSve · (This post was last modified: 2017-08-14, 08:50 by JockeSve.)

(2017-01-04, 19:14)SliceOfPi Wrote: Hi Rob. Yes, that's exactly what I was trying to do albeit more complicated than it needed to be! I'll try that cron expression and see how it goes.

How did that work?
Is it better to use

Code:
0 4,8,12,16,20 * * *

or

Code:
0 */4 * * *

to run scanning every 4 hours?
Running LibreElec 8 on RPi

(Sorry for noobish Q...)

robweber · 2018-01-11, 17:35

(2017-08-14, 08:46)JockeSve Wrote: How did that work?
Is it better to use

Code:
0 4,8,12,16,20 * * *
or

Code:
0 */4 * * *
to run scanning every 4 hours?
Running LibreElec 8 on RPi

(Sorry for noobish Q...)

The two statements basically amount to the same thing, the second one is just a lot easier to read. In your first statement you missed the "0" hour but otherwise you'll run the script every 4 hours. The second statement is just a shorthand */4 amounts to every four hours as well - which for cron will default to 0,4,8,12,16,20.