-
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for EV charger-card UI #84
Comments
Great! Did you also connect it to ocpp services? |
No I didn't look into that yet. |
Thinking it would be better to recreate the charger card that is already there and make it OCPP complaint, So my 2 cent, as OCPP is a standard we (I can code JS) should maybe try to start from scratch and make it OCPP complainant. |
And I just noticed that Easee charger user can still use our card via the ocpp service that Easee provides through their API: |
@jeremycoppey would be great if you could develop a card specifically for ocpp! Here's another card that could be used for inspiration: https://github.com/JonahKr/power-distribution-card This has animations and a versatile editor. |
Quick question, do you add it into this integration or do we need to create a new repo with only the card? |
I would prefer to keep things together, but I am not sure that this is supported by HACS |
Hi @jeremycoppey and @lbbrhzn, I am interested about the status of the card. If you need help I could look into it during the Christmas holiday :) |
The Alarmo component also includes a lovelace card. This could be a similar approach |
Stale issue message |
Is your feature request related to a problem? Please describe.
Our ocpp integration represents the ChargePoint as a set of sensors and switches. Some may find it more user friendly to use a single graphical representation of the charger that shows the status and access to services, like lock/unlock, reset, fw upgrade etc.
Describe the solution you'd like
There is a HACS project for a custom
EV charger-card
We should see what would be required to facilitate users to combine our integration with this.
Describe alternatives you've considered
Alternatively, we can create our own card that is specifically designed for ocpp. Not sure if we can integrate the .js file of the card with the custom_component in a single hacs integration, though, so installation may still be a multi-step process.
Additional context
I’ve opened an issue at the charge-card project to discuss how to facilitate integration.
The text was updated successfully, but these errors were encountered: