Read the statement by Michael Teeuw here.
MMM-News
-
@sdetweil
I don’t want to make an argument about your success. The difficulty is always relative. :)As you’ve said, all cloned modules should manage their own ID by themselves. (not only for the one device but also for each clients if multi-devices are working under server-clients)
It could not be difficult, frankly, usual web sites/applications/components are developed like that.
But the MM… hmmm. I always consider MM would be a standalone running device. Even though there exist some server/client usecases, most of the modules are developed as standalone. Using H/W peripheral(like GPIO or mic) is an example.
Of course, we, developers can make the module clonable from the early stage of development. But I often have a question it’s worthy.For an imaginary use-case of other users, should I consider to make module clonable? Always my answer for this MM was… no.
Because;- I’m not using clones. If I need something similar, I would make a new module, which might be able to manage multi-views(like CALEXT2) or to share some resources.(AMK2 and HOTWORDS), but it makes things too complex. I hate this way.
- I feel some cul-de-sac from MM legacy. MM needs to provide more friendly way to reuse modules. At this moment, not. So that’s why I haven’t considered cloning. and why I lost interest in MM.
Anyway, to say shortly. This module is not made for that purpose. Unless modification by myself or somebody, not possible. That’s all.
-
@Sean yes, I understand. I have made a couple this way , because the use case shows multiple instances very quickly.
but many do not, if they are hardware constrained…
-
git pull and npm install says it updated packages but when I check the version in the package.json it shows 2.0.0? What am I doing wrong? Thanks
pi@raspberrypi:~ $ cd MagicMirror pi@raspberrypi:~/MagicMirror $ cd modules pi@raspberrypi:~/MagicMirror/modules $ cd MMM-News pi@raspberrypi:~/MagicMirror/modules/MMM-News $ git pull Updating 081fcb2..bff080d pi@raspberrypi:~/MagicMirror/modules/MMM-News $ npm install audited 95 packages in 3.8s found 0 vulnerabilities>\
-
Anyone having an issue of news feed working then not working…just a black screen in the mirror portion position.
-
Yes, i have this problem this week, don’t know really why.
i have not read log for debugging itNext time, if i have this problem i will see what happen
-
@Bugsounet ok thanks, let me know if I can do anything to help.
-
Anything I can do in the mean time to troubleshoot to help get this resolved. It is happening now, I looked in the dev window but didn’t see any errors. I don’t know where else to look. Attached should show the news on the bottom bar but nothing there. Thanks, Scott
-
@Bugsounet Just circling back on this…would it be easier if I created an issue on github or leave it here?
-
@swvalenti whos news? did u look in the console window where u started MM?
or pm2 logs if using pm2?
news and calendar use the node_helper to fetch info…
-
Thanks Sam, checked the pm2 logs and unbeknownst to me…they now went to a paid tier api it seems!
1|MagicMir | [2020-11-17 16:23:16.523] [LOG] [NEWS] Error : https://newsapi.org/v2/top-headlines?country=us&pageSize=20&apiKey=99d1bd76c7f140f58c237d54c41ab334 result.code:You have made too many requests recently. Developer accounts are limited to 100 requests over a 24 hour period (50 requests available every 12 hours). Please upgrade to a paid plan if you need more requests.