@sdetweil
Jackpot!!!
A quick update and I finally think I figured it out, at least for MMM-OpenWeatherForecast by:
node_helper.js line 44 from 2.5 to 3.0 :var url = https://api.openweathermap.org/data/3.0/onecall?"
Thanks again and I’ll share on the other thread as well. “https://forum.magicmirror.builders/topic/17644/a-working-weather-module”
@N6NG and @sdetweil
Hi All,
Passing along some info as I was also having problems with my ASUS VZ27EHE monitor staying off / my monitor coming back on with MMM-PIR-Sensor-Lite. The display would turn off, then a blue screen come on saying “HDMI No Signal” but then automatically turned back on. I used both xrandr and xset commands but nothing worked on my pi 4 running Bullseye.
After some digging and looking at this site “https://github.com/raspberrypi/linux/issues/2517”, I replaced the code in the node_helper.js (I know you’re not supposed to touch but this is what worked for me) and it works now. The only issue is on reboot, I have to run a command once to avoid the screen going to a gray state xsetroot -display :0 -solid Black.
case 'xset':
exec("xset -display :0 s noblank", null);//default: xset dpms force off
//Have to run 'xsetroot -display :0 -solid Black' on reboot to avoid gray screen
exec("sleep 1", null);
exec("xset -display :0 s off", null);
exec("sleep 1", null);
exec("xset -display :0 -dpms", null);
exec("sleep 1", null);
exec("xset -display :0 s 0 0", null);
exec("sleep 1", null);
exec("xset -display :0 dpms 0 0 0", null);
exec("sleep 1", null);
exec("xset dpms force off", null);
Don’t ask me how it works and I’ll give credit to E3V3A for posting that code. Hopefully this will help for those with a non-CEC compliant monitor and can fully turn off the monitor when not in use.
@TangoE30
A quick update and I finally think I figured it out, at least for MMM-OpenWeatherForecast by:
I hope this helps someone else because it was difficult for me to understand why some modules would work and others would not with the same API key.
@sdetweil
Jackpot!!!
A quick update and I finally think I figured it out, at least for MMM-OpenWeatherForecast by:
node_helper.js line 44 from 2.5 to 3.0 :var url = https://api.openweathermap.org/data/3.0/onecall?"
Thanks again and I’ll share on the other thread as well. “https://forum.magicmirror.builders/topic/17644/a-working-weather-module”
@bclinton1962
I’ve recently been down this rabbit hole and @sdetweil helped me investigate along with @KristjanESPERANTO. I’m new to MagicMirror but I think the issue is related to API keys (registered on March 2023 with OpenWeatherMap) and the particular weather module. I found that MMM-weatherforecast was another module that worked for me using my new API keys, similar to the default weather module. For now, I’ll be searching for some other modules and using the default module until a newer module becomes available that uses the API 3.0 keys.
@sdetweil
Thanks again Sam! I put the touch ~/MagicMirror/css/custom.css back into the directory and those two errors (Refused to apply style & 214 Error) did go away.
I tried to install another module MMM-OneCallWeather, with the option to change from 2.5 to 3.0. Upon adding the module and my latitude and longitude and API Key, I’m still receiving an “Loading” message. There are three errors related to icons not showing up.
For now, I’m going to see how I can modify the default Weather Module or continue to search for another that accepts the 3.0 API key.
@sdetweil
Thanks for the quick reply! Good information about the API versions and you’re correct that I just signed up (March '23) for a new API.
Per your suggestions, the following two error codes are displayed as follows:
Refused to apply style from 'http://localhost:8080/css/custom.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled. loader.js:214 Error on loading stylesheet: css/custom.cssThis previously did not show because I followed a command:touch ~/MagicMirror/css/custom.css. Since then, I have deleted the custom.css in my directory as there was no change.
At the end of the day, if the modules need an updated API version, I may have to stick with the default module or search for another that works with the API version 3.
Any suggestions on how to fix the current errors or a recommended weather module is appreciated.
@thad
Hi All - I wanted to post this here as I’m also using MMM-OpenWeatherMap and I figure better to post here than create another Weather topic. This is my first post but I have done some digging yet I’m striking out and looking to the forums for any guidance or suggestions.
Here is my issue - The default weather information is working correctly with an API from OpenWeather using Magic Mirror v2.22.0 however, I’m having issues getting any other weather module to display properly.
I have rebooted and tried four (4) other modules, yet they are all coming back “loading” even though the default is working. I prefer some of the other modules outputs, hence the reason I’m interested in this fix. I did try to replace the “k” with “K” in the apiKey section of the module, but that did not work either.
If there is any additional information needed, please let me know and thank you in advance.
Magic Mirror version is
My config code is below:
module: "weather",
position: "top_right",
config: {
weatherProvider: "openweathermap",
type: "current",
location: "Orlando",
locationID: "4167147",
apiKey: "6XXXXXXXXXXXXXXXXXXXXXXXXa"
}
},
{
module: "weather",
position: "top_right",
header: "Weather Forecast",
config: {
weatherProvider: "openweathermap",
type: "forecast",
location: "Orlando",
locationID: "4167147",
apiKey: "6XXXXXXXXXXXXXXXXXXXXXXXXa"
}
},
{
module: "MMM-OpenWeatherMapForecast",
header: "Weather",
position: "top_right",
classes: "default everyone",
disabled: false,
config: {
apikey: "6XXXXXXXXXXXXXXXXXXXXXXXXa",
latitude: "28.53834",
longitude: "-81.379242",
iconset: "4c",
concise: false,
forecastLayout: "table"
}
This is a screen shot of my result as well including developer section:
