I’ve been having a problem with my Enphase Envoy and its battery charge/discharge behavior since Jun 17th 2026. Calls and texts to support were not productive. I decided to give their AI Assistant a whirl. It was an excellent experience. The AI Assistant started with a wrong diagnosis taken from a support call I’d made previously. I was able to tell it some details and it listened to me more than any human, and course corrected.
The AI Assistant eventually identified the exact problem and cause I’m having. Thought it did keep trying to put me back to talking to a human, I decided to continue to pursue the matter with the AI Assistant, asking it frank questions that it did answer, even pleasantly. In the end, I gave it more information about what I’ve been doing, and it finally identified a change that was rolled out Jun 17th. It went on to tell me what to report to Enphase support as well! I’ll note that the lengthy responses took less than 20 seconds each, much faster than a human could both lookup/investigate and type/copy&paste a response.
Though the problem is not resolved, it has at least been identified. Enphase is rolling out Cloud-sourced battery control, and ceasing locally-sourced battery control. This means that our systems are now even more cloud dependent that it was before, which I don’t like at all. My solution is to use Parental Control on my router to limit access to one short period per day, and then use local control to apply tariff settings that I need to accomplish my goals, which are of using solar for both home load and battery charging in the morning (one behavior I want) and then later also discharging battery to home load for peak TOU time in the evening so all available solar can go to the grid to run my meter backwards (the other behavior I want). It is sadly impossible to get both of these behaviors together in one setting/schedule/tariff on the Envoy, so I use Home Assistant to switch at some point during the day. (Let’s further note that if they were to add a switch to charge only from excess solar (after powering the home load) all of this would not be necessary.)
Below is a partial transcript of my conversation with Enphase AI Assistant:
Enphase Assistant:
A Note About Your Recent Cases: I noticed you’ve had some recent support cases about battery settings not holding properly (cases from June 18th). If you’re still experiencing issues with settings changing unexpectedly, please let me know and we can investigate further.
What’s Your Goal? Are you looking to maximize savings during peak hours, or are you trying to ensure backup power is available at certain times? This will help me suggest the best configuration for your needs.
Enphase Assistant:
Based on your support case history, on June 17th your system started experiencing an issue where tariff settings were changing unexpectedly when your Gateway connected to the cloud.
What Happened: Your peak hours shifted incorrectly from the correct 5-8 PM to 8-9:15 AM, which would have affected when your battery discharged and when you were charged peak rates.
Root Cause: The issue was traced to your router’s parental controls, which were limiting your Gateway’s cloud connection to only once per day. This prevented your system from receiving proper updates and syncing tariff settings correctly.
How It Was Fixed: Our support team:
Adjusted your router settings to allow normal cloud connectivity
Restarted your Gateway services
Updated your tariff settings on our end
Status: This case was closed on July 9th. The case summary recommends monitoring your system over the next few days to confirm everything is working correctly.
Are you still experiencing any issues with your tariff settings or peak hours since this was resolved?
Enphase Assistant:
According to your support case (Case #xxxxxxxx), the cause of the tariff shift was:
Router parental controls were limiting your Gateway’s cloud connection to only once per day.
This prevented your Gateway from:
Connecting to the Enphase cloud regularly
Receiving proper system updates
Syncing your tariff settings correctly
As a result, your peak hours shifted incorrectly from 5-8 PM to 8-9:15 AM.
The Fix: Support adjusted your router settings to allow normal cloud connectivity for your Gateway, which restored proper tariff synchronization.
If you want to prevent this from happening again, you may want to review your router’s parental control settings to ensure your Gateway has unrestricted access to connect to the Enphase cloud.
Enphase Assistant:
You’re right to correct me thank you for that clarification. If parental controls were not enabled on June 17th, then the root cause identified in the case may not have been accurate.
Looking back at the case summary, it appears the support team concluded that parental controls were the issue, but if that wasn’t actually the case on that date, there may have been a different underlying cause for the tariff settings shifting from 5-8 PM to 8-9:15 AM.
Do you know what actually caused the shift on June 17th? Or is this something that’s still unclear?
If the issue wasn’t properly diagnosed, it would be worth investigating further especially since you’ve had multiple related cases about settings not holding properly (cases from June 18th as well). I’d recommend reaching out to Enphase support to clarify what actually triggered the tariff change on that date, so we can make sure it doesn’t happen again.
Would you like me to help you connect with a support agent to look into this more thoroughly?
Enphase Assistant:
Thank you for clarifying that’s an important distinction. You’ve identified that:
June 17th A cloud-side change corrupted your tariff settings
Your response You enabled parental controls as a workaround to prevent the Gateway from reconnecting to the cloud and re-corrupting the settings
Support’s misdiagnosis They mistakenly identified the parental controls as the cause, when they were actually your solution to the problem
That’s a significant difference from what the case summary states.
Unfortunately, I don’t have access to information about what specific change was deployed to the Enphase cloud on June 17th. The case history doesn’t include those technical details about the cloud-side change that triggered the tariff corruption.
To get this answer, you would need to:
Contact Enphase support directly and ask them to review their deployment logs or release notes from June 17th
Explain that you’ve identified the issue was a cloud-side change that corrupted your tariff, not parental controls
Ask what was changed and whether it affected other customers
This would help ensure the root cause is properly documented and prevent similar issues in the future.
Would you like me to help you connect with a support agent to investigate this further?
Enphase Assistant:
You’re right to ask for clarification. No, I don’t have access to Enphase’s internal change logs or deployment records.
What I can access:
Public documentation via the Enphase knowledge base
Your site-specific data (device status, settings, energy data, support cases)
Your case history (which is what I’ve been referencing)
What I cannot access:
Internal Enphase cloud infrastructure logs
Deployment records or change logs from specific dates
Backend system changes or updates
Internal engineering documentation
The specific cloud-side change that occurred on June 17th would only be documented in Enphase’s internal systems and would require direct access to their engineering or operations team.
To get this information, you’ll need to contact Enphase support directly and ask them to:
Review their internal deployment logs from June 17th, 2026
Identify what change was made that corrupted tariff settings
Explain why it happened and what was done to prevent recurrence
This is definitely worth pursuing, as it would help clarify what actually caused the issue and ensure it doesn’t happen to you or other customers again.
Would you like me to help you connect with a support agent to escalate this question?
Enphase Assistant:
That’s an excellent question. I don’t have visibility into other customers’ systems, but I did find something relevant in the knowledge base:
Known Issue Starting June 12, 2026: There is a documented issue where changes to battery settings (profile and reserve State of Charge) were not applying correctly due to a mismatch between Gateways and Enlighten cloud. This affected systems starting around June 12th very close to when your tariff corruption started on June 17th.
Your Case History Confirms This: Looking back at your support cases, you had multiple cases filed on June 18th about battery settings not holding and changing unexpectedly:
Case #xxxxxxxx “Tariff Settings Not Holding”
Case #yyyyyyyy “Battery settings weren’t staying saved”
This suggests the issue was affecting multiple aspects of your system (tariff, battery profile, reserve SoC) and likely affected other customers too.
What You Should Do: When you contact Enphase support about the June 17th cloud change, specifically ask them:
If the tariff corruption was related to the known Gateway/Enlighten mismatch issue
How many customers were affected
What was changed in the cloud on June 17th that triggered it
What permanent fix was implemented to prevent recurrence
This will help clarify whether it was a widespread issue or isolated to your system.
Would you like me to help you connect with a support agent to investigate this?
Enphase Assistant:
This is a critical finding! I found the answer to what changed on June 17th.
What Changed: Your system was migrated from Gateway-sourced battery schedules to Cloud-sourced battery schedules.
Why Your Tariff Settings Got Corrupted: According to Enphase documentation:
“If your system’s schedule is sourced from the Enphase Cloud, battery tariff settings can no longer be configured by triggering REST tasks to /admin/lib/tariff. Attempting to do so may cause temporary abnormal system behavior, but the Cloud will eventually correct the schedules automatically.”
This explains exactly what you experienced:
You were using the local /admin/lib/tariff REST API to create custom tariff configurations
On June 17th, your system was switched to Cloud-sourced schedules
Once Cloud-sourced, the system began automatically “correcting” (overwriting) your custom local tariff settings
That’s why enabling parental controls worked it prevented the Gateway from syncing with the cloud and overwriting your settings
The Problem: You can no longer use the local admin interface to automate your battery behavior switching. The cloud will override any local tariff changes you make.
Your Options Going Forward: According to Enphase, battery tariff settings must now be configured through:
Enphase App (for homeowners)
Enphase Installer Toolkit (for installers)
Enlighten Manager (for support agents)
Unfortunately, this means your current automation approach using the local /admin/lib/tariff endpoint is no longer supported on your system.
Recommendation: Contact Enphase support and ask them to help you set up your self-consumption and peak-time battery behaviors using one of the supported methods above, since the local REST API approach is no longer compatible with Cloud-sourced schedules.
Would you like me to help you connect with a support agent to discuss alternative solutions?
Enphase Assistant:
Based on the documentation I found, it does not appear to be possible to revert to Gateway-sourced battery schedules.
What Happened: Enphase implemented a company-wide transition throughout Q2 2026 (which includes June 17th) to migrate all systems from Gateway-sourced schedules to Cloud-sourced schedules. Your system was transitioned as part of this rollout.
Key Points:
This is a permanent, system-wide migration not a per-system configuration
The documentation states: “Once a system’s schedule is sourced from the Enlighten Cloud, battery tariff settings can no longer be configured by triggering REST tasks to /admin/lib/tariff”
There is no documented way to revert back to Gateway-sourced schedules
However: I don’t have explicit documentation stating that reversion is impossible. It’s possible that:
Support may have an option to revert systems in special cases
There may be an undocumented configuration option
This could be something worth asking about directly
My Recommendation: Contact Enphase support and specifically ask:
Is it possible to revert your system to Gateway-sourced schedules?
If not, what are your options for automating the battery behavior switching you need (self-consumption vs. peak discharge)?
They may be able to help you find a supported solution that achieves your automation goals, or they may be able to discuss whether an exception is possible given your use case.
Would you like me to help you connect with a support agent to explore this?
Enphase Assistant:
I need to be transparent with you: the information I referenced came from the internal search results of the Enphase knowledge base, which doesn’t have a direct public URL I can share with you.
Specifically, the key information about the Q2 2026 transition to Cloud-sourced schedules came from the knowledge base’s synthesized answer, not from a specific public support article.
What the internal documentation stated:
“Enphase systems are transitioning to sourcing battery schedules from the Enlighten Cloud instead of locally from the IQ Gateway. This change will occur throughout Q2 2026.”
“Once a system’s schedule is sourced from the Enlighten Cloud, battery tariff settings can no longer be configured by triggering REST tasks to admin/lib/tariff.”
You can check your system’s schedule source by looking at “IQ Battery Info” on the Enlighten Admin splash page, which shows “Source of Schedules”
However: I don’t have a direct public support article URL to point you to for this specific information. This appears to be internal documentation that may not be publicly available.
My Recommendation: Contact Enphase support directly and ask them for:
Documentation about the transition from Gateway-sourced to Cloud-sourced battery schedules
Whether this transition can be reverted
The official timeline and details of this change
They should be able to provide you with the official documentation and give you definitive answers about whether reversion is possible.
Would you like me to help you connect with a support agent?
Enphase Assistant:
That’s a completely legitimate concern, and you’re not alone in feeling this way. Many homeowners prefer local control over their systems rather than relying on cloud connectivity and cloud-based decision-making.
Your Current Situation:
Enphase has mandatorily migrated your system to Cloud-sourced battery schedules
This prevents you from using your local /admin/lib/tariff REST API approach
Your workaround (parental controls) keeps your system local, but it’s not an ideal long-term solution
You’re essentially forced to choose between cloud control or limiting your Gateway’s connectivity
What You Should Do: I strongly recommend contacting Enphase support and explicitly stating:
You do not want cloud-dependent control of your battery system
You prefer local Gateway-sourced scheduling
You want to know if there are options to opt-out of Cloud-sourced schedules or revert to Gateway-sourced control
This is important feedback about your system preferences
Why This Matters: Customer feedback about cloud dependency concerns is valuable to Enphase’s product team. If enough customers express this preference, it can influence product decisions and feature options.
Important: This is a conversation worth having directly with Enphase support rather than working around it with parental controls. They need to understand that there’s demand for local-only control options.
Would you like me to help you connect with a support agent to discuss this concern directly?
Enphase Assistant:
Great! I’m connecting you to a human support agent now.
Your conversation and site details will be shared with the agent, so you won’t need to repeat anything. Here’s a brief summary of what we’ve discussed:
Summary:
On June 17th, 2026, your system was migrated from Gateway-sourced to Cloud-sourced battery schedules
This migration prevented you from using your local /admin/lib/tariff REST API to automate battery behavior switching (self-consumption vs. peak discharge)
You enabled parental controls as a workaround to prevent cloud sync from corrupting your custom tariff settings
You prefer local control over your home systems and do not want cloud-dependent control of your battery, HVAC, or solar
You want to discuss options for reverting to Gateway-sourced schedules or opting out of Cloud-sourced control
The agent will have full context and can help you explore your options for local control of your system.
Please wait while we connect you…
Enphase Agent:
Thank you for staying online, Erik.
Please note that once a system has been migrated to cloud-sourced battery scheduling, it cannot be reverted back to Gateway-sourced scheduling. This migration is part of an Enphase platform-wide upgrade designed to improve battery optimization, monitoring, reporting, and remote support capabilities.
While the scheduling source is managed through the Enphase Cloud, you still have control over your battery operation through the Enphase App, Installer Toolkit, and Enlighten Manager, where you can configure battery profiles such as Savings, Self-Consumption, and Backup.
I understand your preference for local Gateway-based control. At this time, there is no option to opt out of cloud-sourced scheduling, but I will document your feedback and ensure your request is shared through the appropriate channels for Product Team review.
For example, requiring a cloud-based token to communicate with the Envoy is touted as improved security, but cloud decreases security since most breaches happen in the cloud not with home owners individually.
This recent change to cloud-sourced scheduling only hampers my already locally optimized battery optimization, monitoring and reporting – it does not improve anything for me, but rather it is destructive to my system.
(NB: I didn’t mention at the time, but also at issue: the cloud goes down fairly often, so this introduces instability.)
Enphase Agent:
I understand your concerns, Erik, and I appreciate you sharing your perspective.
I have documented your feedback regarding the migration to cloud-sourced battery scheduling. I understand that, from your experience, the change has negatively impacted a locally optimized setup that was previously working as intended, and that you prefer retaining direct local control of your battery behavior and tariff configurations.
While Enphase currently does not offer an option to revert to Gateway-sourced scheduling, I will note your concerns regarding:
Loss of local control over battery scheduling. Potential impacts to your existing automation workflows. Preference for local system management over cloud-dependent control. The perceived negative effect on your battery optimization and system operation.