I can confirm my version of https://github.com/jclarke0000/MMM-MyWeather is no longer working or supported due to the doomed nature of the weather underground API.
I wrote MMM-DarkSkyForecast to replace it. It uses the Dark Sky API for weather data.
Find it here if you’re interested.
https://github.com/jclarke0000/MMM-DarkSkyForecast
@MajorC I would just go with the 4GB version as it is not a massive difference in price. Now that the Pi has better graphics we are likely going to see much more capable and sophisticated modules. I’m thinking in particular things like facial recognition can get to the point where it is much more responsive than it is today (not sure if the extra memory helps in this particular scenario, but it’s just one example of many I’m sure).
Given how long it took for the 4 to be released, you’re better off future proofing yourself as much as you can now. It would be a shame to be handcuffed by a relatively inexpensive option you decided not to get.
If you haven’t built a mirror yet, you’ll find that the price of the Pi is one of the least expensive parts of the project. Go with the best available.
@hermlam I haven’t looked at this code for a long time and it’s quite possible this module no longer works properly. I believe there are newer forks you can try that are currently under active development.
Try here:
https://github.com/jclarke0000/MMM-MyCommute/network/members
I’m the author of this plugin and I can confirm that the module will not poll for data outside the window you set. I designed it this way specifically to deal with Google’s quota.
@rudibarani it’s a great idea but not exactly as simple as enabling a second data source URL. As my module is designed to use the Dark Sky API, I would need a separate routine to handle the different data format, and it would be a one-off for just your sensor model. Of course others will want their sensors supported and so on… unfortunately I don’t have the time to support such variances in functionality, which all do what my module already does — provide you with real-time weather information.
One of the major benefits of the Dark Sky API is how accurate it is, given you can put in your exact long/lat coordinates. The temperature you’ll get from the API should be very close to what your sensor is providing, maybe off by at most one or two degrees.
That said, my module is very much open-source. You are free to fork it and try to add this functionality on your own. If your programming experience is limited, modifying someone else’s code is a good way to learn. My code is very well documented so you should have a good idea as to what each part does. Also JavaScript is very forgiving and makes for a great beginner’s language.
I know this isn’t the answer you wanted to hear, but I hope you’ll be encouraged give modifying my module a shot. It’s very satisfying when you make something like this work for your exact needs. It’s how I got started, and I guess it’s just snowballed from there! :D
@twosquirrels any errors show up either in the log or in Electron’s console?
When you turned it off before, how did you power down the pi? Did you use the inline power button in the power cable? If so, it’s possible that the card might have been corrupted. If you have a known good backup, I would try flashing that back to the card to see if it boots. I don’t know why the power supply includes a push button switch, as this is a known way to mess things up. It’s best to SSH in and use the command sudo shutdown instead, or wire up a momentary switch to the GPIO that runs a script to execute that command.
However the fact that you say that not even the red light comes on leads me to believe there is a larger problem, and the board might indeed be dead. If you have a spare SD card lying around, try flashing NOOBS on it and see if that boots.
@pugsly said in MMM-DarkSkyForecast - Yet ANOTHER weather module:
Trying to find out how to remove this spacing circled in RED.
By default my module forces a fixed width of 300px. It looks like your parent column (i.e.: top_right) is either explicitly set to be larger or is being forced larger by another module (maybe the “Devices Online” module underneath the forecast in your screenshot).
You can address either of the above situations in your custom.css file. If you’ve set an explicit width for the parent column, then this should fix the issue:
.MMM-DarkSkyForecast .module-content {
width: 100%;
}
Otherwise, if another module is forcing the width of the column to be larger than normal, then you can either try to tame the width of that module, or you can set an explicit pixel width for your forecast to use the extra space. Try something like this:
.MMM-DarkSkyForecast .module-content {
width: 450px; /* adjust this as desired */
}
@mydiva said in MMM-DarkSkyForecast - Yet ANOTHER weather module:
Hi all, why my day forecast jambs to the hourly forecast? This happens not always just rendemly?
By default, my module does not force a size for the tiles in this view, as I can’t guess how many columns you’ll have if you’ve adjusted the size of your main layout columns. It should be three columns on a default magic mirror installation, but the actual forecast information might cause the tiles to grow or shrink.
You can fix this in your custom.css file. Try this:
.MMM-DarkSkyForecast .forecast-item {
width: 33%; /* for a three column layout */
}
Adjust as desired. For a four-column layout, specify 25% (You may need to also increase the size of the main container (e.g.: top_left) to get it all to fit. For a two-column layout, use 50%.
I might add a specific configuration to handle this in the future so that you don’t need to write CSS to address this.