Read the statement by Michael Teeuw here.
MMM-SoccerLiveScore
-
@np27np27 can you try to check out from master now and let me know if the problem is gone? :D
-
@0m4r
Yes it works now! Thanks for the quick help and update ;) -
-
@np27np27 I guess you are correct, something is wrong since the second last update.
I have tried to reduce the number of API calls trying to have them issued only when games are on or about to start rather than each and every 2 mins… but sometimes things do not work as I expect.You should be able to see a message at the bottom of the standings telling you when the next API request is expected to be executed, that should help d figure if the new data are requested at a meaningful time.
-
@0m4r
For me the module has an api request date of yesterday! So it’s probably not called the api? -
@np27np27 probably. I have realized I have a mistake when the event is finished and the next date should be set to be used…
If you manually refresh with F5 or restart does it get any better?
-
@0m4r
Yes if you manually restart MM the the data updates. -
@np27np27 alright - I will try to fix it, but it may take some time, I usually dedicate time to my side project on the weekend
-
@0m4r
No problem, thanks for trying and keeping this module going 👍🏾👍🏾 -
@np27np27 can you try check out and run this branch:
https://github.com/0m4r/MMM-SoccerLiveScore/tree/feature/node-fetch> cd [YOUR_PATH_TO_MMM-SoccerLiveScore] > git fetch -p > git checkout feature/node-fetch > git pull -r > npm ci > [RESTART MM]
I did do some major changes (removed request for node-fetch, and some other code improvements amongst which I hope to have fixed the problem of the refresh you reported)