Again -- MMM-Navigate can't get installed.

rkorell

@crowimu Found in completely different context another hint to onoff - also related to GPIO (in concrete a GPIO related implemetation of a rotary decoder).
There was a suggestion

npm install --save onoff@6.0.0

I currently only „assume“ that @6.0.0 is the version - cause the cited post is from 2021 there could be a new version.
A quick google delivers this page and this one stated

npm install onoff

Will do the trick…

Good luck.
Ralf

crowimu

@rkorell Thank you and all others for the hints, however up to now I did not manage to get the ‘onoff’ and the MMM-Navigate module workingon my system.
I have recompiled onoff, installed it globally, changed the node version.
Nothing helped yet :(

I have started to create a simple module for my needs to control some fuctions with a rotary encoder,
https://github.com/crowimu/MMM-RotaryNav
It’s early stage, please wish me luck. :)

rkorell

@crowimu
very unfortunate!

cross the fingers & good luck for you…

Ralf

rkorell

@crowimu - Just a quick question: Have you considered to use a newer version of a Pi? A 4B or even 5?
Pi2 is somewhat old - may there is a kind of a root cause?

Regards,
Ralf

crowimu

@rkorell Hi Ralf,
I think the quadcore RPi2 is quite sufficient for a Magic Mirror, but I’ve also tested it on a RPi3 with the same results.
I don’t like the power consumption of RPi4 and 5 and I also don’t like to add cooling fans to an SBC.
So up to now I have always used RPi Zero / Zero2 / RPi 1/2 and 3 smoothly for my projects. :)

crowimu

@rkorell finally I got it solved :)

The issue is really the GPIO numbering, I found this SO thread:
https://stackoverflow.com/questions/78173749/use-raspberry-pi-4-gpio-with-node-js
It is also valid for Pi3 and Pi2

cat /sys/kernel/debug/gpio

gpiochip0: GPIOs 512-565, parent: platform/3f200000.gpio, pinctrl-bcm2835:
 gpio-512 (ID_SDA              )
 gpio-513 (ID_SCL              )
 gpio-514 (GPIO2               )
 gpio-515 (GPIO3               )
 gpio-516 (GPIO4               )
 gpio-517 (GPIO5               )
 gpio-518 (GPIO6               )
 gpio-519 (GPIO7               |spi0 CS1            ) out hi ACTIVE LOW
 gpio-520 (GPIO8               |spi0 CS0            ) out hi ACTIVE LOW
 gpio-521 (GPIO9               )
 gpio-522 (GPIO10              )
 gpio-523 (GPIO11              )
 gpio-524 (GPIO12              )
 gpio-525 (GPIO13              )
 gpio-526 (GPIO14              )
 gpio-527 (GPIO15              )
 gpio-528 (GPIO16              )
 gpio-529 (GPIO17              |sysfs               ) in  hi IRQ
 gpio-530 (GPIO18              )
 gpio-531 (GPIO19              )
 gpio-532 (GPIO20              )
 gpio-533 (GPIO21              )
 gpio-534 (GPIO22              |sysfs               ) in  hi IRQ
 gpio-535 (GPIO23              )
 gpio-536 (GPIO24              )
 gpio-537 (GPIO25              )
 gpio-538 (GPIO26              )
 gpio-539 (GPIO27              |sysfs               ) in  hi IRQ

I needed to set up the numbers according to the output
e.g. Pin27 is 539 in the MMM-Navigate config.
Now everything works so far as expected, thank you all for your help!

rkorell

@crowimu COOL!
congratulations!

For me the “confusing” part was the fact that INSTALL doesn’t work…
Installing should NOT check GPIO pinouts …

Really great that you worked this out!

Warmest regards,
Ralf

rkorell

@crowimu said

It is also valid for Pi3 and Pi2

A Pi4 or a Pi5 had solved this as well :-)

sdetweil

@rkorell because MagicMirror is started with the electron binary, the compiled module code must match the engine version

electron rebuild does that.

tricky problem if not running under electron
then npm rebuild works for nodejs engine match

rkorell

@sdetweil said in Again -- MMM-Navigate can't get installed.:

the compiled module code must match the engine version

OK, sounds plausible.
Thanks.

Learned a lot, today :-)

Regards,
Ralf