Caruna

A connected Caruna Oy customer account - a Finnish electricity DISTRIBUTION network operator (not a retailer like Helen), reporting your own electricity consumption as read-only sensors - logged in with the same Caruna Plus email address and password you already use on Caruna's own website or app.

Connecting

Devices & Services > Caruna > "+ Add account" asks for your Caruna Plus (plus.caruna.fi) email address and password directly - there's no OAuth consent screen or app credentials to create, since Caruna has no public API for this; Athena logs in the same way the website itself does.

Entities

Four read-only sensors, in kWh: today_consumption, yesterday_consumption, month_consumption, and daily_consumption (today's own total again, but the one sensor "Backfill history" below writes historical rows against, so a Chart or Statistics card following it shows a continuous series instead of only what's accumulated since the account was connected). Consumption is metered and reported by Caruna at most a few times a day, so a background loop checks for new numbers every 3 hours rather than polling constantly. Works with Dashboard cards, History, and Automations exactly like every other integration - there's nothing to control, so it never appears as an Action node target, only as a state source.

Backfill history

The account's own Consumption card menu has a "Backfill history" action - pick a start date (up to 365 days back) and Athena fetches your daily consumption straight from Caruna for that whole range, adding it as history for daily_consumption. Days already covered by existing history are skipped automatically, so running it again (or extending the range later) never double-counts a day.

This isn't a public, documented Caruna API - it's a real (if unofficial) browser-login flow, reverse-engineered against Caruna Plus. If Caruna ever changes their login page, this integration may need updating before it works again. Also worth knowing: at least one existing community project built on this same reverse-engineered API has reported occasional implausibly large consumption readings - Athena defensively drops any single hourly reading over 100 kWh (far beyond what a real residential connection's fuse size allows) rather than trusting it outright, but if your own numbers still look off, that's a known open question with this API, not necessarily an Athena bug.