I am on:

running on a Windows 10 mini pc.

In node-red, using https://flows.nodered.org/node/node-red-node-email I have first created a local SMTP server:

followed by a change node in order to extract the html portion of the message from the message object:

In order to avoid email clogging I inserted a

to limit the email send rate to 1 email per second.

Finally, the message containing the html payload is sent to

which connects nicely to t the Gmail SMTP server, using my camper email account.

Gmail SMTP requires an App Password, which can be obtained following these instructions
https://support.google.com/mail/answer/185833?hl=en

This is how the flow looks like in node-red

This is how I set up the email notification in MyController

As you can see the email and domain are fake, since this SMTP server is local. I just needed to define an SMTP user. The same user is added to the list of the allowed users in the Email MTA node.

Hope it helps anyone who, like me, struggled with Gmail SMTP restrictions.

Simple timer based relay activation

This guide goes through the steps need to create a schedule to turn on and off a relay. In my case, the relay was to operate a sprinkler valve at 1:00am, for 45 minutes, so the values used in the following instructions reflect my use case, and may not suit your specific needs.

This first section, sets up the OPERATIONS used to turn the sensor (in this case, a relay) ON and OFF

Setting the DELAY on the OFF OPERATION, does exactly what it sounds like. Delays the activation of that OPERATION by however many seconds are entered. To activate the OPERATION as soon as it is called, enter 0 for the delay.

1. Create an OPERATION to turn the RELAY ON
   a) Click RESOURCES > OPERATIONS > "Add Operation"
   b) Give your new OPERATION a name
   c) Select ENABLED
   d) OPERATION TYPE: Send Payload
   e) RESOURCE: Sensor Variable
   f) Select relay sensor from list
   g) PAYLOAD: 1 (ON)
   h) DELAY: 0
   i) Click SAVE

2. Create an OPERATION to turn the RELAY OFF
   a) Click RESOURCES > OPERATIONS > "Add Operation"
   b) Give your new OPERATION a name
   c) Select ENABLED
   d) OPERATION TYPE: Send Payload
   e) RESOURCE: Sensor Variable
   f) Select relay sensor from list
   g) PAYLOAD: 0 (OFF)
   h) DELAY: 2700 (45 minutes)
   i) Click SAVE

The last step sets up the schedule as a TIMER. Select the options required for the day and time you want the SENSOR (relay) to operate, and add both of the OPERATIONS you just created to the timer.

3. Create a TIMER to run the schedule
   a) Click RESOURCES > TIMERS > "Add Timer"
   b) Give your new TIMER a name
   c) Select ENABLED
   d) Select the schedule using the drop-down lists.
   e) In my example, I have used a NORMAL timer, that runs DAILY, with every day selected.
   f) Select the start time for the timer
   g) If you only want your timer to run between specified dates, enter them into the VALIDITY fields.
   h) Select BOTH of the OPERATION (ON and OFF) in the selection field and add them to the RIGHT column by clicking the single right arrow
   i) Click SAVE

You now have a TIMER that will activate BOTH OPERATIONS, but as your OFF OPERATION has a delay of 2700 seconds (45 minutes) the sensor (relay) will remain active until that delay has passed and the OFF OPERATION is activated.

Hopefully this is simple enough, let me know if you'd like some pictures added to help

Note: Upgrade supports from 0.0.3-alpha1. Older than this release will not support the upgrade.

Before moving to new version version,

• Take a backup
• Stop mycontroller server (command: mycontroller/bin/stop.sh)
• rename the directory. (Command: mv mycontroller mycontroller_old)
• Extract new version (command: tar xzf mycontroller-dist-standalone-*-bundle.tar.gz)
• Restore backup from

Steps to take backup:

• Navigate to Settings -> Backup.

• Click on Settings. add location where you want to keep backup files. save
  

• Click on Run backup
  

Steps to restore:

• after backup completed successfully. Stop MyController from command line (Command: mycontroller/bin/stop.sh)
• rename mycontroller directory (Commnad: mv mycontroller mycontroller_old)
• Now extract new version. (Commnad: tar xzf mycontroller-dist-standalone-*-bundle.tar.gz)
• Start new version of MyController. (Commnad: mycontroller/bin/start.sh)
• Configure backed up file location on our new installation
• Now old backup file will be listing in our new installation
• Click on the file and run restore in action
  
• after successful restore change mycontroller/conf/mycontroller.properties manually compare to latest version
• start the server manually from command line. (Command: mycontroller/bin/start.sh)
• After successful migration compare and change your mycontroller/conf/mycontroller.properties file with latest file.