@chris47803 no. sorry

Hello, I use the MM-TomTom Traffic module I received this email below from tomtom yesterday, and I am having trouble understanding this email. Will this change something for the module, is there an update to do and which one ? "We’d like to notify you about the deprecation of Traffic Incidents Details API v4, part of the Traffic API family. The deprecation will be effective as of 04/13/2021 under the TomTom deprecation policy. The planned withdrawal date is in one year later, on 04/13/2022. Why is this happening? We’re constantly making improvements in our products based on feedback from the users. In this update specifically, we eliminated superfluous steps, simplifying the overall usage. Here’s the changes to expect with version 5 of the Traffic Incidents Details API: | Only EPSG4326 coordinate system is supported; | Only JSON format is supported; | Flexibility to work with selected attributes only: | Bandwidth optimization (no over- and under-fetching problems) | Adding new attributes is always backward compatible and does not affect existing clients | Support for event codes (Alert-C); | No relation to styles or visualization: | - No shifted geometry provided | - No support for clusters | Different bounding-box limitation | Clearer end-point parameter names" This is the link of TomTom Traffic API : https://developer.tomtom.com/traffic-api/traffic-api-documentation-traffic-incidents/incident-details-v4?utm_source=oneoff&utm_medium=email&utm_campaign=dev_all_trafficincidentdetailsdeprecation_202104_oo_news

I’m sorry I restarted the PI 3 times. It works now

Suddenly MMM-AllsvenskanStandings doesn’t work any longer. Worked fine before but now no data is loaded: [image: 1618333020294-c7ff2992-5c36-44f0-8d1b-5774b04f4388-image.png]

@jack_barnard the items after position need to be in a config section { module: position: config:{ . dateFormat: . } }

Looks like they changed the UI again… no idea where it is… similar problem on Amazon… can’t activate services on a device cause its not recognized as an approved commercial device

@tippon Thanks this now working perfectly.

@caxapok I created a module for this https://github.com/sdetweil/MMM-PythonPrint.git

@sceetch Hi, This is what I’m running with 8 gigs of ram and an SSD. :)

@sdetweil Here you go: install starting - Fri Apr 9 08:58:51 EDT 2021 installing on armv7l processor system the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) $ ^[[96mUpdating packages ...^[[90m Hit:1 http://archive.raspberrypi.org/debian buster InRelease Hit:2 http://raspb$ apt-get update completed ok apt-get upgrade started apt upgrade result =rc=0 Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ^[[96mInstalling helper tools ...^[[90m Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.6). curl is already the newest version (7.64.0-4+deb10u2). git is already the newest version (1:2.20.1-2+deb10u3). unzip is already the newest version (6.0-23+deb10u2). wget is already the newest version (1.20.1-1.1). wget set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ^[[96mCheck current Node installation ...^[[0m ^[[93mNode.js is not installed.^[[0m ^[[96mInstalling Node.js ...^[[90m Node release info = ## Installing the NodeSource Node.js 10.x repo... ## Popula$ v10.24.1 ^[[92mNode.js installation Done! version=v10.24.1^[[0m ^[[96mCheck current NPM installation ...^[[0m ^[[0mNPM currently installed. Checking version number. ^[[0mMinimum npm version: ^[[1mV6.0.0^[[0m ^[[0mInstalled npm version: ^[[1mV6.14.12^[[0m ^[[92mNo npm upgrade necessary.^[[0m ^[[96mCloning MagicMirror ...^[[90m ^[[92mCloning MagicMirror Done!^[[90m package.json update for armv7l completed ok ^[[96mInstalling dependencies ...^[[90m ^[[92mDependencies installation Done!^[[90m fixing sandbox permissions setting up initial config.js ^[[96mCheck plymouth installation ...^[[0m ^[[90mSplashscreen: Checking themes directory.^[[0m ^[[90mSplashscreen: Create theme directory if not exists.^[[0m ^[[92mSplashscreen: Changed theme to MagicMirror successfully.^[[0m install and setup pm2 pm2 not installed, installing pm2 install result /usr/bin/pm2 -> /usr/lib/node_modules/pm2/bin/pm2 /usr/bin/p$ get the pm2 platform specific startup command startup command = sudo env PATH=$PATH:/usr/bin:/bin /usr/lib/node_modules/pm2/b$ ------------- __/\\\\\\\\\\\\\____/\\\\____________/\\\\____/\\\\\\\\\_____ _\/\\\/////////\\\_\/\\\\\\________/\\\\\\__/\\\///////\\\___ _\/\\\_______\/\\\_\/\\\//\\\____/\\\//\\\_\///______\//\\\__ _\/\\\\\\\\\\\\\/__\/\\\\///\\\/\\\/_\/\\\___________/\\\/___ _\/\\\/////////____\/\\\__\///\\\/___\/\\\________/\\\//_____ _\/\\\_____________\/\\\____\///_____\/\\\_____/\\\//________ _\/\\\_____________\/\\\_____________\/\\\___/\\\/___________ _\/\\\_____________\/\\\_____________\/\\\__/\\\\\\\\\\\\\\\_ _\///______________\///______________\///__\///////////////__ Runtime Edition PM2 is a Production Process Manager for Node.js applications with a built-in Load Balancer. Start and Daemonize any application: $ pm2 start app.js Load Balance 4 instances of api.js: $ pm2 start api.js -i 4 Monitor in production: $ pm2 monitor Make pm2 auto-boot at server restart: $ pm2 startup To go further checkout: http://pm2.io/ ------------- [PM2] Init System found: systemd Platform systemd Template [Unit] Description=PM2 process manager Documentation=https://pm2.keymetrics.io/ After=network.target [Service] Type=forking User=pi LimitNOFILE=infinity LimitNPROC=infinity LimitCORE=infinity Environment=PATH=$PATH:/usr/bin:/bin:/bin:/usr/local/sbin:/usr/local/bin:/usr/s$ Environment=PM2_HOME=/home/pi/.pm2 PIDFile=/home/pi/.pm2/pm2.pid Restart=on-failure ExecStart=/usr/lib/node_modules/pm2/bin/pm2 resurrect ExecReload=/usr/lib/node_modules/pm2/bin/pm2 reload all ExecStop=/usr/lib/node_modules/pm2/bin/pm2 kill [Install] WantedBy=multi-user.target Target path /etc/systemd/system/pm2-pi.service Command list [ 'systemctl enable pm2-pi' ] [PM2] Writing init configuration in /etc/systemd/system/pm2-pi.service [PM2] Making script booting at startup... [PM2] [-] Executing: systemctl enable pm2-pi... [PM2] [v] Command successfully executed. +---------------------------------------+ [PM2] Freeze a process list on reboot via: $ pm2 save [PM2] Remove init script via: $ pm2 unstartup systemd pm2 startup command done configure the pm2 config file for MagicMirror start MagicMirror via pm2 now save MagicMirror pm2 config now stop MagicMirror via pm2 now disable screensaver via gsettings was true and uint32 300 disable screensaver via lightdm.conf disable screensaver via lxsession ^[[92mWe're ready! Run ^[[1m^[[97mpm2 start MagicMirror^[[0m^[[92m from the ~/M$ install completed - Fri Apr 9 09:04:39 EDT 2021

How to add MagicMorror as a device in Google Home app?

@mykle1 Only thing I can think is my PiHole is catching something and blocking it. I’ll disable and give it a try. Thanks for checking!

Hello, I’m having error when checking my config file : [07.04.2021 18:28.20.938] [ERROR] Line 115 column 93: Parsing error: Parenthesized pattern It seems to be caused by the customCommand. Could someone help me finding out what is wrong in my syntax ? customCommands: [ { command: "nextpage", description: "Passe à la page suivante", callback: (command, handler) => { self.sendNotification("PAGE_INCREMENT"), handler.reply("TEXT", "Voici la page suivante!") } }, { command: "previouspage", description: "Passe à la page précédente", callback: (command, handler, self) => { self.sendNotification("PAGE_DECREMENT") handler.reply("TEXT", "Voici la page précédente!") } }, { command: "pronote", description: "Passe à la page PRONOTE", callback: (command, handler, self) => { self.sendNotification("PAGE_CHANGED",6) handler.reply("TEXT", "Voici ProNote!") } }, { command: "pause", description: "Stop la rotation automatique", callback: (command, handler, self) => { self.sendNotification("PAUSE_ROTATION") handler.reply("TEXT", "OK, rotation arretée") } }, { command: "resume", description: "Redémarre la rotation automatique", callback: (command, handler, self) => { self.sendNotification("RESUME_ROTATION") handler.reply("TEXT", "OK, rotation démarrée") } } ] Thanks

@lavolp3 hm… if u turn on debug ( add “DEBUG” to the logLevel variable array in config.js can u identify the calendar entry causing trouble… and be willing to share with me… (chat is good)

@ujwalreddy267 i don’t know… the doc says all, i don’t think we know what the pickle file looks like

@robinsin17 I am home now from the hospital, but your task is still a big one. amazon is supporting their avs ask google has their assistant api.

@oberfragger ah… got it…

@sdetweil Well… we are here again: npm run start errors: [03.04.2021 21:46.00.432] [ERROR] (node:2588) UnhandledPromiseRejectionWarning: Error: invalid_grant at createError (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/core/createError.js:16:15) at settle (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/core/settle.js:18:12) at IncomingMessage.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/adapters/http.js:202:11) at IncomingMessage.emit (events.js:327:22) at endReadableNT (_stream_readable.js:1220:12) at processTicksAndRejections (internal/process/task_queues.js:84:21) [03.04.2021 21:46.00.435] [ERROR] (node:2588) 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) [03.04.2021 21:46.00.439] [ERROR] (node:2588) [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. [03.04.2021 21:47.03.919] [ERROR] (node:2588) UnhandledPromiseRejectionWarning: Error: invalid_grant at createError (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/core/createError.js:16:15) at settle (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/core/settle.js:18:12) at IncomingMessage.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/adapters/http.js:202:11) at IncomingMessage.emit (events.js:327:22) at endReadableNT (_stream_readable.js:1220:12) at processTicksAndRejections (internal/process/task_queues.js:84:21) [03.04.2021 21:47.03.922] [ERROR] (node:2588) 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: 4) [03.04.2021 21:47.59.391] [ERROR] (node:2588) UnhandledPromiseRejectionWarning: Error: invalid_grant at createError (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/core/createError.js:16:15) at settle (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/core/settle.js:18:12) at IncomingMessage.handleStreamEnd (/home/pi/MagicMirror/modules/MMM-GooglePhotos/node_modules/google-auth-library/node_modules/axios/lib/adapters/http.js:202:11) at IncomingMessage.emit (events.js:327:22) at endReadableNT (_stream_readable.js:1220:12) at processTicksAndRejections (internal/process/task_queues.js:84:21) [03.04.2021 21:47.59.392] [ERROR] (node:2588) 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: 6) developers window: Load script: modules/MMM-GoogleAssistant/MMM-GoogleAssistant.js module.js:508 Check MagicMirror version for module 'MMM-GoogleAssistant' - Minimum version: 2.14.0 - Current version: 2.15.0 module.js:516 Module registered: MMM-GoogleAssistant loader.js:157 Bootstrapping module: MMM-GoogleAssistant loader.js:185 Load script: /modules/MMM-GoogleAssistant/components/response.js loader.js:162 Scripts loaded for: MMM-GoogleAssistant loader.js:204 Load stylesheet: /modules/MMM-GoogleAssistant/MMM-GoogleAssistant.css loader.js:164 Styles loaded for: MMM-GoogleAssistant translator.js:107 MMM-GoogleAssistant - Load translation fallback: translations/en.json loader.js:166 Translations loaded for: MMM-GoogleAssistant MMM-Assistant2Display.js:687 [A2D] Found: GoogleAssistant loader.js:185 Load script: modules/MMM-GooglePhotos/MMM-GooglePhotos.js module.js:516 Module registered: MMM-GooglePhotos loader.js:157 Bootstrapping module: MMM-GooglePhotos loader.js:162 Scripts loaded for: MMM-GooglePhotos loader.js:204 Load stylesheet: modules/MMM-GooglePhotos/MMM-GooglePhotos.css loader.js:164 Styles loaded for: MMM-GooglePhotos loader.js:166 Translations loaded for: MMM-GooglePhotos module.js:199 MMM-GoogleAssistant is suspended. module.js:199 MMM-GooglePhotos is suspended. main.js:297 Will not show MMM-GoogleAssistant. LockStrings active: GA_LOCKED main.js:297 I will create a new token Edit: Just deleted token.js, and did again “node generate_token.js”, pasted the code, and everything works again

@saltedcod I can’t answer on the module info.

@scumbelly great solution! css is really powerful!