MartinViljoen

I managed to resolve the issue. I didnt have the clamp the right way around, my mistake! Its now facing the grid. Also I didnt know i needed to change the System mode to "Limited to Home" , initially when i enabled Limited to home with the CT facing the Inverter it gave weird and negative values.

My 5kW Sunsynk inverter has been operating without any issues since 2023. The non-essential load (Home Load) has always displayed as 0W, while the UPS load typically shows between 500W and 800W, which is expected. My understanding is that the Home Load remains at 0W because the CT clamp was originally installed just before the cable enters the inverter, with the CT arrow pointing towards the grid. I mapped out my DB and inverter connections, as shown in the attached diagram. Based on recommendations, I moved the CT clamp from Position 2 to Position 1, as indicated in the drawing. The inverter was completely powered down during the change, so it performed a full reboot afterwards. Despite moving the CT clamp, I still cannot see any non-essential load being reported. The sub-DB and geyser loads remain completely invisible on the Sunsynk flow diagram. Is there a setting that needs to be enabled for non-essential loads to be displayed, or should this work automatically once the CT is installed in the correct position? I have also logged a support ticket to have the inverter firmware upgraded in case this is a firmware-related issue.

There was an issue with the Addon today , SunSynk enhanced their security and the addon had to be adapted. https://github.com/martinville/solarsynkv3/issues/48#issuecomment-3576239133 If you wont write settings back , You can just ignore the message it wont do any harm. But if it bothers you just create the Helper entity.

Go to Settings --> Devices and services -- Helpers Tab Create new helper, select "Text" as the type and call it solarsynkv3_********_settings be sure to replace the redacted text with your inverter serial. Entities created via the API are static and unmanageable, therefore it requires you to manual create it.

An Addon is a docker. Almost like a VM but not quite. ;-) You dont need hacs, you simply add the repository, refresh you list of addons and install from your addon-store. I stopped mapping entities between the addon and the slipx card. Reason is simple, too much work to maintain it. 😁 Besides its not possible to provide a direct copy and paste without intervention due to the serial number mentioned in the entity. With regards to old entities. Make sure the entities are no longer updated by stopping the addon. then give the system a full reboot. Make sure addon is not set to auto start else it will appear as if they were not removed because it will repopulate the entities after reboot. (Best to un install the addon)

Hi. Yes there was an issue earlier on. Looks like Sunsynk is preparing to use a more secure authentication method. Both new and old Auth method is now working again. I suspect that soon the old method will be phased out. FYI when that happens the v2 integration will most probably stop. I don't maintain the repository anymore. V3 on the other hand has already been adapted to the new Auth method. Once the old methos is phased out the new end point will most probably take the place of the original which will again cause a hiccup in V3, but it will be a super quick fix.

Hi There. Yes its been running for quite some time already --> https://github.com/martinville/solarsynkv3 Also fully supports sending system mode and battery settings.

Not quite sure. This is bash script and i dont have much error control in it so when ever there is an unexpected string or int encountered it will give this kind of error. But looking at your log I suspect you have a semicolon at the end of your inverter serilal numbers. I.E Serial1;Serial2; Serial1;Serial2 , So its parsing Serial1 Serial2 then a blank serial ? Seeing there are many request for better error control , sending settings ect I decided to re-create the addon using python which will be much better. Its almost done i'm in the process of testing it and adding the ability to send settings then I will make it available. instead of

Unfortunatly not. I havent realy given it thought yet, I dont use this addon anymore I make use of modbus over serial.

I think I know what you mean now. Since the original post further developments were made. On the SlipX card there is now a GUI, all you do go to each datapoint and search for the entity you want in order to link it. You can also offcoarse opt to manually edit the SlipX configuration yaml file if you wanted to. (Not to be confused with Home assistant's configuration file) I.E What I meant in the first post was I named the entities to be similar to the slipx card (On a developer level) so its easy to map them. As a user you cannot change them. The naming of both addon and card also later changed slightly so its not relevant anymore.

I'm not 100% sure what you mean. How would I now get a nice flow chart or something similar to what Slipx has? Are you having problems installing the SlipX card via HACS ? Cause from first post in this discussion I thought I would just be able to change the name of the sensor but what I can see there is no sensor if its not configured in the configurations. So should I then add stuff in my configuration.yaml? You dont have to fiddle with the configuration.yaml The SolarSynk Addon will send which ever values it found to a predefined entity. The naming convention is Example sensor.solarsynk_[INVERTERSERIAL]_battery_power1 You cannot rename them, unless you clone the repository and edit the run.sh file. But I dont see any reason to do that. The SlipX card and the SolarSynkv2 Addon are totally 2 different developments and are not directly related in any way. SolarSynk Addon - Fetches information from your Sunsynk Cloud Account and then populates entities with values. Doesnt do anything else. SlipX Card - Is used to graphically display the entity information on a nice looking card on your HA dashboard. You dont have to use the slipX card there are some of the boring default HA cards you can also use.

It should be fixed now in the new update, the sunsynk server issues is still causing the auth token to not be handed out reliably. But to fix this I added a check in place for the script to keep retrying until the server gives a valid token.

Yes ,just put multiple serial numbers in the serial field separating them with a semicolon ; I.E 12345;54321

No thats should be it 😉

Thanks, I fixed the error. If you update it will hopefully not show the error anymore. With regards to the update rate. You also have to set the update rate to 60s on the sunsynk portal.