Affect on other Emporia functionality
Kevin Wanek avatar
Written by Kevin Wanek
Updated over a week ago

Load Management will override some features like Scheduling (Time of Use), Excess Solar as well as Peak Demand Management for the EV Charger. This is because service capacity (and over usage) is primarily a safety concern, so Load Management will be the first priority within the Emporia functionality to override existing control settings.

Dynamic/adjustable Charge Rates: since Load Management controls your available charge rate dynamically, the ability to manually adjust charge rates is disabled.

Time of Use Management (Schedules): Timing will still be respected, so if you have a schedule to only allow charging during certain periods of the day, then that will be followed. Only difference is that the actual charge rate supplied from the EV Charger to vehicle may be reduced as compared to other times if there are any restrictions required by Load Management.

Excess Solar Management: this feature should not conflict with Load Management in anyway since they're essentially on opposite ends of the control spectrum. Excess Solar generation (net production) will not cause any limitations for Load Management since any Net Production (generated power going back to grid) will erase any load limitations from consumption happening in the system.

Peak Demand Management: Load Management will take precedence over any Peak Demand management features since Load Management is safety critical. That being said, if you're getting close to Peak Demand thresholds, then Load Management will also probably be adjusting the available load to the EV Charger given available service load.

Feedback and Suggestions

This knowledge base is pretty new for the Emporia team. Our goal is to provide all of the information we can to help you manage your energy in better ways. If this article wasn't helpful, or we could be more clarifying on any points please reach out to the Customer Support team and we'll certainly work to improve these guides.

Did this answer your question?