Feature overview

What ESP RainMaker Neo gives you out of the box, what your firmware has to do to get it, and what is not there yet. Each row links to the page that explains it properly.

Available today

Feature	Where the user meets it	Firmware work
Groups	Phone app, dashboard	None
Schedules	Phone app	Time sync
Automations	Phone app	None
Time series data	Phone app history	Parameter flags
OTA updates	Dashboard, then silent	One enable call
Notifications	Push, webhooks	None
Local control	Phone app on the same network	One enable call
Voice assistants	Alexa, Google Home	Standard device types

"None" means the cloud does the work and your firmware only needs the standard data model. Where a feature needs firmware, the linked page says exactly what.

Two things worth knowing before you plan

Schedules run on the node; automations run in the cloud. A schedule is stored on the device and fires even if the node is offline. An automation is evaluated centrally, so it needs the node reachable to act. This single distinction decides which one a product feature should use.

Voice assistants only see standard device types. A parameter typed esp.param.brightness gets a brightness slider and answers "dim the lamp". The same parameter under a custom type renders as a generic control and is invisible to Alexa and Google Home. Pick standard types wherever one fits — see Custom and standard types.

Not in Neo today

Not available today. If your product depends on one, raise it early:

• Scenes — grouped parameter presets recalled together
• Command–response — request/reply beyond parameter writes
• ESP Insights integration — device diagnostics and crash reporting
• Secure signing — the hosted signing service for firmware images
• Matter — there is no Matter support in the firmware SDK

Related

• System architecture — where each feature actually runs
• Terminology — the vocabulary these pages assume
• Firmware guides — the implementation side of every row above