This page outlines current and past outages and issues with optimisation between SmartShift automation and our integrated device brands. These outages can cause temporary data loss in the Amber app, issues with commands or controls either not appearing or failing, and curtailment not working as expected. Our team will send a notification to the app to alert you of any fleet wide incidents.
If your commands, controls or curtailment are not functioning as expected when there are no live issues reported, ensure your system firmware is up to date and your wifi connection is stable.
Current issues
See Resolved Issues below
See Archived Issues (resolved for >2 months) below
Fleet-wide
No live outages
1KOMMA5° BETA
No live outages
AlphaESS
Overview of Issue: Some sites with 2 or more AlphaESS inverters, in a leader/follower installation, may not be charging or discharging the batteries at their correct combined total power (e.g. if you have 2 AlphaESS inverters, it may only respond to SmartShift commands by discharging at half the expected rate). This is due to the way SmartShift's commands are sent to AlphaESS and how they are executed by the inverters.
Impact: Some AlphaESS sites with 2 or more inverters, in a leader/follower configuration.
First Identified: 7th January 2026
Last Updated: 14th January 2026: Our engineers are aware of this issue and investigating a solution.
Anker BETA
No live outages
Enphase BETA
No live outages
FoxESS BETA
No live outages
Fronius
No live outages
GivEnergy BETA
No live outages
Neovolt
Overview of Issue: Some sites with 2 or more Neovolt inverters, in a leader/follower installation, may not be charging or discharging the batteries at their correct combined total power (e.g. if you have 2 Neovolt inverters, it may only respond to SmartShift commands by discharging at half the expected rate). This is due to the way SmartShift's commands are sent to Neovolt and how they are executed by the inverters.
Impact: Some Neovolt sites with 2 or more inverters, in a leader/follower configuration.
First Identified: 7th January 2026
Last Updated: 14th January 2026: Our engineers are aware of this issue and investigating a solution.
Redback
No live outages
Sigenergy
No live outages
SolarEdge
Overview of Issue: Some SolarEdge onboarding requests are currently experiencing significant delays. SolarEdge is aware of this issue and we are working with them to receive an update to the situation. No action is currently required for affected enrolments.
Impact: Long processing times for some SolarEdge enrolments.
First Identified: 6th January 2026
Last Updated: 14th January 2026: SolarEdge has identified the cause of the issue and are now working through processing all aged/delayed enrolments. This may take some time. When your inverter has been enrolled, you will see an update in the Devices section of the Amber app. If there is an issue with your enrolment, we will contact you to let you know.
Sungrow
No live outages
Tesla
No live outages
Resolved issues
Fleet-wide
See older resolved issues below
Overview of Issue: Due to recent price instability in NSW, our price forecasts have shown increased chance of price spikes. This lead to some systems charging from the grid to prepare for those forecasted price spikes. As the day went on, it's become clear that a price spike event was unlikely.
Impact: Some sites may have noticed charging from the grid, or more cautious actions from SmartShift than would usually be needed.
First Identified: 4th December 2025
Last Updated: 4th December 2025 at roughly 4pm; Our engineers have resolved this issue. The price forecasts shown in the 'Devices' tab of the Amber app have now stabilised and SmartShift's planned actions will adjust to this.
Overview of Issue: SmartShift is experiencing intermittent connectivity and performance issues due to backend scaling constraints following a recent increase in enrolled devices. This resulted in database delays when processing device health metrics. To customers, this may appear as though SmartShift has lost connection to your battery or solar inverter, even if the device remains online locally.
Impact: Mainly impacting Tesla and Sungrow devices enrolled in SmartShift. Symptoms include unpredictable behaviour, random failures to execute automation commands, or gaps in telemetry data.
First Identified: 26th November 2025
Last Updated: 26th November 2025; Our engineers are currently investigating this issue.
Overview of Issue: The SmartShift replace device flow was temporarily down. This has been fixed and is now operating as normal. Hard close and reload the Amber app to ensure you're on the latest version of the app.
Impact: All brands
First Identified: 17th November 2025
Resolved: 17th November 2025
1KOMMA5° BETA
Overview of Issue: For some 1KOMMA5° sites, the export limit appeared to be stuck at 0. This value should automatically update every 5 minutes under the SmartShift automation.
Impact: Users reported that their devices were not responding to SmartShift commands e.g. under a dispatch command, the device was not discharging energy to the grid.
User Actions: No immediate action is required from users. Our integrations engineers have deployed a fix to resolve the issue.
First Identified: 23/12/2025
Resolved: 07/01/2025
Overview of Issue: Solar curtailment was not working properly across a number of 1KOMMA5° sites. It was mainly affecting sites that are AC-coupled where the external solar system cannot be controlled, however, we have found it to be happening on a few DC-coupled sites as well. The manufacturer has completed a firmware upgrade, which has resolved most of the issues with curtailment.
Impact: Users may have noticed that while automated solar curtailment was active and their battery was fully charged, their system continued to produce excess solar which was then exported to the grid during negative FiT periods. This did not affect the battery automation.
User Actions:
If you notice this behaviour, please Log an issue via the Plan section of the Devices tab. This will help us track the number of sites that are experiencing this issue.
If you have an external solar system that is AC-coupled to your 1KOMMA5° hybrid inverter and it's compatible with SmartShift, we recommend registering it to enrol in SmartShift. For more information, please read AC- vs DC-Coupling: What It Means for SmartShift.
First Identified: 2nd December 2025
Resolved: 17th December 2025
Overview of Issue: The SmartShift automation was experiencing degraded performance due to unreliable API responses from the manufacturer's server. This appeared to users as a Wi-Fi or connection issue in the Amber app, even if their network connection was stable.
Impact: All 1KOMMA5° devices enrolled in SmartShift. Users may have experienced inconsistent or failed automation control commands.
First Identified: 18th November 2025
Resolved: 10th December 2025
AlphaESS
Overview of Issue: AlphaESS's server experienced an issue for around 1 hour on December 23rd. This issue has now been restored and resolved.
Impact: All AlphaESS devices
First Identified: 23rd December 2025
Resolved: 23rd December 2025
See older resolved issues below
Enphase BETA
See older resolved issues below
Overview of Issue: Smartshift automation is experiencing failure in canceling curtailment commands, causing sites to become permanently curtailed. Enphase are able to restore a limited range of sites back to max-export generation
Impact: All Enphase devices enrolled in SmartShift. Users may experience limited or zero solar generation
First Identified: 6th December 2025
Last Updated: 17th December 2025 - Enphase have now resolved this issue. Any sites that have their curtailment 'stuck' being activated will have the curtailment command cancelled at midnight each night.
Overview of Issue: There are currently a select number of Enphase devices not reporting back telemetry as of this morning, the error is occuring due to outages in Enphase dependent software. Enphase are currently looking to resolve the issue.
Impact: Limited Enphase devices
First Identified: 9:30am 3rd November
Resolved on: 4th November 2025
Overview of Issue: Enphase devices are experiencing strange / incorrect behaviour after recent onboarding, due to incorrect firmware version. To confirm firmware version, go to settings > System > Devices and select your Gateway. For the firmware to be compatible with Amber it must be 8.2.4398 or higher. To upgrade the firmware you will need to reach out to Enphase Customer Support.
Impact: Limited Enphase devices
First Identified: 1st September 2025
Resolved on: 19th November 2025
Overview of Issue: Some customers with an Enphase device enrolled in SmartShift may notice a "Communication error" in the Devices tab of the Amber app, due to a data regularity/consistency issue.
Impact: Some Enphase sites. SmartShift may be unable to create forecasts and send the expected control commands to your Enphase system.
First Identified: 10th December 2025
Last Updated: 7th January 2026: If you are experiencing this issue, the resolution requires manual intervention from the team at Enphase. Resolved on: 14th January 2026
FoxESS BETA
See older resolved issues below
Overview of Issue: For some FoxESS sites, the export limit appeared to be stuck at 0. This value should automatically update every 5 minutes under the SmartShift automation.
Impact: Users reported that their devices were not responding to SmartShift commands e.g. under a dispatch command, the device was not discharging energy to the grid.
User Actions: No immediate action is required from users. Our integrations engineers have deployed a fix to resolve the issue.
First Identified: 23/12/2025
Resolved: 07/01/2025
Overview of Issue: Solar curtailment was not working properly across a number of FoxESS sites. They have completed a firmware upgrade, which has resolved most of the issues with curtailment and they are currently working on a longer term fix. It is mainly affected sites that are AC-coupled where the external solar system cannot be controlled, however, we have found it to be happening on a few DC-coupled sites as well.
Impact: Users may have noticed that while automated solar curtailment was active and their battery was fully charged, their system continued to produce excess solar which was then exported to the grid during negative FiT periods. This did not affect the battery automation.
User Actions:
If you notice this behaviour, please Log an issue via the Plan section of the Devices tab. This will help us track the number of sites that are experiencing this issue.
If you have an external solar system that is AC-coupled to your FOXESS hybrid inverter and it's compatible with SmartShift, we recommend registering it to enrol in SmartShift. For more information, please read AC- vs DC-Coupling: What It Means for SmartShift.
First Identified: 2nd December 2025
Resolved: 17th December 2025
Overview of Issue: The SmartShift automation was experiencing degraded performance due to unreliable API responses from the FoxESS server. This was appearing to users as a Wi-Fi or connection issue in the Amber app, even if their network connection was stable.
Impact: All FoxESS devices enrolled in SmartShift. Users may have experienced inconsistent or failed automation control commands.
First Identified: 18th November 2025
Resolved: 10th December 2025
Fronius
No known issues within the last 2 months.
See older resolved issues below
Neovolt
See older resolved issues below
Overview of Issue: Some Neovolt customers are currently experiencing intermittent issues receiving telemetry from their device into Amber. This is being caused by a Neovolt server upgrade. This is causing intermittent data resulting in less automation from SmartShift. Our team is investigating this with Neovolt and will issue an update once available.
As of 17 December, Neovolt have completed their server upgrade, and have let us know these telemetry issues should subside.
Impact: Intermittent data and less automation for some Neovolt sites.
First Identified: 8th December 2025
Resolved: 7th January 2026
Overview of Issue: Amber failed to ingest telemetry from Neovolt devices for approximately 5 hours on November 17th. This was a result of an Amber side bug, and was resolved by the team as quickly as possibly.
Impact: Neovolt Devices
First Identified: 10am 17 November 2025
Resolved: 3pm 17 November 2025
Redback
See older resolved issues below
Overview of Issue: Our monitoring detected an issue with communication and control of Redback devices. This has been resolved with Redback and normal operation has been resolved.
Impact: Redback
First Identified: 11am November 6
Resolved: 5pm November 6
Sigenergy
Overview of Issue: Some Sigenergy single phase inverters (8 kW, 10 kW, 12 kW models) have recently received a firmware update from Sigenergy. This update temporarily limits the inverters maximum export to 7 kW as a safety measure until the inverters can be inspected and if necessary, updated or repaired.
This limitation can affect how SmartShift optimises energy usage in your home. Because the inverter can't exceed the 7 kW limit, your system may export less energy than usual, and your battery may not discharge at the same level as it normally would. Please note: this limitation has been applied by Sigenergy and has not been implemented by by SmartShift directly.
Impact: Limited export for the above mentioned Sigenergy devices.
First Identified: 17th November 2025
Last Updated: 7th January 2026 - The cause of this issue has been identified as a hardware based issue, so may require a visit from your installer to resolve. Please contact Sigenergy or your installer for more information.
Overview of Issue: A number of Sigenergy devices enrolled in SmartShift were experiencing automation errors. Users found that SmartShift control commands were not working. Signenergy advised that the issue was related to rate-limiting strategy on their end and have swiftly resolved the issue.
Impact: ~5,500 Sigenergy devices enrolled in SmartShift
First Identified: 4.30pm 04/01/2026
Resolved: 1:00pm 05/01/2026
See older resolved issues below
SolarEdge
No known issues within the last 2 months.
See older resolved issues below
Sungrow
See older resolved issues below
Overview of Issue: Some sites that have a Sungrow system AND another brand of inverter enrolled with Amber, may currently be experiencing issues with on/off curtailment.
This may result in curtailment commands being unsuccessful, leading to exports to the grid during times of negative export prices.
Impact: A limited number of sites that have both a Sungrow system AND another brand of inverter enrolled with Amber.
First Identified: 18th November 2025
Last Updated: 10th December 2025; Our engineers have resolved this issue and are continuing to monitor the performance of affected sites.
Tesla
No known issues within the last 2 months.
See older resolved issues below
Archived issues (resolved for >2 months)
Overview of Issue: We are aware of an issue impacting Amber's communication and control with SmartShift devices. As of 9pm on October 30th this issue is recovering and connection with devices are coming back. Impacted customers may notice incorrect stats on their 'Devices' tab, but this will not impact billing or earnings.
Impact: Communication and control dropout
First Identified: 30 October 6pm
Resolved: 3 November 10pm
Overview of Issue: We experienced an issue with price generation, which caused a temporary interruption in automation. The issue is now resolved and services are now back to normal.
Impact: Interruption to automation
First Identified: 11 July 14:25
Resolved: 11 July 15:15
AlphaESS
Overview of Issue: We noticed some communication issues in the Devices tab for AlphaESS devices enrolled in SmartShift. The problem was related to how SmartShift receives data from these devices. We deployed a fix to make the data flow more reliable.
Impact: 100s of AlphaESS devices per week
First Identified: 11th September 2025
Resolved: 8th October 2025
Overview of Issue: Telemetry data issue
Impact: We've identified a large number of AlphaESS enrolments are missing solar telemetry as a result of an AlphaESS update. This is now resolved and services are now back to normal.
First Identified: 6pm 31/07/2025
Resolved: 2:25pm 01/08/2025
Fronius
Overview of Issue: Some Fronius systems are currently not responding to some or all commands coming from Amber. This is due to broader system outages that Fronius are currently working to resolve. Once this has been resolved by Fronius, no action should be required by our customers to restore function.
Impact: Limited Fronius devices
First Identified: 19th October 2025
Overview of Issue: We have detected an issue with control of Fronius devices. Fronius is working on this issue to restore normal operation as soon as possible.
Impact: Control of Fronius inverters are not being sent successfully. Customers will still be able to see data in the app however, but automated and manual controls are not being actioned.
First Identified: 5pm AEST 24/06/25
Status: Resolved
Neovolt
Overview of Issue: Some sites were missing power attributes resulting in battery commands not being carried out correctly. Users were finding that their devices were not responding to dispatch or charge commands. We raised this with Neovolt and they were able to resolve the issue from their end.
Impact: 5% Neovolt devices
First Identified: 18th September 2025
Resolved: 25th September 2025
Redback
Overview of Issue: We have detected an issue with control of Redback devices. Redback is working on this issue to restore normal operation as soon as possible.
Impact: We're unable to automate all Redback devices
First Identified: 23 July 9am
Resolved: 23 July 5pm
Sigenergy
Overview of Issue: We have detected an intermittent issue with control of Sigenergy devices. We have notified Sigenergy of this issue and are working with them to restore normal operation as soon as possible.
Impact: All Sigenergy devices
First Identified: August 13th
Resolved: August 26th
Overview of Issue: We detected an issue where Sigenergy devices are being read as having very low (near 0kwh) energy levels. We notified Sigenergy of this issue and they have restored normal operation.
Impact: Battery energy is being read as very low, which is impacting automation and displaying incorrect energy levels in the app.
First Identified: 10pm August 5th.
Resolved: 2pm August 6th
Overview of Issue: A communication issue has been detected limiting SmartShift's ability to control Sigenergy devices. Sigenergy are aware, and are assisting us in resolving the issue. In-app notification has been sent to customers with Sigenery devices.
Impact: All Sigenergy devices
First Identified: 4pm 04/08/2025
Resolved: 1pm 05/08/2025
Overview of Issue: A communication issue has been detected limiting SmartShift's ability to control Sigenergy devices. Sigenergy are aware, and are assisting us in resolving the issue. In-app notification has been sent to customers with Sigenery devices, with follow up in-app notification notifying Sigenergy customers the issue has been resolved, and normal service resumed.
Impact: All Sigenergy devices
First Identified: 10.05am 19/06/2025
Resolved: 12.40pm 19/06/2025
SolarEdge
Overview of Issue: We're aware of significant delays currently affecting multiple SolarEdge device enrolments.
Impact: Pending SolarEdge enrolments (displayed as 'Device Link Requested' in the Amber app)
First Identified: 1st August 2025
Resolved: 2.50pm 2/09/2025
Sungrow
Overview of Issue: Solar curtailment issues were impacting Sungrow hybrid devices from late August - mid October. SmartShift was successfully delivering curtailment commands to the inverter, however the inverter would not respond. This resulted in SmartShift believing curtailment is happening when it was not.
Sungrow firmware updates are required to address this issue, and Sungrow are in the process of making these available.
The latest status by hybrid model number is as follows:
- SH5T, SH10T, SH15T, SH20T, SH25T, SH8.0RS, SH10RS: The latest firmware update has been published on iSolarCloud, and customers can update their devices directly through the iSolarCloud platform. See here for instructions from Sungrow on how to check for and update your firmware.
- SH5.0RS, SH6.0RS: A preview version of the firmware update is available upon request. Customers who wish to update can contact Sungrow Support directly at: service@sungrowpower.com.au.
- SH5.0RT, SH10RT: The firmware update for these models is not yet available. It will be released on iSolarCloud shortly. No action is required at this stage. Impact: Some Sungrow hybrid systems utilising curtailment
First Identified: 29th August 2025
Resolved: 5th November
Overview of Issue: A Sungrow-side outage resulting in communication errors when SmartShift is attempting to communicate with Sungrow devices. Sungrow team are aware, and investigating resolution. In-app notification has been sent to customers with Sungrow devices - further updates will be communicated via in-app notification.
Impact: All Sungrow Sites
First Identified: 7.40am 23/06/2025
Resolved: 9.55am 23/06/2025
Overview of Issue: Communication issue identified, preventing Sungrow customers from discharging to the grid. Our engineers are actively working with Sungrow to implement a resolution. In-app notification has been sent to customers with Sungrow devices, with follow up in-app notification notifying Sungrow customers the issue has been resolved, and normal service resumed.
Impact: Limited Sungrow devices
First Identified: 2.00pm 12/06/2025
Resolved: 9.55pm 12/06/2025
Tesla
Overview of Issue: We have detected an intermittent issue with telemetry and control of some Telsa devices. We have are working to restore normal operation as soon as possible.
Impact: Subset of Tesla Powerwall customers
First Identified: 10.00am 14/08/2025
Resolved: 4.00pm 14/08/2025
Overview of Issue: Communication issues have been identified impacting SmartShift's control of Tesla Powerwall devices. Tesla has been engaged, and are working with our engineers to resolve the issue. In-app notification has been sent to customers with Tesla Powerwall devices, with follow up in-app notification notifying Tesla Powerwall customers the issue has been resolved.
Impact: All Tesla Powerwall devices
First Identified: 12.05pm 18/06/2025
Resolved: 4.45pm 18/06/2025
Comments
Article is closed for comments.