@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