Bugsounet and MMM-Pir

sdetweil

@rkorell yes, i posted a warning early after he left to save what you could, without knowing the details of such work effort

rkorell

@sdetweil Yes, indeed - we had a chat at these time as you might remember.
And here seems to be an opportunity to do “something” against this "bug"sounet thingi …
As @coernel suggested a re-upload could help (a little bit), so I considered this as a really good and nice idea.
But it went wrong - for unknown reasons the given copy is incomplete.

So my suggestion to complete this ta - at least - have a working copy of an elder status …

Ralf

sdetweil

@rkorell yeh, or forget it and move to a current module.
very troubling

lif

Thank you everyone, I’m sorry for opening this can of worms.

I’ve now got a Python script that runs at boot and does the job after destroying my MM installation trying to apply upgrades.

rkorell

@sdetweil :-).
I like it very much because it offers a lot nice and fancy stuff as the others don’t …
(progress bar, dimming, cron-steering for sleeping times)

Ralf

sdetweil

@lif can you talk about this python after …

MagicMirror upgrades? if so , did you use my upgrade script?

this highlights a problem. some modules need a refresh install when nodejs and MagicMirror change
so the upgrade script does that. but that wipes the node_modules folder for the module. and the dependencies are also not available anymore.

so, if i DO try the npm install it breaks, if i dont try the npm install it might break. fun times.
i will add a check for the authors url and skip the install action

sdetweil

@rkorell i hear yah.

rkorell

@sdetweil said in Bugsounet and MMM-Pir:

some modules need a refresh install

at least in bugsounet’s README.md there is a hint in this direction …

sdetweil

@rkorell yes, but there is nothing I can do… the dependencies no longer exist
he had some integrated update mechanism, I added code to launch that once…
now its dead too…

rkorell

@sdetweil OK.
really unfortunate.
I do not understand these dependencies - so I was hopeful that an update will not destroy module’s ability to work …

So I have to stay with the old mirror version to keep module running?

Regards,
Ralf

lif

@sdetweil said in Bugsounet and MMM-Pir:

@lif can you talk about this python after …

MagicMirror upgrades? if so , did you use my upgrade script?

this highlights a problem. some modules need a refresh install when nodejs and MagicMirror change
so the upgrade script does that. but that wipes the node_modules folder for the module. and the dependencies are also not available anymore.

so, if i DO try the npm install it breaks, if i dont try the npm install it might break. fun times.
i will add a check for the authors url and skip the install action

I was trying to upgrade Nodejs and if failed with lots of errors.

my mm and the whole system had got messy, so I’m using this as an opportunity to clean things up (it didn’t help insofar as a restore from the most recent backup didn’t work.

sdetweil

@rkorell said in Bugsounet and MMM-Pir:

So I have to stay with the old mirror version to keep module running?

i do not know…

I do not understand these dependencies
rather than put all the code in the module, there are libraries of things
that can be called…

so you make those libraries as separate packages and list them in the dependencies section of package.json and npm install goes and gets them

he might have decided that multiple components needs the same functions and packaged as library, to be loaded by all that needed it, code once, ship multiple times…
except that breaks now as the dependencies also are no longer available

as I said in my initial warning post, plan for them all to fail to work

sdetweil

@lif yeh, my upgrade script does the nodejs upgrade too…

use the n command

sudo npm install n -g 
sudo n xxx
where xxx is the version you want to use

recent backup didn’t work

how backup? use my backup/restore

yes that is broken too, as the authors repos no longer exist and binary backup may not work on different OS level/nodejs level

lif

@sdetweil said in Bugsounet and MMM-Pir:

how backup? use my backup/restore

yes that is broken too, as the authors repos no longer exist and binary backup may not work on different OS level/nodejs level

IMG file on my (new) linux desktop

lif

@sdetweil said in Bugsounet and MMM-Pir:

@lif yeh, my upgrade script does the nodejs upgrade too…

use the n command
sudo npm install n -g 
sudo n xxx
where xxx is the version you want to use

Thanks, added to my install notes

sdetweil

@lif n is the nodejs version of nvm

rkorell

@sdetweil said in Bugsounet and MMM-Pir:

plan for them all to fail to work

yes - as stated -really unfortunate!
Thanks for your clarification!
Ralf

lif

@sdetweil

I’ve reinstalled MagicMirror with your script, it worked wonderfully, than you very much for doing this.

Best regards from France.

rkorell

@sdetweil @lif
For your information:

I was successful with installing MMM-Pir on my brand new Pi5/bookworm:

pi@MagicMirrorPi5:~ $ cd MagicMirror/modules
pi@MagicMirrorPi5:~/MagicMirror/modules $ tar -xf MMM-Pir.tar.gz 
pi@MagicMirrorPi5:~/MagicMirror/modules $ cd MMM-Pir/
pi@MagicMirrorPi5:~/MagicMirror/modules/MMM-Pir $ npm install

> MMM-Pir@2.4.4 preinstall
> echo ⚠ npm install will be deprecated on next release!.

⚠ npm install will be deprecated on next release!.

> MMM-Pir@2.4.4 install
> npm run setup


> MMM-Pir@2.4.4 presetup
> npm run dependencies && installer/preinstall.sh


> MMM-Pir@2.4.4 dependencies
> installer/dependencies.sh -d 'unclutter ddcutil cec-utils python3 python-is-python3 python3-gpiozero gpiod libgpiod2 libgpiod-dev'


Welcome to MMM-Pir v2.4.4

① ➤ dependencies installer

Checking OS...
OS Detected: linux-gnu (debian 12 aarch64)

Checking all dependencies...
All Dependencies needed are installed !

② ➤ Preinstall

No root checking...
Checking MMM-Pir: pi/pi
Checking MagicMirror: pi/pi

Installing @sdetweil sandbox fix...
fixing sandbox permissions

③ ➤ Install npm dependencies

> MMM-Pir@2.4.4 setup
> npm prune


up to date in 990ms

124 packages are looking for funding
  run `npm fund` for details

> MMM-Pir@2.4.4 postsetup
> installer/postinstall.sh -m -r


④ ➤ Postinstall

Minify Main code...
Found: 10 files to install and minify

Process File: MMM-Pir/MMM-Pir.js
Process File: MMM-Pir/node_helper.js
Process File: MMM-Pir/components/cronJob.js
Process File: MMM-Pir/components/governorLib.js
Process File: MMM-Pir/components/motion.js
Process File: MMM-Pir/components/motionLib.js
Process File: MMM-Pir/components/pirLib.js
Process File: MMM-Pir/components/screenDisplayer.js
Process File: MMM-Pir/components/screenLib.js
Process File: MMM-Pir/components/screenTouch.js
Done

Try to Disable screen saver...
Found: screen saver in gsettings
disable screensaver via gsettings was true and uint32 300
Found: screen saver in lightdm
disable screensaver via lightdm.conf
Found: screen saver in lxsession
disable screensaver via lxsession
Found: wayfire.ini

[WARN] There is some change for disable screen saver
[WARN] Please, don't forget to reboot your OS for apply the new configuration!
Done

Rebuild MagicMirror...
✔ Rebuild Complete
Done


MMM-Pir is now installed !

> MMM-Pir@2.4.4 postinstall
> echo ⚠ On next release, Please use: npm run setup

⚠ On next release, Please use: npm run setup

added 1 package in 31s

124 packages are looking for funding
  run `npm fund` for details
pi@MagicMirrorPi5:~/MagicMirror/modules/MMM-Pir $

I will have to play with the screen options (caused for sure by bookworm) because right now I get an error notification from MMM-Pir (screen error detected: dpms command error(mode 1) ) but there are several other modes to try …

Regards,
Ralf

sdetweil

@rkorell yeh, fun times