Anyone had Solis remotely update firmware - Waveshare?

[solarjones]

Hi,
I've been successfully using 2x Waveshares (client/server) for a couple of years with HA. All is good. However, my Solis inverter needs a firmware update and Solis haven't been able to remotely establish a connection. Just wondering if the Waveshare setup prevents them from working on my inverter? Perhaps its my firewall setup (they've provided ip/ports to open) but thought I'd check with you guys if anyone has had remote firmware updates in combination with Waveshares.

Thanks!

[alienatedsec]

@solarjones that seems to be the case for me too. Remote firmware updates are not working for my inverter when using Waveshares.

[solarjones]

Bit of an odd one this. After the Solis firmware update, I updated the SolaX HA integration (v2025.08.3). I thought everything was working, however, the Solis app shows the inverter as offline after Initially working in parallel for a couple of hours. HA still receiving updates, just not Solis. Any ideas? Everything had been working flawlessly previously.

[alienatedsec]

Try unplugging your datalogger for a minute.

[solarjones]

Datalogger unplugged, waited 30seconds, reconnected. All the usual traffic lights on, but no data flowing to the Solis cloud. Reports inverter as offline, but data logger online...

I'll bypass the waveshares and plug it directly into the inverter again just to verify it's still working (I ran it this way last week for the Solis firmware update).

[solarjones]

So plugging the data logger directly into the inverter works fine. Switched back via waveshares and it works for approximately an hour before Solis cloud goes offline. The only things changed were inverter baud rate (dropped from 19200 to 9600 at Solis request, I also reflected this reduction on both waveshares) and the Solis firmware update.

Still running at 9600 baud. Perhaps I'll increase it back to how it was originally but can't see how it would work for an hour then drop out on the cloud data.

[alienatedsec]

Run the inverter at the highest possible baud rate. Match it with the TCP Server. The TCP client needs 9600 so your datalogger can communicate.