I Finally Got Into K’s Basement

EHEIM aquaAlert+e • Home Assistant • Tailscale • SMLIGHT SMHUB Nano

Quick Take: The aquaAlert+e gave K temperature monitoring and aquarium alerts, and it gave me an excuse to put her fish tank in Home Assistant. Installation was straightforward, the open API was the fun part, and six weeks of graphs gave us something interesting to look at. Trusting the water-change guidance has taken longer.

Disclosure: EHEIM provided the aquaAlert+e for review. This article reflects our experience and opinions.

K has a basement.

For most of our three years together, I’ve been allowed to know just that much.

Before this project, I’d been down there once. Was she hiding something or someone? I needed a reason to investigate.

A few months ago, her brother-in-law gave her an aquarium as a thanks for looking after his aquarium long-term while he remolded. She’d been talking about it ever since. Some of the fish even had names. And there were now gurgling sounds coming from somewhere I apparently needed security clearance to visit.

When EHEIM agreed to send an aquaAlert+e, K was excited.

So was I. Aquarium monitoring. Basement access. Double whammy!

K’s aquarium with fish, plants, rounded stones and the aquaAlert+e probe to the right of the green-lit device.
K’s aquarium. The fish finally gave me a reason to go downstairs.

Dinner First, Fish Time Second

The aquaAlert+e measures conductivity and temperature, then uses those readings to provide warnings and water-change guidance. Conductivity measures how easily electricity passes through the water. Dissolved substances affect that number, but it doesn’t identify which substances are present or their individual concentrations.

About six weeks ago, I brought it over. K made dinner while I spent that time figuring out the remote-networking side (more on that later).

After we ate, she led me downstairs.

No major revelations yet. I still have questions.

Installing and calibrating the aquarium hardware took about 15 minutes. K handled the app. The instructions were generally easy to follow, although the app switched back to German at least once, maybe zweimal.

EHEIM aquaAlert+e controller, coiled probe cable, suction mount and clips, calibration solution, power adapter and printed instructions on a table.
The aquaAlert+e kit, with its probe, mounting pieces, calibration solution, power adapter and instructions.

Then, near the end of setup, it asked for a water change.

She’d recently done one. It was 8 p.m. That wasn’t happenin.

A heads-up earlier would have helped. The device also has an initial two-day learning period. Buckle your seat belts.

The Fish Are Eight Miles Away

K could use EHEIM’s app, web interface and status light without any of my additional efforts or skills. She also enabled its warning emails and confirmed they worked.

But she didn’t have a Home Assistant server at the time, and I wanted the readings in mine.

The SMLIGHT SMHUB Nano I’d previously tested gave me somewhere to run Tailscale at her place. With a private route into her network, Home Assistant could reach the EHEIM on her Wi-Fi.

The aquarium uses Wi-Fi. The Nano’s Zigbee radio isn’t involved, it simply runs Tailscale so I can reach her network.

EHEIM supplied REST API documentation. I fed that to ChatGPT and quickly got something I could paste into Home Assistant YAML. The first pass was basic (just the LED light). Later I added more readings and controls.

I also vibe coded a dashboard, because you know… keeping up with the guppies.

Temperature, conductivity, warnings, history, settings. On my computer. On my phone. Fish statistics from another house. I even gave K access.

It took a few tries to get this right, but it was surprisingly little effort. Good documentation and some AI assistance made a project I could have struggled through myself much more approachable.

There’s a reusable YAML example below. Vibe code your own dashboard. We can get downvoted on Reddit together.

Custom Home Assistant aquarium dashboard showing high conductivity, 78.7 degrees Fahrenheit, a 100% pollution index and conductivity of 1,132 microsiemens per centimeter.
An earlier view of my custom Home Assistant dashboard, showing a high-conductivity warning and a 100% pollution index.

Okay, But What Do These Numbers Mean?

That was our next question. I even emailed EHEIM asking what I was supposed to do with all this information.

Their explanation was that water changes should follow the aquarium’s actual data rather than just a calendar. Sensible enough. Justifying another water change so soon was harder.

K put it well:

“I think the temp monitoring is the most helpful.”

And:

“The water quality alerts don’t mean much to me, but that could be a result of me not really knowing much about fish tanks and the terminology/vocabulary.”

Three days ago, she replaced roughly a third to half the water, about 10–15 gallons. She added water treatments but didn’t clean or move the probe, or clean the filter.

Home Assistant recorded conductivity falling from 1,199 to 1,008 µS/cm, about 16%. The drop started before she marked the water change in the app.

That was cool. Something actually happened, and the graph caught it.

The pollution index initially stayed at 100%. K selected “Set reference value now,” and the app said it needed another two days to learn. The newer dashboard shows 10% and no active warnings.

It also says the next water change is in eight days. Earlier, the timer had reset to 30.

Custom Home Assistant aquarium dashboard showing no active warnings, a 10% pollution index, conductivity of 1,043 microsiemens per centimeter and a clear drop in the seven-day conductivity graph.
Custom dashboard, showing no active warnings after the reference was reset. This is my layout in Home Assistant, not EHEIM’s interface.

EHEIM bases its water-change guidance on conductivity, so its recommendations won’t necessarily match the schedule K is used to. We understood what it wanted. Our reaction was more along the lines of, “Already? We just did that.”

Some of that is probably us being stubborn. Changing aquarium water is work, and neither of us has much experience using conductivity to decide when to do it. We wanted information that might change how we care for the tank. Then it suggested changing something, and we looked at it suspiciously.

The reference reset and an aquarium profile that keeps switching itself from “mixed” back to “fish” also make this particular estimate difficult to judge. We're not sure why it keeps changing or whether it affects the recommendations. Eight days seems too soon but we’ll keep watching it. We’re still getting comfortable trusting the recommendation enough to start filling buckets.

Would We Keep It?

K liked the temperature monitoring and looking back through the conductivity graphs. Whether the water-change guidance becomes part of her routine will take more time living with it.

For me, the API is the standout. K gets to use the product normally, while I get to build around it. It was a fun way to bring something she already cared about into my smart home experiments and share in her hobby.

The aquaAlert+e is still relatively new to the U.S. market. If you're interested, you can currently find it at Flowgoby.

Her fish are online. I’ve been downstairs twice.

Progress.

Setup in Home Assistant Example

This is an example based on my setup. It polls the EHEIM API every five minutes for temperature, conductivity, EHEIM’s calculated pollution index, its next-water-change estimate and the water-change alert. It does not include my dashboard or controls.

  1. Make sure Home Assistant can reach the EHEIM API. If they are on the same network, you don’t need Tailscale. My two-house setup needs a route to the remote LAN.
  2. Back up your configuration. Create a packages folder inside your Home Assistant configuration directory and save the full package below as packages/eheim.yaml.
  3. Enable packages using the first code panel. If you already have a homeassistant: section, add the packages: line inside it. Don’t create a second homeassistant: section or replace an existing packages setup.
  4. Add the four example entries to your existing secrets.yaml, replacing the URL, aquarium device MAC, password and display name with your own. Use the appropriate API/master address for your EHEIM setup. The username is api unless you changed it.
  5. Check the configuration, then restart Home Assistant for the initial setup.
1. configuration.yaml — enable packages
homeassistant:
  packages: !include_dir_named packages
2. secrets.yaml — replace these example values
# Example entries to add to your own /config/secrets.yaml
# Replace the EXAMPLE values below; do not publish your real secrets.yaml.

# For IPv4: http://192.168.1.50/api/aquaalert
# For IPv6: http://[YOUR_DEVICE_IPV6]/api/aquaalert
eheim_aquaalert_url: 'http://192.168.1.50/api/aquaalert'
eheim_device_id: 'AA:BB:CC:DD:EE:FF'  # EHEIM device ID (the API's `to` parameter)
eheim_api_password: 'REPLACE_WITH_YOUR_API_PASSWORD'
eheim_tank_name: 'Living Room Aquarium'
3. packages/eheim.yaml — full package
# EHEIM aquaAlert+e — Home Assistant package (shareable example)
# Save as /config/packages/eheim.yaml
# Configure the four values shown in eheim_secrets_example.yaml.
# Read-only example: polls measurements; does not modify device settings.

rest:
  - resource: !secret eheim_aquaalert_url
    authentication: basic
    username: api
    password: !secret eheim_api_password
    params:
      to: !secret eheim_device_id
    headers:
      Accept: application/json
    scan_interval: 300
    timeout: 15

    sensor:
      - name: !secret eheim_tank_name
        unique_id: eheim_example_tank_status
        icon: mdi:fishbowl
        value_template: >-
          {% if value_json is mapping and is_number(value_json.get('alertState')) %}
            Connected
          {% else %}
            {{ none }}
          {% endif %}
        availability: >-
          {{ value_json is mapping and is_number(value_json.get('alertState')) }}
        json_attributes:
          - alertState
          - alertMails

      - name: EHEIM Temperature
        unique_id: eheim_example_temperature
        device_class: temperature
        state_class: measurement
        unit_of_measurement: '°F'
        value_template: >-
          {% if value_json is mapping and is_number(value_json.get('isTemperature'))
                and value_json.get('mUnit') in [0, 1] %}
            {% set raw = (value_json.isTemperature | float) / 10 %}
            {{ (raw if (value_json.mUnit | int) == 1 else (raw * 9 / 5 + 32)) | round(1) }}
          {% else %}
            {{ none }}
          {% endif %}
        availability: >-
          {{ value_json is mapping and is_number(value_json.get('isTemperature'))
             and value_json.get('mUnit') in [0, 1] }}

      - name: EHEIM Conductivity
        unique_id: eheim_example_conductivity
        state_class: measurement
        unit_of_measurement: 'µS/cm'
        icon: mdi:water-percent
        value_template: >-
          {% if value_json is mapping and is_number(value_json.get('isConductance')) %}
            {{ value_json.isConductance | float | round(0) }}
          {% else %}
            {{ none }}
          {% endif %}
        availability: >-
          {{ value_json is mapping and is_number(value_json.get('isConductance')) }}

      # EHEIM calculated index, not a direct test for individual pollutants.
      - name: EHEIM Water Pollution
        unique_id: eheim_example_water_pollution
        state_class: measurement
        unit_of_measurement: '%'
        icon: mdi:waves-arrow-up
        value_template: >-
          {% if value_json is mapping and is_number(value_json.get('waterPollutionLevel')) %}
            {{ value_json.waterPollutionLevel | int }}
          {% else %}
            {{ none }}
          {% endif %}
        availability: >-
          {{ value_json is mapping and is_number(value_json.get('waterPollutionLevel')) }}

      - name: EHEIM Estimated Next Water Change
        unique_id: eheim_example_next_water_change
        unit_of_measurement: d
        icon: mdi:water-sync
        value_template: >-
          {% if value_json is mapping and is_number(value_json.get('serviceTimeWaterChange')) %}
            {{ value_json.serviceTimeWaterChange | int }}
          {% else %}
            {{ none }}
          {% endif %}
        availability: >-
          {{ value_json is mapping and is_number(value_json.get('serviceTimeWaterChange')) }}

    # This exposes only the water-change alert (bit 0), not every alarm.
    binary_sensor:
      - name: EHEIM Water Change Alert
        unique_id: eheim_example_water_change_alert
        device_class: problem
        value_template: >-
          {% if value_json is mapping and is_number(value_json.get('alertState')) %}
            {{ ((value_json.alertState | int) | bitwise_and(1)) != 0 }}
          {% else %}
            {{ none }}
          {% endif %}
        availability: >-
          {{ value_json is mapping and is_number(value_json.get('alertState')) }}

Comments