Solis inverter stays initializing, one other offers limited control #142

Activity

1. mkuthan commented on May 30, 2026

   

   mkuthan

   on May 30, 2026

   Owner

   More actions

   I'm new on HA but have managed to load all my devices into HA. This including my two Solis inverters. I've let Solis suppert enable the API's and installed the cloud control Integration via HAC. So far so good. But the smaller and older inverter (2019) gives an initialization error. The larger one (2023) does not but only shows limited entities (on/off, date &time, max load). Nothing else. No control items. Both inverters are connected via a WiFi stick (s3-wifi-st for the larger model, the smaller one and S2 I think)

   I've consulted Solis support for de smaller one that stays initializing. Wanted to find out if that firmware supports api control. I did get an answer but only the suggestion to seek support in the HA community.

   Hahaha, Solis support asks HA community about support for their own API in their own products. So nice.
   The integration supports all inverters supported by the official Solis Cloud API.

   My questions:

   * is the older model unsupported by the HA solis Integration?
   

   I don't know. It could be incompatible firmware, or data logger or inverter itself.

   * is the age and firmware level the cause of limited control option from HA.
   

   S5-GR3P is a string inverter, so the control part is limited as documented in the project readme.
   Most likely you are looking for monitoring part, use: https://github.com/hultenvp/solis-sensor/

   * any suggestion on how to gain more control options? Via RS422?  (New to me). And what control functions can I expect than?
   

   I use solis modbus integration for real-time monitoring and this integration for controlling hybrid inverter, see: https://github.com/mkuthan/solis-cloud-control/#can-i-use-this-integration-together-with-local-modbus-integration

   See the screenshot below for more info Maybe someone can give me some guidance?

   Thx, Hans
   
2. Repository owner locked and limited conversation to collaborators on May 30, 2026
3. mkuthan

   converted this issue into a discussion #145 on May 30, 2026