@sdetweil – True. I usually setup my Raspberry Pi servers with vnc enabled, but it’s been a while so I appreciate the reminder.

@sdetweil - Thanks Sam. Viewed from that perspective it makes perfect sense! I’ll see if I can put a vnc client back on my phone and do it that way.

@sdetweil - ok, I think I understand. Somehow I thought if I removed into the network, the magic mirror would perceive me as just being there on the local network - and thereby continue presenting the local data.

There must be something in the tailscale VPN that affects the magic mirror.

@sdetweil - the mirror is in the US (running on a raspberry pi connected to a local monitor), and I’m viewing it on my phone from Japan by accessing my home network over a tailscale VPN/zero tier network.

I’m traveling internationally and accessed the mirror in my home office over my tailscale VPN. When doing so, the clock module shows the time where I am and not where it is. I think openweathermap does too.

Is this expected behavior?

@MMRIZE – Ok, thanks. I had enabled the ‘showImage: true’ and didn’t see images so I was just wondering.

@MMRIZE – So to recap, is it the case that all that’s needed to get the pictures to display is to add “showImage: true” to the default newsfeed, or is something more required? If more is required, what would that be?

@ChrisLeduex – OK, thanks. I wasn’t sure that the url path went anywhere in particular.

@ChrisLeduex – Interesting exercise. Where did you put the .svg image[s]? In with the clock faces in the module folder? In the module folder root? Other?

@sdetweil --Sam, thanks!! for your patience. I do have this resolved, at least in one MM instance.

I did go back and commit the one command I missed as advised above, but still no joy. But then, …

Strangely enough while I WAS using a valid ver 3 API key, you were right in saying my issue was an invalid API key in the call… After doing the above I was still getting a 401 error, so I accepted that the computers were doing exactly what I was telling them to do [as opposed to what I WANTED them to do]. I discovered the root cause after copying in the API key again and comparing. What I found was this:

 apiKey: "123456789"

When it should have been this:

api_key: "123456789"

I’m not sure why I started using “apiKey” instead of “api_key”, but putting it the way the module wants it fixed my issue. Thanks again!

@sdetweil – OK, so I did install the pull request, and it’s not working. After following the steps above, I still get errors:

Actions taken:
   - git fetch origin pull/52/head:with_30_apikey
   - realized I misread the instructions, so went back, and did the reset...
   -  git reset --hard HEAD 
    - git fetch origin pull/52/head:with_30_apikey
    - enable module in config.js
   - pm2 restart MM ]

Results as shown in pm2 logs, which was running at the time:
Immediate Results:
0|MagicMirror  | [2024-11-11 17:02:25.687] [ERROR] [MMM-DynamicWeather] Failed getting api:  AggregateError [ETIMEDOUT]:
0|MagicMirror  |     at internalConnectMultiple (node:net:1117:18)
0|MagicMirror  |     at internalConnectMultiple (node:net:1185:5)
0|MagicMirror  |     at Timeout.internalConnectMultipleTimeout (node:net:1711:5)
0|MagicMirror  |     at listOnTimeout (node:internal/timers:575:11)
0|MagicMirror  |     at process.processTimers (node:internal/timers:514:7) {
0|MagicMirror  |   code: 'ETIMEDOUT',
0|MagicMirror  |   [errors]: [
0|MagicMirror  |     Error: connect ETIMEDOUT 38.89.70.82:443
0|MagicMirror  |         at createConnectionError (node:net:1647:14)
0|MagicMirror  |         at Timeout.internalConnectMultipleTimeout (node:net:1706:38)
0|MagicMirror  |         at listOnTimeout (node:internal/timers:575:11)
0|MagicMirror  |         at process.processTimers (node:internal/timers:514:7) {
0|MagicMirror  |       errno: -110,
0|MagicMirror  |       code: 'ETIMEDOUT',
0|MagicMirror  |       syscall: 'connect',
0|MagicMirror  |       address: '38.89.70.82',
0|MagicMirror  |       port: 443
0|MagicMirror  |     },
0|MagicMirror  |     Error: connect ENETUNREACH 2604:86c0:5001:b::2:443 - Local (:::0)
0|MagicMirror  |         at internalConnectMultiple (node:net:1181:16)
0|MagicMirror  |         at Timeout.internalConnectMultipleTimeout (node:net:1711:5)
0|MagicMirror  |         at listOnTimeout (node:internal/timers:575:11)
0|MagicMirror  |         at process.processTimers (node:internal/timers:514:7) {
0|MagicMirror  |       errno: -101,
0|MagicMirror  |       code: 'ENETUNREACH',
0|MagicMirror  |       syscall: 'connect',
0|MagicMirror  |       address: '2604:86c0:5001:b::2',
0|MagicMirror  |       port: 443
0|MagicMirror  |     }
0|MagicMirror  |   ]
0|MagicMirror  | }
0|MagicMirror  | [2024-11-11 17:02:25.701] [LOG]   [MMM-OpenWeatherMapForecast] 11-Nov-24 17:02 ** ERROR ** fetch failed

Periodic Fetch results:

0|MagicMirror  | [2024-11-11 17:12:23.363] [ERROR] [MMM-DynamicWeather] Failed getting api:  401
0|MagicMirror  | [2024-11-11 17:12:29.902] [INFO]  Newsfeed-Fetcher: Broadcasting 30 items.
0|MagicMirror  | [2024-11-11 17:12:30.278] [INFO]  Newsfeed-Fetcher: Broadcasting 24 items.
0|MagicMirror  | [2024-11-11 17:12:30.611] [INFO]  Newsfeed-Fetcher: Broadcasting 25 items.
0|MagicMirror  | [2024-11-11 17:17:29.108] [INFO]  Newsfeed-Fetcher: Broadcasting 40 items.
0|MagicMirror  | [2024-11-11 17:22:23.126] [INFO]  [MMM-DynamicWeather] Getting Weather API data
0|MagicMirror  | [2024-11-11 17:22:23.324] [ERROR] [MMM-DynamicWeather] Failed getting api:  401

@sdetweil Yes, I realize that… I guess I skipped some thoughts that were rolling around in my head but never made it to the keyboard: I had disabled the module, figuring I would just wait for it to be updated.

I should have some time this evening to go in and install the pull request - I will let you know what happens.

@mmmallday – Thanks. Good to know there are options.

@sdetweil – Thanks Sam. I’m certain the API key is good, as I can format queries as web addresses and paste them into the browser and get openweathermap to return the data.

I didn’t install the pull request.

@sdetweil – No, it’s still erroring but oddly, possibly not on every API call.

I just now fired up a terminal session and ran pm2 logs. The output appears to show this module getting weather API data without error, then the last log lines show errors.

The really strange part is there appear to be timestamps for sucessful and error API calls right around the same time [but not contiguous in the log display]. pm2 logs output follows:

0|MagicMir | [2024-11-08 08:33:43.472] [INFO]  [MMM-DynamicWeather] Getting Weather API data
0|MagicMir | [2024-11-08 08:36:28.802] [INFO]  Newsfeed-Fetcher: Broadcasting 30 items.
0|MagicMir | [2024-11-08 08:36:34.550] [INFO]  Newsfeed-Fetcher: Broadcasting 31 items.
0|MagicMir | [2024-11-08 08:37:18.166] [INFO]  Newsfeed-Fetcher: Broadcasting 25 items.
0|MagicMir | [2024-11-08 08:41:10.851] [INFO]  Newsfeed-Fetcher: Broadcasting 35 items.
0|MagicMir | [2024-11-08 08:43:43.885] [INFO]  [MMM-DynamicWeather] Getting Weather API data
0|MagicMir | [2024-11-08 08:46:29.642] [INFO]  Newsfeed-Fetcher: Broadcasting 30 items.
0|MagicMir | [2024-11-08 08:46:34.913] [INFO]  Newsfeed-Fetcher: Broadcasting 32 items.
0|MagicMir | [2024-11-08 08:47:18.479] [INFO]  Newsfeed-Fetcher: Broadcasting 25 items.
0|MagicMir | [2024-11-08 08:53:43.477] [INFO]  [MMM-DynamicWeather] Getting Weather API data
0|MagicMir | [2024-11-08 08:56:11.172] [INFO]  Newsfeed-Fetcher: Broadcasting 35 items.
0|MagicMir | [2024-11-08 08:56:30.089] [INFO]  Newsfeed-Fetcher: Broadcasting 30 items.
0|MagicMir | [2024-11-08 08:56:35.273] [INFO]  Newsfeed-Fetcher: Broadcasting 32 items.
0|MagicMir | [2024-11-08 08:57:18.818] [INFO]  Newsfeed-Fetcher: Broadcasting 25 items.
0|MagicMir | [2024-11-08 09:03:43.477] [INFO]  [MMM-DynamicWeather] Getting Weather API data
0|MagicMir | [2024-11-08 09:06:30.344] [INFO]  Newsfeed-Fetcher: Broadcasting 30 items.
0|MagicMir | [2024-11-08 09:06:35.673] [INFO]  Newsfeed-Fetcher: Broadcasting 32 items.
0|MagicMir | [2024-11-08 09:07:19.177] [INFO]  Newsfeed-Fetcher: Broadcasting 25 items.
0|MagicMir | [2024-11-08 09:11:11.483] [INFO]  Newsfeed-Fetcher: Broadcasting 35 items.
0|MagicMir | [2024-11-08 09:13:43.480] [INFO]  [MMM-DynamicWeather] Getting Weather API data

/home/pi/.pm2/logs/MagicMirror-error.log last 50 lines:
0|MagicMir | [2024-11-08 01:03:43.562] [ERROR] [MMM-DynamicWeather] Failed getting api:  401
0|MagicMir | [2024-11-08 01:13:43.563] [ERROR] [MMM-DynamicWeather] Failed getting api:  401
0|MagicMir | [2024-11-08 01:23:43.532] [ERROR] [MMM-DynamicWeather] Failed getting api:  401
0|MagicMir | [2024-11-08 01:33:43.574] [ERROR] [MMM-DynamicWeather] Failed getting api:  401
0|MagicMir | [2024-11-08 01:43:43.559] [ERROR] [MMM-DynamicWeather] Failed getting api:  401
0|MagicMir | [2024-11-08 01:53:43.559] [ERROR] [MMM-DynamicWeather] Failed getting api:  401
<snip>
0|MagicMir | [2024-11-08 08:53:43.658] [ERROR] [MMM-DynamicWeather] Failed getting api:  401
0|MagicMir | [2024-11-08 09:03:43.690] [ERROR] [MMM-DynamicWeather] Failed getting api:  401
0|MagicMir | [2024-11-08 09:13:43.694] [ERROR] [MMM-DynamicWeather] Failed getting api:  401

@mmmallday – Update: I now have this running. I made two changes and it now displays alerts.

It is not clear why these changes made any difference, because when i revert the changes the module still works. I would expect that if either or both made a difference, the module behavior would have changed back…

The first change was to remove a line I had added in the config to specify the endpoint, which is now removed

weatherEndpoint: "/onecall",

The other change was to reduce the number of decimal points in the lat and lon from the six (6) produced by Google Maps to four(4), which I recall having used in the past.

As I said, it’s not clear what I did, but it’s working now so I will leave this module alone and go on to something else. Before I mark this as solved, I will wait a bit to see if anyone had further input as to the actual resolution.

Thanks for your time and attention.

@mmmallday – I already have a ver 3.0 API key, so if that is what you are referencing it’s covered.

Query: When you say “It’s not there…”, what “it” are you referencing? If you mean the weather in general, it’s definitely there - pulled from openweathermap and displayed on two different modules. I see it on my Magic Mirror as we speak on the default weather module and on MMM-OpenWeatherMapForecast.

I’m asking specifically about the alert information that gets delivered along with current conditions, forecasts, etc. This module [MMM-WeatherAlerts] should pull the weather data from openweathermap and display when [and only when] there is an active alert for the designated location. That is what is not happening… [FWIW, AFAIK other modules should also display alerts, e.g: MMM-OpenWeathermapForecast.]

I just now confirmed that openweathermap is actually sending the data. My location had a warning but it just expired, so I used my API key and queried them for a location the National Weather Service says is under a tornado warning.

Testing this is relatively straightforward. Go to the NWS alerts page to find a location with a current alert: https://alerts.weather.gov/search?region_type=land

Once you have a candidate location get the lat + lon from Google Maps, then use that and your API key to get the data in the browser, e.g.: https://api.openweathermap.org/data/3.0/onecall?lat=35.0194&lon=-97.3709&exclude=minutely&units=metric&lang=en&APPID=123456789123456789

Following is a snippet of the data retrieved (it’s at the very bottom of the page):

alerts	
0	
sender_name	"NWS Norman OK"
event	"Flood Watch"
start	1730730660
end	1730764800
description	"* WHAT...Flooding caused by excessive rainfall continues to be\npossible.\n\n* WHERE...Portions of Oklahoma, including the following counties,\nAtoka, Blaine, Bryan, Caddo, Canadian, Carter, Cleveland, Coal,\nComanche, Cotton, Garfield, Garvin, Grady, Grant, Hughes, Jackson,\nJefferson, Johnston, Kay, Kingfisher, Kiowa, Lincoln, Logan, Love,\nMarshall, McClain, Murray, Noble, Oklahoma, Payne, Pontotoc,\nPottawatomie, Seminole, Stephens and Tillman and northern Texas,\nincluding the following counties, Archer, Baylor, Clay, Foard,\nHardeman, Knox, Wichita and Wilbarger.\n\n* WHEN...Until 6 PM CST this evening.\n\n* IMPACTS...Excessive runoff may result in flooding of rivers,\ncreeks, streams, and other low-lying and flood-prone locations.\nFlooding may occur in poor drainage and urban areas.\n\n* ADDITIONAL DETAILS...\n- Additional rounds of heavy rain will be possible through\nMonday, ending from west to east Monday afternoon. Many areas\nin the watch have seen 2 to 4 inches of rainfall, with some\nlocations 5 to 8 inches. The additional rain could lead to\nrapid flooding, especially in low lying and poorly drained\nareas.\n- http://www.weather.gov/safety/flood"
tags	
0	"Flood"

So my question remains - why is it that the National Weather Service is creating alerts, onerweathermap is collecting and delivering the alerts, but the alerts aren’t being processed by our modules?

@sdetweil – I was able to search out a fix.

For the benefit of anyone else running Wayland and wanting or needing to switch back to x11, see: https://linuxconfig.org/how-to-use-x-instead-of-wayland-on-ubuntu-22-04 where you are asked to edit one line in a file, then reboot.

sudo nano /etc/gdm3/custom.conf

I will mark this as solved now.

@sdetweil – OK, thanks for the effort!

@sdetweil – Humm, I see what you mean. unfortunately this isn’t running on an actual Raspberry Pi so I don’t have that utility available to me.

It’s a VM running Ubuntu 23.10. If you can point me in the right direction, I’d be willing to give it a shot.