1
0
mirror of https://github.com/node-red/node-red-nodes.git synced 2023-10-10 13:36:58 +02:00
Commit Graph

6 Commits

Author SHA1 Message Date
borpin
dbea8a484a Updates to match API changes (#392)
* Updates to match API changes

Update to the node to match the server API changes. An attempt has been made to leave a legacy path for existing installations that may have not updated the server side.

* Updated following comments.

Update following comments.

Output removed and node.warn or error used.

oneeditprepare added.

Name moved to last item.

In addition, a check added to ensure nodegroup has valid value.

Question: I have added a 'return' as I do not want data posted if there is not a valid nodegroup.  Is this the best way to exit the function?  Always taught that multiple exits was a bad idea.  I wondered about raising an error / exception and then catching it but not sure how to do that.

* Update documentation for revised node
2018-01-07 15:37:28 +00:00
Dave Conway-Jones
0880ad3987 update io nodes info style 2016-03-02 13:27:52 +00:00
Dave Conway-Jones
bbed4bab9a Emoncms - drop time if not a number
and update docs.
2015-12-09 13:21:42 +00:00
Glyn Hudson
dc3c1b7cc4 Don't log when all is good, parse JSON retun 2015-10-26 00:47:55 +00:00
Glyn Hudson
df6fe4b17c Add 'Emoncms in' to fetch latest feed value from emoncms server 2015-10-21 12:08:30 +01:00
dceejay
0065227c68 Fix emoncms spilling mistake
Also add it as an npm package node-red-node-emoncms
2015-01-04 20:34:12 +00:00