Testing the ADA485 device with a battery

This is a huge advantage in household energy storage, where the user needs to monitor not just production and consumption, but also battery health.

How does it work?

The key to the ADA485 is protocol management. The .485 file uploaded to the LittleFS file system contains the BMS or meter protocol. This is encrypted onto the device, and the firmware decodes and loads it. Thus:

• no firmware update is required for new device support,

• downloading and activating the appropriate protocol file is sufficient,

• endpoints are automatically built based on the protocol fields.

Available endpoints

The device runs a built-in JSON server on port 8989 and offers numerous API endpoints:

• GET /protocol/raw → the raw, last processed frame

• GET /protocol/schema → schema of the protocol's fields (id, name, unit)

• GET /protocol/values → current processed data in JSON

• POST /protocol/load → download and activate a new protocol from the greenhess firmware server

• GET /protocol/current → metadata of the currently used protocol

• POST /protocol/erase → delete protocol file from LittleFS

• GET /protocol/info → decoded metadata (product_name, manufacturer, model, type, etc.)

Additional endpoints:

• GET /json → quick access to cached data

• GET /time → synchronized time (UNIX, ISO, short timestamp)

• POST /write → manual data writing (e.g. for testing, demo)

• GET /restart → restart the device

• GET /factoryreset → factory reset and erase EEPROM

MQTT integration

The ADA485 also publishes all data via MQTT, typically under the following topics:

• ada485/ → live measured data in JSON format

• ada/cmd/ → remote commands (e.g. restart, load protocol)

• ada/ack/ → responses / ACKs for commands

Supported MQTT commands include:

• op: "restart" → restart the device

• op: "factory-reset" → erase EEPROM and restart

• op: "getraw" → retrieve raw frame via MQTT

• op: "load-protocol" → download and activate protocol remotely

This means that the ADA485 is not only a data source but also a controllable IoT endpoint, which, similar to a P1 Meter, can be programmed remotely.

Battery test

The screenshots show that the system displays in real time:

• the minimum, maximum, and difference values of cell voltages,

• the temperature sensors (MOSFET, BMS, environment),

• SOC and cycle count status,

• as well as the aggregated charge-discharge kWh data.

The HMKE.app interface visualizes these in daily, weekly, monthly, and yearly breakdowns, giving the user a complete picture of their battery’s operation.

Why is it important?

Energy storage systems operate effectively only when they are not used as "black boxes" but when precise data about their internal state is available. Through the ADA485, the battery can be remotely controlled over the local network and MQTT, integrated into smart home systems, or even aggregator centers.

This is the first step toward the ADA485 becoming not just an inverter and meter, but a comprehensive energy management gateway.