The OdieBotnet server should be able to:

• Handle web socket events from devices on the network.
• Keep track of device IDs -> IP addresses/Socket Connections
• Namespace IDs into groups (I.E. kitchen devices, light devices, lock devices, etc.)

OdieBotNet/modules/email.js
Pull in template html

OdieBotnet Device handshake:

1. Listen for broadcast UDP messages from a new device on port 8080
2. Assign device an ID number and add to ID to IP map for connected devices.
3. Send back a UDP direct message containing the webSocket port on server and the device's ID number
4. Device connects to Server through a webSocket to handle messages both directions.

Using the bash shebang, common file extensions, omitting semicolons, and using $() instead of `` for command substitution should give us more flexibility in development and deployment.

I am using this style guide for reference. I will submit a PR for this

Create restful API for OdiePlugins to use and send messages to devices.

These will be used by OdiePlugins that operate as the brains of Odie. OdiePlugins should know the device IDs it cares about and any grouping that it has setup.

OdieBotNet/modules/email.js

SentTestMail method must pull in handlebars template to render to email.