Apex Fusion (Local) – Neptune Apex LAN integration

Share your Projects! Custom Integrations
1

Hi everyone — I’m looking for testers for a Work-In-Progress custom integration: Apex Fusion (Local).

This integration talks directly to a Neptune Apex aquarium controller over your LAN. It does not use Apex Fusion cloud and is not affiliated with Neptune Systems.

Project link

Inspiration

If you’ve tried other Apex options and found gaps (cloud dependence, stale support, or missing local REST/module support), I’d love feedback on what you need—this project aims to close those gaps with a local-first approach.

Contributors are welcome (issues, testing feedback, and PRs).

What it does

  • Local polling on your LAN (REST-first with legacy/CGI fallback)

  • UI config flow setup

  • Probe/input sensors (Temp, pH, Cond, etc.)

  • Digital inputs as binary sensors (leak/float switches, etc.)

  • Output control via 3-way select entities (Off / Auto / On) using the local REST API

  • Firmware update entities (informational only; does not install updates)

  • Trident support (entities created only when a Trident module is detected)

  • Trident reagent/waste levels in mL (controller-reported data)

Important notes

  • This is an early release only tested by myself: expect changes.

  • Best practice is to use a dedicated Apex account for Home Assistant if you also use the local Apex web UI, since multiple local sessions using the same account can conflict.

  • If you run more than one HA instance / local integration against the same controller, use separate Apex accounts for each.

  • HACS support is planned later once this has more testing time.

What I’m currently testing

As of 2026-01-31, I actively run this integration against:

  • Controller type: AC6J (A3 Apex Jr)

  • Firmware: 5.12J_CA25

  • APIs available: REST (/rest/*) is expected; legacy CGI endpoints (/cgi-bin/status.*) may also be present and are used only as fallback

  • Modules observed via REST:

  • FMM (Software Version: 24)

  • EB832 (Software Version: 8)

  • MXM (Software Version: 1)

  • Trident ACM (TRI) (Software Version: 23)

  • Trident NP (TNP) (Software Version: 54)

  • PM2 (Software Version: 3)

  • VDM (Software Version: 13)

What I’m looking to test

  1. Different controller models / firmware versions

  2. REST-capable vs legacy-only controllers

  3. Module discovery and entity creation (Trident / FMM / VDM / PMx / MXM, etc.)

  4. Output control reliability (select entities)

  5. Any missing/odd entities, incorrect units, or update interval/backoff issues

How to install (HACS custom)

  1. HACS → Integrations → 3-dot menu → Custom repositories

  2. Add this repository URL as Integration

    https://github.com/roblandry/apex-fusion-home-assistant

  3. Install Apex Fusion (Local)

  4. Restart Home Assistant

If you hit issues, please include

  • Controller model + firmware version

  • Whether http://<apex>/rest/status works on your controller

  • A snippet of Home Assistant logs around the issue (with integration debug enabled)

  • If possible, a redacted dump of relevant endpoints (I can provide a helper script / instructions)

Enable debug logging:


logger:

default: info

logs:

custom_components.apex_fusion: debug

Thanks in advance — feedback from different setups will help stabilize this quickly.

2

I just installed this because I’m looking to track my remaining quantity of dosing liquid on my DDR.

When I installed it, my overflow sensors weren’t listed as sensors and I couldn’t see how to access the information around dosing and remaining quantity.

A2 Apex
5.12 CA25

3

If you could run this script on the ip address of your apex, I could get the necessary data to implement the dos and any other devices you have that I do not. It outputs to a .dev directory (optionally can use --out-dir to change). Please zip it up and attach to an issue in the repo.

Note: the script attempts to redact all potentially sensitive data.

python3 apex_dev.py dump --username admin --password 12345 --ip YOURIP

4

Sent you a PM