So far I can add the device from a local network and use homey to read it’s values:
Now I want to take the next step, actually setting values through homey.
I’m puzzled though on how to do this. Is there a simple example available somewhere? The dev documentation is a little cryptic for a starter like me. Which app would you recommend for me to review the code of, to learn from?
Have you advanced with this app? The go-e charger specs look very tempting. Have you been able to add action to change the charge current? This way one could limit the charging for example according to household intake current or solar power generation etc.
Sorry for not been able to help, but I’m very interested with this device and your app.
Thanks for the encouragement, always nice to know there’s an interest.
I think it’s more of a time limitation than the difficulty which is holding me back at the moment. Also, I do understand the API of the go-e-charger but not so much the way I have to match the values to flow cards in Homey…? But I’m sure I’ll figure it out in the next month or so.
I’m considering two options for setting the charge current:
A. set an actual Aperage value
B. choose one of the five presets as set in the Go-e Charger app.
The former (option A) will give Homey more control, but also is more difficult to make as it has to be a value between the Max Amp as set in the go-e-charger app and the Min value of 6A. The Max Amp as set in the go-e-charger app can vary as per the users setting. If a user fails to match this to wall connection maximum, homey may actually break something / set of the cirquit breaker or worse…
The latter (option B) will give just a little less control for homey but will be easier to implement and will always follow the 5 preset Amps. It also has the benefit that you can move to one setting higher or lower depending on a flow and repeat this - so for instance if the Plugwise P1 notices your house total current use starts to match the total house connection, it can set one lower preset on the go-e-charger. If it still comes close, the flow will be triggered again to lower it once more.
I was first thinking and also have tested a flow where I calculate the “remaining” amperage value that the charger can use in accordance of household intake power (3-phase). So the charger amperage value would be changed according to this value.
But your idea about the 5 preset values could be also used in same way.
So on my point of view there is no actual difference between the choices. Both of them gets the job done.
If you select the preset values, one can still make the mistake that set too large amperage value to the preset value and may trip the circuit breaker, but in any case the user have to know what he/she is doing.
I would suggest that you go with the B option if it is easier to make. Maybe later you can add the A option if someone needs it for some reason.
Couple of questions about the charger:
Is there a limit at which rate can you change the charger amperage value or preset amperage values?
Have you tested how the charged car reacts to the amperate or preset change? Does it work “online”? I mean that one is charging with 6A and then changes it to 10A, does the car change the charging current straight away or do you have to disconnect and reconnect first?
The “Car connected…” trigger will trigger all the time when the car is connected (about every 2 seconds), not only when the car is actually first time connected. Should be fixed.
The “Car connected…” trigger is not triggered when the charging is started straight away when you connect the car. I know that you don’t get this information straight from the charger, but probably can be made in the app? Other option is to rename the trigger into something like “Car connected and waiting for charging permit”.
The “Charging started” trigger seems to work properly. Great!
The “Finished Charging” trigger does not trigger if you manually disconnect the car (unplug) during charging. I know that you don’t get this information straight from the charger, but probably can be made in the app? Other option is to rename the trigger into something like “Finished Charging and car connected”.
The status of the charging (Status integer “car”) is also a little bit off I think. Here are some proposions
a. Status integer value 1 is now “Waiting for connection” in the status page of the device and in the “Device status” tag it’s “Ready to connect car”, these should be at least the same. In my opinion it should be something like “Car not connected”
b. Status integer value 2 is pretty much ok. It can also be “Car connected, charging”
c. Status integer value 3 is now “Communicatin with car…” in the status page of the device and in the “Device status” tag it’s “Car connected, waiting for car data”, these should be at least the same. In my opinion it should be something like “Car connected, charging not allowed”
d. Status integer value 4 is pretty much ok. It can also be “Car connected, charging finished”
Can you make all the charger measurement available also in insights?
Thanks again for the good work, it’s going to the right direction.
This one is difficult. I will have to look into this, in accordance with 5c. The suggestion “Car connected, charging not allowed” is not correct, as this status (3) actually means the charger and car are getting ready to start the charging and are communication the charging parameters. I think i will rename to “Getting ready to start charging”.
I noticed the same so that is good to know!
This raises the question: Should unplugging manually, fire this trigger? Maybe another trigger should be there, ‘charging terminated’ (meaning the charging has stopped for a number of reasons, including unplugging). Personally I would want to use ‘Finished Charging’ only for when the car is finished charging (100%) or the max session kWh is reached. Termination of the charging (Charging terminated) could then be used for other use cases and will be tiggered if status value ‘2’ changes to any other status value. If charging’s finished and the car is disconnected within the 5 seconds it takes to update the valueof status to “charging finished”, I don’t have enough info to trigger this status. My BMW i3 gives a ‘charging finised’ signal to the charger every time I unlock the car so that this status will almost alway be triggered. I’m not sure if this goes for every EV.
a. I will change this to : “No car connected” everywhere.
b. I will keep this “Charging”. I will see if there is another value to be created which is “Car connected” and is set to YES for status 2, 3 and 4 and to NO for status 1.
c. Like i said at #2, I think i will rename to “Getting ready to start charging”.
d. I will keep this “Charging finished” and try to make another boolean which monitors if a car is connected.
I will look into this.
Many thanks for doing tests! This is valuable information for further developing the app.
You are right about that. Your suggestions sounds good to me.
Another trigger for the “Charging terminated” would be better solution. I have done this with the GET http request card, and made the logic that whenever the value changes from 2->something else the charging is finished, disregarding is the charging actually 100% or not (I don’t care :D)
Every suggestion sound good to me.
I have Opel Ampera which has a one phase charger. The amperage in the device shows the actual amperage divided by three. Can this be fixed somehow? There is a status (hex value “pha”) in the api which could be used. This is not vital thing to do, but to the end of todo list.
Thanks for the update. Can you lighten up what is the situation with the app after the homey store update? I cannot find the app in the store, so do I have to install the app with the github source and CLI or is there some other way to install the beta app?
Apparently I had to have had the app submitted for certification, so it was removed from the app store. I’ve done so again but it failed due to some minor compliancy issues. I’ve fixed the issues in version 0.3.3 which is now under review for certification.
You got the commands for amperage and on/off working! Great work. The one phase amperage measurement value is now also working.
I did some testing and the app is looking great at the moment. I did get rid of most of my API request workaround which I have made in the meanwhile to get the Go-e connected.
I have still couple of suggestions, observations and one bug to report. I will continue the testing and let you know if I find anything.
In conditions, the inverted condition is not working. For example I made the condition “Car not charging”. It is true always when the car is charging, so not inverted. Didn’t test the “charging finished” trigger.
When you have the charging allowed and you connect the car the triggers “car connected” and “charging started” sometimes trigger both (which in my opinion is correct), but sometimes only “charging started” is triggered. I think this might be due to the update frequency of the homey<->Goe, so that you don’t always get the “car connected”. Is there some logic to be done in the app?
Same happens when you disconnect the plug during charging. The “car disconnected” won’t always trigger.
Same happens when the car is connected and the charging is allowed. The “charging allowed” is not always triggered.
And I think all the triggers have the same issues than presented in points 1-3 due to the status handling of the Go-e device.
The points 2-4 are minor nuisance, but if there is a possibility to make some kind of “state machine” inside the app according to the state changes of the Go-e it would be great.
Could you add a trigger for the any “device status” change?
Could you add the total energy measurement to variables so that it can be used to calculate charged energy. I find the “Power supplied in this session” hard to use because when you unplug the car the “power supplied in this session” will go to 0 value. And I want to unplug the car whenever I want
Will make a donation for you for this work! Thanks a lot.
I’ll look into it this weekend. My car was fully charged last time I was working on it so I had no way of testing
You’re right about the update frequency being an issue. The API of the Go-E charger gives all status values at each request and I’ve now setup the update frequency to each 5 seconds. Much faster can’t be done because the charger will stop responding to too many requests.
There already is some logic in the app where it compairs the previous status value with the new status value, I can work this out further to make it function even better. This might also fix the issue I found myself that if you use the homey to ‘activate’ the charger, It won’t detect the status change.
same as for #1, i’ll look into it
that should be easy, there is already the logic.
As regards to the donation: thank you very kindly!