I was thinking of just having X3-MIC in plugin_solax_old as a worse case.
Then new SolaX would have all SolaX & X3-MIC on v1.38+
Might be able to work around it like you suggest though.
If it a workaround is possible it might help with Solis Inverters as they sometimes appear to be unreliable with communications.
I will try to make the adaptation and let you decide whether you accept the PR or not …
Unsure how much time I will need, but on first sight, it should be simple …
I don’t think moving it to its own plugin is a good idea. I think you need to have a mechanism in place anyway, this is probably not going to be the only time a newer firmware will have more registers.
I have merged the code, incase @Kars wants to clone and manually set it up.
As I might not be able to adapt the new attribute tonight and push a new Beta out.
Ok, be aware that the ignore_readerrror declarations are still missing in plugin_solax.py.
So it is recommended to add a ignore_readerror = True statement to the entity with a newblock that causes problems.
Hi wills106 , i received modbus rtu table for Solax EVCharger, i can share it for you.
My friend is using solax inverter g4 and next week will receive SolaxEVcharger and will be happy for integration in HA. EVCharger ModbusRTU
Here is instalation manual: Manual When i looked at it, i think, communication between charger and inverter is only via solax cloud, RS485 interface is free for use. (sorry for my english, i`m from czech republic)
SolaX X3-MIC:
Replaced all newblock = True, with single ignore_readerror = True,
Workaround for supporting Modbus Power Meter registers failing on Inverters without the updated register set (ARM Firmware less than v1.38 (Gen1 only))
Solis:
Implemented ignore_readerror = True, to try and resolve #340#341
Beta 3 Changes:
Generic:
Moved value_function = value_function_sync_rtc, to const.py
SolaX EV Charger:
New plugin.
Doesn’t appear to have time control implement in Modbus yet.
Please use #349 to discus SolaX EV Charger.
I have just released 2023.03.2b8 Are you able to see if it detects your Inverter and returns entities?
I have added in detection for SPH Inverters. If you get an error it can’t detect you Inverter can you provide feedback. I will need the start of you firmware version and Inverter type.
There is no write support yet, it’s just set to read from the Inverter until more testing has taken place.
yesterday I watched this: the system was some hours offgrid. When on-grid again the SolaX EPS Yield Today shows 4,1 kWh (this is ok). But the SolaX EPS Yield Total jumped from 21 to 63 kWh. Why ? 21+4,1 should result in 25,1…?
(my inverter is the X3-hybrid10 G4)
I’m on version 2023.03.01 and just updated from Home Assistant core 2023.3.5 to 2023.3.6, now all my SolaX entities are unavailable. I have the following log entries:
unrecognized inverter type - serial number : unknown
13:05:01 – (ERROR) SolaX Inverter Modbus (custom integration) - message first occurred at 12:40:17 and shows up 2 times
SolaX: cannot find serial number, even not for MIC
13:05:01 – (ERROR) SolaX Inverter Modbus (custom integration) - message first occurred at 12:40:17 and shows up 2 times
SolaX: reading serial number from address 0x300 failed; other address may succeed
13:05:01 – (WARNING) SolaX Inverter Modbus (custom integration) - message first occurred at 12:40:17 and shows up 2 times
SolaX: reading serial number from address 0x0 failed; other address may succeed
13:05:01 – (WARNING) SolaX Inverter Modbus (custom integration) - message first occurred at 12:40:17 and shows up 2 times
After deleting the integration and installing it again with the same settings I have only 4 entities (button.solax_battery_awaken, sensor.solax_inverter_temperature, button.solax_unlock_inverter & button.solax_unlock_inverter_advanced).
Anyone else experiencing problems after this update?