Solis Firmware 4B00

[fboundy]

Describe the bug

Solis firmware 4B00 introduces a completely new set of registers for time based control. It also adds a target SOC (and a voltage though it’s unclear what this is used for) to each slot.

The old registers are no longer read so the registers used need to depend on the FW version.

I’ve polled the API and Modbus and come up with this list: fboundy/pv_opt#305 (comment)

Integration Version

2024.11.2

Homeassistant core version

2024.11.2

Inverter brand

Solis

Plugin used

plugin_solis.py

Serial prefix

NA

Connection Method

Waveshare

Detailed Error Log

No response

Additional context

No response

[alienatedsec]

@wills106 Is it possible to introduce a switch that uses a new set of registers if, for example, another register represents a specific value?

The input register hex value is part of the firmware version.

The below 33002 is the HMI version - 4A in my case (currently unaffected)

This is usually followed with 00, and combines with the register 33001 the DSP version - 4C in my case - and 33069 both unrelated at this moment - or could be if DSP has any specific function defined.

FW version 33002 + 00 + 33001 + HMI subversion 33069

So, the final logic should be that if the register 33002 is 0x004b or higher, then the new set of registers should be used.

@fboundy @infradom @jmccrohan FYI

[fboundy]

@alienatedsec - I think it might be easier just to use a separate plugin then all the logic will be very similar but a separate set of registers etc

[fboundy]

Should be addressed by #1143

[alienatedsec]

Should be addressed by #1143

That looks ok for now, cannot test at the moment.

@alienatedsec - I think it might be easier just to use a separate plugin then all the logic will be very similar but with a separate set of registers etc

There would be a period for maintaining two sets of solis plugins. I guess the new registers will not be changed moving forward.

[fboundy]

I've been running this for a few days now. The integration works but the firmware is buggy. The time slots can appear set but they don't start working until the SOC is changed.

[alienatedsec]

@fboundy
I got the new firmware files from Solis, but I am delaying to load them. I also believe it's a newer version than 4B00, so I guess I will have to decide at some point.

[fboundy]

I was told yesterday that 4B00 is still the latest

…

On 26 Nov 2024 at 10:03 +0000, alienatedsec ***@***.***>, wrote: @fboundy I got the new firmware files from Solis, but I am delaying to load them. I also believe it's a newer version than 4B00, so I guess I will have to decide at some point. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[wills106]

If the Firmware was read at the same time as the Serial Numer then it should be possible to use the unused GEN block to split it up?

If lower than y = GEN if above x = GEN2?
Depends how the version numbering works as a whole really on Solis.

[fboundy]

The differences between the f/w setups are so significant that I think it is simpler to simply use a different plugin as has been done for other brands

[alienatedsec]

The firmware needs to be read in either plugin as it would be the condition for correct functionality. It's no longer just a Serial Number dependency.