Hi again @Borgen
After the OCPP update what status does then match the “Car connected to charger” card in the flows?
Because the documentation is got from Charge Amps for v.4 api looks like this and there is not “Connected” status in there regarding OCPP:
That have actually puzzled me for a while also 
My charger (HALO) has up until today been CAPI but today it got upgraded to OCPP. Unfortunately it was two days to late Have just sold my Hybrid car and are waiting for the delivery of my new fully electric car (VW ID7 Tourer GTX) but it will take until new year befor it is delivered. So I don’t have the possibility to do any testing what so ever now 
But if someone with knowledge about ChargeAmps API swagger could help me with some different statues I can easily implement correct handling of it in the APP.
What I would need is the Swagger status of the charging port:
I believe I Can support on that. But I need a little more guidance of the procedure. I Will need to test with charge amps api swapper against my car? Or?
@Rune_Bronimo I will send you a PM with instructions.
Have you made your own capability for power/electricity usage?
It does not show up in the app under Energy anymore. But its visible under “Hale: Energy”. Can you please add or use ‘measure_power’ instead? 
Yes, that is correct. I have implemented custom capabilities to get consistency between all the different chargers the App offers.
Currently the development work are focused on sorting out new functionality for communicating with ChargeAmps API, I have a dialog with ChargeAmps on that topic. Once that is sorted out I can revisit this topic and see what I can do
@Borgen
Keep up the good work, this app is very good and used every week, much appreciated. Cheers
New Test version (v4.1.2) has been made available.
News in this release:
Long development/test work have been put in to try to use WebHooks for data collection from ChargeAmps. Have had a lot of e-mail conversations with one of their development managers but unfortunately we was not able to come up with a solution that works.
WebHooks would have made this App even quicker and would also reduce the amount of communication needed between the App and ChargeAmps. But the way that ChargeAmps have implemented WebHooks are not compatible with Homey.
So this release are using the traditional Pull method, but timers have been changed a bit and intelligence in the App have been implemented to only Pull certain information when it is actually needed. This to reduce communication with ChargeAmps cloud services a bit.
Hi Borgen, thanks for creating this app!
I have an Aura, but I’m experiencing some issues:
Any ideas? I’d be happy to help in any way (I’m a software developer).
@Mosb I will contact you in PM
I wonder if any have the api-key to Dawn?
Kind regards Crister
Crister, the API key is individual and tied to your user account at ChargeAmps.
You need to contact ChargeAmps support to get it.
Ok thanks for your help
Kind regards Crister
Hi Borgen, I am interested in buying a Halo for my home. One question, maybe I mist it.
Can I get the consumption Amps per fase in Homey?
I would like to use that information for load balancing with a flow in Homey.
Thanks a lot, Willem
@Borgen Thanks a lot for this app! I have a DAWN charger and I’m currently facing some issues with my car not ”waking up” when the charger starts with smart charging based on spot prices (i.e. the car goes into some kind of sleep mode after a while). Therefore I would like to trigger a flow when the charger is trying to start but the vehicle has not started to actually charge. This shows as ”Paused by EV” in the ChargeAmps mobile app.
Could this be added in the future? Currently, the trigger in flows for when the charging is started only gets triggered after the vehicle actually is accepting it as well.
Best Regards
Borgen,
I have similar problems as mosb, but using a Halo with fw 182, and just got it upgraded by ChargeAmps to 184.
Flows enable the charger, car starts to pull energy, but the status card and triggers does not reflect that.
Very seldom the ”trigger when car is connected” or ”Halo draws more than N kW ” can be used. They do work, but not reliable.
And the status page on the homey device sometimes show current numbers/status, and sometimes not.
Not super nice for optimizing the power peak if I cannot detect the car…
I am currently working on a total rewrite of the “status” handling.
Given that there are two different SW branches for the chargers and that there are a lot of different statuses the chargers can have the code for my App need a rewrite in some parts and I am currently working on that.
First out will be changes for the HALO charger and if it work out well on the model it will be quickly implemented on the other charger models as well.
These are the available statuses for the different SW Versions:
CAPI
0. Available
OCPP
0. Available
CAPI are more simple to handle in the app as it has fewer states and more clear states (has a connected state).
Can someone with a OCPP charger tell me what state the charger is in (Looking in ChargeAmps own standalone App, not the Homey App) if:
In CAPI it changes from Available to Connected. But how does this change in a OCPP charger?
I have a Halo in occp mode, and I have written a bash script I can run on my laptop to query any of the rest API endpoints to debug.
At the moment I have the charger Off, since I want to block charging until 22pm (power rates…)
And the Chargeamps app say ”Charger turned off”.
I am happy to assist with a live debug session, since I am a developer too… just drop me a private message.
…and I thought this was, for OCCP, well defined in the standard?
HALO OCCP mode:
Chargingport/Cable is turned off - REST API say “Unavailable” - Chargeamp say “Charger turned off”.
A car gets connected to the Chargingport/cable - REST API say “Charging” or “SuspendedEV” depending on what I have asked the Tesla to do. The Chargeamp app says basically the same thing.
Do believe that in ChargeAmps own App there are two status rows, at least when the charger is turned off.
Top row says: Not available
Bottom row says Charger turned off
The bottom row is a ChargeAmp implementation and must come from some logic they use when they read the values from OCPP Status.
Top row is a rewrite of the OCPP status message. The actual status message should according to the standard be Unavailable and I guess that they rewrites it to make it more clear.
The really bad thing with OCPP compared to CAPI is that there are now way to determine if a car is actually connected or not if the charging port is in state “Off” then it will always have status “Unavailable” (as far as I understand it). In the CAPI even if the charging port is turned off it can change status from Available to Connected when a car is connected to that charger.
But the thing I would like to have confirmed is:
With the charging port turned off and no car connected to the charger the status is “ Not Available” in Charge Amps own stand-alone App.
But does the status in Charge Amps own stand-alone App change if a car is connected to the charger (with the charging port still being turned off)? Or does it just remain at “Not Avilable”?
