Read the statement by Michael Teeuw here.
MMM-Ring:  Module error
- 
 MMM-Ring: Module, is giving me this error when running pm2 logs, this is the only module failing. It was working good until I updated npm I think and now I can’t figure it out. 0|MagicMirror | [17.07.2021 00:33.49.258] [ERROR] 
 0|MagicMirror | 2021-07-17T00:33:49 (node:3641) UnhandledPromiseRejectionWarning: TypeError: Cannot read property ‘subscribe’ of undefined
 0|MagicMirror | at Class.monitorRingActivity (/home/pi/MagicMirror/modules/MMM-Ring/node_helper.js:84:40)
 0|MagicMirror | at Class.socketNotificationReceived (/home/pi/MagicMirror/modules/MMM-Ring/node_helper.js:61:12)
 0|MagicMirror | (/home/pi/MagicMirror/internal/process/warning.js:32 writeOut)
 0|MagicMirror | [17.07.2021 00:33.49.260] [ERROR]
 0|MagicMirror | 2021-07-17T00:33:49 (node:3641) 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: 1) (/home/pi/MagicMirror/internal/process/warning.js:32 writeOut)
 0|MagicMirror | [17.07.2021 00:33.49.261] [ERROR]
 0|MagicMirror | 2021-07-17T00:33:49 (node:3641) [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. (/home/pi/MagicMirror/internal/process/warning.js:32 writeOut)pi@mm:~/MagicMirror/modules/MMM-Ring $ npm list 
 MMM-Ring@1.0.0 /home/pi/MagicMirror/modules/MMM-Ring
 ├── chokidar@3.5.1
 ├── dotenv@8.6.0
 ├── hls.js@0.13.2
 ├── latest-version@5.1.0
 ├── ring-client-api@4.2.3
 └── rxjs@6.6.7pi@mm:~/MagicMirror/modules/MMM-Ring $ npm install latest-version up to date, audited 105 packages in 3s 1 package is looking for funding 
 runnpm fundfor details2 high severity vulnerabilities To address all issues (including breaking changes), run: 
 npm audit fix --forceRun npm auditfor details.Forgot to include npm version 
 pi@mm:~/MagicMirror $ npm -v
 7.19.1
- 
 @kanostic yes, we’ve seen some errors on npm 7. I would fall back to v6. 
- 
 @sdetweil Thanks I downgraded npm to 6.14.13 $ npm -v 
 6.14.13Restarted mm and I’m still getting the same error in the logs, do I need to reinstall MMM-Ring and all it’s dependencies? Thanks 
- 
 @kanostic maybe just npm install in the module folder 
- 
 @sdetweil Thank you doing a npm install and npm audit fix --force did the trick, apologies for all the basic questions, I am pretty new to Magic Mirror. 
- 
 @kanostic said in MMM-Ring: Module error: npm audit fix --force careful on that, many times it causes more problems than it fixes… 
 generally recommend to ignore the messages (and we can’t hide them)
- 
 @kanostic said in MMM-Ring: Module error: @sdetweil Thank you doing a npm install and npm audit fix --force did the trick, apologies for all the basic questions, I am pretty new to Magic Mirror. Good to know, thank you again. 
