I have the same software version on my gateway too, and I don’t see 3 phases.
After looking into it a bit, the 3-phase or 1-phase configuration is set during the system installation. To change it later, you have to contact Enphase support. (ref: Enphase Community)
Unfortunately for you, I think you’re going to have the “pleasure” of contacting them again.
OK, thank you very much.
The system has always been configured as single-phase, and Enphase confirmed this, stating that the installation is still single-phase and that the only change is in how the information is displayed.
Following that response, I asked whether it would be possible for only L1 to be displayed on single-phase installations. They replied that they would escalate the request to the appropriate team.
However, a couple of hours later, I received another email stating that, after reviewing the issue, the problem was actually related to the new Victron interface.
However, as shown in the screenshot, it is now Enphase that sends ac/NumberOfPhases with a value of 3, whereas it previously sent a value of 1. For that reason, I believe the source of the issue lies with Enphase rather than Victron, since Victron simply displays the information it receives via Modbus TCP.
I’ll wait to see how they respond.
Thanks again.
A month later and 4 or 5 cases further, my connection is working again, 1fase and even PEL is working with node-red. Last chat whit Swatika D ended in my suggestion to kick some ass by de engeneers and that I will contact next month. 1 minute after closing the chat Modbus TCP was back again…
still on 8.3.5289
unbelievable !
I checked the SunSpec Modbus TCP specifications to see which parameter indicates the number and type of phases.
To my surprise, my system returns a value of 2, indicating a 3 phases installation while it is single phase.
I’m not saying there isn’t an error on the Victron side, but there is already one on the Enphase side.
FYI they finally fixed it again, in case it’s useful my case number was 20099739.
As of today, the case remains open. Although Modbus TCP communication has been restored, the system still reports my installation as three-phase instead of single-phase.
At this time, I have not received any further updates from Enphase.
Same issue here, I called the support in the Netherlands, they mentioned they fixed it temporarily. He did not mention any specific details. After ~15minutes I was able to discover the PV inverters again (I have two single phase Enphase Metered Envoys).
Sweet! It is working again!
“I hope you are doing well.
I wanted to provide you with an update regarding the Modbus issue. Our team has completed the necessary actions, and the issue has now been resolved on our end.
Could you please check the system and confirm whether the Modbus communication issue has been resolved from your side as well? If you are still experiencing any problems, please let us know and share any relevant details so we can continue investigating.
Thank you for your patience and cooperation throughout this process. I look forward to your confirmation.
Best regards,
Hamdhan Sageer
Enphase Energy”
note: it now even works on non-metered devices, even with old Victron firmware.
Wich firmware do you have right now?
Thanks for the info.
This is an “old” Enphase firmware, it comes from April 15th, the most problematic firmware is 8.3.5528.260506 coming in May the 6th. Older firmwares from 2025 an back are working with the modbus. The most annoying issue is that Enphase cannot roll back or downgrade the firmware to prior versions. Still waiting for a solution as long as we have 200 systems with Enphase and 10 with Victron and Enphase. Most of them are still working because they didn’t update. I don’t know their politics to update the installations, and also can’t block them to update 
. Hoping this is solved ASAP or we’ll have to move to energy meters.
My understanding is that the metered envoy runs a newer firmware version. This is my test system with the standard envoy. The software is up-to-date. Even triggering the firmware update in the toolkit won’t change that.
note: it now even works on non-metered devices, even with old Victron firmware.
@BAnders Do you mean I can read my PV power and such on the enphase non-metered envoy?
So now it works with standard Envoy but still doesn’t work with metered…
And if it works with the standard Envoy, does Modbus TCP (port 502) also need to be enabled by Enphase?
Six months ago, Enphase stated that the Modbus option cannot be enabled on a standard Envoy.
Probably not. I do have a MID certified meter for this. Which is a whole lot faster of course. But it enables me to lower the power to what I want.
Edit: there are values for the lowest, normal and highest voltage. The lowest is 230 minus 5% (219V). The highest is 230 plus 15% (264V). The latter is too high. Should be 253V.
My case involves firmware version SW VERSION D8.3.5528.260506, which I believe has been one of the most problematic releases.
The Modbus TCP service stopped working on May 27, 2026. After contacting soporte_es@enphaseenergy.com, support@enphaseenergy.com, and api@enphaseenergy.com, following Enphase’s instructions, the Modbus TCP service was re-enabled on June 29, 2026, after I provided the IP address of my Victron Cerbo GX. I therefore assume that this procedure is related to security requirements.
However, since the service was re-enabled, the IQ Gateway has been reporting my system as a three-phase installation, even though my installation is single-phase. When I contacted Enphase again, I was informed that the issue was caused by Victron’s interpretation of the data sent by Enphase. However, before the Modbus TCP service stopped working, the system had been operating correctly for approximately one year, and the Gateway was reporting the installation correctly as single-phase.
As of today, I have disabled Modbus TCP data acquisition on the Cerbo GX. As a temporary workaround, I retrieve the production data directly from Enphase using the HTTPS API (with an authentication token). I then use Node-RED to transfer this information to virtual sensors in Home Assistant, allowing the Victron system to use the data.
It is unfortunate that, throughout this process, the information provided by Enphase has been, in my opinion, limited and at times contradictory. In addition, the response times have been excessively long, at least in my case.
