You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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.
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!
The text was updated successfully, but these errors were encountered: