search

cathiele / homeassistant-goecharger

Home Assistant custom_component for controlling the go-eCharger EV-Charger
MIT License
89 stars 29 forks source link

Problem with 0.19 with multiple chargers #37

Closed michis0806 closed 3 years ago

michis0806 commented 3 years ago

Hi @cathiele ,

thanks for your great work and the recent implementation of multiple charge points this week.

I just updated to the latest 0.19 and want to give you some feedback. (I used HACS to install the new version of the component). My config is

goecharger:
  chargers:
    - name: goe_dgar
      host: 192.168.x.y
    - name: goe_mgar
      host: 192.168.x.z

I restarted home assistant and found some new entities. The old ones did not disappear so I deleted them. The new naming-scheme seems less specific than the old one. The "goecharger_SERIAL"-prefix is missing so sensor.goecharger_SERIAL_charger_max_current became simply sensor.charger_max_current, sensor.goecharger_SERIAL_car_status became sensor.status which is very generic ;).

My main problem is, that I can only find a switch-entity for my first charger. That was named switch.goecharger_SERIAL_allow_charging in the old implementation. Now I can only find switch.SERIAL2 but no switch for my first charger.

Maybe I made a mistake in setup?

Thanks! Michael

michis0806 commented 3 years ago

Quick update: I completely deleted the integration from HACS and removed the config-part. Restarted. installed the integration from HACS again. Added one Charger. Restarted. Added second charger.

Now both charger switches are visible and named correctly, but the entities are still without the goecharger_SERIAL prefix...

Thanks Michael

cathiele commented 3 years ago

Thanks for reporting this. will look into it... @michis0806 could you try 0.18 please with the same config?

michis0806 commented 3 years ago

Hi @cathiele, I just deinstalled 0.19 and installed 0.18. No change in the naming.

cathiele commented 3 years ago

last option without checking the code: 0.19.0 but setup via config flow and not configuration.yaml.

cathiele commented 3 years ago

i can reproduce it

michis0806 commented 3 years ago

Okay, I deinstalled go-e completely, purged goe entries from .storage/core.* and removed the entries from configuration.yaml. Then I restarted, installed go-e 0.19 from HACS and tried to set it up with the integration-workflow. I get the following errors:

Bildschirmfoto 2021-05-14 um 15 25 51 Bildschirmfoto 2021-05-14 um 15 26 01

After a restart:

Bildschirmfoto 2021-05-14 um 15 27 54
cathiele commented 3 years ago

@michis0806 please test version 0.20.0

cathiele commented 3 years ago

@michis0806 please test version 0.20.0

Sorry, i mean 0.21.0

michis0806 commented 3 years ago

Setup worked well, now. Entity-naming is solved. But now, the "switch" is missing again ;)

cathiele commented 3 years ago

yes.. sorry, maybe i should setup some tests and a GithubAction Pipeline.... :-)

michis0806 commented 3 years ago

;) And I think the goecharger.set_max_current is broken. It doesn't accept any parameters

Sorry, worked, had a typo in it...

cathiele commented 3 years ago

0.22.0 fixes the switch

michis0806 commented 3 years ago

Perfect! Works without any problems now ;) Thanks for your help!