MMM-Remote-Control

rkorell

@sdetweil
BTW: Do you know if it is possible to restore the “old” version from remote-control?
May THIS is the better option for me?

sdetweil

@rkorell can you tell me when old was? luckily this module uses tags for releases, so you could restore to one of the previous releases…

in the module folder do

git fetch --all --tags

then when we figure out which release to try, we can

git checkout <tag_name>

Release 3.2.1 was about 5 months ago.

rkorell

@sdetweil I’ve found V3.3.2 and just try "git checkout 1f451ce "

sdetweil

@rkorell if you pull the tags, you can use the tag name

git checkout v3.3.2

rkorell

@sdetweil
For some really strange reasons, neither

pi@MagicMirrorPi5:~/MagicMirror/modules/MMM-Remote-Control $ git fetch --all --tags
pi@MagicMirrorPi5:~/MagicMirror/modules/MMM-Remote-Control $ git fetch --tags

currently give any feedback…

So I’ve worked with the found git-hash:

git checkout 1f451ce

This at least worked and rolled back to V. 3.3.2.

Unfortunately some dependencies (package-lock.json ???) are not strict enough, so the rollback produces an error message:

[ERROR] Error when loading MMM-Remote-Control: require() of ES Module /home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/uuid/dist-node/index.js from /home/pi/MagicMirror/modules/MMM-Remote-Control/API/api.js not supported.

So I downgraded UUID:

cd ~/MagicMirror/modules/MMM-Remote-Control
npm install uuid@9.0.1
npm ci --omit=dev

With this module is running again.

From now on I’m in a in ‘detached HEAD’ state - but this seems OK.
Thanks for your time, effort and always great help!

Ralf

sdetweil

@rkorell I was just about to add that you needed to redo the npm install for the module after deleting the node_modules folder
else you were trying to run the new dependencies with the old code

but you fixed it…

rkorell

@sdetweil
Yes :-)

In fact I’ve used

npm ci --omit=dev

this does the deletion of the node_modules folder inherently AFAIK …

Thanks again, dear Sam!

Ralf

sdetweil

@rkorell said in MMM-Remote-Control:

npm ci

be careful… the package.json was built and tested on a cloud based virtual machine.
pi and other hardware types MAY need a different version of a dependency, i’ve only seen it myself twice in 6 years, but

npm ci uses the exact package.json
npm install will get the appropriate for this platform, even if the version changes.

anyhow… I use npm install --omit=dev when I do the installs script or MMM-Config

rkorell

@sdetweil
OK; thanks for this hint.
May npm install has avoided the resulting error which I had to solve…

Anyway: Thanks a LOT!
Regards,
Ralf