It would be nice if someone updated or rewrote the Fitbit module, as the current one is 3 years old, apparently no longer supported (several unresolved issues from three years ago in the troubleshooting forum), and Fitbit has completely redesigned their developer portal so the instructions are of little help.
There are quite a few Fitbit users out there, and its a logical application for the MagicMirror.

I would think from a high level architecture view you would be better served running your database on a different node and doing a read every X seconds for display on the mirror. You could run the system stats module to monitor cpu and volatile memory management while testing various approaches, but if you accrue historical data very quickly you could exceed the storage limit on the operating partition and cause performance issues.
My understanding of hardware/software architecture is a bit dated, however, so someone with more experience on node.js, electron and the various bits that support the Magic Mirror application may have a better response.

Wow I was really starting to lose my mind over this one. Have been going over and over my config.js file.

Do all of your editing, configuration and addition of new modules in the MagicMirror/config/config.js file.
Did you modify each module’s javascript file separately?

@chef said in So ... to update MagicMirror I would ... ??:

Perhaps try stopping all instances of electron and node.

Stop pm2

Then try the install again.

Reboot the Pi.

Tried this, same result. Blank mirror although pm2 reports it is online.

v6.12.3
Not working

btw that command if anyone else needs to look it up is just
$ node -v

@NoNameRo Intuition tells me I should have stopped the service before applying the update, but unfortunately the instructions do not…

One more for blank screen, no joy after update per the instructions. Restarted MM using pm2, then rebooted the Pi. Ran the git reset --hard command, still nothing.

@aro28 That didn’t work on mine. I suspect you would need to go into alsamixer, locate your playback device’s configuration and adjust the default volume there.

@KRegan There are a fair number of missing details from the 3rd Party Module instructions, especially when it comes to registering the device. I ended up jumping over here:

https://developers.google.com/assistant/sdk/guides/library/python/

and just going through the Google instructions in detail. Once you have the demo software working (audio only, without MM integration), it was fairly easy to sew them together and get it working on the mirror as well. I used my Jabraspeak USB speakerphone, which registered as card 1, device 0 on both the speaker and mic.

Have a scratch pad of some sort handy (OneNote, Notepad, etc) to track the various keys you will generate along the way. Once you get everything onboard, the sequence is boot the Pi (I have pm2 set to autostart the Mirror), connect vis SSH then start the virtual environment (source env/bin/activate), drill down to the pi folder (cd MagicMirror/modules/MMM-GoogleAssistant/pi) and start the assistant.py file (python3 assistant.py).

I took the better part of a weekend. ymmv.