@sdetweil Wow, thank you so much! Perfect :folded_hands: :grinning_face_with_big_eyes:
Read the statement by Michael Teeuw here.
Best posts made by chrisfr1976
-
RE: MMM-weconnectid with 2 accounts
-
RE: MMM-euro2024
@0m4r There is a problem with the token. I think, I’m stupid, but:
You write for the config
token: [YOUR_TOKEN]
So I’ve tried
token:[1234567890],
With this I get an error in the config.js and the mirror does not start up.
Then I’ve triedtoken:1234567890,
. Same issue.
Then I’ve triedtoken:"1234567890",
Then the config.js is okay and electron starts. But in this case I get an error message:
[ERROR] MMM-euro2024 fetchTeams 2018 {"message":"Your API token is invalid.","errorCode":400}
…of course I received a real API-key from Daniel. Copy+paste, so the key real in my config is okay.
How should I enter the API-Key? :thinking_face:
Latest posts made by chrisfr1976
-
RE: MMM-euro2024
@0m4r There is a problem with the token. I think, I’m stupid, but:
You write for the config
token: [YOUR_TOKEN]
So I’ve tried
token:[1234567890],
With this I get an error in the config.js and the mirror does not start up.
Then I’ve triedtoken:1234567890,
. Same issue.
Then I’ve triedtoken:"1234567890",
Then the config.js is okay and electron starts. But in this case I get an error message:
[ERROR] MMM-euro2024 fetchTeams 2018 {"message":"Your API token is invalid.","errorCode":400}
…of course I received a real API-key from Daniel. Copy+paste, so the key real in my config is okay.
How should I enter the API-Key? :thinking_face:
-
RE: MM failed after updating
@sdetweil I was able to fix it.
git reset --hard
followed bynpm run install-mm
fixed the issue. I don’t know why but now everything is fine again. I’ll do a SD-card back-up now :-) -
RE: MM failed after updating
In the beginning I’ve used the described update method here:
https://docs.magicmirror.builders/getting-started/upgrade-guide.html
So only
git pull && npm run install-mm
was used. But I’ve used the back-up script you’ve provided. Then I found also your update script. I’ve used it then, too. But same error. I’ll send the update.log via email :-)Here the lines around line 87. I’ve marked it to show the position only:
// Loads a package.json at given path and JSON parses static async load (path, opts = {}) { const p = new PackageJson() // Avoid try/catch if we aren't going to create if (!opts.create) { return p.load(path) } *87* try { return await p.load(path) } catch (err) { if (!err.message.startsWith('Could not read package.json')) { throw err } return await p.create(path) } }
Chris.
-
RE: MM failed after updating
Same issue here:
chris@MagicPi:~/MagicMirror $ pm2 logs --lines=75 [TAILING] Tailing last 75 lines for [all] processes (change the value with --lines option) /home/chris/.pm2/pm2.log last 75 lines: PM2 | 2024-04-03T10:25:09: PM2 log: App [mm:0] starting in -fork mode- PM2 | 2024-04-03T10:25:09: PM2 log: App [mm:0] online PM2 | 2024-04-03T10:25:30: PM2 log: App [mm:0] exited with code [1] via signal [SIGINT] PM2 | 2024-04-03T10:25:30: PM2 log: App [mm:0] starting in -fork mode- PM2 | 2024-04-03T10:25:30: PM2 log: App [mm:0] online PM2 | 2024-04-03T10:25:48: PM2 log: Stopping app:mm id:0 PM2 | 2024-04-03T10:25:48: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT] PM2 | 2024-04-03T10:25:48: PM2 log: pid=3783 msg=process killed /home/chris/.pm2/logs/mm-out.log last 75 lines: /home/chris/.pm2/logs/Display-Drehen-out.log last 75 lines: /home/chris/.pm2/logs/Display-Drehen-error.log last 75 lines: /home/chris/.pm2/logs/mm-error.log last 75 lines: 0|mm | npm ERR! code EJSONPARSE 0|mm | npm ERR! JSON.parse Invalid package.json: JSONParseError: Expected double-quoted property name in JSON at position 3351 (line 87 column 1) while parsing near "...moment\": \"^2.30.1\",\n<<<<<<< Updated upst..." 0|mm | npm ERR! JSON.parse Failed to parse JSON data. 0|mm | npm ERR! JSON.parse Note: package.json must be actual JSON, not just JavaScript. 0|mm | 0|mm | npm ERR! A complete log of this run can be found in: /home/chris/.npm/_logs/2024-04-03T08_25_30_215Z-debug-0.log
Complete log:
0 verbose cli /usr/bin/node /usr/bin/npm 1 info using npm@10.5.0 2 info using node@v21.7.1 3 timing npm:load:whichnode Completed in 5ms 4 timing config:load:defaults Completed in 5ms 5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 1ms 6 timing config:load:builtin Completed in 2ms 7 timing config:load:cli Completed in 6ms 8 timing config:load:env Completed in 2ms 9 timing config:load:file:/home/chris/MagicMirror/.npmrc Completed in 5ms 10 timing config:load:project Completed in 7ms 11 timing config:load:file:/home/chris/.npmrc Completed in 1ms 12 timing config:load:user Completed in 1ms 13 timing config:load:file:/usr/etc/npmrc Completed in 1ms 14 timing config:load:global Completed in 1ms 15 timing config:load:setEnvs Completed in 3ms 16 timing config:load Completed in 27ms 17 timing npm:load:configload Completed in 27ms 18 timing config:load:flatten Completed in 7ms 19 timing npm:load:mkdirpcache Completed in 0ms 20 timing npm:load:mkdirplogs Completed in 0ms 21 verbose title npm start 22 verbose argv "start" 23 timing npm:load:setTitle Completed in 2ms 24 timing npm:load:display Completed in 2ms 25 verbose logfile logs-max:10 dir:/home/chris/.npm/_logs/2024-04-03T08_25_30_215Z- 26 verbose logfile /home/chris/.npm/_logs/2024-04-03T08_25_30_215Z-debug-0.log 27 timing npm:load:logFile Completed in 23ms 28 timing npm:load:timers Completed in 0ms 29 timing npm:load:configScope Completed in 0ms 30 timing npm:load Completed in 107ms 31 silly logfile start cleaning logs, removing 2 files 32 timing command:run-script Completed in 21ms 33 timing command:start Completed in 36ms 34 verbose stack JSONParseError: Invalid package.json: JSONParseError: Expected double-quoted property name in JSON at position 3351 (line 87 column 1) while parsing near "...moment\": \"^2.30.1\",\n<<<<<<< Updated upst..." 34 verbose stack at PackageJson.fromJSON (/usr/lib/node_modules/npm/node_modules/@npmcli/package-json/lib/index.js:162:24) 34 verbose stack at PackageJson.load (/usr/lib/node_modules/npm/node_modules/@npmcli/package-json/lib/index.js:156:17) 34 verbose stack at async PackageJson.normalize (/usr/lib/node_modules/npm/node_modules/@npmcli/package-json/lib/index.js:115:5) 34 verbose stack at async RunScript.run (/usr/lib/node_modules/npm/lib/commands/run-script.js:72:27) 34 verbose stack at async module.exports (/usr/lib/node_modules/npm/lib/cli-entry.js:61:5) 35 verbose cwd /home/chris/MagicMirror 36 verbose Linux 6.1.21-v7l+ 37 verbose node v21.7.1 38 verbose npm v10.5.0 39 error code EJSONPARSE 40 error JSON.parse Invalid package.json: JSONParseError: Expected double-quoted property name in JSON at position 3351 (line 87 column 1) while parsing near "...moment\": \"^2.30.1\",\n<<<<<<< Updated upst..." 41 error JSON.parse Failed to parse JSON data. 41 error JSON.parse Note: package.json must be actual JSON, not just JavaScript. 42 verbose exit 1 43 timing npm Completed in 228ms 44 verbose code 1 45 error A complete log of this run can be found in: /home/chris/.npm/_logs/2024-04-03T08_25_30_215Z-debug-0.log
:anxious_face_with_sweat:
Cheers,
Chris. -
RE: MMM-weconnectid with 2 accounts
@sdetweil Wow, thank you so much! Perfect :folded_hands: :grinning_face_with_big_eyes:
-
RE: MMM-weconnectid with 2 accounts
Short update: CalendarExt3 is now okay. Maybe it needed just some more time.
And the SoC is just missing. The remaining km-range is there. I checked it in the cars. The value is correct.
-
RE: MMM-weconnectid with 2 accounts
@sdetweil Okay, nearly okay. I see the module twice on the screen. The following issues are on my Mirror:
- SoC for both cars is 0% - main point of interest :-)
- The pictures are the same (it is stored in the same folder with the same name. That is the reason for sure.) - not really needed
- My Calendar Ext3 stays empty. All events are broadcasted without any error. That is something in behind. I had that before when both modules (the original and my copy if both had
enabled=true
set). No error in the logs or any entry that is new for me.
-
RE: MMM-weconnectid with 2 accounts
@sdetweil Hello, yes, sorry for that delay. Yesterday I was out with my company colleagues :clinking_beer_mugs:
I’ve just tested the configuration:
- same module, twice in the config
- my copied module with new name with the original module together
then both versions with “git checkout main” and for doublecheck your “git checkout test_multi-2”.
And unfortunately without success. For Option 1 it stops with “loading…”. For Option 2 I get 1 car shown without any information from VW and the other stops also with “loading…” on the screen.
In the logs I just get this:
0|mm | [22.02.2024 19:12.02.704] [LOG] Got data from weconnectid for VIN WVWZZZE1ZNP0339xx 0|mm | [22.02.2024 19:12.07.203] [LOG] Got data from weconnectid for VIN WV2ZZZEB5PH0306xx
No Errors.
So same issue as last time. :crying_face:
-
RE: MMM-weconnectid with 2 accounts
@sdetweil unfortunately it works just a little.
I can see two modules the first time on my screen but I can’t see the SoC and the loaded pictures shows the same car. That is clear for me when I check the module.js file. But 2 different cars are loaded what can be seen on the run kilometers.
So your approach works in general to show the module twice. Thank you for that. That might be helpful for other modules, too.
But to get the MMM-weconnectid fully working there needs to be some more coding in the module.js to be done. Python grabs the information I think since I see no errors or strange things in the log.
Unfortunately I’m a mechanical engineer who just starts with some very simple coding. I can’t fix that.But again thanks a lot for your support and time you’ve spent!
Chris.
-
RE: MMM-weconnectid with 2 accounts
@sdetweil Wow, sure I can wait. But I’m already excited :-)