Many Unknown values for Q-Cells/Solax with serial H34C12Ixxxxxx

[plu]

Some values are working, for example the serial number, and some of the setters are also working. But most values just show up as Unknown. I've enabled the debug log and attached the log file here:

home-assistant_solax_modbus_2023-11-03T07-54-57.286Z.log

I'm connecting via ModBus TCP. The COM-Port is exposed via TCP using some ESP8266 using Tasmota's ModBus TCP Bridge.

The inverter reports following version:

• DSP-Version: 2.07
• ARM-Version: 2.03

HA version:

• Home Assistant 2023.10.2
• Frontend 20231005.0 - latest
• homeassistant-solax-modbus - just checked out the git repository at 85a6117

I'm not even sure where to start debugging this further without any help, would be great if somebody could give me some pointers. If there's more information that I could or should provide, please let me know.

[wills106]

Do they look like the bottom two?

Then when you click on them...

If so look at point 1 https://github.com/wills106/homeassistant-solax-modbus#faq

[plu]

I'm still confused why I only see two ModbusReceived every time the plugin connects to the bridge. Maybe my next step should be to add some debug logging to Tasmota to also log what values it's actually sending onto the bus.

[plu]

Thank you for all your help so far, and for developing and maintaining this plugin!

[plu]

from pymodbus import pymodbus_apply_logging_config
pymodbus_apply_logging_config("DEBUG")

I've added this now to custom_components/solax_modbus/__init__.py, and the logs produced by this are looking all just fine to me: pymodbus.log

If you spot something unusual, please let me know. I've tried to mask some of the response by replacing values with ..............

The way I understand your plugin so far is that the model is being detected by the serial number, right? I'm wondering if that's what might be going wrong in my case, that it picks the wrong model and then uses the wrong modbus addresses?

[plu]

Looking more closely again at the logs I've noticed this:

[pymodbus.logging] Not a valid slave id - 0, ignoring!!

Not sure how much that might play a role...

[plu]

Got some Waveshare adapter yesterday, and now everything works \o/.

If I'm really bored, I might be poking around again with Tasmota, as I'd prefer that solution, but for now we can say "case closed". Thanks again for your help and for making this plugin!