Every system you install, in one place.

Monitoring across brands

Most installers end up with a mixed fleet, and one portal per manufacturer. Helios reads all of them through their cloud APIs and presents one fleet.

Fully verified with Huawei FusionSolar and SolarEdge. Integrations are also built for Sungrow, Fronius, Azzurro, SMA, GoodWe, Growatt and SolaX — these are real integrations, and they are validated against your fleet when a system connects. We would rather tell you that than claim nine-brand parity we have not proven.

How often the data arrives

Cloud APIs are polled every five minutes, which is as fast as vendor rate limits sensibly allow. Where a site has an optional Helios edge gateway — a small Modbus RS485 to MQTT device — readings arrive every 30 to 120 seconds instead, pushed rather than polled, which sidesteps the vendor API limits entirely.

So: near-real-time with an edge device, five-minute resolution without one. Both are honest descriptions of the same product in different configurations.

What you can see

• A live energy-flow view — production to home, to grid, to battery — updating over a live connection rather than on page refresh.
• Per-device energy breakdown, and per-phase and per-MPPT diagnostics: voltages, currents, temperatures, fault codes, conversion efficiency.
• Device-offline detection at three independent layers: polling failures, a 30-minute data-gap sweep, and per-minute watchdogs on edge gateways and EMS controllers. Recovery is detected automatically too.
• Automatic gap detection and backfill. This is Huawei-only today and we do not generalise it.
• Raw readings retained for five years under a GDPR-audited retention policy.

Detecting problems before the customer calls

Six automated detectors run over each system's telemetry every fifteen minutes. They split into two groups, and the distinction matters.

Three work from day one

• Sustained grid voltage outside the EAC grid-code band of 207–253 V.
• The same inverter fault code recurring repeatedly.
• One MPPT string under-producing against its sibling strings — the signature of shading, soiling or panel damage.

Three need history before they can say anything

• Inverter conversion efficiency falling below its own 30-day baseline.
• Battery charging behaviour degrading against a 12-week baseline.
• Monitoring-device radio signal deteriorating over time.

These three compare a system against its own past, so they need roughly 7 days to 12 weeks of history depending on the detector. They are not useful on a system commissioned yesterday, and we will not pretend otherwise.

Alerts carry the measured value, a plain-language likely cause and a repair suggestion, in English and Greek, and they land on the installer dashboard. They clear themselves when the condition resolves. Detection depth depends on what each brand's telemetry actually exposes — these detectors are designed to catch the categories above, not to catch any conceivable fault.

The battery detector is an early-warning trend indicator. It is not a state-of-health test and should not be presented to a customer as one.

Savings, reporting and what a system is worth

Production figures alone do not answer the question a customer asks, which is what the system is doing for their bill. Under net billing that gap is wider than it used to be — see net billing in Cyprus for why.

• Daily and monthly aggregates: production, consumption, import and export, self-consumption rate (calculated battery-aware), peak values, battery state-of-charge range.
• Savings in euro computed against a database-driven Cyprus tariff engine — EAC components, fuel adjustment, wholesale export rates. A rate change is a data change, not a software release.
• Virtual net billing settlement: a monthly credit ledger with a 36-month expiry sweep.
• CO₂ avoided at the Cyprus grid factor of 0.707 kg/kWh, with a trees-equivalent figure.
• Expected versus actual production, genuinely irradiance-corrected using weather data rather than compared against a flat annual assumption. Curtailment and throttling detection for commercial sites.
• Customer-facing energy, savings and history reports with CSV and PDF export, plus a monthly report email.
• An ROI calculator and bill estimator, implemented once in the backend and once in the browser with enforced parity, so a proposal figure and an app figure agree.

Where a site reports production only, self-consumption has to be estimated, and the product marks those figures as estimated rather than presenting them as measured. Where there is no usable import price, the report shows no money figure at all rather than inventing one.

Control, stated precisely

What you can do to a system from Helios depends entirely on how that system is connected. There are three tiers and they are genuinely different.

The installer side of the business

Monitoring is half of it. The other half is that most installers are running the commercial side across a spreadsheet, a mailbox and a filing cabinet.

• Leads on a kanban pipeline with stages you configure, follow-ups, and conversion to a customer.
• Leads and customers recorded as a person or a business, with companies (the VAT number checked against the EU VIES register), contact persons, and an owner for every record.
• Proposals built from your product catalogue, with an ROI snapshot and a branded PDF. The customer accepts or declines from a link, without an account, and you can see when they opened it. Optionally through a DocuSign signing step, and optionally with a card payment at acceptance — the full amount, a fixed deposit or a percentage — paid straight into your own Stripe account.
• Invoices, including recurring ones, carrying a payment link once you connect your own Stripe or Viva Wallet account; receipts; and automatic overdue reminders you can switch off per invoice. An invoice can be raised automatically when a service ticket is completed or a proposal is accepted. The accountant export hands over invoices, payments and VAT by rate as a spreadsheet or CSV files.
• On Installer Pro, Xero or QuickBooks sync — issued invoices go across every 30 minutes, and payments recorded there mark the invoice paid here — and 3CX, which matches each call to the lead or customer, logs it on their timeline and saves unknown callers as leads.
• A product catalogue with cost and selling prices, warranty details, and stock levels with a low-stock threshold.
• Service tickets and a service board, checklists whose items can require a photo or a note, maintenance plans, contracts and visits, and an equipment register with warranty tracking and photos.
• Teams, employees, tasks, a personal calendar and a team calendar, and staff time off — assigning work to someone who is away shows a warning, never a block.
• A shared inbox: connect a Microsoft 365 mailbox, or forward and BCC mail to your organisation’s Helios address from any provider, and mail from known leads and customers lands on their record. Gmail is offered once Google has verified the Helios app.
• Workflow rules on leads, customers, systems, service tickets, contracts, proposals, invoices, tasks and products. Triggers include a stage change, a field update, a date arriving, a proposal being viewed, an invoice paid or overdue, a contract expiring, stock running low, and a system going offline or coming back. Actions include notifying someone, creating a task, updating a field, adding a tag, logging an activity and assigning a lead.
• Custom fields — text, numbers, dates, choice lists, checkboxes, contact details and more — arranged into tabs with rules for when each tab shows; tags; a form builder; and documents.
• Data import from CSV — customers, products and invoices — with instructions for exporting each file from Zoho. Imported customers keep their ID from the old system, so invoices imported later attach to the right customer, and imported invoices send no automatic reminders until you switch them on.
• White-label branding per organisation on Installer Pro: your logo and colours, and your own email and document templates.

Installer analytics covering sales performance, pipeline, revenue, team and service are available depending on plan.

Alerts

Alerts reach your team by email and in the app. Under Settings › Notifications you decide which automatic messages go out, type by type and channel by channel, and one switch pauses everything to your customers. Marking a customer or lead “do not contact” stops every automatic message to them — receipts, reminders, renewals, workflow messages — while your staff can still write to them by hand.

Triggers include systems going offline and recovering, inverter cloud alarms with anti-spam cooldowns, temperature alerts, EMS safe-fallback events, a sustained performance-ratio drop checked weekly, and reminders for maintenance, contracts, invoices and trials.

Access, security and language

• Installer and customer portals with per-request tenant isolation, so one organisation's data cannot be reached from another's session.
• TOTP two-factor authentication with recovery codes. Two-factor can be enforced for administrators.
• Roles: built-in ones (owner, admin, manager, staff, read-only, accountant) and your own. A role sets, feature by feature, no access, view only or full access, and whose records it reaches — the person’s own, their team’s, their team tree’s or everyone’s. Only features your plan includes appear.
• An organisation audit log of every change, field by field, kept 24 months, which nobody can edit or delete; a log of every request, refused ones included; sign-in history with failed attempts; and a command audit log on every system.
• Recently deleted: a deleted record can be restored for 30 days (90 for leads) before it is removed for good.
• One email address can hold logins in more than one organisation; the person picks which one when they sign in.
• GDPR support: self-service raw-data export delivered as a signed link, plus retention and purge jobs.
• Fully bilingual English and Greek, including server-generated alerts, emails and reports.

The customer portal

Each customer you connect gets their own portal: live energy flow, energy history, savings in euro against their own tariff, reports, recommendations, alerts, their system and its devices, their electricity bills — which Helios can read from an upload — and a bill estimator, equipment and warranties, maintenance visits and support. On an Edge EMS site they also see the controller’s live state.

Your customers pay nothing for it.

Mobile apps

Two native Android apps. The installer app carries the working day: My Day, the fleet and each system, alerts, leads, customers, proposals and the ROI calculator, invoices, service tickets, tasks, the calendar, products, forms and time off. The customer app shows energy, battery, savings and reports, bills, proposals, maintenance visits and alerts. iPhone versions are on the way; the web app works on any device in the meantime.

AI add-ons

AI in Helios is a set of add-ons, each switched on separately in Settings by an account admin, all drawing on one monthly AI allowance (AI pricing). The models are Anthropic’s Claude.

• Data assistant — plain-language questions about your own records, answered from live queries, in English or Greek. It reads; with the separate assistant-actions add-on it can also propose a task or a note, created only once you confirm it.
• Connect your own AI app — add Helios as a connector in Claude, ChatGPT or Copilot. The app reads what you can see, as you, and cannot change anything.
• Drafting — inbox reply drafts, follow-up suggestions for overdue leads, drafts written by workflow rules, and an annual energy report per customer. Drafts wait in a review queue; nothing is sent by itself.
• Reading the situation — a briefing on a lead or customer, a morning fleet briefing, lead signals drawn from notes and history, and ticket triage that suggests a type and priority.
• Solar-specific — the battery opportunity radar, bill audit, and reading an uploaded EAC bill, which every plan includes.
• Import — AI-assisted import of customers, products and invoices from your own spreadsheets.

Every assistant and AI-app call runs as the person who asked, with their access, and is recorded in the audit log. Control of batteries and inverters never involves AI: it is deterministic by design.

API and webhooks

On Installer Pro, a documented REST API and 20 webhook events connect Helios to your own systems, with keys capped by a role, IP allowlists, expiry dates, OAuth tokens, signed deliveries and verified endpoints. How the API and webhooks work.

Read next

Helios Edge EMS is the on-site controller for solar-plus-battery sites. Pricing covers the installer plans, Edge EMS sites and AI. The FAQ answers the specifics — supported brands, what control really means, what happens to data.