Docs

Developer docs

Build smart apps and integrations for the Novon hub.

The Novon hub runs your code next to your devices. Two kinds of code run there:

One platform, not a bundle of products

Novon is built as a single system, which is what makes code written for it different from code written for a hub that only switches lights:

  • Multi-channel frontend. A home is controlled from the Novon mobile app, tablets and wall-mounted touch screens, the desktop, and voice assistants such as Alexa and Google. A device, scene or notification you add through the smart-app API or an integration shows up in every one of them.
  • An always-on local automation engine. Every automation runs on the hub itself, not in a data center: it watches device events, keeps schedules and timers, and acts on devices around the clock without a round trip to the cloud. That is the engine the smart-app API and the Flow Editor are written against.
  • Automation at the level each person wants. Flows for people who want to draw it, smart apps for developers who want to code it, and the AI flow builder for homeowners who would rather describe what they want in plain words and let the assistant draw it. All of it runs on the same engine and shares one device catalog, one run history and the same notification channels.
  • Presence and people, not just devices. Who is home, who just arrived, and which part of the day it is are first-class inputs: flows can start when someone arrives or leaves and gate on someone being home, and notifications reach the household, not one phone.
  • Visibility into what the home did. Every flow run and smart-app instance writes to one run history, so a homeowner can see what ran, when, and why it stopped. Flows add Recent runs with failure reasons and a debug mode with breakpoints; smart apps get a live log.
  • Professional monitoring built in. 24/7 UL-certified central-station monitoring is part of the platform, not an add-on. Your automations run alongside a real security system and its sensors, modes and alarm states.
  • Keeps working when the network does not. When the mobile app is on the same network as the hub it connects to it directly, so control is fast and keeps working while the internet is out. The hub also carries battery and LTE cellular backup, so events keep firing and alarms keep reaching the central station through a power or internet outage. Only cloud-dependent channels such as push, email, SMS and voice assistants wait for connectivity to return.
  • Local and private. Automation logic and device data are processed on the hub. Remote access is encrypted end to end, and Novon does not collect or sell behaviour data.
  • One hub, many devices, one household. The hub speaks Wi-Fi, Z-Wave, Zigbee and LTE, works with thousands of partner-brand devices, and takes on more through community integrations. People join a home with roles that decide who can view, run and edit automations, and flows can be moved between locations.

Start here

On this page