SOLVED MMM-Tool stopped displaying in 2.17.1
i recently updated from 2.16.0 to 2.17.1 and MMM-Tools stopped being displayed on my mirror. All other modules are beeing displayed.
These are the errors I found in the log:
0|MagicMirror | [04.10.2021 09:07.15.554] [ERROR] 0|MagicMirror | (node:13630) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE] [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received type number (1) 0|MagicMirror | at Object.writeFile (fs.js:1436:5) 0|MagicMirror | at /home/pi/MagicMirror/modules/MMM-Tools/node_helper.js:308:29 0|MagicMirror | at new Promise (<anonymous>:null:null) 0|MagicMirror | at Class.getRecordUptime (/home/pi/MagicMirror/modules/MMM-Tools/node_helper.js:295:12) 0|MagicMirror | at Class.startScan (/home/pi/MagicMirror/modules/MMM-Tools/node_helper.js:50:54) 0|MagicMirror | at Class.socketNotificationReceived (/home/pi/MagicMirror/modules/MMM-Tools/node_helper.js:45:12) 0|MagicMirror | at Socket.<anonymous> (/home/pi/MagicMirror/js/node_helper.js:109:11) 0|MagicMirror | at Socket.emit (events.js:315:20) 0|MagicMirror | at Socket.emitUntyped (/home/pi/MagicMirror/node_modules/socket.io/dist/typed-events.js:69:22) 0|MagicMirror | at /home/pi/MagicMirror/node_modules/socket.io/dist/socket.js:428:39 0|MagicMirror | at processTicksAndRejections (internal/process/task_queues.js:75:11) 0|MagicMirror | (Use `electron --trace-warnings ...` to show where the warning was created) 0|MagicMirror | [04.10.2021 09:07.15.557] [ERROR] (node:13630) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2) 0|MagicMirror | [04.10.2021 09:07.15.562] [ERROR] 0|MagicMirror | (node:13630) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
On the author’s github (Bogsunet) there is no option to submit an issue. Can anyone help me further?
Thanks in advance!
@swvalenti Thanks a lot for the link! I’m just wondering why someone sets up a separate forum for a bunch of modules where you need a further login to get support…My professor in maths said once „there are things you have to believe, you can’t understand them“…a wise man.
Once I was the original creator of this module (and many others)
For some personal reasons, I couldn’t maintain my modules anymore at that time by myself. But I didn’t want to break the maintenance of the modules for the community. So I transferred all the ownership to any volunteer who wants to take over. I believed that they could keep the module’s maintenance and develop more than me.
After one and a half years passed, I return to this scene now.
What I see is, …
Some modules are being maintained still well, some are abandoned, some are, …
Well, I will not claim my ownership back, those modules are not mine anymore from my discard. And I believe everyone has his own good mind. So I don’t care.
However, a little sorry to you for this situation though.
Sometime I read and I …
@mmrize Thanks a lot for your response!
After reading through my emails this morning, I deeply regret that you had to hand over ownership and maintenance of your modules. Apparently, your regrets are partially deeper than mine, when you see what happened to your babies.
Last night, after @swvalenti pointed me to the new owner’s forum, I opened there an issue and requested support. A very nice guy tried to help me late at night, but in the end the owner himself closed and locked publicly my issue in an unexpected, rude and passively aggressive manor (see last comment in thread), of course without solving the issue.
So, I solved quickly the issue by myself by kicking out the module from my config, as well as any other module maintained by the new owner. I am sorry, that it unfortunately hit your module, cause I liked it and I had it installed from the very beginning.
Anyways, live goes on