Hello, and welcome to this video on connecting to and transferring files in Muse Automator.  In this video, we’ll cover three core Muse Automator concepts, the Controller node, Deploying Automator flows, and how to Push and Pull projects to and from a MUSE controller
Every Automator flow starts with the Controller node. The Controller node defines which controller or simulator you are connected to and which devices are available to your flow. Without a Controller node, Muse Automator cannot communicate with a Muse controller.
Begin by dragging a Controller node onto the workspace. Doubleclick  the node to open the configuration options. In the Remote section of the Controller Node settings, we will select HTTP from the drop-down menu and enter the IP address and port number of our Muse controller.  
Next, enter the controller’s username and password, and then Click Connect.  Automator will now establish communication with the NodeRED  server on the Muse controller.  If it is successful, you will see the list of providers and devices now populated with the information on the controller.  We will discuss these sections in more detail in another video.

 

After building or modifying a flow, it must be deployed. Deploying saves your changes and updates flows running locally by sending your changes to the local NodeRED  service running on your computer, not the Muse controller. Deploying DOES NOT send flows to the Muse Controller. 
The Deploy button can also be used as a status indicator. If the button is Gray, there are no undeployed changes. If the button is Red, there are changes pending that must be deployed. You must deploy before pushing a project so that all the recent changes are included in the flows that are pushed to the Muse Controller.
Keep in mind that if a project is running on the controller AND a project has been deployed to your computer, it is possible for multiple events to be triggered instead of a single event.  When testing/running code, make sure that only one location is running the project at a time.
Push and Pull move projects between your local Automator system and a Muse Controller. Push is used to send your project from your computer to your Muse controller so that the program is running on the Muse hardware. Pull is used to retrieve a project that was previously sent to a Muse Controller to your computer so that the project can be edited in Muse Automator. Both Push and Pull require that a controller node be included and connected to the Muse Controller that you want to Push a project to or Pull a project from. 
To push a project to your Muse Controller, click the arrow beside the Push/Pull button.  Next, under Local you will see the list of all projects on your computer.  Hover the cursor over the project you want to Push, and click the icon that looks like an arrow pointing Up. The deployed project will now be sent to the Muse Controller. 
To pull a project from a Muse Controller, click the arrow beside the Push/Pull button.  Under Remote, you will see the projects loaded to the Muse controller.  Hover over the project you want to retrieve, click the Down Arrow icon, and press OK. You will be prompted to choose to pull flows only or devices; select Pull Flows Only. Once the transfer is complete, you will be presented with a Review changes button. Click this button and if no conflicts are reported, click merge to complete the process.  
It is important to note that if there is already a project with the same name on your local system as the project you are pulling from the Muse controller, the local project will be overwritten in this process.  Make sure that the project has been backed up if necessary.