@sdetweil said in [Electron] display, MM faded away:

disabled:true,

I’m confused… if the module is still in the MagicMirror file and folder structure? is it still executed even if the module is completely commented out of the MagicMirror config.js? or does disabled:true; do the same thing as commenting it out?

@Bugsounet I was using a small SD card 8MEG and my logs got too full and kept things from running correctly.

I had to pm2 flush to clear out the logs.
and then restart and it worked.

So I got a bigger sd card and have been working on the errors. I found changing the timer in the grove-gestures script got rid of a lot of timeout errors on it’s python script. I also made the news feed refresh less frequently and got less 401 errors from that. Now I can probably go back to the 8gb card. :-)

@Mykle1 Yes you are a F****** genius! Way to go Pops!

@raymondjspigot I had a thought that might apply. MagicMover adds a div to all the modules. maybe having that surreounding div added to the backgroundslideshow… is breaking the css for the BackgroundSlideshow.

Are you wanting a background with stuff floating around on top of it?

I’m thinking you would need to alter the javascript code in the MagicMover to exclude the BackgroundSlideshow from having the div added around it. It would break any updates for MagicMover as you would have to add-in your custom code again if you pulled an update from the source.

@sdetweil Having what you have on hand makes a ton of sense. I would probably go that on route myself except I’m making this as a gift for my Dad. He is an absolute paranoid dude when it comes to cameras especially in his bathroom or bedroom, which is where this will go. And the PIR sensors are cheap. cheaper than even a pi camera. And this mirror will always be on due to the cheap monitor I"m using.

I do think something in the currentweather and forecastweather is tossing out dom information that is switching the style css from display off to display block.
i have commented out all the other modules except the MMM-grovegestures and the two weather modules. So it’s not coming from elsewhere.

From looking at the code, it appears that there is an onIdle somewhere. I want to find that.

I wish I had Coda on this pi. I’m used to coding in a Mac environment. I’m being stubborn and trying to do this all on the pi.
Is there a graphic code editor which can search files in a project and not just the file you have open?

@dhanushx012 I am like the guy who started this topic. I can’t just blank the screen by turning the hdmi output off on the pi. And, I can’t power off the monitor using CEC commands. Even though I am using a HDMI instead of VGA I have the simililar issues.

Q: why not turn hdmi output off?
A: Because my tv monitor detects no hdmi signal and just has to scream at me about it with a not very cute logo and ugly text. There are no settings within the monitor to turn off that message.

Q: Why not power the monitor on/off?
A: I can’t power it off and on using the CEC commands because I also get a annoying message and logo from the monitor when it starts up.

Q: why do you have to use that monitor when it’s easy to get another one that will work either way?
A: I have to use a cheap VIZIO on sale for $32 US that I got. I don’t have a spare lcd panel around to use. Some of us can’t simply buy another monitor. We are using what we have. So far all together with my pi, my $32 monitor, and some cables, molding (frame), glass, and film and a gestures sensor for $2.50. I’ve managed to spend just around $120.

Problem: Same as the guy who originally posted. I need the monitor to be on at all times and sending a signal because of the first two issues listed. So, I am trying to use the MMM-grove-gestures built in way to hide all the modules… but some of the modules don’t behave and turn themselves back on. Super annoying. I’m still debugging that. I think it is inside the currentweather and weatherforecast modules

Solution: get the screen to turn black

And getting it to do that is the crux of the problem.

@sdetweil what sleepwake module are you using?

@Bugsounet I found that in the config.js for the grove gestures and changed it. … no effect. I fully stopped and restarted the magic mirror.

the other modules stayed hidden like the are supposed to, but not the current weather or weather forecast.

@sdetweil
It’s the default behavior of the MMM-GroveGestures module.

in config.js

"CLOCKWISE": {
          moduleExec: {
            module: [],
            exec: (module, gestures) => {
              module.hide(1000, null, {lockstring:"GESTURE"})
            }
          }
        },
        "ANTICLOCKWISE": {
          moduleExec: {
            module: [],
            exec: (module, gestures) => {
              module.show(1000, null, {lockstring:"GESTURE"})
            }
          }
        },

in the code is looks like it adds a div around each module and sets it to

class="container" style="display: none;">

No “GESTURE” is being sent as all would show instead of hide. It’s just the weather stuff that reappears. The added DIV is being altered by some other process to

class="container" style="display: block;">

I can’t figure out what is doing it.

When using a button, PIR, gesture sensor, microwave sensor etc to blank the screen the currentweather and weatherforecast always turn themselves on. I want to turn them off to prevent screen burn in. So I have protyped several ways I ust mentioned to have the screen blank unless I physically (with a button or my presense or a gesture) make it display. All the modules respect this EXCEPT the currentwewather and weather forecast.

It seems to be happening when they update their data. If I have, for example, currentweather set to fetch an update at 10 minutes, and the forecast set to update at 15 minutes. Those are the time intervals it takes for those respective modules to reapear. And they shouldn’t because I haven’t sent them the notification to do so.

Any ideas of what code needs to be changed to make them respect the setting and not alter the DOM by themselves?

p.s.
I read this and am not sure how it applies, but I"m thinking it is involved in my issue…Re: Why does currentweather use lockstring???