-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Solax X1 Mini G2 support #15
Comments
This
looks like an incomplete frame. If you compare the payload with the long (61 byte) frames starting with the header
|
It looks like the payload has changed a bit. I will try to compare the old status report payload with your payload.
|
--> The last 2 bytes are missing compared to the Solax X1 mini |
Please update your configuration yaml to
and recompile + flash your ESP. The payload of your device should be accepted/parsed now. |
Thank you for your quick feedback.
|
You have to use three back ticks instead of one for nice code blocks. ;-) The no errors state and operation mode "Wait" looks good already! Could you provide some details (type label) about your inverter? I would like to mention the supported device at the documentation. |
Communication is now stable throughout the day. [17:03:11][D][text_sensor:067]: 'solar-powermeter errors': Sending state ''
[17:03:11][V][text_sensor:016]: 'solar-powermeter mode name': Received new state Normal
[17:03:11][D][text_sensor:067]: 'solar-powermeter mode name': Sending state 'Normal'
[17:03:12][VV][scheduler:185]: Running interval 'update' with interval=1000 last_execution=10953068 (now=10954072)
[17:03:12][VV][modbus_solax:218]: TX -> AA.55.01.00.00.0A.11.02.00.01.1D (11)
[17:03:12][VV][uart.arduino_esp8266:180]: Flushing...
[17:03:12][VV][modbus_solax:083]: RX <- AA.55.00.0A.01.00.11.82.32.00.1A.00.3D.07.08.00.00.00.03.00.00.00.06.09.0F.13.8A.00.3B.FF.FF.00.00.5D.F0.00.00.10.5B.00.02.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.06.E6 (61) I use a SolaX X1 mini inverter model X1-2.0-S-D(L).
|
Perfect! You should decrease the log level now. ;-) Printing UART traffic is expensive. I will merge the feature branch to
|
[15:42:31][VV][modbus_solax:218]: TX -> AA.55.01.00.00.0A.11.02.00.01.1D (11)
[15:42:31][VV][uart.arduino_esp8266:180]: Flushing...
[15:42:31][VV][modbus_solax:083]: RX <- 00.21.00.02.07.EF.00.00.00.1D.00 (11)
[15:42:31][W][modbus_solax:086]: Invalid header.
[15:42:32][VV][scheduler:185]: Running interval 'update' with interval=1000 last_execution=16039 (now=17046)
[15:42:32][VV][modbus_solax:218]: TX -> AA.55.01.00.00.0A.11.02.00.01.1D (11)
[15:42:32][VV][uart.arduino_esp8266:180]: Flushing...
[15:42:32][VV][modbus_solax:083]: RX <- AA.55.00.0A.01.00.11.82.32.00.21.00.02.07.EC.00.00.00.1D.00.00.00.18.09.55.13.80.02.2B.FF.FF.00.00.5D.AF.00.00.10.50.00.02.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.07.A4 (61)
[15:42:32][W][solax_x1:076]: Invalid response size: 50
[15:42:33][VV][scheduler:185]: Running interval 'update' with interval=1000 last_execution=17039 (now=18044)
[15:42:33][VV][modbus_solax:218]: TX -> AA.55.01.00.00.0A.11.02.00.01.1D (11)
[15:42:33][VV][uart.arduino_esp8266:180]: Flushing...
[15:42:33][VV][modbus_solax:083]: RX <- AA.55.00.0A.01.00.11.82.32.00.21.00.02.07.DB.00.00.00.1D.00.00.00.18.09.56.13.81.02.2C.FF.FF.00.00.5D.AF.00.00.10.50.00.02.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.07.96 (61)
The text was updated successfully, but these errors were encountered: