Integration of goe-charger (in local wifi)

Share your Projects!
5

Have you found the issue in the meantime?
I have the same problem, see my other post.

6

no answer from author. So just deleted it again.

7

When you have problems using the plugin please open an issue on the Plugin-github project, because i am not actively monitoring his community pages.

https://github.com/cathiele/homeassistant-goecharger/issues

As for the Serialnumber. please try the serial without the “CM-02-” prefix, just the numbers as shown in the plugin documentation replace your numbers with the example “111111” numbers.

8

I solved it as follows:

  1. add the custom_compontent (just unpack/copy the integration itself)
  2. reboot
  3. add configuration
  4. reboot

If I add the component and add the configuration in one step, I will get the error. If I do it in 2 steps then I’m good.

9

Hi
Tried to implement your config in configuration.yaml and failed.
image

What is the problem?

Cheers,
Rene

10

Hi René,
did you try to implement the solution manually in your configuration.yaml or did you use the custom component provided by Carsten?

Your error message is a little bit too few of information.

Regards
Ralf

11

Hi Ralf
Thanks for you reply.
Just added your definitions at bottom of my configuration.yaml. Updated the resource link (link (http://192.168.0.20/status) tested in browser and works)

Now did a config check with Homeassistant and got the errors.

So did not use Carsten solution.

Here my System Infos:

Version 0.118.5
Installation Type Home Assistant OS
Development false
Supervisor true
Docker true
Virtual Environment false
Python Version 3.8.6
Operating System Family Linux
Operating System Version 4.19.127-v7
CPU Architecture armv7l

Thanks for any help in advance.
Cheers
Rene

12

Hi René,

can you send your charger part of the configuration.yaml? Then I will do a quick check.

Regards
Ralf

13

Here you are:
#charging station go-e

  • platform: rest
    resource: http://192.168.0.20/status
    scan_interval: 30
    name: “ladestation”
    value_template: “{{ value_json[‘car’] }}”
    json_attributes:
    • car
    • err
    • eto
    • tmp
    • dws
    • nrg
  • platform: template
    sensors:
    charger_status_pwm:
    friendly_name: ‘Status’
    value_template: >-
    {% if is_state_attr(‘sensor.ladestation’, ‘car’, ‘1’) %}
    Ladestation bereit, kein Fahrzeug
    {% elif is_state_attr(‘sensor.ladestation’, ‘car’, ‘2’) %}
    Fahrzeug lädt
    {% elif is_state_attr(‘sensor.ladestation’, ‘car’, ‘3’) %}
    Warte auf Fahrzeug
    {% elif is_state_attr(‘sensor.ladestation’, ‘car’, ‘4’) %}
    Ladung beendet, Fahrzeug noch verbunden
    {% else %}
    Prüfen
    {% endif %}

To start with just did Status part to narrow down the problem.

14

I just wanted to leave a thank you for Carsten! Found your integration here and what can I say - it just works :slight_smile:

15

@RalfP first of all THX for the template. Just easy and it works. LIKE!
PS a hint that the above should be added to the sensor.yaml ?

@cathiele THX for the integration. Would like to go ahead but stugling currently with my samba.
is it possible to run the commads for installation also with hass.io as base?

16

After installing the custom integration of @cathiele I found all entities in HA but they were all unavailable. After some search I found that the /status endpoint was not exposed because it has to be activated in the settings of the charger first. This can easily be done through the go-e app but is not mentioned in the custom integration’s readme.

I would like to create a PR for the documentation, but I have a feeling that this setting might be new and maybe only available with special hardware or firmware versions. Mine is hardware version V3 and firmware 050.2.

Can any of you report back whether you find this setting in your app or not?
Check the go-e app at → Internet → Extended Settings → Activate local HTTP API v1 (v2 also available)

Screenshot_20210624-124612~2
Screenshot_20210624-124612~21080×2340 195 KB

17

Hint:
With firmware 050 the go-e currently reports deka-Wh instead of deka-Ws for data point dws. So current_session_charged_energy of the custom integration is wrong too.

The issue is known and will be fixed in a future release of the firmware.

1 Like
18

Works great! Thank You for your work!

19

This have been working well, since yesterday when I upgraded firmware 051.1 to 051.3.
they did fix that mqtt settings, now its saved but broke something from API v1.
edit:
strange this morning all goe-charger entities shows unavailable now they are back…

20

Same problem for me. API v2 seems to work. v1 sends timeout error after a while.

In this context: Is somewehwere a full API v2 documentation? This one on github isn’t complete: https://github.com/goecharger/go-eCharger-API-v2

21

I’ve prepared a custom component to consume the MQTT messages of the go-eCharger MQTT API v2:

I would be happy about some beta testing and support of the heavy EV charger users. :wink: Naming and value transformations could be improved step by step.

22

I’m not sure whether it’s fair to promote another integration here in this thread. On the other hand I have been waiting for an API v2 integration for quite some time and even started to directly consume the v2 API through Node RED, without a dedicated integration (which actually works quite well).
I would like to ask some questions about your new integration, but honestly I don’t want to hijack this thread. Maybe you want to open up another thread re your integration and leave a link here?

23

It wasn’t my intention to hijack this thread or to be unfair. :slight_smile: I’ve created a new one: Custom component goecharger_mqtt - go-eCharger HOMEfix EV charger integration

1 Like
24

i had the same problem… follow your instruction works :slight_smile: