Events & Timeline (History, Charts, Logs)

Reading time: ~8 minutes ยท Execution time: none (this is a consultation page) ยท Audience: anyone who has the portal configured and wants to "see what happened" to the tank

๐ŸŸก Important Guide โ€” a consultation page. You don't "configure" anything here: this is where you go to read and diagnose. Everything you do on other pages produces events here.


1. What the Events page is for

The Events page is your tank's black box: everything significant that happens is recorded here, in chronological order, with a severity level and a category label. Examples:

On the same page, you can also see charts for the last 24h / 7d / 30d of the main metrics: temperature, levels, ATO activity, and plug status. Together with the timeline, they provide the "what was happening when" picture.

Typical use cases:

In this guide, we will see how to read and filter the information on the page.


2. Open the Events page

From the JoyReef portal:

  1. Left menu โ†’ "Events" (timeline icon ๐Ÿ“‹)
  2. Or go to portal.joy-reef.com/events

The "Events" page of the primary tank opens.

If an orange banner "Tank not selected" appears โ†’ primary tank missing (guide 04).

The page is divided into 2 main sections:

Plus, potentially, an alert banner at the top if there is an active emergency (e.g., "ATO in fault" with a "Reactivate ATO" button).

๐Ÿ“ท PLACEHOLDER-EVENTS-PAGE-OVERVIEW

๐Ÿ–ผ๏ธ Image to insert here (Events page overview): general screenshot of the page with the ATO banner (if active), the charts section, and the events list below.


3. "ATO in fault" Banner (when it appears)

When the ATO goes into fault for any reason (see guide 06), an amber banner appears at the top of the Events page with:

Clicking "Reactivate ATO"

By clicking the button:

  1. You will see "Reactivating..." for a few seconds.
  2. The portal sends a command to the controller to unlock the ATO.
  3. A green confirmation banner: "ATO reactivated. Waiting for controller update..."
  4. The amber banner disappears when the controller confirms the new state (~10-30 sec).

โš ๏ธ Do not unlock without understanding why: see guide 06 sec. 9 for possible causes. Unlocking blindly can lead to a second fault very quickly (= more RO water in the tank = salinity imbalance).


4. "History and Charts" Section

Time Range Selection

At the top right of the section, you find 3 buttons:

Click to change the period shown in the charts. The filter also applies to the events list below.

Temperature Chart

Shows the tank temperature in the selected range. Typically you see:

What to look for:

Levels Chart (Average ON)

Shows the tank float sensors as 0-1 values:

What to look for:

ATO Active Chart

Shows when the ATO topped up: short vertical bars (= seconds/minutes of delivery). What to look for:

Plugs Chart

Shows the last known state for each smart plug. Rather than a continuous chart, it is a "who is on now" summary. Useful for confirming everything is in the state you expect (heater running, skimmer ON, etc.).

๐Ÿ“ท PLACEHOLDER-EVENTS-CHARTS

๐Ÿ–ผ๏ธ Image to insert here (Charts section): screenshot of the History and Charts section with the "7 days" range selected and the 4 charts visible (temperature, levels, ATO, plugs).


5. "Events and Logs" Section

Chronological list of events for the selected period (same range as the charts above).

Category Filters

Below the title, you find 5 filter buttons:

Filter Shows
All All events without distinction
Sensors Events related to probes (anomalous reading, probe offline, calibration performed)
Automations Events related to ATO, temperature, water change, reactor, etc. (start/stop/fault)
Plugs Events related to smart plugs (on/off, offline, consumption alert)
Errors ONLY Warning, Alarm, or Emergency level events (excludes OK)

๐Ÿ’ก For quick diagnosis: click "Errors" immediately and see if anything is wrong. If the list is empty โ†’ everything is ok. If there's something โ†’ read what happened.

Structure of an Event

Each event in the list shows:

[โ—] [LEVEL] [category-icon] Event Title
                            Detail (longer description)
                            Category ยท relative timestamp (e.g., "5 minutes ago")

Real example:

๐ŸŸข OK ๐Ÿ’ง Plug "Heater" turned on
            State changed from OFF
            Plugs ยท 2 hours ago
๐ŸŸ  Warning ๐ŸŒก๏ธ Temperature probe stuck
            Same value (25.3ยฐC) for 35 minutes
            Sensors ยท 35 minutes ago
๐Ÿ”ด Alarm โšก ATO in fault: max_dose
            Pump on for 180s without level recovery
            Automations ยท 1 hour ago

Levels (color of the dot + left border)

Level Color Meaning
OK ๐ŸŸข Green Informational event, everything normal. E.g., "ATO topped up 30s"
Warning ๐ŸŸ  Orange Minor anomaly, to be monitored but not urgent. E.g., "Probe not updating for 5 min"
Alarm ๐Ÿ”ด Red Problem to be solved as soon as possible. E.g., "ATO in fault"
Emergency โšซ Black/Dark Red Immediate danger to the tank. E.g., "Return pump stopped > 5 min"

"Clear" Button

At the top right of the section, you find a "Clear" button (trash icon).

โš ๏ธ Attention: clicking "Clear" deletes all tank events and logs irreversibly. A confirmation "Do you want to delete all tank events and logs?" will appear. Use it only if you know what you are doing (e.g., end of debugging, end of noisy initial setup, starting fresh).

Charts are NOT deleted: they are based on different, persistent metric tables.

Pagination

If there are many events, you will see "Showing 1-50 of 234" at the bottom with arrows to navigate the pages.

๐Ÿ“ท PLACEHOLDER-EVENTS-LIST

๐Ÿ–ผ๏ธ Image to insert here (Events list with filters): screenshot of the "Events and Logs" section with the "Errors" filter active, list with 3-4 Warning/Alarm type events visible.


6. Common Patterns โ€” What to look for when

"I have the impression something is wrong but I don't know what"

  1. Open /events
  2. Filter "Errors"
  3. Range "7 days"
  4. Read from the top (most recent)

If you find recurring patterns (e.g., "ATO in fault" every 2 days, "probe stuck" occasionally), there is a systemic problem to investigate.

"Temperature was strange this morning"

  1. Open /events
  2. Range "24h"
  3. Look at the Temperature chart: where is the deviation?
  4. Scroll the events list to the corresponding time.
  5. Search for events like: "Heater on/off," "Probe anomaly," "Maintenance mode activated."

"The ATO is not topping up"

  1. Range "7 days"
  2. Look at the ATO Active chart: do you see vertical bars? - No bars โ†’ ATO is not starting. Filter "Automations" and search for "ATO deactivated" or "ATO in fault." - Normal bars โ†’ ATO is starting but maybe it's not enough (water level continues to drop, anomalous evaporation).
  3. Filter "Sensors" โ†’ check if the ATO level sensor is active or has strange patterns.

"What is the weekly energy consumption?"

You can find this in the plugs chart or on the specific Energy & Health page (see guide 13), not on the events page. Here you see only the current state + specific state changes.

"Was there a blackout? For how long?"

  1. Range "24h" (or "7 days" for older blackouts)
  2. Filter "Sensors"
  3. Search for events like "Controller offline" / "Controller online" with close timestamps = that's the blackout.
  4. Duration: the difference between the two timestamps.

7. Current limitations of the page

Things the page does not do yet (useful to know so you don't look for them in vain):


8. If something goes wrong

The list is empty even though I know things are happening

I see events but they are all old (nothing recent)

Events seem duplicated (same event multiple times in a row)

This happens for states that change rapidly (e.g., a float that oscillates slightly and activates/deactivates the ATO every 2 min). It's not a bug of the page; it's a behavior to analyze:

The "ATO in fault" banner doesn't disappear after "Reactivate"


9. Next step

You have explored the events page. To receive notifications of serious problems without having to check manually, configure the notifications:

โžก๏ธ Guide 15 โ€” Email/Push Notifications

๐Ÿ’ก Recommended routine: every morning open /events, filter "Errors," range "24h." 30 seconds that tell you if the night went smoothly. For those who want full automation: configure email notifications (guide 15) and receive alerts even without opening the portal.