@Borgs my Helo have no 230v outlet 
will test the new version later today
Thanks for the verification!
Then the new v5.4.1 should sort out the issue you saw.
Actually I didn’t know that there was HALO chargers without the 220v outlet.
In addition a v5.4.2 TEST was just released to hide 220v info in the App if the HALO charger doesn’t have a 220v outlet. (Flowcards can unfortunately not be hidden)
Hi, you’re welcome.
Yes, the Halo 1-phase 7.4 kW does not have a 230V outlet.
I am currently on version 5.4.2, and when I open the device, I see the following error:
It seems to work, but I haven’t tested every option yet (and you added a lot of them 
).
Request:
Could the device price number show more decimal places? Right now, the price is limited to 2 decimals, but with a dynamic energy contract, prices can vary and may require more digits.
And the dashboard widget looks cool, but some free spaces:
@Steven_Bareman greate feedback! Highly appreciated!
so you see the similar error message as before but now it goes away rather quickly and then everything works ok?
regarding more decimals, I will add to my todo list and change it in a coming release.
Regarding widget, that “free space” could be filled with more graphical data during an active charging session. If no charging is ongoing it will be empty. But will see if I can make it a bit more dynamic.
That is because you don’t have an ongoing charging session 
When a charging session is active more data will be displayed just as it does in the screenshot shared by Steve_Bareman.
But I will se if I can make it more dynamic in size, small when no charging is ongoing and larger when charging is ongoing.
New TEST version released, version 5.4.3
Changelog:
- HALO without a 220 V outlet: no more brief \“Connector data may be outdated\” info message on app open.
- Electricity price and widget session cost now show three decimal places.
- Dashboard widget default height reduced to 350 px (still grows when charging controls need more space)."
@Swe Thanks for the screenshot.
Size of the Widget have been reduced in v5.4.3 (TEST) that are available now.
To everyone that are testing the TEST version
Highly appreciate all your effort in this, your input are truly valuable and highly appreciated!
But I have some requests:
- Highly important to get information about what is not working. But almost as important are to know what is working. So if you have time please report back on things you have tested (could be simple things as Start/Stop, Led Ring intensity, Different flowcharts you used etc. etc.)
- Another valuable feedback would be if you in your ChargeAmps device “Advanced settings” would change Debuglevel to “Full” and then in the ChargeAmps App setting would initiate a “create diagnostic report”. In the Text field just write what Charger model you have. And this you could do from time to time (but once a day is enough) even if you don’t have an issue, log feedback is valuable from a development perspective. (You don’t need to send me the report number, I see the report in the development tools and get notifications when new reports are available.
I sent you some new logs. For now it was actually failing with some things, but I will try to send successful logs in the future also. One problem was that the cable lock button didn’t work one other problem was that the Charging button didn’t just stop the current charging session, it did instead turn off the charger completely - i.e. it was behaving just as the Activate-inactivate button does. Same applies for the Stop button in the widget, it turned off the charger. You have both these scenarios in your logs.
@Swe I hope the initial problems you reported are fixed in the below release. But you will need to do some extra config in ChargeAmps user portal and also in my App. (See below guide)
@Steven_Bareman Thanks for your logs, appreciated, could you please change debug level from Normal to Trace for future logs (Done in device settings)
@Goliath Are the issues you reported earlier solved now?
New TEST version published v5.4.5
Change Log:
- First attempt to try to solve a “Cable Lock” issue reported
- First attempt to try to solve a “Start/Stop charging” issue reported
IMPORTANT Information about the “Start/Stop Charging”
If the charger is running CAPI (old ChargeAmps code version) then everything should work as expected even before this fix. In CAPI you just turn the charging port on/off.
But ChargeAmps are moving towards OCPP (industry standard) and here everything is handled in a totally other way when it comes to start/stop charging. There is still an option to turn the charging port on/off, but that normally does not start a charging session. The charger also needs a “start charging” command and a “stop charging”.
But doing this in code isn’t straight forward, the way ChargeAmps implemented this RFID needs to be enabled to issue the Start/Stop command. In normal commercial implementations of this it is possible to create a RFID in code and use that for this, but that is not possible for me. So to be able to do start/stop of charing if your charger runs OCPP code you need to follow this guide:
- Go to ChargeAmps user portal ( My Charge Space )
- Login with your ChargeAmps account
- Go to the “Profile” page
- In the RFID-taggs section:
- Enter a 8 character long hex code (allowed character are 0-9 and A-F)
- Example: 1A2B3C4D
- Enter Homey in the comment box
- Press “Update”
- If you don’t get an successful response try a different code until it accepts it.
- Enter a 8 character long hex code (allowed character are 0-9 and A-F)
- Copy/remember the code you entered
- Go to your ChargeAmps device in your Homey
- Go to Settings page in the device
- Go to Advanced settings
- Go into “RFID for start/stop charging (OCPP)”
- Enter the exact same code as you did in the ChargeAmps user portal
- Go back
- Press save
In theory start/stop should now work This is unknown areas for me and this implementation truly beta testing area. I am not sure that this will work and unfortunately Im a bit lost if it doesn’t work. 
What the App does now when starting charging:
- enables RFID
- Issues a “Start charging” command with the RFID code you put in
- and once the charging is completed issues a “Stop charging” command
- disables RFID
If this work I will look at options to use existing/registerd RFID which can be useful for users that uses the RFID support in the charger to do things.
Hi!
unfortunately I have not been home during these days but looking on your latest release I can tell that the first issue is fixed! The second one I need to be at home to find out! I will get back to you soon!
[edit] I asked my fiancee to verify everything, and it looks like you’ve resolved both issues. Thank you very much for the work you’ve done, it’s greatly appreciated. It now feels like the implementation is fully complete.
Thank you for your and your fiancées test and verification. Good to hear that my fixes did what they intended to do.
I am on the other hand still a bit worried about the start/stop implementation for OCPP chargers, it is a complicated issue to sort out and as I can’t test anything myself it becomes even more challenging. If my implementation for this doesn’t work I don’t know how (or even if possible) to solve it.
So it is with mixed feelings I am looking forward to test reports regarding the start/stop implementation for OCPP chargers…….
For the record, my Halo OCP charger works fine with the on and off function from Homey 
@Steven_Bareman greate news!
Just to verify, is this with the latest version 5.4.5 and that you followed my guide to setup an RFID in ChargeAmps user portal and entering the same RFID in my App?
Yes, this is with this version, only i don’t use RFID. Is this a must to test?
RFID is not a must, but for most reliable functionality following my Guide above would be recommended (if the solution work which I don’t know yet).
@Steven_Bareman You are not required to use RFID, I can see in the loggs that you control the charger with turing On / Off the charging port. That is how you normally controlled a CAPI charger. But with OCPP they changed things, you can still do On/Off of the Charging port. But the new standard adds an additional layer of control where you can Start/Stop the actual charging.
If you’ve used the app before with CAPI, On/Off feels familiar — and it still works. But on OCPP there is a better way for day-to-day use.
Why use Start/Stop instead of On/Off?
-
Port stays ready — After you stop charging, the port remains On. You can start again without toggling the port. With On/Off, stopping often means turning the whole port off.
-
Pause without “shutting down” the charger — Stop the session when you want to pause; the charger stays available for the next start.
-
Better for smart charging / cheap hours — Typical pattern: keep the port On, plug in the car, then use Start when you want charging (e.g. at night). Stop when you’re done — without disabling the port. (But for this RFID must be active, otherwise the charging will start automatically when the car is connected)
-
Clearer in the app — The Energy tab Start/Stop and the Flow cards “Turn on/off charging” are built for OCPP sessions. On/Off on the device panel is only for enabling/disabling the port.
-
RFID handling — Start/Stop uses the app’s remote start (you need to configure RFID in both ‘ChargeAmps user Portal’ and in my App). On/Off does not use RemoteStart; charging may start automatically when the car is plugged in and the port is On (plug-and-charge), depending on your charger setup.
Simple recommendation for OCPP
- On/Off — use when you want the charger port enabled or disabled for a longer period.
- Start/Stop — use for daily charging (Energy tab, widget, or Flow).
Your logs show you’re using On/Off — that works. Trying Start/Stop with buttons (or Flow cards) is the OCPP-native way and usually gives smoother control.
But…..
So far I am not sure that the “OCCP way of operating” works in my App. The Start/Stop control is difficult to control in code and requires RFID configuration in both ‘CargeAmps user portal’ and in my App. It does not require you to use RFID, but RFID needs to be configured and then the App will take care of RFID control during Start/Stop.
Have you been able to test the latest TEST version?
Would be good to know if the two problem that you reported are solved or not:
- Cable Lock issues
- “Stop” charging but not turning the port completely Off.
(Please not that for best possibilities for my fix to work for #2 you should follow my Guide a few posts up.)
Hi,
I’m using the latest TEST version v5.4.5. I’ve tried the cable lock and now it’s working as intended!
I haven’t been able to try the Stop charging feature yet. Also, when reading your RFID instructions I feel that this is quite complex and not optimal, so I’m not sure if I would want to use it in that way. I totally understand that you have very limited control both due to being unable to test and that you are limited to their API implementation. One interesting fact is that I’m also using Tibber and they have an integration to ChargeAmps to stop/start my charging session which doesn’t require any RFID (that’s the one I’m mainly using for start/stop atm).
I do remember Tibber earlier mentioned some limitation that you weren’t able to use RFID with their integration, but now I don’t see those instructions anymore so I guess they have fixed that as well. But I never had to input any RFID myself at least, so that should mean there is a way to start/stop without RFID?
Edit: I was reading your post to quickly, I see now that you mentioned that commercial implementations can achieve this differently.
Lastly, if I could add a request I would appreciate if it’s possible to change the behaviour when single tapping the device in the Homey app. Now that means turning off the charger completely which I never have a need to do. Instead this is something that both me and others in the household might do unintentionally when trying to open the device settings, so it would be nice if you could use the ”long press”-message as seen below instead. I have this on some of my other devices in Homey where it’s not needed to turn it on/off easily.
