Unrecognized Inverter - SolaX

[wills106]

If you get the following error in your log:
"unrecognized inverter type - serial number : {your_serial_number_here}"

Please list below the first 6 digits here including the Inverter type and kW rating and which plugin you got a response with.
I can then add in your Inverter.
Please do not raise an issue in addition.

If you get unrecognized XYZ inverter type - serial number : unknown you don't have a working Modbus connection.
Don't raise an issue, this isn't a fault of the Integration.
Either use one of the existing discussions or start a new one, don't comment in this discussion about unrecognized XYZ inverter type - serial number : unknown

[MartinPicman]

Hi, here is it: Solax X3 Hybrid 10.0M, ser. n. begins: H34B10

[wills106]

How are you trying to connect? RES485-Ethernet, RS485-USB, PocketWiFi? You don't have a working Modbus connection.
If PocketWiFi have you read https://github.com/wills106/homeassistant-solax-modbus#solax---pocketwifi-readme

[MartinPicman]

I use modbus connection over TCP by Waveshare (RES485-Ethernet) for more than 5 month. Wifi pocket was very unstable.

[MartinPicman]

hmm, smthng magic inside of HA modbus. I have my own integration of modbus for recuperation unit which is not supported. Last change I did on Wednesday. And yesterday morning I saw 1st trouble with Solax. I restarted HA and it was ok. Then I appied HA core update and then your update to 9.3. And that raised an issue. Now, after our discussion, remove my own modbus lines in configuration.yaml, restart HA and TaDa .. Solax is back. I put my modbus integration back to configuration.yaml, restart HA, and both are still running :-). I'll check the HA core updates what they did ...

[wills106]

Might be related to #528

[MartinPicman]

Hi, HA 2023.9.2 and your Solax modbus integration 9.4 fully solved this issue.
Thanx a lot.

[romankysely]

Hi wills106, please add this SN to invertor.
Thank you and let me know how can I buy the coffe to you. You are doing great job.
Roman

This error originated from a custom integration.
Logger: custom_components.solax_modbus.plugin_solax
Source: custom_components/solax_modbus/plugin_solax.py:5327
Integration: SolaX Inverter Modbus (documentation, issues)
First occurred: 2:49:36 PM (3 occurrences)
Last logged: 3:03:13 PM

unrecognized inverter type - serial number : unknown

HA version: 2023.9.1
Integration version: 2023.09.3
Inverter Master+Slave: X3-Hybrid-G4
Inverter Master+Slave S/N: H34A12 12kW
Interface: Waveshare RS485 TO POE ETH (B)

[romankysely]

Could You react Will? Thank you, I sent you some cups of coffes :-)

[wills106]

Have you seen #528 HA 2023.9.1 introduced a pyModbus change. The Beta Integration 2023.09.4b5 has resolved that. So I would update to that first.

Edit: Your Inverter is already supported. But you don't have any communications between your Inverter and Waveshare. If 2023.09.4b5 doesn't resolve your connection issue, double check your settings vs the Wiki.

[romankysely]

Thank you Will. The problem was in modbus addresses at invertors. I had Master and Slave both on the number 1. When I changed Slave modbus address to 200 and gave RJ45 to COM of the Slave I have got data immediately. May be good hint to Wiki in case of more invertors. Interesting is that both Master and Slave were working fine on the Modbus with same address before.
The second problem probably was in SolaX Invertor Modbus modul in Configure/TCP/IP Parameters. There I choose Modbus RTU over TCP instead Modbus TCP. BTW it seem that is doesn't matter where is RJ45 connector connected. Master ort Slave COM port. Are the Entities are consolidated for both invertors when I have checked Parallel Mode (Master-Slave) option ? Many thanks for help.

[HeinzDanny]

ich bekomme auch die fehlermeldung
"unrecognized inverter type - serial number : {your_serial_number_here}"
hier meine daten
Solax X3
8,1kw
Serien Nr.: SRB4S2Y
Plugin SolaX Wechselrichter Modbus

[Maska9]

Hi, here is it

errors:
unrecognized inverter type - serial number : unknown
cannot find serial number, even not for MIC

HA version: 2023.9.2
Integration version: 2023.9.4b5
Inverter: X3-Hybrid-G4
SN 6-digits: H34A10

thx ;)

[infradom]

Did it work before 2023.9.2 ?
Which adapter do you use (Ethernet, USB, ..) ?
Have you tested removing the integration, reboot HA and reinstall the integration ?
Do you use other Modbus devices ?
It is hard for us to help without this information

[Maska9]

yes everything worked before installing HA 2023.9.2 (Solax modbus was version 2023.9.3).
I am connected via WiFi dongle and modbus/tcp.

After installing HA 2023.9.2 the modbus stopped working and shows the mentioned errors.
I removed the integration, tried to install version 29.9.4b5 and then found this post where to send 6 numbers from SN.

I don't have any other modbus devices

[wills106]

Your Inverter is already supported as it's previously worked.

I would install Integration 2023.09.4 that I released earlier today. Also check the Readme for advice on trying to get the PocketWiFi working again. They aren't exactly the most reliable connection method.

[Maska9]

Thanks a lot for the direction.

I removed the integration again, installed version 2023.9.4 and disconnected pocketWifi for a minute. After the new addition, everything works as it should again.

[thb2602]

Hi wills106, all,

I have a Q.Cells QHome ESS Hyg G3, aka Solax X3.
I'm also struggling now to get modbus working with my waveshare after it had worked already ~6weeks ago.
The inverter was turned off for more than a months because my energy meter is not yet replaced.
After turning it on I only get home assistant with modbus working via the wifi dongle.

Last time I got it working was when after several tries also wifi didn't work anymore and I found a forum comment from wills,
that the inverter allows only one modbus connection. After a power cycle I was able to connect to the waveshare and it
worked for weeks.
This process doesn't succeed anymore and I just tried a power cycle even with wifi dongle disconnected.
Any hint/idea?
My serial begins with H34C10

PS: Latest Solax integration updates and HA updates have been installed.

thanks and best regards,
Thomas

[bennybauer1978]

Hi Wills106, thank you for your efforts

I try to connect My Solax X3-Mic-5k-G2 with the following error message: "unrecognized inverter type - serial number : MC205TI819XXX"

please add this Inverter

Thank you and best regards,

Benjamin

[bennybauer1978]

It is a three phase, 5kw Inverter. Using latest solax Inverter modbus from hacs

[wills106]

Thanks just added into 2023.11.1

[jankorous]

Hey, I have a question - is that solved? Because today I've updated HA and Modbus module and any entity's lost...

My SolaX X3 10K G4 Hybrid, SN SRBP6C...

[jankorous]

Ok, I will wait until it get solved... or buy another way to connect inverter with HA

[cleveHEX]

PocketWiFi upgrade is described in readthedocs well, even fw repo, you most likely did not read the version properly, just look at pages Will sent you (I have never seen dongle with the oldest fw, they are very rare). Make sure you have a static IP set. If you didn't look, it's https://homeassistant-solax-modbus.readthedocs.io/en/latest/solax-faq/

PS. Will, can you turn off the Wiki tab in repo settings, so I can refer to RTD as wiki? It should not erase it, just turn it off.

[jankorous]

After a second HA hard reboot, the modbus started providing data again. I thought multiple restarts only solved problems with windows os...

But... The firmware is downloaded, but I don't know if I will update because there is a saying: if it works, don't fix it.

[cleveHEX]

Well obviously there is some kind of problem, so it does not work properly, probably something about your setup. With this philosophy we would be still using rocks and sticks.

[jankorous]

Well, I think technological progress depends on people's laziness... :D Anyway, I will go through the settings after updating the module and the inverter

[zidekm]

Hi,

would be possible to add my inverter.

SN : MU602T
Model : X3 MIC G2

Thanks

[zidekm]

i forgot 6KW

[Deedsy]

Hello Mr.Wills106 and thank you for your work with this integration SW.

I'm trying to connect My Solax X3-Mic-6k-G2 with HA SolaX Inverter Modbus v2023.11 but I'm getting the following error message: "ERROR (MainThread) [custom_components.solax_modbus.plugin_solax] unrecognized inverter type - serial number : unknown"

Can you please add this inverter.

Thank you

[Deedsy]

SN: MC206TIXXXX

[wills106]

Your Inverter is already supported, you have no working Modbus communications with the Inverter

[abaretta]

Hi,

I have a Solax X1 Boost 4.2 (X1-4.2-T-D) with SN: XB4221XXXXXXXX which is connected through RS485. The integration is able to pull the 'registration number' from the invertor which leads me to believe the modbus connection is working. However I am guessing the registers are different as for the other entities the status is 'unavailable'.

If support could be added for this type of inverter it would be awesome :-)

Thanks in advance.

[wills106]

Do you know what address the Inverter is returning the Serial number on?

Do you get an error that it failed at address 0?

homeassistant-solax-modbus/custom_components/solax_modbus/plugin_solax.py

Lines 65 to 68 in 1cef574

	except Exception as ex: _LOGGER.warning(f"{hub.name}: attempt to read serialnumber failed at 0x{address:x} data: {inverter_data}", exc_info=True)
	if not res: _LOGGER.warning(f"{hub.name}: reading serial number from address 0x{address:x} failed; other address may succeed")
	_LOGGER.info(f"Read {hub.name} 0x{address:x} serial number before potential swap: {res}")
	return res

Depending on how you have setup your logger you should also see

[custom_components.solax_modbus.plugin_solax] Read SolaX 0x0 serial number before potential swap:
Or Read SolaX 0x400

[abaretta]

Thanks for the quick response 👍 It turns out I had a conflict between two identical RS485 converters. It seems at some point the Solax integration was at least able to pull the registration number and create a hoist of entities, but that appears to have been a fluke. I can't reproduce it. Anyway, I resolved the USB conflict and am able to poll the inverter directly from the server (using Solaxd):

2023-12-08 10:41:05.290 [TRACE] ComTx: AA 55 01 00 00 0A 11 02 00 01 1D
2023-12-08 10:41:06.290 [TRACE] ComRx: AA 55 00 0A 01 00 11 82 32 00 12 00 00 09 AB 04 E1 00 01 00 01 00 08 08 E3 13 89 00 31 FF FF 00 02 29 18 00 00 56 4D 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08 22

The ID of the inverter appears to be '00 0A' corresponding to device 1 on the bus, correct? I now get the following logging from the HA integration (running in docker with a device mapping):

2023-12-08 11:06:03.117 INFO (MainThread) [custom_components.solax_modbus.plugin_solax] Read SolaX 0x0 serial number before potential swap:
2023-12-08 11:06:03.118 ERROR (MainThread) [custom_components.solax_modbus.plugin_solax] unrecognized inverter type - serial number :

Thanks!

[wills106]

It's possible you still don't have a fully working Modbus connection if the Integration has previously returned your Serial Number correctly.

You can assign the USB-RS485 by the usb-id #513 (comment)

Which gets around the ttyUSB0 / ttyUSB1 issue you can have.

[abaretta]

I do indeed have the correct device mapping based on the device ID. However, what is different is that the inverter is now connected together with an Eastron SDM220 to the same USB RS485 converter, exactly like the setup mentioned in the X1-Boost, X1-Mini, X1-Air modbus documentation thread. I can successfully poll both the SDM220 as well as the inverter from the server through the same USB device.

There's an error popping up in the log that I didn't mention as it appeared to occur after the failed serial number detection, but now I notice it happens right before/during the serial number detection. I don't know if that's an issue or not for the setup process?

Never mind, I see this is a known issue (nr. 2, the async issue, I have added the logging filter).

I now get the error you mentioned above:

2023-12-08 20:07:34.613 ERROR (MainThread) [custom_components.solax_modbus.plugin_solax] unrecognized inverter type - serial number :
2023-12-08 20:07:57.498 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX: reading serial number from address 0x0 failed; other address may succeed
2023-12-08 20:08:02.165 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX: reading serial number from address 0x300 failed; other address may succeed
2023-12-08 20:08:02.165 ERROR (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX: cannot find serial number, even not for MIC
2023-12-08 20:08:02.166 ERROR (MainThread) [custom_components.solax_modbus.plugin_solax] unrecognized inverter type - serial number : unknown

And I think solaxd connect to the inverter at address10 not 1 (00 0A), although it doesn't seem to make a difference when I use that as the modbus address.

[mameli1]

Hello
X1-Hybrid-G4 6kw
SN inverter H4602BHB xxxxxx

ERROR unrecognized inverter type - serial number : unknown
connected with Pocket wifi 3.0 FW Pocket_WIFI_V3.010.16

I see only 4 entitier
Thanks very much
Paolo

[wills106]

You don't have a working Modbus connection. Your Inverter is already supported.

[mameli1]

Thanxs a lot for quick resp.

So Pocket_WIFI_V3.010.16 is not working.
I have to install WAVESHARE serial to ETH
Can you confirm this ?

Best regards
Paolo

[wills106]

If the Waveshare is this version, it will work if setup correctly and is the prefered method.
https://homeassistant-solax-modbus.readthedocs.io/en/latest/modbus-adaptor-setup/#waveshare-rs485-to-eth-b

Have you tried unplugging and replugging in the PocketWiFi?
They can be temperamental.
https://github.com/wills106/homeassistant-solax-modbus#pocket-wifi-30-with-firmware-v300403-and-above-is-only-officially-supported-solax-only-mentions-gen4-hybrid-other-inverters-may-work

[Womble1962]

SolaX X1 AC 3.6

2023-12-31 18:35:21.419 ERROR (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX: cannot find serial number, even not for MIC
2023-12-31 18:35:21.419 ERROR (MainThread) [custom_components.solax_modbus.plugin_solax] unrecognized inverter type - serial number : unknown

XAC362F (I think)

I have 2 entities showing

Modbus Waveshare with 3 lights on red green (which changes blue every 10 seconds) and blue

[Womble1962]

I have pinged my Waveshare in the terminal window in HA and it returns as connected

So looks like my Waveshare is connected to Homeassitant ok

Now I have another port on my inverter that the modbus reader is plugged into by RJ45 this is for the meter (C on the manual). I f I unplug that I get an inverter error.

Yesterday I plugged my PC into Port 485 on the inverter directly with a network cable and the inverter shut down, so the 485 port on the inverter must do something.

I have my Waveshare plugged into the port arrowed H RS485

My batteries are in I

My Modbus meter is in C External meter Port

I have just bought new network cables and replaced them 3.5 metre cable from inverter to Waveshare, 0.4m cable to Wifi Extender

[wills106]

Yesterday I plugged my PC into Port 485 on the inverter directly with a network cable and the inverter shut down, so the 485 port on the inverter must do something.

You are lucky you haven't damaged your PC or Inverter doing that.

Just because they use an RJ45 connector doesn't mean they are Ethernet.

[Womble1962]

I realise that now.

I meant to plug the Waveshare into the network port to check that the wifi was not stopping us connecting, but plugged the inverter cable in by mistake.

We were trying to get our Eastron 100 amp meter to work as well but I think we are going to a ct type instead as it is not safe how it is installed now as the 60amp meter is basically the fuse as we have a 100 amp fuse outside. Should never of been installed like that.

[Womble1962]

Does this help?

How much coffee do you require?

[Womble1962]

This error originated from a custom integration.

Logger: pymodbus.logging
Source: custom_components/solax_modbus/init.py:350
Integration: SolaX Inverter Modbus (documentation, issues)
First occurred: 6 January 2024 at 5:58:12 pm (274 occurrences)
Last logged: 8:58:36 pm

Connection to (192.168.1.83, 502) failed: [Errno 111] Connection refused
Connection to (192.168.1.200, 502) failed: [Errno 111] Connection refused
Connection to (192.168.1.200, 502) failed: timed out

Still struggling

I have changed my baud rate on my inverter and the port to use and set these up in the Waveshare

Should my destination be set to 192.168.1.38? with 4196? and not 502?

Obviously a comms problem now.

When you change the baud rate in the inverter do you have to shut it down and restart it?

[darksider90]

Hello
X1-Hybrid-G4 7.5kw
SN inverter HH4752AI96xxxxx

ERROR unrecognized inverter type - serial number : unknown

thank you and happy new year ;)

[cleveHEX]

This means your Modbus connection is not working.

[darksider90]

Hi,
i'm deseperate :( Because the led is blue when HA read information. I check in the inverter and the speed is ok (at 9600). In the web portal of rs485 eth (B), i check and configure with the same . But i have the same message.

Could you help me ?

[cleveHEX]

iir the baud rate on inverter might be for power meter, see https://homeassistant-solax-modbus.readthedocs.io/en/latest/baudrates/ for one that might work

[darksider90]

Yes ! it's ok. The pb is on the number of the modus ID. In the inverter, it's at 2 :/ . After replace by ID1, rock and roll :)

For information, if you want to modify this, it's an obligation to connect with a installator password : 2014

Thank you for your Help

[Womble62]

Wonder if I change mine from 1 in the invertor to 2 it might work for me.

[kupfi1212]

Hi,
in my Home Assistent I found the error "unrecognized inverter type - serial number : unknown"
Typ: Q.VOLT_HYB-G3-3P - 10kW
SN: H34B10I23xxxxx
Pingtest from a terminal from Home Assistent to WaveShare is ok, but Waveshare-Link-LED is "green" everytime.
Thank you and happy new year :-)

[superdafi1979]

I found it. I'm testing it now.. Thank you

[superdafi1979]

Logger: custom_components.solax_modbus.plugin_srne
Quelle: custom_components/solax_modbus/plugin_srne.py:65 Integration: SolaX Inverter Modbus ( Dokumentation , Probleme ) Erstes Auftreten: 08:26:22 ( 2 Vorkommen) Letzte Protokollierung: 08:26:28

Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht

Logger: custom_components.solax_modbus.plugin_srne
Quelle: custom_components/solax_modbus/plugin_srne.py:452 Integration: SolaX Inverter Modbus ( Dokumentation , Probleme ) Zuerst aufgetreten: 08:26:28 ( 1 Vorkommen) Letzte Protokollierung: 08:26:28

PowMr3: Seriennummer kann nicht gefunden werden, auch nicht für MIC

PowMr3: Lesen der Seriennummer von Adresse 0x0 fehlgeschlagen; Eine andere Adresse kann erfolgreich sein
PowMr3: Lesen der Seriennummer von Adresse 0x300 fehlgeschlagen; Eine andere Adresse kann erfolgreich sein

[superdafi1979]

I have the problem, he always downloads the previous version..

[superdafi1979]

[superdafi1979]

[superdafi1979]

[wills106]

You probably don't have the Beta option ticked. https://hacs.xyz/docs/faq/beta

[superdafi1979]

[wills106]

That's the one you need to install.

[Matthiasvoigt1]

Hi,
would be possible to add my inverter.
SN : MPT15Txxxxxx
Model : X3-MIC/PRO-G2 15KW

Thanks

[wills106]

Should already be supported, try the latest Beta 2024.07.0b5

[MiRe-CZ]

Can you please add the inverter below:

Inverter model: X3-PRO-25K-G2
Inverter S/N: MPT25R...
Integration version: 2024.05.7
HA version: 2024.7.2
Error: "unrecognized inverter type - serial number : MPT25R..."

Thank you
BR, Milan

[wills106]

String Inverters only expose 30 - 40 or so useful entities.

I can have another look to see what control options there are, but string Inverters are normally set to maximum export to generate as much money as possible.

[wills106]

What value does "Active Power Limit" return?

[MiRe-CZ]

"Active Power Limit" gives 27500W (inverter is 25 kW and limit is currently set to 17500W) and it is the read only sensor. [NeeoTheOne] confirms similar status (see below in his individual comment)

It would be good to have some controls - in fact the most crucially needed one is the export control as spot prices are often negative and modifying the export limit via the Solax application manually is annoying

Thank you
BR, Milan

[wills106]

I think I have found the corresponding write register for that limit. I'll release an update later today.

[wills106]

Just released 2024.08.7 Set the upper limit to 30,000W. Should cover all MIC's and MIC Pro's.

But you probably can't set it to a value larger than it's capable of.

[ash-dz]

Can you please add this one too?

Model: X1-SMART-G2
Serial Number: XSTC10K
10kW model
SolaX Modbus Ver: 2024.05.7 (also tried with 2024.07.0.b2)
HA Ver: 2024.7.3

[ash-dz]

Heya, so I updated and PV3 is showing 0w (and perhaps interestingly a static 0.1A that doesn’t change)

also, the CT number will jump to 65,000w+ for a period during the day, and then go back to correct readings per the inverter screen readout.

any thoughts/tips? I’ve tried removing, uninstalling and reinstalling and setting up and same result the next day.

[ash-dz]

I wish there was some kind of documentation of what the correct registers are - as I’m assuming it’s not got the right ones for PV3 yet.

The CT thing is a weird one - it seems to only go up to that crazy high level when running, and not during in the ‘waiting’ state which I find weird too, but might make sense so I’m sharing here 🤷‍♂️

[shockerchocker]

I've not read everything about this plugin, so excuse ignorance, but assuming it's like the return from the get live data POST, i've got PV1 v10/PV2 v10/pv1 amp10/pv2 amp10/PV1 power/PV2 power in columns 5 through 10. For string 3, it's 71-73 for PV3 v10/a10/power.

[shockerchocker]

sorry, the v10 / amp10 was voltage times 10 etc.

[wills106]

Is PV3 Still an Issue on the X1 Smart?

If so could someone raise it as an Issue, so it doesn't get lost in the "Unrecognised" thread.

[jfh75]

Hello,

Sorry for the issue, I closed it.
Could you please add
SolaX X1 boost 3kw
serial XAU302
solax modbus 2024.05.7

It's working perfectly with my solax hybrid G4 with batteries !

Thank you for your help,

JFH

[jfh75]

I have searched my invoice and it says X1 AIR and not boost, on the notice, they explain at beguinning X1 is type, 3.0 is power, S = single MPPT string, D= with DC switch, (L) = LCD display. As I thought, it is older type. I bought it in 2021.
Does this help you ?
X1 AIR doesn't exist anymore it seems.
Thank you for your time ! :=)
JFH

[wills106]

Just released 2024.07.0b5 I have added it the same as a G3 Boost for now. But yours will only return the first MPPT string. I'll need to look into removing PV2 on yours.

[jfh75]

Thank you very much. I don't think it is a problem, and Solax doesn't even bother because indeed, on solaxcloud.com, there has always been PV1 and PV2. And PV2 is far far away from producing anything ! It is stuck to 0. They use one template !
Thank you I try like this :-)

[jfh75]

ok so I tried and it's worse. On modbus side, I see one way traffic only now. And no inverter serial appearing anymore in the Home assistant logs like the one i posted in my closed issue.
What has changed also in the logs is that before, calling 0x0 said no answer, and then it was trying calling 0x00 then he was getting Serial number.
Now, it just calls 0x0.

       ^^^^^^^^^

pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Client is not connected
2024-08-02 17:49:39.448 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX_Cabanon: reading serial number from address 0x1a10 failed; other address may succeed
2024-08-02 17:49:56.148 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.0x385b44fffe93c0e8_over_current_threshold: 0 (range 1.0 - 64.0)
2024-08-02 17:49:59.453 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX_Cabanon: attempt to read serialnumber failed at 0x32 data: None
Traceback (most recent call last):
File "/config/custom_components/solax_modbus/plugin_solax.py", line 89, in async_read_serialnr_alt
inverter_data = await hub.async_read_input_registers(unit=hub._modbus_addr, address=address, count=8)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/solax_modbus/init.py", line 557, in async_read_input_registers
resp = await self._client.read_input_registers(address, count, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pymodbus/client/base.py", line 183, in async_execute
raise ModbusIOException(
pymodbus.exceptions.ModbusIOException: Modbus Error: [Input/Output] ERROR: No response received after 3 retries
2024-08-02 17:49:59.454 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX_Cabanon: reading serial number from address 0x32 failed; other address may succeed
2024-08-02 17:49:59.454 ERROR (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX_Cabanon: cannot find any serial number(s)
2024-08-02 17:49:59.454 ERROR (MainThread) [custom_components.solax_modbus.plugin_solax] unrecognized inverter type - serial number : unknown
2024-08-02 17:50:01.150 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.0x385b44fffe93c0e8_over_current_threshold: 0 (range 1.0 - 64.0)
2024-08-02 17:50:11.591 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX_Cabanon: attempt to read serialnumber failed at 0x0 data: None
Traceback (most recent call last):
File "/config/custom_components/solax_modbus/plugin_solax.py", line 69, in async_read_serialnr
inverter_data = await hub.async_read_holding_registers(unit=hub._modbus_addr, address=address, count=7)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/solax_modbus/init.py", line 549, in async_read_holding_registers
resp = await self._client.read_holding_registers(address, count, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pymodbus/client/base.py", line 183, in async_execute
raise ModbusIOException(
pymodbus.exceptions.ModbusIOException: Modbus Error: [Input/Output] ERROR: No response received after 3 retries
2024-08-02 17:50:11.592 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX_Cabanon: reading serial number from address 0x0 failed; other address may succeed
2024-08-02 17:50:27.424 DEBUG (MainThread) [custom_components.solax_modbus] device group inverter
2024-08-02 17:50:28.042 DEBUG (MainThread) [custom_components.solax_modbus] device group read done
2024-08-02 17:50:29.459 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX_Cabanon: attempt to read serialnumber failed at 0x0 data: None
Traceback (most recent call last):
File "/config/custom_components/solax_modbus/plugin_solax.py", line 69, in async_read_serialnr
inverter_data = await hub.async_read_holding_registers(unit=hub._modbus_addr, address=address, count=7)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/solax_modbus/init.py", line 549, in async_read_holding_registers
resp = await self._client.read_holding_registers(address, count, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pymodbus/client/base.py", line 183, in async_execute
raise ModbusIOException(
pymodbus.exceptions.ModbusIOException: Modbus Error: [Input/Output] ERROR: No response received after 3 retries
2024-08-02 17:50:29.459 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX_Cabanon: reading serial number from address 0x0 failed; other address may succeed
2024-08-02 17:50:29.459 INFO (MainThread) [custom_components.solax_modbus.plugin_solax] Read SolaX_Cabanon 0x0 serial number: None
2024-08-02 17:50:29.459 INFO (MainThread) [custom_components.solax_modbus] Inverter is not connected, trying to connect
2024-08-02 17:50:29.459 DEBUG (MainThread) [custom_components.solax_modbus] Trying to connect to Inverter at 192.168.0.191:502
2024-08-02 17:50:29.466 INFO (MainThread) [custom_components.solax_modbus] Inverter connected at 192.168.0.191:502
2024-08-02 17:50:31.599 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX_Cabanon: attempt to read serialnumber failed at 0x300 data: None
Traceback (most recent call last):
File "/config/custom_components/solax_modbus/plugin_solax.py", line 69, in async_read_serialnr
inverter_data = await hub.async_read_holding_registers(unit=hub._modbus_addr, address=address, count=7)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/solax_modbus/init.py", line 549, in async_read_holding_registers
resp = await self._client.read_holding_registers(address, count, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pymodbus/client/base.py", line 183, in async_execute
raise ModbusIOException(
pymodbus.exceptions.ModbusIOException: Modbus Error: [Input/Output] ERROR: No response received after 3 retries
2024-08-02 17:50:31.599 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX_Cabanon: reading serial number from address 0x300 failed; other address may succeed
2024-08-02 17:50:31.599 INFO (MainThread) [custom_components.solax_modbus.plugin_solax] Read SolaX_Cabanon 0x300 serial number: None
2024-08-02 17:50:31.599 INFO (MainThread) [custom_components.solax_modbus] Inverter is not connected, trying to connect
2024-08-02 17:50:31.599 DEBUG (MainThread) [custom_components.solax_modbus] Trying to connect to Inverter at 192.168.0.191:502
2024-08-02 17:50:31.601 INFO (MainThread) [custom_components.solax_modbus] Inverter connected at 192.168.0.191:502
2024-08-02 17:50:36.425 DEBUG (MainThread) [custom_components.solax_modbus] device group inverter
2024-08-02 17:50:36.603 ERROR (MainThread) [pymodbus.logging] Cancel send, because not connected!
2024-08-02 17:50:36.603 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX_Cabanon: attempt to read serialnumber failed at 0x1a10 data: None
Traceback (most recent call last):
File "/config/custom_components/solax_modbus/plugin_solax.py", line 69, in async_read_serialnr
inverter_data = await hub.async_read_holding_registers(unit=hub._modbus_addr, address=address, count=7)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/solax_modbus/init.py", line 549, in async_read_holding_registers
resp = await self._client.read_holding_registers(address, count, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pymodbus/client/base.py", line 175, in async_execute
resp = await asyncio.wait_for(
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/asyncio/tasks.py", line 520, in wait_for
return await fut
^^^^^^^^^
pymodbus.exceptions.ConnectionException: Modbus Error: [Connection] Client is not connected
2024-08-02 17:50:36.603 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX_Cabanon: reading serial number from address 0x1a10 failed; other address may succeed
2024-08-02 17:50:36.603 INFO (MainThread) [custom_components.solax_modbus.plugin_solax] Read SolaX_Cabanon 0x1a10 serial number: None
2024-08-02 17:50:36.603 INFO (MainThread) [custom_components.solax_modbus] Inverter is not connected, trying to connect
2024-08-02 17:50:36.604 DEBUG (MainThread) [custom_components.solax_modbus] Trying to connect to Inverter at 192.168.0.191:502
2024-08-02 17:50:36.605 INFO (MainThread) [custom_components.solax_modbus] Inverter connected at 192.168.0.191:502
2024-08-02 17:50:37.042 DEBUG (MainThread) [custom_components.solax_modbus] device group read done

Best regards
JFH

[jfh75]

24 hours of searching and retrying, all of a sudden it works !!!!! My X1 AIR 3kw is recognized, I now have both in Home Assistant !!!
Thank you very much for your help !!!
JFH

[NeeoTheOne]

22000W, but in real limited to 19800, need to switch to 0 depend on hourly market, but I got only passive access too. Dne út 6. 8. 2024 9:36 uživatel wills106 ***@***.***> napsal:

…

What value does "Active Power Limit" return? — Reply to this email directly, view it on GitHub <#520 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BHV4WPCNMEAN4ULWICRXGALZQB4IRAVCNFSM6AAAAABJMYSW36VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMRVGA3DGNQ> . You are receiving this because you were mentioned.Message ID: <wills106/homeassistant-solax-modbus/repo-discussions/520/comments/10250636 @github.com>

[NeeoTheOne]

Hello dont work, if it will help, I talk with one solax expert and he says that in G4 its registry value 48 and in x3 pro its on value 12. Dne út 6. 8. 2024 18:02 uživatel wills106 ***@***.***> napsal:

…

Just released 2024.08.7 <https://github.com/wills106/homeassistant-solax-modbus/releases/tag/2024.08.7> Set the upper limit to 30,000W. Should cover all MIC's and MIC Pro's. But you probably can't set it to a value larger than it's capable of. — Reply to this email directly, view it on GitHub <#520 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BHV4WPA5BQY2JPEBQNFEUYLZQDXRPAVCNFSM6AAAAABJMYSW36VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMRVGU3DEOI> . You are receiving this because you were mentioned.Message ID: <wills106/homeassistant-solax-modbus/repo-discussions/520/comments/10255629 @github.com>

[wills106]

Is that reading or writing? Also which register type?

According to the docs on the MIC's:

Read Holding starts at 0x300
Read Input starts at 0x400
Write Single starts at 0x600
Write Multi starts at 0xFFB

Those are all HEX values by the way.

[NeeoTheOne]

Update: It work, but it limit output of inverter, not only export, and it worked only if I log with password to advanced setting on inverter, if I dont log in advanced, changes dont apply to inverter. So it need to send password before set value. This is out of my knowledge: Read Holding starts at 0x300 Read Input starts at 0x400 Write Single starts at 0x600 Write Multi starts at 0xFFB I just got info that export control is possible but on different place in X3 Pro. Dne út 6. 8. 2024 21:53 uživatel wills106 ***@***.***> napsal:

…

Is that reading or writing? Also which register type? According to the docs on the MIC's: Read Holding starts at 0x300 Read Input starts at 0x400 Write Single starts at 0x600 Write Multi starts at 0xFFB Those are all HEX values by the way. — Reply to this email directly, view it on GitHub <#520 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BHV4WPEGSNIKCLFJOKEVI4DZQESSPAVCNFSM6AAAAABJMYSW36VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMRVG42DGNQ> . You are receiving this because you were mentioned.Message ID: <wills106/homeassistant-solax-modbus/repo-discussions/520/comments/10257436 @github.com>

[MiRe-CZ]

Hello NeeoTheOne,so that control limits performance of an inverter itself,  no wonder it needs higher privilege. Can you dig out, from that expert you mentioned, more detailed info about export control? I can't help here as I have another brand of inverters, this Solax has my neighbourThank youBr, Milan -------- Original message --------From: NeeoTheOne ***@***.***> Date: 07/08/2024 09:09 (GMT+01:00) To: wills106/homeassistant-solax-modbus ***@***.***> Cc: MiRe-CZ ***@***.***>, Comment ***@***.***> Subject: Re: [wills106/homeassistant-solax-modbus] Unrecognized Inverter - SolaX (Discussion #520) Update: It work, but it limit output of inverter, not only export, and it worked only if I log with password to advanced setting on inverter, if I dont log in advanced, changes dont apply to inverter. So it need to send password before set value. This is out of my knowledge: Read Holding starts at 0x300 Read Input starts at 0x400 Write Single starts at 0x600 Write Multi starts at 0xFFB I just got info that export control is possible but on different place in X3 Pro. Dne út 6. 8. 2024 21:53 uživatel wills106 ***@***.***> napsal:

Is that reading or writing? Also which register type? According to the docs on the MIC's: Read Holding starts at 0x300 Read Input starts at 0x400 Write Single starts at 0x600 Write Multi starts at 0xFFB Those are all HEX values by the way. — Reply to this email directly, view it on GitHub <#520 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BHV4WPEGSNIKCLFJOKEVI4DZQESSPAVCNFSM6AAAAABJMYSW36VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMRVG42DGNQ> . You are receiving this because you were mentioned.Message ID: <wills106/homeassistant-solax-modbus/repo-discussions/520/comments/10257436 @github.com>

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[MiRe-CZ]

Hello @NeeoTheOne,

no luck with that Solax expert?

BR, Milan

[shockerchocker]

Getting unrecognized inverter type - serial number : H5802Axxxxxxxx

Serial 6 chars: H5802A
Solax X1-IES 8kw ( 3MPPT)
Integration 2024.8.7

HA:
Core 2024.7.4
Supervisor 2024.08.0
Operating System 12.4
Frontend 20240710.0

Anything to help connect please/add support for this inverter. Have the combo ethernet/wifi dongle and Waveshare RS485 to ETH (B)

[wills106]

Just added it into 2024.08.8

[shockerchocker]

Amazing. Thanks for the speedy response. After fighting with a waveshare, it turns out the ethernet on the pocketwifi works for modbus, i'm still getting upto speed. Working through the data, but so far obvious funnies are:

• only 2 PVs showing - inverter has PV1, PV2, PV3 (all with panels)
• 2nd battery readings all zero, battery 1 seems to show total power usage.
  Please let me know if any logs/more info is useful.

[wills106]

Just added the 3rd MPPT into 2024.08.9

[shockerchocker]

Saw that appear, fantastic. Think the battery counts as a single unit behind the BMS so all good there too.

[markushue]

Hi, please add my inverter

unrecognized inverter type - serial number : H35A10KXXXXXX (Solax X3-IES 10 K)

connected via pocket-wifi 3.0, fw 3.017.02. Thank you!

[wills106]

Just added it into 2024.08.9

[markushue]

it works! thank you very much!

[NeeoTheOne]

[Solax.X3-PRO.Modbus-Protokoll.V2.7.pdf](https://github.com/user-attachments/files/16677601/Solax.X3-PRO.Modbus-Protokoll.V2.7.pdf) Just got modbus registers for MIC G2. út 20. 8. 2024 v 16:36 odesílatel MiRe-CZ ***@***.***> napsal:

…

Hello @NeeoTheOne <https://github.com/NeeoTheOne>, no luck with that Solax expert? BR, Milan — Reply to this email directly, view it on GitHub <#520 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BHV4WPBDKA6HWLGNXWKQHWTZSNH6LAVCNFSM6AAAAABJMYSW36VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZZGY4DMNQ> . You are receiving this because you were mentioned.Message ID: <wills106/homeassistant-solax-modbus/repo-discussions/520/comments/10396866 @github.com>

[MiRe-CZ]

Thanks @NeeoTheOne !

@wills106 - I can see in the provided document these writable registers, where "Uservalue" is exactly what we need to have in the integration, can you please check? It would be nice to have "ExportCheckEnable" available as well.

0x65B ExportCheckEnable W 见ExportCheckEnable_t结构体 /
0x65C Uservalue W 1W
0x65D UservalueHard W 1W

I am not sure regarding this one:
0x65E GeneralControlUservalue W 1W

And which registers are "Active Power Limit" & "Select Q Curve" which you've added into 2024.08.7?

Thank you
BR, Milan

[MiRe-CZ]

Hello @wills106,

I fully understand you are very busy, however can you please at least briefly review my previous mail and document provided by NeeoTheOne and estimate if there is any chance for support of export limit in the integration? If no, we can close this case; if yes, we can patiently wait for it.

Thank you
BR, Milan

[wills106]

Those registers you quote are the read registers not the write. You can see the one I have used here:

homeassistant-solax-modbus/custom_components/solax_modbus/plugin_solax.py

Lines 2051 to 2065 in 5139f2f

	SolaxModbusSelectEntityDescription(
	name = "Q Curve",
	key = "q-curve",
	register = 0x640,
	option_dict = {
	0: "Off",
	1: "Over Excited",
	2: "Under Excited",
	3: "PF(p)",
	4: "Q(u)",
	5: "FixQPower",
	},
	allowedtypes = MIC | GEN2,
	icon = "mdi:dip-switch",
	),

You are best raising a Feature Request, so the comment doesn't get lost in a post about adding in a unknown Inverter

[MiRe-CZ]

If I am not totally mistaken, all those registers are write registers as they belong to the Write single register group, starting with 0x600.

Anyway, I created feature request @ #1049 Enhancement of entities supported by integration for Solax X3-PRO-xxK-G2

[webnugget]

Hi @wills106 I tried to setup a Modbusconnection to my new Inverter.
It's an X3-ULT-25K Hybrid Inverter with a Power Rating of 25000W.

https://www.solaxpower.com/products/x3-ultra/

Do you need any further Information? Is there another way to read values from this inverter?

Thank you,
Christian

2024-09-09 22:32:22.145 INFO (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX: trying to determine inverter type
2024-09-09 22:32:22.395 INFO (MainThread) [custom_components.solax_modbus.plugin_solax] Read SolaX 0x0 serial number: H3BF25xxxxxxxx
2024-09-09 22:32:22.395 ERROR (MainThread) [custom_components.solax_modbus.plugin_solax] unrecognized inverter type - serial number : H3BF25xxxxxx

[webnugget]

@wills106 thanks for adding my inverter, didn't expect an update that fast. awesome.

[potesek]

Hello

Please add support for my inverter:
Serial 6 chars: MC602T
Solax X3 MIC gen1 (6KW)
Integration 2024.09.05

HA Core 2024.9.3

Thanks.

Best regards,
Tom

[wills106]

The latest docs I know of for the Gen1 MIC is v1.07
There maybe newer?

I'll go over your error log in the next few days.

[potesek]

@wills106 this docs have date 2021-09026 - v1.1,
I have the newest firmware - updated about month ago by support :
ARM: 1.38
DSP: 1.33

I have Pocket WiFi gen 2 and this is last version of firmware - Module Comm 2.035.01. Gen3 Pocket is not compatible with my Solax MIC G1 )

[wills106]

PocketWiFi 2 don't officially support Modbus. Some work, some work unreliably and some don't work at all over Modbus.
You are best sticking to one of the USR devices. Are you using the correct baud of 9600 on the MIC?

[potesek]

Yes, I set everythig like on https://github.com/nathanmarlor/foxess_modbus/wiki/USR-W610.
Now I saw that when I open USR webinterface connection work even slower and additional errors appear (Failed to connect)
2024-10-13 15:22:13.365 WARNING (MainThread) [pymodbus.logging] Failed to connect 2024-10-13 15:22:44.443 ERROR (MainThread) [pymodbus.logging] General exception: unpack requires a buffer of 2 bytes 2024-10-13 15:22:44.443 ERROR (MainThread) [homeassistant] Error doing job: Fatal error: protocol.data_received() call failed. (None) Traceback (most recent call last): File "/usr/local/lib/python3.12/asyncio/selector_events.py", line 1017, in _read_ready__data_received self._protocol.data_received(data) File "/usr/local/lib/python3.12/site-packages/pymodbus/transport/transport.py", line 302, in data_received self.datagram_received(data, None) File "/usr/local/lib/python3.12/site-packages/pymodbus/transport/transport.py", line 336, in datagram_received cut = self.callback_data(self.recv_buffer, addr=addr) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/pymodbus/client/base.py", line 207, in callback_data self.framer.processIncomingPacket(data, self._handle_response, slave=0) File "/usr/local/lib/python3.12/site-packages/pymodbus/framer/base.py", line 139, in processIncomingPacket self.frameProcessIncomingPacket(single, callback, slave, **kwargs) File "/usr/local/lib/python3.12/site-packages/pymodbus/framer/socket_framer.py", line 91, in frameProcessIncomingPacket raise ModbusIOException("Unable to decode request") pymodbus.exceptions.ModbusIOException: Modbus Error: [Input/Output] Unable to decode request 2024-10-13 15:22:49.104 ERROR (MainThread) [pymodbus.logging] General exception: unpack requires a buffer of 2 bytes 2024-10-13 15:22:49.105 ERROR (MainThread) [homeassistant] Error doing job: Fatal error: protocol.data_received() call failed. (None)

I also tried change interval polling(normal, medium fast) but the same situation.

Probably I will have a new USR N520 (with faster CPU) on Tuesday, then I will let you know if anything has changed

[potesek]

Hello,

@wills106
After switch connection to USR N520 everything works properly. Data are correct reading.
N520 is really faster.. web interface works much faster.

Thanks for your help

[kkozlik]

Hello,
I am getting the unrecognized inverter type - serial number : unknown error after updating HA to new version. It was working nicely before. My understanding is that it is some problem with modbus comunication. However I have no idea how to debug it. Could you please give some advice what to check? I have tried to update and reinstal the solax integration but it did not help.

There is some change regarding to modbus in latest HA, but I have no idea whether it could be related to this issue: home-assistant/core#126104

Thanks for your work!

HA version: 2024.10.1
Integration version: 2024.09.5
Inverter: X3-Hybrid-G4
serial: H34A10

[wills106]

Are you using a PocketWiFi? If so have you tried unplugging it and plugging it back in again?

[kkozlik]

I am not sure what do you mean by PocketWiFi. There is some wifi dongle in the inverter. But there is not problem with wifi connection. The inverter could be accessed using the solax app. And I can read some data with: curl -d "optType=ReadRealTimeData&pwd=<PWD>" -X POST http://<IP>

[kkozlik]

Hmm, I have tried to unplug and re-plug the wifi dongle from the inverter and surprisingly I have now two solax inverters in my home assistant. One of them is working (the new one) and the other is not. I am quite puzzled/curious what happened??

How can I remove the older non working inverter from my home assistant? I cannot find a possibility for this.

Anyway, thanks for the hint!

[wills106]

Have you tried restarting HA? The wifi dongle is a PocketWiFi, that's the proper name of it.
PocketWiFi are known for their unreliable Modbus connection, there may be a newer Firmware available for it?

[kkozlik]

Yes, many restarts of HA.

What confused me is that the problem appeared just after update of HA. So I did not expected that there could be any problem on inverter side. Moreover this was first outage after ~3 months of use.

It would be nice if I could somehow remove the fake/non-working inverter from my HA. Otherwise I have banned it for now so I should be good.

[BEMSman]

Have you tried this method; Go to Configuration > Entities or settings>Devices & Services – click on entities tab at the top Wait for the list to show up, then click on Status column header twice to filter by Status with unavailable entries showing on top Select the items you want to delete, then click on Remove Selected From: Karel Kozlik ***@***.***> Sent: 12 October 2024 21:32 To: wills106/homeassistant-solax-modbus ***@***.***> Cc: BEMSman ***@***.***>; Comment ***@***.***> Subject: Re: [wills106/homeassistant-solax-modbus] Unrecognized Inverter - SolaX (Discussion #520) Hmm, I have tried to unplug and re-plug the wifi dongle from the inverter and surprisingly I have now two solax inverters in my home assistant. One of them is working (the new one) and the other is not. I am quite puzzled/curious what happened?? How can I remove the older non working inverter from my home assistant? I cannot find a possibility for this. Anyway, thanks for the hint! — Reply to this email directly, view it on GitHub <#520 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASBCYAQSZVUF3K2F3E4GL3TZ3GBLJAVCNFSM6AAAAABJMYSW36VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOJSGQ4DONQ> . You are receiving this because you commented. <https://github.com/notifications/beacon/ASBCYAXDEB4NLCHOWDHPNBTZ3GBLJA5CNFSM6AAAAABJMYSW36WGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAU2ZUY.gif> Message ID: ***@***.*** ***@***.***> >

[kkozlik]

I tried, but there are still 14 entities remaining which cannot be deleted. The HA says that the device have to stop providing them first. All those entities are in forbidden state.

[potesek]

For me, sometimes it helps to perform a manual full backup (entire HA) and then restore. I think there is some cleaning task in the restore process.
If you can, check this option.

[kkozlik]

Good tip. Unfortunately did not helped :-(.