@robiv8

the modul MMM-Navigate disappears by design. If it is faded out and you use rotary or button it comes back on (fades in).

Yes MMM-Dreambox can be controlled bei MMM-Navigate, see https://github.com/Ax-LED/MMM-Dreambox#further-options

AxLED

@keineAhnung123,

great to hear it works, i will update the readme at github.
The line in config.txt only tells the pi at boottime, that GPIO16 is set to input and the internal resistor is set to pullup. So there is nothing else to know unless you change your GPIO Pins for something else.
@Eisblume maybe this is a solution for your issue.

AxLED

@keineAhnung123 ,

thanks for your patience.
to first:
it seems to be something with the pullup / pulldown resistors, see also https://github.com/fivdi/onoff#configuring-pullup-and-pulldown-resistors
See also the new “gpio” config command (https://www.raspberrypi.org/forums/viewtopic.php?f=117&t=208748)
So here is another idea, can you try (based on informations mentione above):

• (i suppose your SW pin is 16)
• add following line in /boot/config.txt
  gpio=16=ip,pu
  Meaning: sets your GPIO 16 as input (ip) and pull up (pu)
• if this doesnt work try:
  gpio=16=ip,pd
  Meaning: sets your GPIO 16 as input (ip) and pull down (pd)

Maybe this way MMM-Navigate works without the python script.

To SW.watch you mentioned, this is ok, as i dont need to know the initial state of SW.

to third:

• i added the line in node_helper.js in the github repo.

Regards

AxLED

@keineAhnung123 ,

informations to your second issue:
Your request is not provided by MMM-Navigate, maybe it is possible with one of the following modules (untested):

• MMM-ModuleScheduler
• MMM-ModuleToggle

AxLED

@keineAhnung123,

thanks for feedback.
first:
Idea A:

• maybe the pin 19 is the problem, because it is not only a GPIO pin rather it has SPI features. Can you change to BCM16 (and change it in config.js as well) and try it?

Idea B:

• Do you use capacitors for debouncing? If not, you can change debouncing value of following line: https://github.com/Ax-LED/MMM-Navigate/blob/master/node_helper.js#L37

second:

• Which module should start hidden? MMM-Navigate?

third:
I tried to reproduce on my pi 3 and get no error, so i checked the code.
You can add following line as new line 19 in node_helper.js
var lastdir = '';

AxLED

@keineAhnung123,

to your first issue:

• is only click not working or is rotation also not working?
  Because rotation and click (Button press) uses the same library (onOff).
• on which pin is click connected, as the pi GPIO Pins have different features?
• what versions you are using (pi, OS, MM-Version)?

To your second issue.

• MMM-Navigate uses the MM notification system, so you can do almost everything you want. What are you trying to to, maybe i can give you a sample for your config.js
• for shortening time of hidding see MM Docs -> search for hide, there is a parameter for speed.

Regards

AxLED

Dear MagicMirror user,

today i released version 1.3 of MMM-Navigate

1.3 Changelog:

• added some functions to no longer have a dependency to MMM-Remote-Control

  • SHELLCOMMAND
    Executes code in a terminal of you pi, so you can do almost everything you want. Example you want to shutdown your pi; Config: {notification: ‘SHELLCOMMAND’, payload:‘sudo shutdown -h now’}

  • module is now listening to yourmmip:8080/MMM-Navigate/remote?

Download: MMM-Navigate

[card: Ax-LED/MMM-Navigate]

Regards

AxLED

@Mrtrol2013
i never tried what you are expecting to do. For me a navigation (f.e. on a website) doesnt change either. You can give it a try with duplicates.

AxLED

Dear MagicMirror user,

today i released version 1.4 of MMM-Navigate

1.4 Changelog:

• changed code for better recognition of the rotary encoder
• changed code enables faster movement of the rotary

Download: MMM-Navigate

[card: Ax-LED/MMM-Navigate]

Regards

AxLED

Hi,

testing completed, today i uploaded new release to github.
MMM-Navigate - V1.3 released

Regards

AxLED

Dear MagicMirror user,

today i released version 1.3 of MMM-Navigate

1.3 Changelog:

• added some functions to no longer have a dependency to MMM-Remote-Control

  • SHELLCOMMAND
    Executes code in a terminal of you pi, so you can do almost everything you want. Example you want to shutdown your pi; Config: {notification: ‘SHELLCOMMAND’, payload:‘sudo shutdown -h now’}

  • module is now listening to yourmmip:8080/MMM-Navigate/remote?

Download: MMM-Navigate

[card: Ax-LED/MMM-Navigate]

Regards

AxLED

@TheDuDiop
see english text below
Ich verstehe deine Frage nicht, das Modul “weatherforecast” wird angezeigt, wenn die die entsprechende Seite anwählst, in deinem Fall die erste Seite von “MMM-pages”.

I don’t understand your question, the module “weatherforecast” is displayed when you select the corresponding page, in your case the first page of “MMM-pages”.

AxLED

i had the same issue with a clean install of MM on raspian buster.
For manually setting the MM bootscreen this worked for me:

cd /usr/share/plymouth/themes/
sudo mkdir MagicMirror

sudo cp ~/MagicMirror/splashscreen/splash.png /usr/share/plymouth/themes/MagicMirror/splash.png
sudo cp ~/MagicMirror/splashscreen/MagicMirror.plymouth /usr/share/plymouth/themes/MagicMirror/MagicMirror.plymouth
sudo cp ~/MagicMirror/splashscreen/MagicMirror.script /usr/share/plymouth/themes/MagicMirror/MagicMirror.script

sudo plymouth-set-default-theme -R MagicMirror

AxLED

@sdetweil
@Sean
Thanks for your quick response, you are faster than my programming timeslots in my “mancave” are. Today i had some time and got it working.

I will test my module changes (for MMM-Navigate) on my mirror for some days, maybe i find some errors and can fix them before i upload it to quick to github in a poor “quality”.

My intension was to get rid of MMM-Remote-Control in my installation, as i found errors (while a new install of my MM) and as it seems that MMM-Remote-Control is not maintainanced anymore.

I added following features to MMM-Navigate:

• Raspberry operations: any Shellcommands, i use it for
  • restart of MM (pm2 restart mm)
  • restart of Raspberry (sudo shutdown -h now)
  • reboot of Raspberry (sudo reboot)
• controlling MM by URL Calls (if you dont have a rotary encoder connected or while programming)

stay healthy

Regards

AxLED

@sdetweil
Thanks for the response, it think now i have enough to read and i will try to get in up and running.

I will give feedback within the next day.

AxLED

@sdetweil
No i didnt set any path so far, but express path seems to be the right search word and helps.
If i understood the documentation right, express path has to be located in node_helper.js.
But i still dont know how to move forward with this information.
Are there some modules which are using express path, where i can try to figure out how it works?

Greetings

AxLED

I

@sdetweil
User is presenting / entering datas by URL in his browser and module should be able to handle the datas.
AxLED

Dear Developers,

i want to redesign one of my modules. Therefore i need a hint how i can make the following possible.

I want to pass a query / parameters from a module URL, f.e.

http://IPofMM:8080/MMM-Navigate/index?value1=xxx&value2=yy

to my module.
What do i need?

1. a page in my module folder index.js(?)
2. code do read the values of querystring and do something with it.

Maybe somebody can give me a tip how to do that or in which module it was already realized (except MMM-Remote-Control).

Regards

AxLED

@tommy1974
If you develop a timer module which can handle notifications, you can use my module MMM-Navigate out of the box.
AxLED

@Kevinho195
@dicker182

maybe https://github.com/Ax-LED/MMM-Podcast2/issues/7 is the solution.

AxLED