Greate to hear and thanks for the feedback
Thanks for vital feedback of basic functionality!
Highly appreciated!
Pushing v5.0.4 to release as Current version.
A few tips about the current live release (v5.0.4):
This is a ”breaking change” which is not backwards compatible. What you should do when you want to run this version:
- Remove any ChargeAmps devices from your Homey.
- Remove the ChargeAmps app completely from your Homey.
- Install/Reinstall the 5.0.4 version
- Enter your credentials in the App settings (e-mail, password and API token)
- Add your ChargeAmps device in your Homey
- If your ChargeAmps device does not work as expected in Homey I would recomend to do step 1-5 again but this time install the TEST version (currently 5.1.0) which is found below in this post. (Many bugs and issues should been solved in version 5.1.0)
TEST VERSION 5.1.0 Released
This contains a HUGE re-write of the code, there are probably a few bugs in the code. As I don’t have access to a ChargeAmps device my ability to test the code in real world scenarios are limited.
Changelog:
- Fixed (hopefully but not 100% verified 
):
- turning a charger on/off now sends the value the ChargeAmps API expects, so start/stop is reliable;
- remote start/stop now uses the correct API endpoint;
- AURA chargers limited to a single outlet (port 1 or port 2) no longer produce errors or go unavailable;
- the LED ring tile on DAWN/LUNA now works;
- the AURA \“charger on/off\” condition card now evaluates correctly;
- Flows that control a charger now affect the device you picked even when you own several chargers of the same model (previously a Flow could end up only controlling the most recently added one — e.g. the HALO downlight);
- chargers no longer error before any charging session exists;
- the charger is marked unavailable only when ChargeAmps can’t be reached (a network/API error), while a charger the cloud reports as offline keeps showing its last-known values (with a soft warning on the device) instead of going unavailable;
- the energy meter can no longer run backwards on a session change;
- live power is reset to 0 when a charger is off;
- remote start now validates the RFID tag (correct byte length);
- device capabilities and their history are no longer reset on every app restart;
- session energy is no longer reset when the charger reports no phase data;
- the charging schedule (Schedule mode) is kept when you change current/RFID/cable lock;
- remote start without an RFID tag now simply enables charging;
- the settings page no longer pre-fills your saved password/API key;
- charger on/off commands now include the connector id for full API compliance;
- live power is shown immediately at the start of a session (no longer 0 for the first moments) and is correctly reported while charging on a schedule;
- the AURA per-outlet on/off tile now updates instantly when you start/stop from the Energy tab.
- Improved:
- automatic re-login if the API token expires
- large internal cleanup that puts all four chargers on shared, unit-tested code.
Hi @Borgs
I have tested the different options, and everything seems to be working well, so I am very happy with that. 
There is only one small detail regarding the displayed consumption. I recently created a virtual device through a Homey Script to monitor the total consumption. This matches the actual consumption, but your Charge Amps shows a slight deviation. Please see the attached photo.
Thanks for feedback and good to hear that it basically works even if you see some small issues in consumption values. Are you running Live version (5.0.4) or the Test version (5.1.0)?
Is this from a completed charging or when the charging was ongoing?
My app only pulls data from ChargeAmps cloud API on intervals. So if it is from an ongoing charging session that could explain the difference that your script pulls data more frequent.
If it is from a completed charging session I will have to dig in and see if I can find anything in the code. I pull the actual data from ChargeAmps cloud API so it should show correct value once a charging session is completed (or at least maximum 1minute after completion)
I am on the test version (V5.1.0)
I will keep a eye on it for a couple of days and get back to you. 
To everyone that are using this App:
For the current release (5.0.4) I have seen some logs and messages that the App is “broken” after upgrade to v5.0.4 was done, this is not a valid statement.
Please note that this is a “breaking change”, if you just update the App to v5.0.4 your existing ChargeAmp device in the Homey will not work!
You need to at least do the following:
- Remove the ChargeAmps device from your Homey
- Re-enter your credentials (e-mail, password & API token) in the App Settings
- Re-add your ChargeAmps device your Homey
If you have flows configured that includes your existing ChargeAmps app you need to edit them, you don’t need to rebuild your Flows, just replace the ChargeAmps device in your Flow with the new one.
I am happy that this application has been picked up and been adopted. Kudos on that. I will be testing and hopefully provide some feedback.
@Daniel_Lofgren Thanks! If possible please do your tests on the TEST version (v5.1.0). Initial feedback on that version have been positive and it should close many of the issues that exists in the older versions.
I’m also back and now testing your latest changes 5.1.0, looks very good so far! Didn’t you have total for indication of power also? Adding the sum of port 1 and 2? Now only I can see total for kWh
I will continue to test and report back!
And one last thing! Glad that you are back
Thanks for the feedback and kind words.
Will check what has happened with the values you are talking about.
Thanks for testing v5.1.0, as soon as that is released I already have 5.2.0 in pipeline with some new features/functions that I hope can be useful:
Changes planned for upcoming v5.2.0:
- Smart charging via Homey Energy.
- Energy overview (today/week/month/year)
- Timeline notifications
- First simple dashboard widget with start/stop.
- Charge targets Flow cards (i.e. ‘Charge X kWh and then stop charging’
- Session tags on Flow triggers.
- Guided pairing login
- Diagnostics information
- Per-phase currents
- Error notifications
- More robust connectivity.
- … and perhaps something more
Hi @Borgs I mentioned earlier that I would monitor the measurement results for a few days. I still see small differences in the readings via the direct API (through Homey script) and the app. The Charge Amps app itself shows different values as well. Here are the results from several different days:
09-06-2026:
10-06-2026:
13-06-2026:
Wat I understand is that the charge amps app counts from the last connected session but the energy homey app from midnight?
@Steven_Bareman @Frank_van_leeuwen @Daniel_Lofgren
Thanks for all your testing, I will dig into the issue @Steven_Bareman reported in coming versions, its a bit hard to determine what value that actually are correct, especially when there are several different values that should display the same thing.
Don’t know if my App shows an incorrect value or not, the App itself doesn’t ”invent” the Numbers it just collects them from the ChargeAmps API. But not saying that you are wrong @Steven_Bareman , I will dig into this and see if I can find anything.
I don’t want to disregard of the things you have found, they will be addressed. But you have provided vital feedback, the App works and no major problems have been seen so far which is good.
I will push 5.1.0 to publication as it seems stable and basic functionality seem to work as it should. Once that is active I will release a new Test version that contains a lot of new things.
Version 5.1.0 pushed to Release and are now live:
Version 5.3.0 published in TEST and are available here:
Version 5.2.0 was an internal testversion and never published, so a complete ChangeLog between 5.1.0 and 5.3.0 looks like this:
- Smart charging via Homey Energy
- Energy overview (today/week/month/year)
- Timeline notifications
- Dashboard widget with start/stop
- Charge targets
- Session tags on Flow triggers
- Guided pairing login
- Diagnostics
- Per-phase currents
- Error notifications and more robust connectivity.
- More data, more control and a cleaner layout.
- The device panel is now grouped in a logical order (charging state, power, energy, charger/outlet mode, status, kWh, current limit, lights, RFID, energy totals, then per-phase current and voltage) — applied to existing chargers automatically without resetting your energy meter.
- Per-phase voltage sensors
- ‘Now/Last charged’ are now graphable kWh sensors (with Insights history)
- Optional electricity price for session-cost estimates (shown in the widget and added as a ‘Cost’ tag on the ‘Charging completed’ Flow card) (*1 See more below)
- A weekly energy summary to the timeline (opt-in)
- An ‘Identify’ button that “flashes” the LED ring
- A ‘Last error’ / ‘Sessions this year’ / ‘Last session’ line in Diagnostics.
- The dashboard widget gains a charging-current slider, quick charge-target buttons (+1h/+2h/+4h) with time-to-target, a live cost line, and HALO outlet/ground-light toggles.
- The duplicate ‘FW Version’/‘Charger Version’ tiles were removed (firmware and protocol are shown in Diagnostics) — no re-pairing needed.
- Secrets (charger password, access token) can no longer appear in the logs.
- The cumulative energy meter is now reconciled against the charger’s own per-session total when a session ends, so it matches the charger exactly.
- The ‘Identify’ button now pulses the LED ring slowly so it’s visible over the cloud connection, stays disabled while running, and reports clearly when the charger is offline.
- A lot of “under the hood” improvements
- Translation updates
*1) In version 5.4.0 (coming soon in the test channel) I have enhanced the cost parameter. There are three options regarding this:
- In settings on the ChargeAmps device in your homey, set cost to 0 (zero) and the App will not do anything in regards of cost for charging
- In settings on the ChargeAmps device in your homey, set cost to the cost you actually have per kWh. The app will then use this value to calculate costs for charging your car.
- Create a flow that uses an a trigger card from an “Energy cost App” (i.e. Power by the hour, Tibber, etc.). The “trigger” card used should be a “Energyprice has changed” flow card. For the "action" card for this Flow you should use the "action" card from my App named “Set price per kWh to xxxxx”. And use the “tagg” from the trigger card that should contain the cost. This will then update the cost per kWh in the App everytime the price changes.
If #3 is done it will override what you have configured in #2, but the App will use #2 as fallback if #3 doesn’t provide a cost. #3 will also override #1.
If you enable this ‘Cost Parameter’ cost will be included in several places in the App and you could also utilize the new Action Flow Card “Charge for [[amount]], then stop charging”
Hi Borgs,
Really glad that you have restarted your work again keep up with the good work!
Two observations so far on 5.3.0, one is already known by you, it’s the total power [W] for both ports that need to be reported.
Second one is in the energy section. It’s not picking up the consumption while charging.
Thanks for the kind words!
Just a few questions so that I fully understand the issues you see:
- I assume that you have a AURA charger?
- Are your charger running CAPI or OCPP code?
- You want to have a “meter” that show the combined W usage for both ports? In addition to the two “Meters” that already are in the app (one for each port)?
- In “Energy Panel” I am a bit uncertain what you are saying. Could you please elaborate a bit? Do you say that nothing at all of the AURA are shown in the “Energy Panel” or is the AURA there but not showing any values? If something is shown of the AURA in the “Energy Panel” does it show one device? Or does it show two devices (one for each port)?
Sorry I am a bit blind here and can’t see or test anything myself. Your explanations are needed and screenshots would be valuable information.
Think I can fix this but need some help with information
New TEST release published
ChargeAmps v5.4.0 (TEST) — release notes
Builds on 5.3.0. No re-pairing needed. After updating, restart the app once so capability migrations can run (especially on AURA).
New features
Dynamic electricity price
- New Flow action “Set price per kWh” (per charger) — feed the current price from any price app’s price changed token (e.g. Power by the Hour, Tibber) or enter a fixed value.
- Session cost is time-accurate: each kWh is priced at the rate that applied when it was charged.
- Your manual price in device settings remains as fallback when no dynamic price is set.
- New “Electricity price” sensor on the device shows the price currently in effect (dynamic → manual → 0).
Charge by cost
- New Flow action “Charge for a set amount of money, then stop” (all models; AURA has one card per outlet).
- Stops charging once the session has cost the amount you set (requires an electricity price).
- Currency is localised in the card title (kr / € / etc.).
Electricity price in Flow completion
- “Charging completed” now includes a Cost tag when a price is configured (in addition to energy, duration, minutes, RFID).
Energy & session accuracy
- Cumulative meter and today / week / month / year totals are more accurate.
- Completed sessions are reconciled even while the charger is Off.
- Sessions are matched by start time (not “similar kWh”), counted by end time, and not double-counted while API history catches up.
- Year overview paginates beyond 1000 sessions; incomplete totals are flagged in Diagnostics.
- “Charging completed” Flow is more reliable: waits briefly for the session in the API, enriches in the background, fires once per session, skips empty zero-energy completions, and no longer blocks polling.
AURA (dual outlet)
Tester-reported fixes (@Goliath )
- Homey Energy tab should now shows live combined power (W) while charging — AURA reports the sum of both outlets (Homey Energy does not support per-outlet sub-capabilities).
- Device page sensors are regrouped and reordered:
- Power: Outlet 1 → Outlet 2 → Power (total)
- Energy: AURA1 Now Charged → AURA2 Now Charged → Energy (total)
Other AURA improvements
- Start/Stop and smart-charging stop affect only outlets with a connected car or active session.
- Per-outlet completion is tracked independently.
- A fault on one outlet no longer hides charging on the other.
- Widget session cost uses combined outlet energy (matches what you see on the device).
Reliability & robustness (all chargers)
- Unknown connector statuses handled correctly.
- Warnings for stale data, offline, read-only, fault, energy/meter incomplete shown together on the device and in the widget.
- Degraded polls no longer report success.
- Live power is only zeroed when the connector is truly idle (not when the car is still connected but not drawing power).
- Time-based charge targets cancel on disconnect.
- Target charging power uses measured line voltage.
- Protocol (CAPI/OCPP) is restored from device store on startup when the cloud fetch is unavailable.
- OCPP protocol label in Diagnostics persists correctly across restarts.
- Large internal consolidation of energy/session handling for long-term stability.
@Steven_Bareman Thanks for your report.
Have pushed out a new TEST version (v5.4.1) where I try to fix the problem you reported.
Question from me: From what the log tells me it looks to be an issue when trying to get data for the 220V outlet. Have you used the 220v before? Or could it be so that your HALO are a version without 220v outlet or that the 220v outlet are disabled?
