Node Ideas

A list of ideas for new node-red nodes.

• Extend node-red-node-email with an oAuth authentication option (PT, 2022-10-27)
  
• Folder Listing (JK, 2015-03-16)
  A quick, OS independent way to return an array of files and/or folders (using Node.js file system core library maybe)
• EXIF/IPTC input node (JK, 2015-03-16)
  Given an array of files and an array of metadata fields, GET the EXIF and/or IPTC metadata from the files and return as an array.
• EXIF/IPTC Output node (JK, 2015-03-16)
  Given an array of files and an array of metadata fields/values, SET the EXIF and/or IPTC metadata on the files.
• RSS Output (JK, 2015-03-16)
  A quick way to produce valid RSS output. Would need to set the correct HTTP headers as well as have an agreed input data schema. This, combined with the RSS "Feedparse" node would allow Yahoo! Pipes style reprocessing of feeds. The most common requirement for this is to add full articles into feeds that normally only supply short summaries.
• Scheduler (DCJ)
  a richer node than inject that can be used to set repeating and one off timer events - eg for heating/lighting control. Should have a concept of calendaring (ie day of week, day of month, etc) and also survive / recover in the case of power outages. See work in progress Scheduler Node and Later node for different pieces of the same puzzle.
• ELM327 / OBD-II node (@vielmetti, 2015-03-16). This node would support setting and getting values from an automotive diagnostic port; a possible library to speed this along is https://github.com/EricSmekens/node-bluetooth-obd which provides a bluetooth interface.
• MQTT Subscribe Node with the ability to change the topic (Ian M, 2015-03-17)
• Compare / Diff node that can compare two files and output changes? (SJ, 2015-03-20)
• LIRC node for sending infrared remote control commands. Perhaps using this: https://www.npmjs.com/package/lirc_node (SJ, 2015-04-06)
• Filter Node
  Although msg's can be filtered using a switch node, this is not intuitive naming. A more generic and logical form would be "filter". Perhaps we could have something similar to the under-query node but instead of filtering elements of the payload, we would be filtering incoming messages. (JK, 2015-04-17)
• Advanced Email Handling
  This one might be quite complex. A suite of nodes for building automated processes (workflows) based on email input. A node to read an IMAP folder (with filters) and return message id's for processing. A node for processing each message id, able to return all or some of the message including headers, text/html body, attachments & the ability to set flags on read (e.g. read/delete markers or other flags indicating processing is in progress). A 3rd node to update flags on a message (e.g. delete marker or other flags indicating processing is complete). (JK, 2015-04-17)
• Templated node data - Generate sample data using templates. This is likely going to be built on top of the NPM package called "dummy-json". (NK, 2016-03-06)