Loading…
Two integrations are live end-to-end today — Aranet Cloud sensor sync and Modbus TCP lighting control — plus an HTTP ingest path for everything else. This guide wires all three, then turns the data into zones, alerts, and dashboards.
Monitoring setups fail when they start with a wall of protocol acronyms. VibeLux takes the opposite approach: start with the integrations that are genuinely production-ready, get real readings on a dashboard, and grow from there. Expect the first two steps to take under an hour if you have your Aranet API key and controller address at hand.
If your facility runs Aranet wireless sensors, this is the fastest path to live data. Go to Integrations → Sensors, open the Aranet Cloud card, and paste your Aranet Cloud API key. VibeLux live-tests the key on the spot and shows connection status, the last sync time, and how many readings came over. Once connected, a background sync keeps pulling readings in — no on-site software to install for this path, since Aranet's cloud does the collection.
For control (not just monitoring), VibeLux ships a production Modbus TCP driver for GrowWise-style control areas — zone-level dimming, on/off, and 4-channel spectrum commands. You register the controller by host and port; if VibeLux can reach it directly (self-hosted or VPN), it probes the connection and marks it live. For cloud deployments, connect through the on-prem bridge agent instead: it makes an outbound-only connection from your network, so you never open inbound ports to your control LAN. The 8-step Energy Setup wizard walks the whole chain — facility, baseline, utility, gateway, lighting controller, meter, zones, review.
For hardware without a first-party integration, generate a sensor ingest key from the same Integrations → Sensors page. Any device that can POST JSON — a SICK Inspector-P vision sensor, a datalogger, a custom script — can push readings to the documented ingest endpoint using that key. The endpoint contract is shown right on the card, so you can point a device at the platform without guessing field names.
Zones are how readings and control meet: each HMI zone groups the equipment for an area of your facility and carries a persisted control mode, so the dashboard reflects how each zone is actually being run. In Operations → Automation you can also set zone control modes and automation rules that act on connected equipment. Zones defined here line up with the zones your designer layouts and lighting recipes target.
With data flowing, Operations → Alerts shows a live alert stream from your connected facility, and the operations analytics and cultivation dashboards read from the same real APIs — environment readings, active recipes, and irrigation intent, not canned demo numbers. Surfaces that don't yet have live data behind them say so with an explicit demo-data banner, so you always know which numbers are yours.