TCP Client & Server - S2-WL-ST Troubleshooting and Config changes about solis-ha-modbus-cloud HOT 9 CLOSED

Touch wood, all good for me. However I've not got round to updating the Waveshare firmware yet so my configuration doesn't match your guide currently. I'll keep a watch on things and check configs etc. Thanks for your diagnostic work!

from solis-ha-modbus-cloud.

Hi @solarjones

While this has been discussed for over a month, I wasn't sure where is the issue and if this is something we should be mitigating. My initial testing with new firmware v1.486 and the Modbus gateway type amended to multi-host non-storage type makes a massive difference to performance.

Can you please confirm this is also working for you?

from solis-ha-modbus-cloud.

I've not loaded the new firmware as yet as I was waiting to see if the other previous parameter tweaks improved things. Dare I say it, but I think it has, as so far I've had no SOC drops or spikes (now I said it, I await it!).

from solis-ha-modbus-cloud.

@solarjones have you just changed the gateway type? or what other parameter tweaks and improvements do you have in mind?

from solis-ha-modbus-cloud.

No I haven't changed the gateway type as yet, only the client configs according to your previous instructions.

I'll try the firmware updates one evening this week. Assuming it resets all configs, is there a known good set of config values to use?
Thanks

from solis-ha-modbus-cloud.

@solarjones if you could try the below setting on TCP Server using the old firmware, it would be great.

from solis-ha-modbus-cloud.

@solarjones I have not experienced any data spiking since 9th June after following the latest configuration guideline

If yours are still ongoing, please follow the same.

from solis-ha-modbus-cloud.

This evening it spiked again. I should point out I've yet to apply the latest firmware as per your guide, but to date, since the last config tweaks we'd previously discussed, all has been well. Until....

I noticed the Backup lightbulb icon was not on the inverter display. Very odd because I'd definitely enabled Backup mode. So I went into the inverter setup, under Storage Control Parameter, and enabled 'Backup'. Within 10 seconds of doing this, I got corrupt data (inspired by one of your previous comments, I've setup an automation to message me when SOC hits zero which has been a constant in this saga of spiky data). To recover, I simply reloaded the Solax plugin. I did not reboot the Waveshares.

This is either a coincidence (doubtful) or enabling Backup mode on the inverter has caused an issue. I also noticed that Backup mode is getting disabled somehow (not by me). I didn't touch any cabling at the time of the Solis parameter change so very puzzled by this.

from solis-ha-modbus-cloud.

@solarjones mine has been stable since the changes I made. Despite a newer firmware (likely related) the key thing for me is the Multi-host non-storage type on the TCP Server

I am also on a higher baud rate just for the TCP Server and the inverter matching 38400. My S2-WL-ST, so the TCP Client is still on 9600.

@jevburchell - Solis confirmed (or maybe just tried to close my ticket) that there is no way to change the baud rate on newer dataloggers S2-WL-ST and S3-WIFI-ST.

from solis-ha-modbus-cloud.