Custom Integrations
Each HEI device-device integration is a custom, unique development effort which requires the direct involvement of one (or both!) HEI device vendors.
The Problem
Without a standard interoperability framework, every integration between two HEI devices requires a custom development effort. Manufacturer A must work directly with Manufacturer B to create a specific integration between their products.
This doesn't scale. With N device manufacturers, you need N×(N-1)/2 bilateral integrations for full interoperability. And each integration requires ongoing maintenance as products evolve.
The Combinatorial Explosion
Custom Integrations Scale Poorly
| Manufacturers | 3 | 5 | 10 | 20 |
|---|---|---|---|---|
| Integrations Required | 3 | 10 | 45 | 190 |
For each pair of manufacturers to integrate:
- Business development negotiations
- Technical API/protocol discussions
- Custom development work
- Testing and certification
- Ongoing maintenance
- Version compatibility tracking
With 10 major HEI device makers, that's 45 separate bilateral agreements!
Vendor Dependencies
Custom integrations require direct vendor involvement, which introduces several problems:
- Business priorities: Vendors prioritize integrations based on market size, not your needs
- Competitive concerns: Competitors may refuse to integrate
- Resource constraints: Small teams can only support limited integrations
- Timeline delays: Integration requests queue behind other priorities
Real-World Examples
Tesla Powerwall + Third-Party Solar:
Tesla has created specific integrations with SolarEdge and a few other inverter manufacturers. If your inverter isn't on the supported list, you're out of luck for direct integration - hence the need for the Neurio CT workaround.
Smart Panel + ESS Integration:
SPAN Panel works seamlessly with Tesla Powerwall (they built the integration) but requires workarounds for other battery systems. Each ESS manufacturer requires separate integration work.
V2H EVSE + Transfer Switch:
A V2H-capable charger needs to know grid status from a transfer switch before it can safely backfeed. Without a standard protocol, each charger manufacturer must integrate with each transfer switch manufacturer individually.
Consequences for Homeowners
The custom integration requirement forces homeowners into difficult choices:
- Single-vendor lock-in: Buy everything from one manufacturer for guaranteed compatibility
- Limited choices: Choose only from "supported" device lists
- Degraded functionality: Accept that mixed-vendor systems won't work together optimally
- DIY workarounds: Implement custom solutions using Home Assistant or similar platforms
Impact on the Market
- Innovation stifled - new entrants can't integrate without vendor agreements
- Market consolidation - only large vendors can afford many integrations
- Higher prices - lack of competition from integration barriers
- Slower adoption - complexity discourages whole-home electrification
- Wasted effort - same integration work repeated by different parties
The Alternative: Standards
Other industries have solved this with standards. USB allows any device to work with any computer. Wi-Fi lets any device connect to any router. Matter is bringing this to smart home devices.
HEI devices need the same approach - a standard way to discover, connect, and communicate that doesn't require bilateral agreements.
How eBus Solves This
eBus provides a common interoperability framework that any manufacturer can implement independently. By adopting eBus:
- Devices automatically interoperate with all other eBus devices
- No bilateral agreements or custom development required
- Third parties can create adapters for non-eBus devices
- Once one adapter exists, everyone benefits
Instead of N×(N-1)/2 integrations, you need N implementations of one standard. 10 manufacturers means 10 implementations, not 45 integrations.