You pretty much have it spot on. There are two ways to get updates from Smartthings with node red and SAS.
- Polling
- Event based automatoins
Polling is by far easier since all you need to do is get your token and just setup the flow with the token in the "My Device" Node. Once you do that you just setup Node red to do what you want with the updates for the device. You should be able to setup one flow for all of the potential status updates needed.
You can create "Event" based automations with Node Red as well. I know the write up I did above seems involved, but most of it is one time setup. Though it seems complicated it really doesn't take long to setup on a raspberry pi if you have one. You will spend more time waiting on the pie to download and install the apps then anything else.
Endpoint Event automatoins are really needed when you want the fastest updates possible. I think of this like when a switch is changed or when motion is detected. Just a few seconds in that case can mean allot. I use endpoints automations with my arlo cameras for motion detection as well as the doorbell for immediate notifications. Most other items I use polling.
Samsung Automation Studio makes setting up a automation super simple. Basically the whole app is handled by 3 nodes. You just need the device profile, automation, and the event node for SAS to create the smartapp for you.
One draw back to keep in mind with SAS for Endpoints is that each endpoint automation requires it's own flow. So just be aware of that.
The summary of what is needed for Endpoints automation is actually quite simple. 1. You need a server to accept the connection. ie node red. 2. You need the connection to be secure between Smartthings and your local server host.
If you have a place to run Node-Red you already have half of that done. Securing it can be the hard part and is the big part of what posted before.
