A supported Conow device
Lyra, CBE or Atlas balcony-solar / all-in-one energy storage.
Activated once in Conow ECO
Official integration · MIT open source
Conow Local
Home AssistantPrivate. Local. Always On.
Bring your Conow battery into Home Assistant over local Modbus. See solar, battery and grid power in real time—and build automations that keep working when the internet does not.
No cloud account
5-second local updates
RTU · USB or LAN adapter
Lyra · CBE · Atlas
100% localData stays on your network
Works offlineNo internet needed after setup
Open protocolStandard Modbus RS-485
Fully yoursMIT licensed on GitHub
Cloud optional
Home Assistant talks straight to your battery.
A small RS-485 adapter creates a direct link between your Conow device and Home Assistant. No round trip to a remote server. No account required for everyday use.
Fast, predictable updates. All monitoring and control registers refresh every 5 seconds.
Native Home Assistant entities. Build dashboards, histories and automations as usual.
Real controls. Set limits, backup reserve and forced charge or discharge from HA.
Home energy · NowLocal connection
☀
▰
⌂
1.84 kWSolar
78%Battery
0.62 kWHome
Grid power−420 W
Battery modeCharging
Cell temp.24.6 °C
Before you begin
Four things. One free afternoon.
If you already run Home Assistant, the only new hardware is usually the adapter and two signal wires.
Home Assistant
Home Assistant OS, Supervised, Container, or a local development install.
HACS installedA connection
USB-to-RS-485 adapter, or a Modbus TCP ↔ RTU Ethernet gateway.
Isolated adapter recommendedTwo signal wires
Connect RS-485 A to A and B to B. Keep the run tidy and away from mains.
Check device port labelStep-by-step guide
From unopened adapter to live energy entities.
Follow these steps in order. The two App steps are required even though your final connection is fully local.
1
One-time requirement
Activate the device in Conow ECO
Commission your Conow device and bring it online in the Conow ECO App at least once. This initializes the RS-485 interface.
!Factory-fresh devices will not answer Modbus. Complete activation before connecting Home Assistant.
2
In the App
Turn on External Control / ModBus RTU
The physical port remains disabled until this switch is enabled.
Conow ECO App → Devices → Your device → Settings → Enable External Control / ModBus RTU
✓Leave this switch on while you use the Home Assistant integration.
3
Hardware
Connect RS-485 A/B
Power down before wiring if your product manual requires it. Match the labels on both ends: A → A and B → B. Then connect the adapter to your Home Assistant host.
| Serial settings | 38400 · 8N1 |
| Slave address | 160 (0xA0) |
| Typical port | /dev/ttyUSB0 (Linux) · /dev/cu.* (macOS) |
ls /dev/ttyUSB* /dev/ttyACM* 2>/dev/null # Linux
ls /dev/cu.* 2>/dev/null # macOS — prefer /dev/cu.* over /dev/tty.*
| What you connect to | RS-485 ↔ Ethernet adapter |
| Host / IP | adapter IP, e.g. 192.168.1.50 |
| TCP port | 502 |
| Slave address | 160 |
!Conow devices speak Modbus RTU over RS-485 only for now — native Modbus TCP firmware is not shipping yet (expected by the end of the year). To reach the unit over your LAN you must add an external 485-to-Ethernet adapter; Home Assistant then talks to the adapter at the IP / port / slave address above. Set the adapter's serial side to 38400 · 8N1 · unit 160 and make sure it passes the unit ID through to RTU.
⚡RS-485 A/B are low-voltage signal terminals. Never connect them to AC mains. If the terminal labels are unclear, stop and check your device manual.
4
Home Assistant
Install Conow Local with HACS
- Open HACS → Integrations.
- Open the menu and choose Custom repositories.
- Add the repository URL below and choose category Integration.
- Install Conow Local, then restart Home Assistant.
https://github.com/conow-labs/home-assistant-local
5
Configuration
Add the integration
Settings → Devices & services → Add integration → Conow Local
Choose your connection type, then enter the matching values:
| Device name | Anything you like |
| Serial port | /dev/ttyUSB0 |
| Slave address | 160 |
| Baud rate | 38400 |
| Device name | Anything you like |
| Host / IP | e.g. 192.168.1.50 |
| TCP port | 502 |
| Slave address | 160 |
iRunning Home Assistant in Docker? Pass the serial device into the container and enter its path inside the container.
6
You are local
Check your entities and build
Within a few seconds, Home Assistant should show battery, solar, grid and status entities. Add the energy sensors to a dashboard or use controls in an automation.
✓Try unplugging the internet while leaving your LAN running. Your local entities should continue to update.
What appears in Home Assistant
From “what is happening?” to “do this now.”
The integration maps Conow’s Modbus registers into familiar Home Assistant platforms.
See every energy flow
Live power, lifetime energy, voltage, frequency, battery state of charge and cell temperatures.
PV powerGrid importBattery SoC
Know what the system is doing
Binary sensors reveal standby, fault, charging and discharging states at a glance.
ChargingFaultStandby
Set limits and modes
Adjust charge/discharge power, backup reserve, off-grid output, curtailment and forced modes.
Power limitBackup SoCForce charge
Important: local control takes priority
While Home Assistant is actively polling over Modbus, the device follows Modbus commands—not App/cloud targets. Stop polling or disconnect RS-485 to let App/self-consumption control resume. The two paths do not combine.
Troubleshooting
If it does not connect, start here.
Home Assistant says “cannot connect”
Confirm External Control / ModBus RTU is enabled, the device was activated once, the slave address is 160, baud is 38400, and A/B polarity matches the device label.
I cannot find the serial port
Unplug the adapter, list serial devices, plug it back in, then compare. Linux paths are commonly /dev/ttyUSB0 or /dev/ttyACM0; on macOS use /dev/cu.* (prefer /dev/cu.* over /dev/tty.*). In Docker or a VM, also enable USB passthrough.
Values are extremely large or clearly wrong
This usually points to wrong serial settings, wiring noise, an incompatible gateway, or the wrong unit ID. Restore 38400 8N1 and unit 160, then retry with only one Modbus master connected.
App settings no longer affect the device
This is expected while Modbus communication is active. Home Assistant has runtime priority. Disable/reload the integration or disconnect the link when you want cloud/App logic to take control again.
A control changes, then appears to change back
The integration writes, waits 0.3 seconds, and reads the complete register set back. Check that required target power and cutoff SoC values are valid before using force charge or discharge.
Ready to make your energy truly local?
Open source, fully documented, and built for people who like to make things work their way.