Re: [node-red] Inject epoch into forecast.io

Message has been deleted

Dave C-J

unread,

Aug 28, 2016, 5:51:31 PM8/28/16

to node...@googlegroups.com

Answered on Slack

Your change is the wrong way round... you need to set msg.time not msg.payload, and epoch is in mS

This works - Jan 1st Year 2000

[{"id":"d4b535d2.c19a08","type":"inject","z":"896b28a8.437658","name":"","topic":"","payload":"946684800000","payloadType":"num","repeat":"","crontab":"","once":false,"x":148,"y":1272,"wires":[["ee0063ea.fe855"]]},{"id":"ee0063ea.fe855","type":"change","z":"896b28a8.437658","name":"","rules":[{"t":"move","p":"payload","pt":"msg","to":"time","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":false,"x":225,"y":1358,"wires":[["4032a22a.6f663c"]]}]

Toshi Bass

unread,

Aug 29, 2016, 7:48:02 AM8/29/16

to Node-RED

Hi am banging my head a little with this one I have a dropdown node to a function node with following code ...

msg1={};

msg2={};

var now = new Date();

var epoch = now.valueOf();

if(msg.payload==1){

var e1 = epoch-(60*60*48*1000);

msg1.payload = new Date(e1);

msg2.payload = e1;

}

blabla

both msg1 and msg2 work fine but on msg2 I just want the date like Sat Aug 27 2016 not 2016-08-27T11:40:07.551Z any help would be appreciated thanks

Capture.JPG

Zenofmud

unread,

Aug 29, 2016, 7:55:18 AM8/29/16

to node...@googlegroups.com

Dave just did an update of node-red-node-forecastio - see the thread: Possible node-red-node-forecastio issue?!?

--
http://nodered.org

Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
For more options, visit https://groups.google.com/d/optout.
<Capture.JPG>

Toshi Bass

unread,

Aug 29, 2016, 8:18:43 AM8/29/16

to Node-RED

yeah saw that, didn't update yet but my post is about javascript to convert msg1.payload = new Date(e1); from full date/time to just date into a text node, I tried everything I can think off but just not getting anywhere

msg2.payload = e1; which goes to forecastio node via change node appears to work fine and perhaps even better when I update that node

Zenofmud

unread,

Aug 29, 2016, 9:35:13 AM8/29/16

to node...@googlegroups.com

Why not use the node-red-contrib-moment node to format the date? Using the format

ddd, MMM Do YYYY

Gives me: Sat, Aug 27th 2016

[{"id":"b9b77df8.46488","type":"function","z":"332bf788.ccd408","name":"","func":"msg1={};\nmsg2={};\n\nvar now = new Date();\nvar epoch = now.valueOf();\n\nif(msg.payload==1){\n var e1 = epoch-(60*60*48*1000);\n msg1.payload = new Date(e1);\n msg2.payload = e1;\n}\nreturn [msg1, msg2];","outputs":"2","noerr":0,"x":398,"y":274,"wires":[["3785cbef.c87a34"],["f0067017.0ff99"]]},{"id":"be72b602.418d48","type":"inject","z":"332bf788.ccd408","name":"","topic":"","payload":"1","payloadType":"num","repeat":"","crontab":"","once":false,"x":198,"y":279,"wires":[["b9b77df8.46488"]]},{"id":"f0067017.0ff99","type":"debug","z":"332bf788.ccd408","name":"msg2","active":true,"console":"false","complete":"payload","x":602,"y":333,"wires":[]},{"id":"3785cbef.c87a34","type":"moment","z":"332bf788.ccd408","name":"","topic":"","input":"","inputType":"msg","inTz":"America/New_York","adjAmount":0,"adjType":"days","adjDir":"add","format":"ddd, MMM Do YYYY","locale":"\"C\"","output":"","outputType":"msg","outTz":"America/New_York","x":609,"y":286,"wires":[["3b64f735.c49b08"]]},{"id":"3b64f735.c49b08","type":"debug","z":"332bf788.ccd408","name":"msg1","active":true,"console":"false","complete":"payload","x":809,"y":227,"wires":[]}]

On Aug 29, 2016, at 8:18 AM, Toshi Bass <toshib...@gmail.com> wrote:

yeah saw that, didn't update yet but my post is about javascript to convert msg1.payload = new Date(e1); from full date/time to just date into a text node, I tried everything I can think off but just not getting anywhere

msg2.payload = e1; which goes to forecastio node via change node appears to work fine and perhaps even better when I update that node

Dave C-J

unread,

Aug 29, 2016, 9:46:28 AM8/29/16

to node...@googlegroups.com

Hi Toshi

if you just need to inject the date into the forecast.io node then leave it as epoch time in mSec. No need to re-format it.

Dave C-J

unread,

Aug 29, 2016, 9:47:29 AM8/29/16

to node...@googlegroups.com

As per my example above...

Toshi Bass

unread,

Aug 29, 2016, 10:35:37 AM8/29/16

to Node-RED

Sorry I wasn't very clear . trying to make like a menu see attached, if I choose today + 2 then forcast io shows correct weather for 31st Aug 2016 problem I am having is with text node I want just the relative date in there preferably in the format 31 Aug 2018, not date/time the date its self calculates correct as does the output to forecastio node.

Capture1.JPG

Capture.JPG

Toshi Bass

unread,

Aug 29, 2016, 10:40:17 AM8/29/16

to Node-RED

Oh sorry paul I didn't see your post I will dowenload node-moment and check your solution

Toshi Bass

unread,

Aug 29, 2016, 10:50:44 AM8/29/16

to Node-RED

OK that solution works fine thanks Paul

Toshi Bass

unread,

Aug 29, 2016, 11:32:38 AM8/29/16

to Node-RED

oh now I updated forcast_io to "version": "0.1.9", and now the below format doesn't appear to work anymore ... it just returns "time": "2016-08-29T23:00:00.000Z", for any input

inject Timestamp node

Function node

msg.time = msg.payload + (60*60*72*1000);

return msg;

Paul Reed

unread,

Aug 29, 2016, 12:09:01 PM8/29/16

to Node-RED

Stopped working for me too since the update to v0.1.9.

Also, if the forecast is set to 'Specify time & date' the 'Time' input box is too small & cannot be expanded.

Dave C-J

unread,

Aug 29, 2016, 6:46:53 PM8/29/16

to node...@googlegroups.com

Oops.. I'll take another look.

Dave C-J

unread,

Aug 30, 2016, 11:16:30 AM8/30/16

to Node-RED

Paul, Toshi,

ok have pushed version 0.1.10 - the function you had now works...

(for some reason it was only accepting that epoch number as a string... - now accepts number as it ought as well.

Toshi Bass

unread,

Aug 30, 2016, 3:11:01 PM8/30/16

to Node-RED

Dave

I installed 0.1.10 rebooted pi but still have problems:

first issue node is not returning all the expected data .. (in 0.1.9 and previous it was returning all)

{ "weather": "clear-night", "detail": "Clear", "humidity": 0.75, "windspeed": 1.42, "winddirection": 13, "lat": 35.9375, "lon": 14.3754, "clouds": 0.07, "precipitation": 0, "units": "us" }

So missing maxtemp, mintemp,sunrise,sunset

second issue data is the same for different days see attached and here is test flow

Capture.JPG

Capture1.JPG

Capture2.JPG

Paul Reed

unread,

Aug 30, 2016, 3:15:18 PM8/30/16

to Node-RED

I was just in the process of posting the same issues, but you beat me to it.

Just compared it with what is returned via a browser api call, which is complete, whilst a lot of the data is missing using the node.

Paul

Paul Reed

unread,

Aug 30, 2016, 4:06:26 PM8/30/16

to Node-RED

To highlight the issues, I've made a browser api request, and compared it with the node output, using the same epoch and location etc.

The forecastio git code shows what should be returned;

msg.data = jsun;

msg.payload.weather = jsun.daily.data[when].icon;

msg.payload.detail = jsun.daily.data[when].summary;

msg.payload.humidity = jsun.daily.data[when].humidity;

msg.payload.maxtemp = jsun.daily.data[when].temperatureMax;

msg.payload.mintemp = jsun.daily.data[when].temperatureMin;

msg.payload.windspeed = jsun.daily.data[when].windSpeed;

msg.payload.winddirection = jsun.daily.data[when].windBearing;

msg.payload.lat = jsun.latitude;

msg.payload.lon = jsun.longitude;

msg.payload.clouds = jsun.daily.data[when].cloudCover;

msg.payload.precipitation = jsun.daily.data[when].precipProbability;

msg.payload.sunrise = jsun.daily.data[when].sunriseTime;

msg.payload.sunset = jsun.daily.data[when].sunsetTime;

msg.payload.units = jsun.flags.units;

msg.location.lat = jsun.latitude;

msg.location.lon = jsun.longitude;

msg.time = new Date(jsun.daily.data[when].time*1000);

msg.title = RED._("forecastio.message.weather-forecast");

msg.description = RED._("forecastio.message.weather-info", {time: msg.time.toLocaleString(), lat: msg.location.lat, lon: msg.location.lon});

callback();

The browser api call returns;

"daily":{"data":[{"time":1472770800,"summary":"Light rain until afternoon.","icon":"rain","sunriseTime":1472793430,"sunsetTime":1472842408,"moonPhase":0.04,"precipIntensity":0.003,"precipIntensityMax":0.0114,"precipIntensityMaxTime":1472806800,"precipProbability":0.44,"precipType":"rain","temperatureMin":54.73,"temperatureMinTime":1472785200,"temperatureMax":68.9,"temperatureMaxTime":1472821200,"apparentTemperatureMin":54.73,"apparentTemperatureMinTime":1472785200,"apparentTemperatureMax":68.9,"apparentTemperatureMaxTime":1472821200,"dewPoint":55.75,"humidity":0.83,"windSpeed":9.94,"windBearing":221,"visibility":10,"cloudCover":0.67,"pressure":1016.39,"ozone":291.53}]},"flags":{"sources":["datapoint","gfs","cmc","fnmoc","isd","metwarn"],"datapoint-stations":["uk-310059","uk-350145","uk-350272","uk-350389","uk-350404","uk-350997","uk-351223","uk-351224","uk-351345","uk-351782","uk-352140","uk-352504","uk-352845","uk-353223","uk-353909","uk-354090"],"isd-stations":["033460-99999","033550-99999","033600-99999","033730-99999","749008-99999"],"units":"us"}}

The forecastio node returned data;

{"weather":"clear-night","detail":"Clear","humidity":0.66,"windspeed":7.65,"winddirection":213,"lat":53.472931,"lon":-1.054628,"clouds":0.02,"precipitation":0,"units":"us"}

You can see what data is missing, but also that it is not the same. Take humidity for an example - the browser api request returns 0.83, whilst the node returns 0.66.

Paul

Paul Reed

unread,

Sep 1, 2016, 3:27:35 PM9/1/16

to Node-RED

For info, dceejay has kindly released v0.1.11 on npm with a number of bug fixes.
Just tried it, and it works great!

Paul

Toshi Bass

unread,

Sep 2, 2016, 2:40:45 PM9/2/16

to Node-RED

Tried it this afternoon works perfectly thanks Dave

For anyone who's interested here's my flow..... would be interested if anyone can make / propose improvements

Paul Reed

unread,

Sep 2, 2016, 6:35:17 PM9/2/16

to Node-RED

Thanks Toshi, I've learnt a lot by looking through your flow.

A couple of minor observations;

Night weather icons

You have msg.payload='/nt+"partlycloudy"'; which doesn't produce an icon, but msg.payload="nt_partlycloudy"; works fine.

Time Format

The existing sunrise & sunset time format doesn't really fit the box very well, and would be better displayed in 24hr format, or hide the seconds, so that the 'AM' doesn't line break, and squash the box into 3 lines (I do realize why it's currently displayed 12hr format).

Many thanks for sharing.

Toshi Bass

unread,

Sep 2, 2016, 6:58:42 PM9/2/16

to Node-RED

Oh sorry about Night weather icons forgot I didn't finish that ( you may see WIP work in progress)

Strange Time Format is in 24hr format for me so it fits nice on iPhone iPad and desktop could this problem be you location (units forcastiio is defaulting to perhaps) I am using uk units set in forcastiio node

Paul Reed

unread,

Sep 2, 2016, 7:05:53 PM9/2/16

to Node-RED

I'm using the uk units too. The other date/time formats are displayed ok, just sunrise/sunset has the problem.

Paul

Paul Reed

unread,

Sep 2, 2016, 7:16:35 PM9/2/16

to Node-RED

Could it be this line in the sunrise function node?

msg.payload = (dates.toLocaleTimeString());

Paul Reed

unread,

Sep 2, 2016, 7:29:20 PM9/2/16

to Node-RED

Yep,

msg.payload = (dates.toLocaleTimeString('en-GB', { hour12: false }));

forces 24hrs format

Sorted!

Paul

Toshi Bass

unread,

Sep 2, 2016, 11:29:19 PM9/2/16

to Node-RED

Happy you resolved that .....found another small problem the moment node Date/Time Formatter needs to be set to Europe/London in both fields.

Julian Knight

unread,

Sep 3, 2016, 5:36:27 AM9/3/16

to Node-RED

That should be the default if the system you are running NR on has its time zone set correctly.

Paul Reed

unread,

Sep 3, 2016, 5:40:30 PM9/3/16

to Node-RED

Thanks Julian, as far as I know my timezone is set correctly;

pi@raspberrypi:~ $ sudo dpkg-reconfigure tzdata

Current default time zone: 'Europe/London'

Local time is now: Sat Sep 3 22:22:06 BST 2016.

Universal Time is now: Sat Sep 3 21:22:06 UTC 2016.

and locale;

pi@raspberrypi:~ $ locale

LANG=en_GB.UTF-8

LANGUAGE=en_GB.UTF-8

LC_CTYPE="en_GB.UTF-8"

LC_NUMERIC="en_GB.UTF-8"

LC_TIME="en_GB.UTF-8"

LC_COLLATE="en_GB.UTF-8"

LC_MONETARY="en_GB.UTF-8"

LC_MESSAGES="en_GB.UTF-8"

LC_PAPER="en_GB.UTF-8"

LC_NAME="en_GB.UTF-8"

LC_ADDRESS="en_GB.UTF-8"

LC_TELEPHONE="en_GB.UTF-8"

LC_MEASUREMENT="en_GB.UTF-8"

LC_IDENTIFICATION="en_GB.UTF-8"

LC_ALL=

Paul

Paul Reed

unread,

Sep 5, 2016, 12:31:13 PM9/5/16

to Node-RED

With a little help along the way, I've got the date to display correctly using a function node, instead of the 'moment' node, so you now have the option of using this instead, or adding the moment node and using that.

Paul

[{"id":"9590e167.4ce51","type":"function","z":"a444a9ff.e7a408","name":"","func":"msg1={};\nmsg2={};\n\nvar now = new Date();\nvar epoch = now.valueOf();\n\nif(msg.payload==1){\n var e1 = epoch-(60*60*48*1000);\n msg1.payload = -2;\n msg2.payload = e1;\n}\nif(msg.payload==2){\n var e2 = epoch-(60*60*24*1000); \n msg1.payload = -1; \n msg2.payload = e2;\n}\nif(msg.payload==3){\n var e3 = epoch;\n msg1.payload = 0;\n msg2.payload = e3;\n}\nif(msg.payload==4){\n var e4 = epoch+(60*60*24*1000); \n msg1.payload = +1; \n msg2.payload = e4;\n}\nif(msg.payload==5){\n var e5 = epoch+(60*60*48*1000); \n// msg1.payload = new Date(e5); \n msg1.payload = +2;\n msg2.payload = e5;\n}\nif(msg.payload==6){\n var e6 = epoch+(60*60*72*1000); \n msg1.payload = +3; \n msg2.payload = e6;\n}\nif(msg.payload==7){\n var e7 = epoch+(60*60*96*1000); \n msg1.payload = +4; \n msg2.payload = e7;\n}\nif(msg.payload==8){\n var e8 = epoch+(60*60*120*1000); \n msg1.payload = +5; \n msg2.payload = e8;\n}\n\n\n\n node.status({text:msg1.payload+\" : \"+msg2.payload});\n \nreturn [msg1,msg2];","outputs":"2","noerr":0,"x":94.5,"y":474.24999809265137,"wires":[["aa531c9f.f9fd8"],["607ce2fb.98d5cc"]]},{"id":"aa531c9f.f9fd8","type":"function","z":"a444a9ff.e7a408","name":"Date format","func":"var qdate = parseInt(msg.payload);\n\nvar monthNames = [\n \"Jan\", \"Feb\", \"Mar\",\n \"Apr\", \"May\", \"June\", \"July\",\n \"Aug\", \"Sept\", \"Oct\",\n \"Nov\", \"Dec\"\n];\n\nvar dayNames = [\n \"Sun\", \"Mon\", \"Tue\",\n \"Wed\", \"Thur\", \"Fri\", \"Sat\"\n];\n\nvar datenow = new Date();\n\ndatenow.setDate(datenow.getDate()+qdate);\n\nvar day = datenow.getDay();\nvar date = datenow.getDate();\nvar monthIndex = datenow.getMonth();\nvar year = datenow.getFullYear();\n\nmsg.payload = (dayNames[day] + ', ' + date + ' ' + monthNames[monthIndex] + ' ' + year);\n\nreturn msg;","outputs":1,"noerr":0,"x":267,"y":430,"wires":[["afc47cc3.dab22"]]}]

Julian Knight

unread,

Sep 6, 2016, 3:42:17 AM9/6/16

to Node-RED

Not sure why you need a function to get the right date format?

[{"id":"d30ae8a2.ec506","type":"moment","z":"462586cc.55d938","name":"","topic":"","input":"","inputType":"msg","inTz":"Europe/London","adjAmount":0,"adjType":"days","adjDir":"add","format":"ddd D MMM YYYY","locale":"en_GB","output":"","outputType":"msg","outTz":"Europe/London","x":477.36668395996094,"y":2361.933334350586,"wires":[["c1c7a591.8cc1d"]]},{"id":"45aea17c.08f58","type":"inject","z":"462586cc.55d938","name":"","topic":"","payload":"","payloadType":"date","repeat":"","crontab":"","once":false,"x":190.86668395996094,"y":2354.2833099365234,"wires":[["d30ae8a2.ec506"]]},{"id":"c1c7a591.8cc1d","type":"debug","z":"462586cc.55d938","name":"","active":true,"console":"false","complete":"false","x":689.8666839599609,"y":2366.6000213623047,"wires":[]}]

The only thing I can think of for the timezone issue would be if you had an older version of moment installed or a different tz that moment has misinterpreted. Might be worth adding a new moment node to see if that works as expected.

Also note that if you want an epoch value, moment is more than happy to oblige. Just use "X" as the output format if you want the epoch in seconds (the UNIX default) or "x" if you want milliseconds.

To get "Sat Aug 27 2016" from moment, the output format is "ddd MMM D YYYY"

Paul Reed

unread,

Sep 6, 2016, 4:05:09 AM9/6/16

to Node-RED

Not sure why you need a function to get the right date format?

As an alternative to using the 'moment' node. Users may not wish to install an additional node which is only being used on one occasion just to format one date, and maybe not used anywhere else. By using the function node instead of moment, means that Toshi's flow can be imported and used with just the forecastio node being added.

The only thing I can think of for the timezone issue would be if you had an older version of moment installed or a different tz that moment has misinterpreted. Might be worth adding a new moment node to see if that works as expected.

The format issue was nothing to do with 'moment', it was occurring in the timestamp produced from a function node (sunrise & sunset) which contained;

msg.payload = (dates.toLocaleTimeString); which did not include the option { hour12: false }

The default setting for toLocaleTimeString is locale dependent, however in my case it was wrongly formatted for some reason, despite my Timezone & Locale being correct (as above post shows).

Paul

Julian Knight

unread,

Sep 6, 2016, 4:49:49 AM9/6/16

to Node-RED

Ah, OK. For some reason I was feeling defensive! ;-)

I'll butt out then now that I know that moment is fine.

Toshi Bass

unread,

Sep 12, 2016, 6:27:33 AM9/12/16

to Node-RED

To get the Date, there is a alternative to using a function node or node-red-contrib-moment (which works great by the way :-) using Angular filters :

In the text node, value format field {{msg.payload | date:"EEE - dd'th' MMM"}}

Dave C-J

unread,

Sep 12, 2016, 6:33:43 AM9/12/16

to node...@googlegroups.com

Nice

Julian Knight

unread,

Sep 12, 2016, 8:31:57 AM9/12/16

to Node-RED

Cool! Good catch:

https://docs.angularjs.org/api/ng/filter/date

Paul Reed

unread,

Sep 12, 2016, 12:50:37 PM9/12/16

to Node-RED

Doh!

Mike Bell

unread,

Sep 12, 2016, 1:03:01 PM9/12/16

to Node-RED

Two, possibly obvious, points here. First, this works only if the msg.payload contains something that can be parsed as a valid date, e.g. a timestamp from an inject node. Second, this will work in the label field as well as the value format field of the text node. This last is hinted at somewhere in the documentation but not clearly enough to keep me from discovering it more or less by accident.