@kayakbabe - thanks for letting me know. I will keep an eye on the one I am using and if I see issues, will try the other one.

@sdetweil - Ah crap, having both disabled: true AND disabled: false would do it!! :) I’m sure the system would execute the last command. Thanks for putting a second set of eyes on it.

@sdetweil - Thanks Sam - I guess I was and am confused.

Below are two code snips showing the subject module and one other. Both are designated to be disabled with the “disabled: true” instruction outside the config section. The top one still operates, while the bottom one [and every other module I have edited this way] is disabled. So, it’s not a big deal and I will keep an eye out for how I do things. Thanks again.

{module: "MMM-OpenWeatherMapForecast", // https://github.com/MarcLandis/MMM-OpenWeatherMapForecast NOTE: See also https://github.com/sdetweil/MMM-OpenWeatherMapForecast
  disabled: true,
  header: "", // "Weather"
  position: "top_right",
  classes: "default everyone",
  disabled: false,
  config: {
    apikey: "xxxxxxxxxxxxx",
------------------------------------------------------------------------------- 
{module: "MMM-Temperature", // https://github.com/Tom-Hirschberger/MMM-Temperature
  disabled: true,
  header: "Office Temp + Humidity",
  position: "top_right", // bottom_right
  config: {
   sensors: [

@kayakbabe FWIW, i installed the jclarke0000 module, and so far it looks pretty good - thanks again!

@kayakbabe PS: another issue with MMM-OpenWeatherMapForecast is that it doesn’t respect the “disabled: true” configuration. I had seen this before and ignored it since the module is active, but when I went in to disable it in preparation for trying one of the others, I am reminded that I cannot just disable it. I CAN put " /* and */ " around the whole thing of course, but that is just clunky, and more importantly may signal more serious coding issues.

@kayakbabe - Thanks for the tip. Can you tell me which one you use? A quick web search shows several modules with the same name. These two look like top contenders:

https://github.com/jclarke0000/MMM-OpenWeatherForecast
https://github.com/themaxgoldman/MMM-OpenWeatherForecast

My instance of this module also displays rainfall in “mm”, even though I have set units = “imperial” for the MagicMirror system as a whole and also in the module configuration.

I see that the Open Weather site has a page specifying “API response parameters with available units of measurement” (https://openweathermap.org/weather-data). There one finds a parameter table specifying Parameter and Description - as well as columns for “Standard”, “Metric” and “Imperial”.

The interesting thing is this: the table specifies temperatures correctly (“Kelvin”, “Celsius”, “Fahrenheit”) but for rain it calls out “mm”, “mm”, “mm” - or other variants for different fields, e.g.: “mm/hr” and “mm/hour”.

As such, I am inclined to just give up and accept the module’s behavior as a quirk of how Open Weather parses what it is getting from the NWS - but I thought i would see if anyone has a better idea.

Re: MMM-WeatherAlerts
@Gjones93 - Can you comment on how alerts are structured in terms of granularity of area? As an example, there are currently no alerts on the MagicMirror when location is set to lon/lat corresponding to Las Vegas, NV - which is in Clark County – while there IS currently a Flood Watch for “Western Clark and Southern Nye County”. I have tried modifying the lat/lon from a detailed level to a more general level (e.g.: “36.111111 / -115.22222” to “36.1 / -115.2”) to no effect.

I recognize this is likely an issue with either how the NWS reports the alerts, or with how OpenWeather parses what it is getting from NWS - but I am hoping you understand how they operate, as I don’t see anything on either organization’s website that would help manage displaying which local/nearby/regional alerts are active…) A practical way to address this might be to specify location by county (since the NWS seems to be reporting it that way…), but it doesn’t look like the OpenWeather API supports that.

The practical effect of this is that I see no alert showing, while there is nearby significant weather. Thanks for the great module!!

@1a2a3a said in MM current version on Raspberry Pi 5 cannot turn off monitor:

vc4.force_hotplug

That does appear to work! So far I have tried it on two different Pi 4 instances, and each responded to a script called in crontab to turn off the monitor display, and then a script to turn it back on, as expected.

Thanks.

@jbat66 - thanks for the offer. If you do wind up sharing your work, I will take a look and see if it works for me.

I don’t run any remote control module, and don’t find the “MMM-remote” you reference when I search. I do, however, find at least two (2) different modules called “MMM-Remote-Control” by two different authors. Do you mean one of those?

My progress so far is that I can get the monitor to turn off using the following script (called by a cron job), but the monitor then turns back on after ~10-15 seconds:

#!/bin/bash

# Script to turn off monitor display when called by crontab
export WAYLAND_DISPLAY=wayland-1
export XDG_RUNTIME_DIR=/run/user/1000
/usr/bin/wlr-randr --output HDMI-A-1 --off