I operate an Anker Solix X1 PV system, which I have integrated into Home Assistant using the well-known HACS integration.
Basically, the whole thing works reliably, but the update interval is rather opaque due to Anker’s cloud requirements and, for my taste, much too slow—the “live” data is only updated every 30–90 seconds. In addition, the connection is completely dependent on the Anker cloud, so Home Assistant no longer provides data as soon as it goes offline.
Since the X1 has Modbus TCP, I have now activated this interface and have already experimented with it a little.
Basically, I got the Modbus connection up and running, but some of the values read out are still implausible at the moment. However, all controlled points can be read out and addressed.
Perhaps there are others who are interested and we can connect to get the integration running perfectly.
I am attaching my Modbus Yaml file, which you are welcome to use for yourselves.
I am getting an Anker X1 system installed in a few weeks. I will probably follow in your footsteps regarding HA integration.
Interested to know for the Modbus TCP configuration in the Anker solix X1 system, did you have to get the installer to enable it, or could you do it as an end user.
Please explicitly inform your installer that you would like to have this feature activated.
It is not part of the standard commissioning process, but can be activated by the installer with a single click in the Anker Professional app.
@Freacly do you have to have your X1 system wired with an ethernet connection to communicate with the modbus? Or is it connected over wifi? I have organised with the installer to enable the modbus communication, however under the modbus settings it is reporting the IP address as 0.0.0.0 (even though I know it has an active wifi connection, and what the IP address should be). Did you experience anything like this?
For anyone else stumbling across this issue, I have confirmed with Anker that currently an Ethernet connection is required to enable modbus. Not sure if this will change in the future, but that is current state.
@Freacly can I ask how you got the addresses you’re using in the example yaml file provided? I can see that some are quite different from the documentation; however I am also finding the documentation is not entirely accurate… Happy to work on getting a fully usable integration here
I just found this after slapping together my own yaml with all the modbus addresses.
Have you also found that both “Solix X1 Total Load Consumption Energy” (10030) and “Solix X1 Total Feed-in Energy” (10034) resets daily, just like the daily registers?
I would ask if there is a firmware update to enable the modbus address to be changed for each inverter so you can make them unique. Modbus is quite capable of supporting many devices, as long as the address of each device is unique. Are you sure their software doesn’t have this capability already?
At the same time, they may be able to remedy the issue with the inverter totals resetting daily.
I’ve gone through the setup with a local support personelle using their support account. There is no Modbus selection available.
I was later told that there is no current support for modbus when there is more than 1 inverter in use. My current setup has 2 inverters in master/slave configuration. I am wondering whether the master/slave configuration is using modbus as the communication protocol between the 2 inverters.
The local support is not able to offer me further instruction or explanation, which is disappointing.
You got problems. Local support cannot resolve them. Ask for it to be escalated higher up. Shout loudly on their user tech support forums. Speak with your installer. Otherwise squeal ‘not fit for purpose’ and ask for warranty money back under consumer protection laws. That should clearly focus them as money doesn’t talk, it shouts.
Curious to hear if you’ve managed to integrate this in a way where you can set the batteries to discharge to the grid? I see in the YAML file there are some of them that is configured as “holding”, which I think means you can write to it
Also, heads up - I just updated firmware from 1.0.13.12 to 1.0.15.6 and both 10030 and 10264 appears to have been fixed and is not resetting to zero anymore.
It sounds like the modbus still has a couple of issues that Anker has to resolve, and you should really push Anker Support to make local Modbus usable for all system constellations.
While not a local Interface, I think all constellations and devices can be monitored and managed via the cloud MQTT servers. It may provide more capabilities than Modbus will ever provide, but relies on the cloud and reverse engineering of the MQTT data and commands from the community.
If the will be described properly through the anker-solix-api library, it can be picked up in the HACS integration as well.
The V1 EV Charger may have similar issues with its modbus interface and I heard that the operational mode cannot be controlled via Modbus. This however is possible via MQTT cloud and will be available with the next HA integration release in April time frame.
I’m curious about this, too. I’m currently considering the Solix X1 for my house solar, but I want to make sure I choose a system with good integration that includes control, not just monitoring.