Read the statement by Michael Teeuw here.
MMM-SoccerLiveScore
-
-
@np27np27 the API the module is fetching the data from does not seem to respond anymore (or at least, they do not in most of the cases).
I have tried with Postman to double-check if it is a problem with my code or of the API, but also with Postman I get the same error/problem.I am trying to figure if I can replace the API with others, but I have not found anything I can really move without losing some of the information or the functionalities implemented now.
-
@karsten13 this could be one reason (I plan to switch to node-fetch), but I experience the same problem as reported by @np27np27 and I have detected the APIs are responding with errors.
Unfortunately, there is not much I can do about it :(
-
@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)
-
@0m4r said in MMM-SoccerLiveScore:
@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 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)
Hi @0m4r ,
Ive tried the above but got an error at the checkout node-fetch line. Can’t find the file or something similar?
Still continued on and did the rest.
The mm restart has updated the module data. I will check when a game plays tonight to see if the live data changes. -
This post is deleted! -
@np27np27 said in MMM-SoccerLiveScore:
git checkout node-fetch
should be:
git checkout feature/node-fetch
-
@0m4r
OK tried again, this time I received the following after npm cinpm WARN prepare removing existing node_modules/ before installation
npm ERR! cipm can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file withnpm installbefore continuing.
npm ERR!
npm ERR!
npm ERR! Invalid: lock file’s node-fetch@2.6.6 does not satisfy node-fetch@v2.6.1
npm ERR!npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2021-12-06T22_20_06_917Z-debug
.log -
@np27np27 said in MMM-SoccerLiveScore:
@0m4r
OK tried again, this time I received the following after npm cinpm WARN prepare removing existing node_modules/ before installation
npm ERR! cipm can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file withnpm installbefore continuing.
npm ERR!
npm ERR!
npm ERR! Invalid: lock file’s node-fetch@2.6.6 does not satisfy node-fetch@v2.6.1
npm ERR!npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2021-12-06T22_20_06_917Z-debug
.logI did npm install then npm Ci and it seems no errors this time. Let’s see if it works now. I’ll let you know 👍🏾
-
Looks like it’s still not working. It’s gone past the api call date that is displayed at the bottom of the module and it’s not updated. Does it work for you?
-
@np27np27 can you try pulling the code once more? I did mess up the logic to re-issue the API requests, but I hopefully fixed it now!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login