This looks great. As mumblebaj said, I too was concerned about the thickness but more about how far out the screen would stick out from the wall, but showing it next to a wall-mounted television shows that the Magic Mirror sticks out about the same.
It also took me far too long to realize that GA is Google Assistant. Some acronyms/abbreviations just never stick in my brain!
Just to make sure, do you have the opening curly bracket before your first line above? Also, why do you have “code_text” after the comma at the end?
I also notice that you use single quote marks instead of double-quotes in the config: block. I am not sure that matters, but all of the examples use double-quotes. (Single quotes should work, but there is always the chance that npm, MM, or some other component is expecting double-quotes.)
When you say you cannot get it working, does having that block of code in your config.js cause MM not to launch correctly at all? (Ie., do you get a black screen or the “create a config or check the existng one for errors” message?) Or does MM launch correctly, and the module does not show up? Or it shows up, but just has a “Loading” message instead of the expected calendar?
Thank you for that. I learned a number of things I did not know, including the pointer for the Inspector window!
I also learned that I needed to put the font-size in rem instead of px. (I especially did not think about this, since the :root defines font-size in px units.)
On the little-closer-to-expected size, I also discovered that I had to specify both the module and the class. For clock, this meant doing “.clock .time” and “.clock .date”, as follows:
.clock .time {
font-size: 10rem;
}
.clock .date {
font-size: 4rem;
}
Again, thanks for the link to the lesson on how to use the Inspector to find this information. I would personally still see the value in including this in the custom.css.sample (or something similar) to demonstrate the need to call both the module and class, and the terminology to use.
Please ignore the ugliness. This is using the default config, and was just for the sake of demoing the effect of the custom.css addition.
I did find the custom.css.sample (https://github.com/MichMich/MagicMirror/blob/master/css/custom.css.sample), which was where I found the :root and --font-size to edit. However, changing anything in :root seems to affect all modules. I was unable to determine how to edit the custom.css to only affect one module.
Can you help me determine what to add/change in custom.css.sample so that I can affect individual modules in my own custom.css (which itself is just a copy of custom.css.sample)?
Thank you.
In the past, I edited the modules directly to get them the right size. When I upgraded MM to 2.16, I decided my best bet was to remove what I had, and build a new config.js from scratch. The main thing I wanted was to only edit the files that would not be changed from GIT (config.js and custom.css).
I started out with a basic config.js. and I wanted to increase the size of the time. I was editing custom.css, but nothing I did seemed to change the clock. I found that I could edit the “–font-size” under the :root section of the custom.css and make everything bigger or smaller, but I am looking for a way to change the size of individual modules.
In custom.css, I tried the following:
.clock {
--width: 400px;
--font-size: 48px;
}
I also tried putting it in the :root section, and tried creating a body section as well. After looking at the clock_styles.css in the clock module directory, I also tried similar things with .clockHour and other sections. Really, after I tried everything I thought should work, I then just started trying random things, with continued non-success.
Part of my problem is that I know a little CSS, but I am much better at editing (or adding/changing deleting) existing samples rather than trying to figure out how to start from scratch. In fact, at this point, I do not even know if .clock is the right thing to do and I am just doing it wrong, or if it needs to be :clock, or just clock with no punctuation.
If someone can help me, I would appreciate it. Additionally, if MichMich would not mind, would it be possible to include a couple of examples in custom.css for a couple of the default modules?
I am not sure this is the problem, but why are you using “apikKey”? My working OpenWeather module uses “appid”. Also, should it be “apiKey” (with only one “K”)?
I am using a config based off an old version, so I looked at the latest config.js.sample from the repo (https://github.com/MichMich/MagicMirror/blob/master/config/config.js.sample ), and it uses apiKey (with only one “K”).
{
module: "weather",
position: "top_right",
config: {
weatherProvider: "openweathermap",
type: "current",
location: "New York",
locationID: "5128581", //ID from http://bulk.openweathermap.org/sample/city.list.json.gz; unzip the gz file and find your city
apiKey: "YOUR_OPENWEATHER_API_KEY"
}
},
Lastly, if you have just generated your OpenWeather api key, it takes some amount of time (24 hours?) before it will start working. Hope this helps.
@BKeyport said in MMM-SystemStats (cpu temp/load, fre ram ...):
@v4r23 If you followed the install completely, reboot the system. It’s the one step that fixed it for me.
I was having the same issue, and rebooting fixed it for me. That surprised me, since I have been able to add modules on the fly (ie., without rebooting) so far. However, since MMM-SystemStats has system calls, I guess that is the difference.
I just donated as well. Hopefully, others are donating without posting, and continue to donate! Thanks to MichMich for MagicMirror, and thanks to the community for all the support, modules, and other contributions. I was amazed when I found MagicMirror and it met my needs exactly.