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 - battery force charge period exposure #201

Open
sabbie-github opened this issue Nov 23, 2023 · 3 comments
Open

Feature request - battery force charge period exposure #201

sabbie-github opened this issue Nov 23, 2023 · 3 comments

Comments

@sabbie-github
Copy link

Could the battery force charge periods be exposed through this cloud integration? I am using both this Cloud version and the modbus via LAN.
The modbus offers exposing the force charge periods, but that requires removing the cloud wifi dongle and needs special hardware and wiring (so not possible via lan).
My logic is that the wifi dongle is already communicating the force charge periods to the cloud - could these be exposed here and edited in a lovelace card (the card already exists in hacs)?
thank you!

@canton7
Copy link

canton7 commented Dec 20, 2023

but that requires removing the cloud wifi dongle

Not true, FWIW. You can run both at the same time just fine.

@Sarelseekat
Copy link

Hi there

I'm also interested in this feature. Is there a way to do at this stage?

@tonywake
Copy link

I would also like this feature as I would like to use an automation to prevent the battery being used to charge my EV when using Octopus Intelligent outside of the standard 11:30 to 5:30 window.
Eg Octopus sets a schedule to charge the car starting at 10:00pm. If I don’t remember to change the Force Battery Charge in the FoxESS app, the car will draw from battery before using the grid. In this scenario, I would like to automatically manage the Force Battery Charge settings within Home Assistant.

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

4 participants