Skip to content
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

[Feature Request] Separate "Plug status" from "EV status" #593

Open
AJediIAm opened this issue Oct 18, 2024 · 2 comments
Open

[Feature Request] Separate "Plug status" from "EV status" #593

AJediIAm opened this issue Oct 18, 2024 · 2 comments

Comments

@AJediIAm
Copy link

Is your feature request related to a problem? Please describe.
When making automations with MyEnergy, I often need to find out what the possible values of a status entity could be. The values of "Plug status" are particularly confusing since they describe the EV status and not the Plug status.

Describe the solution you'd like
It would be nice to have a simple binary sensor which indicates if the plug is plugged in or not.
Similarly, it would be nice to have a binary sensor which indicates if Zappi is charging or not.

Describe alternatives you've considered
I have created template sensors to simplify making automations and conditional cards on dashboards and it is very nice to work with.

Additional context
I'm wondering if there would be an interest in adding these kind of binary sensors for simplicity or if this is not preferred due to architectural reasons.
This issue is intended to make a decision. I (or someone else) can submit a pull request once a decision has been made.

@AJediIAm AJediIAm changed the title Separate "Plug status" from "EV status" [Feature Request] Separate "Plug status" from "EV status" Nov 26, 2024
@G6EJD
Copy link

G6EJD commented Jan 7, 2025

There is already an entity called plug status, therefore this issue can be closed.

@AJediIAm
Copy link
Author

There is already an entity called plug status, therefore this issue can be closed.

This is a feature request to extend the current integration with an additional binary sensor. Since this is not implemented or rejected by the author, it can remain open.

Additional arguments why having additional binary sensors are useful and valuable can be found here: #364

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants