Here is my MagicMirror, not a mirror but a display. The hardware is:

• Raspberry Pi 3 Model A Plus Rev 1.0
• WEme USB 3.0 to SATA Converter Adapter for 2.5 3.5 Inch Hard Drive Disk SSD
• 128GB 2.5 Inch SSD
• ACER 21.5 Inch Monitor 1920x1080
• RPios Bullseye

The software is:

• MagicMirror V 2.26.0 with the following modules:
• Clock - Standard date and time display.
• Calendar - Combines multiple Apple and Google calendar into a single display.
• Weather - Local current and forecast weather.
• MMM-Fuel - Local Gasbuddy fuel prices displayed for lowest price offerings at stations in town.
• Newsfeed - Standard Newsfeed display with headlines displayed at screen bottom.

(Not the best possible image but you get the idea)

It is the combined calendar display that get the most attention and was the most challenging to configure.

I had some problems getting RPios software to operate in portrait orientation. Actually, I never was successful to get portrait mode until the Xwindows system started and was instructed to use portrait mode.

One thing I had to do was increase the RPios swap space from the default 100MB to 2GB. Otherwise the system would get stuck in page thrashing as it got busy and swap space filled up.

Thanks to @sdetweil for his assistance solving some issues.

Butch

Sam,

I built a new SDcard for Raspios and installed MM using your scripts. Started MM and the problem did not occur.

Next, I rebuilt the SSD with Raspios and installed MM. Started MM and the problem did not occur at startup and I waited while tailing the logs but nothing happened.

Next, I move my MM configuration changes, modules, and updates to the SSD. The problem did not occur at startup or after tailing the logs for a time.

I am declaring a victory for me. But we all know, in the end, that the computer demons won.

Butch

The Api has changed and the old apikey no longer works. The old api, V2.5, provided data for free and the new api, V3.0, will charge for daily data access requests that exceed 1,000. The new api requires a credit card to bill for all requests exceeding 1,000 per day.

In addition to establishing a credit card on my account and generating a V3.0 key, I installed the MMM-OpenWeatherForecast module using these instructions:

• Navigate into the MagicMirror modules directory.

• Execute git clone https://github.com/Tom-Hirschberger/MMM-OpenWeatherForecast

• Enter the new MMM-OpenWeatherForecast directory and execute npm install

The configuration instructions and other information is located in:

• Read the instructions in the README.md file.

Butch

@sdetweil I am interested in how the modules work.

I understand how a browser works and how to construct a webpage.

Butch

@sdetweil Sam, Thank you for the help with the answer I needed.

I am interested in learning more about MM. I have tried reading the code but have not been successful.

Do you have a recommendation about where to start for more understanding?

Butch

I opened this issue MMM-pihole-stats: “Duplicate Results Displayed With 2 Instances of MMM-pihole-stats in Config File”. It is issue #54.

In summary, I have two instances of MMM-pihole-stats defined in the configuration file. The first instance displays the data for pihole1 and the second instance display the data for pihole1 instead of pihole2.

The text of the issue is:

I have two Pi-Hole systems, pihole1.lan at 192.168.1.3 and pihole2.lan at 192.168.1.4. Using dig verifies the Pi-Hole names and IPs match up.

In the MM config file, the two MMM-pihole-stats modules are configured the same except for these statements:

• The position: statements, the first is top_left and the second is top_right. The instances display in the proper position.
• The header: statements, the first contains “Pi-Hole1 Statistics” and the second contains “Pi-Hole2 Statistics”. The instances display the proper header.
• The apiURL: statements, the first contains “http://pihole1.lan/api” and the second contains “http://pihole2.lan/api”. The first instance displays data for pihole1 and the second also displays data for pihole1.

Why is the second instance data not displayed? Is this module design problem or must I do something special to have multiple instances of the same module?

Butch

From my own recent experience, you have a copy of the previous config.js file but the modules cloned into the new system may not be the same as what was cloned into the old system.

Butch Kemper

Problem solved. There are multiple MMM-OpenWeatherForecast repositories. The one I cloned for the new system was not the clone I was previously using. I changed to the module from Tom-Hirschberger/MMM-OpenWeatherForecast and everything began working as expected.

I apologize for my error.

Update: To prevent future issues, I have add a comment in config/config.js file on each module statement to remind me of the module repository location. The comment appears as: // github.com/Tom-Hirschberger/MMM-OpenWeatherForecast.

Butch Kemper

I had a MagicMirror that was running on Bullseye and I decided to upgrade to Bookworm. Note to self “Leave running systems alone”.

Bookworm runs, MM starts up, and the modules for Calendar and MMM-Fuel are working properly. However, the MMM-OpenWeatherForecast module does not display any information and this error message is in the MagicMirror-out.log:

** ERROR ** Error: Request failed with status code 401

There are no other error messages from OpenWeatherForecast.

Any hints would be appreciated.

Butch Kemper

@sdetweil I noticed this discretion between the Weather module documentation:

• The “Weather” documentation has “apiKey” - large case “K”,
• The “MMM-OpenWeatherForecast” documentation has “apikey” - small case “k”.

Butch

The configuration parameters I use are:

module "MMM-OpenWeatherForecase"
latitude and NOT lat
longitude and NOT lon
apikey and NOT apiKey   <----  Notice the "K"

Some MM configuration keywords have abbreviations but not all. The module README file gives the values for the keywords.

Also, since your apikey has been revealed to the world, you should cancel the posted key and generate a new key. Always keep the apikey secret.

Butch

@JohnGalt

The api call daily threshold for billing is 1,000. The default setting is to update every 10 minutes and that equals to 144 daily calls.

Butch

The Api has changed and the old apikey no longer works. The old api, V2.5, provided data for free and the new api, V3.0, will charge for daily data access requests that exceed 1,000. The new api requires a credit card to bill for all requests exceeding 1,000 per day.

In addition to establishing a credit card on my account and generating a V3.0 key, I installed the MMM-OpenWeatherForecast module using these instructions:

• Navigate into the MagicMirror modules directory.

• Execute git clone https://github.com/Tom-Hirschberger/MMM-OpenWeatherForecast

• Enter the new MMM-OpenWeatherForecast directory and execute npm install

The configuration instructions and other information is located in:

• Read the instructions in the README.md file.

Butch