EXT-Pir doens't work anymore after upgrade

Selyjohns

Hi,

Today was the upgrade day !
EXT-Screen and EXT-PIR

I updated them, and now my screen doesn’t turn off anymore

During EXT-Screen upgrade :

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'lru-cache@9.0.1',
npm WARN EBADENGINE   required: { node: '14 || >=16.14' },
npm WARN EBADENGINE   current: { node: 'v16.13.0', npm: '8.1.4' }
npm WARN EBADENGINE }

During EXT-PIR upgrade

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'lru-cache@9.0.1',
npm WARN EBADENGINE   required: { node: '14 || >=16.14' },
npm WARN EBADENGINE   current: { node: 'v16.13.0', npm: '8.1.4' }
npm WARN EBADENGINE }
Prepare PIR sensor using
Error command: sudo chmod u+s /opt/vc/bin/tvservice && sudo chmod u+s /bin/chvt
Done

So I’ve updated node too with NVM.

pi@MagicMirror:~/MagicMirror $ node --version
v16.14.0
pi@MagicMirror:~/MagicMirror $ uname -a
Linux MagicMirror 5.10.63-v7+ #1459 SMP Wed Oct 6 16:41:10 BST 2021 armv7l GNU/Linux

I’ve installed Gateway because I’ve seen in another topic that EXT modules need Gateway to works. But not better.

If anyone can help me it would be very apprecated.
Thank you

bugsounet

Hi,

All are in the log error

required: { node: '14 || >=16.14' },
it means: it’s required node v14 or node >= 16.14 (>= means: greater than or equal to)
current: { node: ‘v16.13.0’, npm: ‘8.1.4’ }
It’s inform you your current version of node and npm
That you can see v16.13.0 less than the required v16.14

It’s not because you use NVM inside MagicMirror directory that it will be better

I’ve installed Gateway because I’ve seen in another topic that EXT modules need Gateway to works.
So it’s means that you try to use EXT-Screen and EXT-Pirlike a simple module /!\ EXT-Screen and EXT-Pir are now some plugins (EXTs) and not module (MMMs)
EXTs are plugins of MMM-GoogleAssistant and need Gateway for working
If you don’t use MMM-GoogleAssistant, you can’t use ANY EXTs
Finaly, Best way if you don’t use MMM-GoogleAssistant is using MMMs of the 3rd Party modules

Selyjohns

Hi @bugsounet

Thank you for this reply.

@bugsounet said in EXT-Pir doens’t work anymore after upgrade:

That you can see v16.13.0 less than the required v16.14

This is why I wrote I’ve perform upgrade to 16.14.0 through NVM

@bugsounet said in EXT-Pir doens't work anymore after upgrade:

Finaly, Best way if you don’t use MMM-GoogleAssistant is using MMMs of the 3rd Party modules

Oh…I’m not a Google Assistant module user, but it’s been now 1 year I used EXT-Screen and EXT-PIR without any problem (because the 3rd party module wasn’t maintened anymore, please remember…)

So, you say I can’t use EXT-Modules to use PIR Sensor ?
I need to find another module that is maintened to do this ?

Thank you.
Have a nice day.

bugsounet

Sorry about this,

I have send (or close) all majors of my MMMs, now i works only with MMM-GoogleAssistant (and Google France Team) and It take many many time … (no time for MMMs)

I have upgrade all EXTs with a new protocol (for working in harmony with Gateway / GoogleAssistant and others EXTs) so can’t work in your case.

I use exclusively EXTs in home (and some personal modules not published in public),
So I’m not able to help you for another Pir sensor module

Maybe best way is ask to sdetweil of MagicMirror Forum

See You later, if you want to use MMM-GoogleAssisant and happy using with MagicMirror !
@bugsounet

Solved EXT-Pir doens't work anymore after upgrade