-
Notifications
You must be signed in to change notification settings - Fork 4
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
Trouble with node conditions.js #1
Comments
@centurion800 See step 7 in the readme. |
Weather Underground is no longer providing free API keys, instead, they provide cloud based "Data Packages". Any chance of getting the new APIs integrated? |
After that Weather Underground no longer provides API keys for free, is it possible that some one can fix the conditions.js with Looking forward and hope some can fix the broken conditions.js |
I noticed that http://api.wunderground.com/api/APIKETHERE/conditions/q/pws:IAMERSFO201 doesn't work I found that https://api.weather.com/v2/pws/observations/current?stationId=IAMERSFO201&format=json&units=h&apiKey=APIKEYHERE does give me back results, however, after changing the const url to const url = 'https://api.weather.com/v2/pws/observations/current?stationId=' + pws + '&format=json&units=h&apiKey=' + apiKey + '.json'; I'm stuck there.. |
root@servak:~/RTSP-Utilities# node conditions.js
Running every 5 minutes.
Getting current conditions...
/root/RTSP-Utilities/conditions.js:32
const temp = json.temp_f;
^
TypeError: Cannot read property 'temp_f' of undefined
at IncomingMessage. (/root/RTSP-Utilities/conditions.js:32:30)
at emitNone (events.js:72:20)
at IncomingMessage.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:905:12)
at nextTickCallbackWith2Args (node.js:441:9)
at process._tickCallback (node.js:355:17)
root@servak:~/RTSP-Utilities#
The text was updated successfully, but these errors were encountered: