RainMaker User Features List
about
This feature list is based off the user roles of RainMaker. Mainly to say that it is distinct to features associated to End Users and Admin Users of ESP RainMaker.
It is worth to also note that features pertaining to Admin Users are also accessible to SuperAdmin Users for clients who have deployed Private RainMaker.
To learn more about ESP RainMaker User roles, please click here
End User Features
| End User Features | Capabilities |
|---|---|
| Remote Control and Monitoring | - Query node configuration, parameter values, and connectivity status for one or all nodes in a single call. - Set parameters for single or multiple nodes in a single API call. - View time series data using line or bar charts (Eg. temperature sensor readings, energy consumption, etc.) |
| Local Control and Monitoring | - Faster access when mobile phone and device are on the same network Check details here. |
| Time Series Data | - View complete time-stamped history of values of some parameters. - Perform operations to calculate the minimum, maximum, average, and other metrics within a specified time window of aggregated data. Check details here. |
| Time Management and Scheduling | - Supports network time (SNTP) and timezone, including automatic Daylight Savings adjustments. - Supports automatic actions based on time. - Absolute time (15:00) as well as relative time (Eg. 1 hr from now) supported. - One time or repeat (by specifying days). - Single or multiple nodes. - No Internet connectivity required for the node while executing the schedule at specified time. - Check here for detailed features and usage information. |
| Scenes | - "Scene" refers to a group of parameters set to specific values, where one or more devices may span across multiple nodes. For example, an "evening" scene may turn on all the lights and adjust them to a warm color. - Check details here. |
| Grouping | - Multi-level abstract grouping supported. - Group metadata can be used to create a Home - Room structure and also store other information related to the group. - Group operations supported indirectly via the APIs that support sending data to multiple nodes. - Group Sharing. |
| Node Sharing | - One or more nodes can be shared with one or more users. - New user can be either a primary user (full access) or secondary user (limited access i.e. cannot add/remove other users). - Entire groups can also be shared with primary/secondary permissions. - Any new node added to a shared group will get automatically shared (useful for Home sharing use cases). - Check here for details. |
| Automations | Perform action on one or more nodes based on: - Some event triggered on another node. - Weather conditions like Snow, Rain, etc. - Weather parameters like temperature, humidity, etc. - Daylight timings like sunrise and sunset. |
| Mobile Push Notifications | Following events are notified: - New node(s) added. - Node(s) removed. - Node connected/disconnected to/from cloud. - Node sharing request created/accepted/declined. - Node reported alert message. |
| Voice Assistant Integrations | Alexa and Google Voice Assistant support for the following categories: - Lights - Switches - Outlets/Sockets - Fans - Temperature sensors For complete list of supported device and parameter types, check here. Also check out the usage instructions. |
Admin Features
| Feature | Description |
|---|---|
| Node Registration | - Create certificates and register them using Python CLI. |
| Grouping | - Create abstract groups of nodes or structured groups based on firmware version, type, or model. |
| Over the Air (OTA) Firmware Upgrades | - Upload Firmware Binary and let cloud service auto-extract firmware version and model. - Push OTA upgrades to one or more nodes or a group. - Monitor the status of OTA jobs. - Cancel OTA Jobs. - Archive cancelled/completed OTA Jobs. - Firmware side checks prevent the wrong project/version binary from being sent. |
| OTA Upgrade Strategies | - Force push: OTA Image URL immediately sent to all nodes. Node need to be online to get the URL. Else, the strategy for Normal OTA would be used. - Normal: URL sent to node only if node queries for it. Nodes can query either during boot up or at regular periodic intervals as per the configuration selected in firmware. - User controlled: Once OTA is triggered, end user can query and decide when to start the OTA. - Time based: Can specify a time window within which the OTA job should be performed. - Check here for detailed features and usage information. |
| Statistics | - Node registrations (certificates registered by the admin) - Node activations (i.e. node connecting for the first time). - User account creations. - User-node association count. |
User Management
Sign Up
Supports following methods
- Email id + Password using an OTP based email id verification.
- Phone number + Password using an OTP based phone number verification.
- Sign Up using Google.
- Sign Up using Apple.
- Sign Up using Amazon (not available on public RainMaker or in Phone Apps).
tip
Sign up using Google/Amazon shares the user's email address with RainMaker. Sign up using Apple shares a dummy address that Apple assigns for the user specifically for the RainMaker service.
Sign In
- Email id + Password
- Phone number + Password
- Phone number + OTP
- Sign in using Google
- Sign in using Apple
- Sign in using Amazon (not available on public RainMaker or in Phone Apps).
tip
Sign in using Google/Apple/Amazon for new users is same as Sign Up and the cloud treats both of them as the same.
Change Password
- Valid only for Email id/Phone number based logins. Uses OTP based confirmation along with the old password.
- Logs out all other active sessions after password is changed.
tip
The logged out sessions can still stay active upto 1hr as per AWS Cognito behaviour.
Forgot Password
- Valid only for Email id/Phone number based logins. Uses OTP based confirmation.
Delete account
- Option to delete account with OTP based verification.