Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

currentweather.js fails to display Fahrenheit #1247

Closed
pdanielsen opened this issue Apr 1, 2018 · 3 comments
Closed

currentweather.js fails to display Fahrenheit #1247

pdanielsen opened this issue Apr 1, 2018 · 3 comments

Comments

@pdanielsen
Copy link

pdanielsen commented Apr 1, 2018

Platform: Raspberry Pi Zero W with raspbian-stretch 9.1, chromium-browser 60.0.3112.89

Node Version: v6.14.1

MagicMirror Version: v2.3.1

Description: When config/config.js has units = "imperial", the currentweather module doesn't appear at all. This is due to a typo in currentweather.js. The variable 'windChillInF' is referred to at line 417, but doesn't exist. It was declared and calculated at line 410 as 'windchillinF'.

Change the declaration and calculation to 'windChillInF' to follow the convention for the 'windChillInC' variable used for Celsius.

Steps to Reproduce:
In config/config.js
Set units = "imperial"
Include the currentweather module in the "modules" list
Start the mirror software
Visit the mirror server in a browser

Expected Results: The currentweather module should appear in the browser.

Actual Results: The currentweather module did not appear in the browser.

Configuration:

...
var config = {
  ...
  units: "imperial",
  ...
  modules: [
    {
    module: "currentweather",
    position: "top_right",
    config: {
      location: "New York",
      locationID: "5128581",  //ID from http://www.openweathermap.org/help/city_list.txt
      appid: "YOUR_OPENWEATHER_API_KEY"
    },
    ...
  ]
  ...
}
@MichMich
Copy link
Collaborator

MichMich commented Apr 2, 2018

I made a change which should solve this: 10eb41d

Could you give the develop branch a try and let me know if this fixed your issue?

@CraigDamlo
Copy link

I haven't tried the developer branch, but can confirm on the main branch. The forecast works fine, just not the current.

@pdanielsen
Copy link
Author

pdanielsen commented Apr 2, 2018 via email

@MichMich MichMich closed this as completed Apr 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants