LuxPowerTek hybrid inverter beta support on 1app.energy

LuxPowerTek hybrid inverters are a familiar choice in UK solar and battery homes, especially where customers want battery storage to work alongside solar generation, grid import/export and time-of-use tariffs.

The hardware does an important job. It connects the solar and battery system, reports inverter data, and gives the installer and customer a way to see the system through the LuxPowerTek monitoring experience.

But the customer problem is usually bigger than the inverter alone.

Once a home has a battery, an EV charger, an Octopus tariff or a manually configured time-of-use tariff, the customer needs a clearer answer to a simple question:

Is my whole home using energy in the right way today?

That is the reason we are bringing LuxPowerTek homes into 1app.energy beta onboarding.

1app.energy is built to give customers one clearer place to understand solar, battery, EV charging and tariff behaviour. For LuxPowerTek homes, the first goal is to make the system easier to understand. Where control capability is supported, verified and enabled for the installation, the next step is tariff-aware battery behaviour.

This is a beta article, not a general-availability announcement for every LuxPowerTek installation. We are onboarding carefully so we can verify telemetry, customer experience and control behaviour before presenting LuxPowerTek support as fully rolled out.

Why LuxPowerTek homes need a clearer customer layer

Most renewable homes no longer work as one simple system.

A customer may have:

• a LuxPowerTek hybrid inverter;
• solar panels;
• battery storage;
• an EV charger;
• an Octopus smart tariff or another time-of-use tariff;
• export payments;
• manual tariff periods;
• different apps for inverter, charger and supplier data.

Each individual product can be useful, but the customer still has to join the dots.

For example:

• the inverter can show battery behaviour, but not always the full tariff context;
• the supplier app can show tariff periods, but not always the live battery decision;
• the EV charger can show a charging session, but not always whether the home battery is being pulled down;
• export data may be visible separately from the customer's real daily energy cost.

That is where many customers feel the software gap.

They do not want to spend every evening comparing three apps. They want to know whether the battery charged at the right time, whether the EV charging session affected the battery, whether the home imported during peak periods, and whether the system made sensible use of cheap windows.

What beta support means

Beta support means LuxPowerTek is being onboarded carefully, not treated as a finished blanket rollout.

In practical terms, beta onboarding can include:

• connecting a LuxPowerTek account and selecting the correct plant or site;
• reading LuxPowerTek inverter and battery telemetry where available;
• showing LuxPowerTek source labels clearly inside 1app.energy;
• bringing solar, battery, grid and tariff context into the same customer view;
• checking whether control capability is available for the specific installation;
• enabling control only where the backend confirms the LuxPowerTek control profile is verified and safe to use.

That last point matters.

Battery control is not something we should claim casually. A customer-facing app should not write battery commands unless the account, plant, inverter profile and readback behaviour have been checked properly.

So for some LuxPowerTek homes, the first beta experience may be telemetry and visibility. For allowlisted and verified homes, control behaviour can be enabled where supported.

That is the right way to build customer trust.

What 1app.energy adds for LuxPowerTek customers

1app.energy is not trying to replace the LuxPowerTek inverter or the installer's commissioning work.

It adds a customer-facing software layer around the home.

One place for live energy context

The customer should be able to see the home as one system:

• solar generation;
• battery charge and discharge;
• grid import and export;
• EV charging context where supported;
• tariff periods;
• daily energy and cost visibility.

That kind of view matters because the customer experience is not just "is the inverter online?".

The real question is:

Is the solar, battery, EV and tariff setup behaving in a way the customer can understand?

Tariff-aware battery behaviour, where enabled

For homes on Octopus tariffs, 1app.energy can use tariff context where supported. For other suppliers, customers can manually set import rates, export rates and cheap periods.

That means the app can explain battery behaviour against the tariff the customer is actually using, rather than leaving them to work backwards from a fixed inverter schedule.

Where LuxPowerTek battery control is verified and enabled for the installation, tariff-aware control can help the battery behave more intelligently around cheap windows and expensive periods.

Where control is not yet enabled, 1app.energy can still give visibility and context, which is a useful first step during beta.

EV charging context

EV charging is one of the biggest reasons customers get confused by home batteries.

If an EV starts charging during the day, a customer may not realise the battery has supplied part of that session. That can leave the battery lower than expected before the evening peak.

1app.energy is designed to make that relationship clearer. Where the relevant EV charger or tariff context is supported, it can help the customer understand how EV charging interacts with the battery and tariff periods.

For MyEnergi/Zappi homes, EV context is already part of the 1app.energy story where supported. Future charger integrations such as Ohme and Hypervolt remain roadmap items, not general availability claims.

Manual tariffs as well as Octopus

Octopus support is useful because tariff data can be synced automatically where supported.

But 1app.energy is not only for Octopus homes.

Customers on other tariffs can manually set their import rate, export rate and cheap-rate periods. That lets the app present the home against the customer's real tariff setup, even when there is no supplier API integration.

This matters for installers too. A LuxPowerTek customer should not feel excluded simply because they are not on the same supplier as another customer.

Why this matters for installers

Installers often choose hardware based on system design, battery size, customer budget, availability and site constraints.

But after handover, the customer judges the whole install through the software they use every day.

If a homeowner has to jump between an inverter portal, an EV charger app and a supplier app, the system can feel more complicated than it needs to be. That can lead to avoidable support questions:

• "Why did my battery empty before peak time?"
• "Did my EV charge from the battery?"
• "Why did I import from the grid when I had solar?"
• "Was my battery ready for the expensive period?"
• "Is my tariff actually helping?"

1app.energy gives installers a clearer post-install story for supported homes:

One app for solar, battery, EV and tariff.

For LuxPowerTek, the current message should be honest:

LuxPowerTek homes are entering beta onboarding on 1app.energy, with telemetry and customer visibility first, and control enabled only where the installation is verified and supported.

That is more credible than overselling a control feature before every real-world edge case has been proven.

What customers need to connect

For beta onboarding, a LuxPowerTek customer will typically need:

1. A LuxPowerTek Cloud account for the relevant home.
2. The correct plant or site selected during connection.
3. A supported tariff setup, either through Octopus where supported or manual tariff entry.
4. Connected EV context where available, especially for homes where EV charging affects battery behaviour.

The exact experience can vary during beta because different homes may expose different telemetry and control capabilities.

If a LuxPowerTek account connects successfully but control is not enabled yet, that does not mean the app has failed. It means the installation is being treated safely as telemetry-first until the control profile is verified.

Who should join the LuxPowerTek beta?

This beta is most useful for customers who already have, or are about to install, a LuxPowerTek hybrid inverter and want a better customer view of the whole home.

It is especially relevant if:

• you have solar, battery storage and an EV charger;
• you use Octopus Intelligent Go, Octopus Go, Agile, Flux or another time-of-use tariff;
• you want to understand whether EV charging is affecting your home battery;
• you want a clearer daily view of import, export, battery and tariff behaviour;
• you are an installer looking for a cleaner customer handover story for suitable LuxPowerTek homes.

It may not be the right fit yet if you need guaranteed automatic LuxPowerTek battery control on day one. During beta, control is deliberately gated by verification and installation capability.

How this fits into the 1app.energy roadmap

The bigger goal for 1app.energy is simple:

Bring solar, battery, EV charging and tariffs under one clear customer app.

Solis remains an important part of that story because many Solis homes have a clear customer software gap. LuxPowerTek is now being brought into beta onboarding so we can support more renewable homes over time.

Other inverter and charger integrations remain on the roadmap, including Sunsynk, Sigenergy, FoxESS, Ohme and Hypervolt. Those should be treated as future integrations until they are validated and ready.

Final thought

A LuxPowerTek hybrid inverter can be a strong part of a renewable home.

But the customer still needs a simple way to understand the whole system:

• what solar produced;
• what the battery did;
• when the home imported or exported;
• how the EV charger affected the battery;
• whether the tariff timing made sense.

That is the layer 1app.energy is building.

For LuxPowerTek homes, beta onboarding is the careful next step: clear visibility first, tariff-aware behaviour where supported, and control only where the installation is verified.

Visit 1app.energy to start early-access onboarding.