@BKeyport - That has been my general impression of Adafruit, and for the sake of general continuity, I do hope that is the case. All that said, the situation with the sensor libraries has been a mess for years - with my personal favorite gripe being libraries being deprecated without clear messaging on the website hosting the old, together with new libraries with very similar names but different functionality. For the life of me I cannot understand why simply incrementing the version numbering wouldn’t have accomplished what was needed [accompanied of course, by clear messaging…].

Meanwhile I have ordered and received some DHT20 sensors, and will soon begin standing some of those up. This has entailed first building a development instance to work on, as I find the MagicMirror system to be fragile, and I want to minimize downtime on the production instance. As of yesterday I do have the dev instance running and am trying to iron out a couple of wrinkles, like tracking down why and how the default calendar module on the new dev instance doesn’t display recurring appointments the same as on the existing [production] instance. Seeing as I literally copied and pasted the configuration code from the old to the new, I would think it would perform the same.

Anyway - thanks again for the input and the guidance, as always.

@BKeyport thanks for the response. It looks like my issue is actually with the Linux 12 / bookworm version of Raspbian I installed when rebuilding my MagicMirror, as opposed to the R-Pi 4 hardware.

In reading the Adafruit forums here: https://forums.adafruit.com/viewtopic.php?p=938344&hilit=Adafruit_Python_DHT#p938344 I find the official Adafruit response to someone with the same issues is that “DHT22 really sucks to use on linux” and … “you will be a lot happier just using the DHT20 and friends”, with a reference to an Adafruit web article at https://learn.adafruit.com/modern-replacements-for-dht11-dht22-sensors/overview.

In short, the advice is to just buy all new sensors for your Raspberry Pi installs. The OP pointed out that while he acknowledges the newer sensors may indeed be better, that " I spent a good amount of money buying and building, and for all of that to go away with an update really stinks! :( ".

I agree with him since I have probably five (5) DHT 11/22 sensors working on R-Pis, and while it looks like he found a way to upgrade all pip libraries and get it working again, it also appears to only be a matter of time until another update or upgrade of something breaks the system.

Again thanks for pointing me in the right direction.

I’m having the same issues… I recently built a new MagicMirror instance using the latest Raspbian OS, and the commands I have used in prior instances don’t work in the new OS.

None of the commands listed above work for me. I have also tried the following in the crontab. While it DOES turn off the monitor display, the display turns itself back on in about 10 seconds…

display_off >/dev/null 2>&1

Any help will be greatly appreciated, as the MagicMirror is in a location where running the display all night is disrupting people’s sleep, and having to manually turn it on and off is very inconvenient.

Thanks for your work - it looks good and has the offset feature I need! Like @BKeyport I formerly used MMM-LocalTemperature, but it won’t run on my new MagicMirror build.

For context, I currently do have MMM-DHT-Sensor running on this instance. It runs just fine, but I would prefer the look and feel of yours, as well as needing the offset feature. I have also tried changing from GPIO 4 to GPIO 21 - same results [MMM-DHT-Sensor works on either, MMM-DHT22 works on neither].

My issue with MMM-DHT22 is understanding whether one can get it to run on a Raspberry Pi 4? I have been unable to do so, and it appears to be issues with the Adafruit_Python_DHT libraries. My research appears to show your module relies on that Adafruit library, and the Adafruit library doesn’t support Raspberry Pi 4.

Am I missing something? If so, what? If not, is there a workaround?

@sdetweil - ok, understood. I guess that explains the (usually subtle) differences.

@sdetweil - Sam, how would I go about investigating an issue where it appears my MM install violated your statement (and my understanding) that there is only one web page being published?

The MM runs all the time, directly attached to and displaying on a monitor in my office. At times I will also bring it up in a browser window on the desktop, and see varying values in the weather modules running. ( I’m traveling and lack access to provide a photo showing the simultaneous different outputs, but thought I’d ask.)

@sdetweil - Thanks for the help here and offline. My problem is solved, and for the sake of others following is the resolution.

Problem: MagicMirror install script outputs node.js errors on new RaspbianOS install running under VirtualBox.

Diagnosis [by sdetweil]: “so, the problem is that the intel raspian is a hybrid, x86_64 kernel with a i386 user runtime.
and they stopped making a nodejs for i386 after node 12”

Solution: Rebuilt the virtual machine using Ubuntu instead of RaspbianOS. [I’m sure any Debian or other Linux distribution would work just fine…]

Thanks again - I can now use this as a dev machine and spare myself the risks associated with fiddling with the production machine!

@sdetweil - Thanks, the log file is on its way to you…

@sdetweil - I’m not sure this the correct topic for my error, so if not we can move it - but I am having the issues described above, but on an initial install [as opposed to an upgrade]. This is on a freshly created VirtualBox VM using the current RaspbianOS version of Debian, using Sam’s install script.

After a long series of lines indicating it was setting up various node packages, the install.log file ends with a message that node failed to install:

added 1 package, and audited 2 packages in 1s

found 0 vulnerabilities
installing on bullseye
installing correct version of node and npm, please wait
  installing : node-v20.8.0
       mkdir : /usr/local/n/versions/node/20.8.0
       fetch : https://nodejs.org/dist/v20.8.0/node-v20.8.0-linux-x64.tar.xz
     copying : node/20.8.0
   installed :  (with npm )

Note: the node command changed location and the old location may be remembered in your current shell.
         old : /usr/bin/node
         new : /usr/local/bin/node
If "node --version" shows the old version then start a new shell, or reset the location hash with:
hash -r  (for bash, zsh, ash, dash, and ksh)
rehash   (for csh and tcsh)
node failed to install, exiting

Thoughts??

@Gjones93 - Would there be any reason for this module to stop working? We are currently under an excessive heat warning, but nothing displays… I also tried locating another place under a warning, but it is not triggered by that warning either. Interestingly, when I run 'pm2 logs I don’t see any reference to this module at all. Following is my config:

{ module: "MMM-WeatherAlerts",
      disabled: false,
      position: "top_left", // top_right
      header: "Weather Alerts",
      config: {
      // lat: "36.131148", //Las Vegas = 36.131148
      // lon: "-115.241867", // Las Vegas = -115.241867
      // lat: "62.037360", //Alaska - for testing
      // lon: "-163.272301", // Alaska - for testing
     lat: "36.753342", // Alfalfa County, Oklahoma - for testing
     lon: "-98.355930", // Alfalfa County, Oklahoma - for testing
     weatherAlertProvider: "openweathermapalerts",
     weatherEndpoint: "/onecall",
     type: "alerts",
     apiKey: "xxxx",
     animationSpeed: 10000, // Default = 1000 (1 second)
     alertTimeFormat: "absolute",
     alertDateFormat: "llll",
     alertDescriptionScrollDelay: 100, // Default = 85, Lower = faster alert description will move
     colored: true }, },