LOL!
Seriously folks, we do need people to test out the develop code. It’s one thing for us to write code and push it up and only a select few test it, particularly those who have asked for that bit of code. We need the greater population to test as well. Something may be broken for others, or we may have inadvertently broken existing code and we won’t know.
So please, test the code, let us know what works, what doesn’t, what fails. It’s the only way we can find these bugs.
You mean I shouldn’t, by default, be living on the edge and always use the develop branch? :)
Without the proper tools or instruments, you have to be really careful that you don’t short out the inverter or cause other damage.
Try the 'pm2 logs' and see if that sheds any light.
Yep, open Terminal and edit there, or use an SSH client remotely. The config is a bit finicky I discovered. Try not to change the layout too much, like for example, in your pastes above, I see this:
}, {
… in between modules. While I don’t think that would cause a problem, it also wouldn’t surprise me if that’s tripping up the parser. Keep them on separate lines:
},
{
Assuming the Mini is running the underlying BSD Unix OS, technically it should be possible, however you are pretty much on your own there. You need to find out if there is a recent node version that will run on it, and install that. Then do a manual clone of the repository and run 'npm install' in the cloned folder and see if it runs without errors (warnings are OK).
My fan is quiet, but remember that these are cheap fans. You may get a very noisy one. Fans are cheap, you can buy a bunch of them and figure out which is the quietest. Or you can find some really quiet ones through an electronics vendor such as DigiKey or Mouser, and pay a higher price for them. I replaced two 30mm square, very noisy fans on my 3D printer, $7 each at the time. Now they’re a little over $9. Good fans are expensive.
FYI, both my rpis are running at 1GHz.
Do not copy/paste from one OS to another, the language translations between them will be different, UTF-8, Windows, it’s all foobar. Edit the config file ON the rpi. You can use the command 'nano' for that, as in 'nano config.js'. Doing the copy/paste is why your ‘'’, ‘"’ and others get translated wrong.
Not at the moment. But you can write a module for that.
That sounds about what my rpi was doing. Mine was closer to 65-70 °C. Then I bought this case and now it’s consistently sitting around 45-50 °C. Even with processor intensive tasks, it rarely hits 60°C.
Yeah that’s odd, it’s the same on mine, so you do have en_US locale installed on the rpi. But why is MM² failing for you, when it’s working fine for me, that’s a bit of a mystery. If you don’t mind, just for grins, would you care to run through only Step 2 in this post: https://forum.magicmirror.builders/topic/236/complete-setup-tutorial/4, specifically the Internationalization part.
And in the EN_US.UTF-8 folder? Is there stuff in there?
@Mitchfarino said in Weatherunderground - currently - hourly - daily - configurable:
@KirAsh4 that isn’t showing for me
I just see white space then the screenshot
Oh @paviro … was ist das? Why isn’t Github displaying properly for everyone? I can see them just fine … Is that because I have a GH account? This makes me wonder how many others can’t see them and therefore have no clue how to get to the module source.
The very first post in this thread has the module link posted in it. It’s the exact same link you just posted above.
I don’t have a PIR sensor to fiddle with … however, why are you setting pin 3 HIGH, and as an OUTPUT? If it’s to power the PIR sensor board, don’t, use either pin 1 or 17, those have a constant 3v3 on them (or if you know your sensor can tolerate 5V, use pins 2 or 4). If it’s to read from the PIR sensor, it needs to be set as an INPUT pin so it can detect when the sensor triggers it.
@EoF, you can, as an external process, just like everything else. :)
Odd bug, as I have two different rpi 3s running just fine with 'en' as the value. This makes me wonder … can any of you paste the contents of your ‘/usr/share/X11/locale/’ folder?
$ sudo ls -aF /usr/share/X11/locale/
The webcall:// protocol triggers an external handler to handle the information (such as iCal), whereas the http:// (or https://) handler will simply download the .ics file, which is what we need to then process.
It can be a confusing, sometimes damn near frustrating landscape to maneuver. Glad you got it to work though.
No, the instructions, as written, are accurate. You missed the last bit of Step 1:
npm install to install the node dependencies.Had you done that last bit, you would be executing the next step from within the button module folder, not within the MagicMirror folder.