I'm opening this topic to ask if there's any reason to create a List of Modules for one's first installation of Node-Red.
I ask because it seems there's a few new users to NR every few days and the Flows that are being shared often use a Palette item not on everyone's installation.
- node-red-contrib-hubitat (Node-RED to Hubitat communication)
- node-red-node-rbe (continue down flow only if a value changes)
- node-red-contrib-noop (Simple placeholder node to help visualizations)
Palettes to help with logic:
- node-red-contrib-stoptimer2 (timer with ability to stop/cancel)
- node-red-contrib-easing (fading/dimming)
- node-red-contrib-state-machine (potentially simplifies if-then-else logic. There are a couple other implementations)
- node-red-contrib-time-range-switch (sunrise/sunset, between two times, etc.)
- node-red-contrib-bravia (Sony TVs)
- node-red-contrib-castv2 (ChromeCast TTS/audible announcements)
- node-red-contrib-harmony-websocket (Harmony hub)
- node-red-contrib-huemagic (Philips Hue hub interaction)
- node-red-contrib-lametric-notification (LaMetric smart clock)
- node-red-contrib-pushover (free web-based service)
- node-red-contrib-alexa-remote2 (Amazon routines, TTS and push notifications)
- node-red-contrib-semaphore (semaphore locking, fun but potentially tricky.)
- node-red-contrib-unsafe-function (use in place of Function node, much faster.)
- node-red-node-base64 (tried to use for dynamic images on dashboard.)
- node-red-contrib-average (average values of sensors eg. temp/humidity)
- node-red-contrib-light-scheduler (another timer node for common lighting schedules)
What else should first time NR users add early in the process?