-
-
Notifications
You must be signed in to change notification settings - Fork 31.5k
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
SolaX Power integration can't access inverter information (Failed to connect) #66617
Comments
Hey there @squishykid, mind taking a look at this issue as it has been labeled with an integration ( solax documentation |
Likewise, same issue |
Same problem here. Failed to connect. |
Same problem here. on a fresh HA install |
I cant set up the integration. When I enter the IP the error "Failed to connect" always comes up. Can someone help me? |
yeah this seems to be the issue with the integration atm. |
Hello, same issue here. I looked through Wireshark and the API is answering, but the result is the same - Failed to connect. |
This comment was marked as abuse.
This comment was marked as abuse.
Please don't ping specific users. I don't use this integration myself and I'm not convinced balloob/cdce8p do either. You may need to contribute on the parent library: https://github.com/squishykid/solax which seems well maintained. |
Ok, sorry and thank you! |
Same issue here with X3-Hybrid-G4, dongle on 2.035.01 firmware. |
Same issue with X3-Hybrid-G4, dongle firmware 3.001.02. |
Please perform the troubleshooting steps as outlined here under "Inverter not Supported Yet": https://github.com/squishykid/solax/wiki/DiscoveryError#inverter-not-supported-yet Share ALL of the following:
When you paste your results, use the code formatting option I am a volunteer, just like lots of other people helping out with this project. I do not receive any compensation for providing assistance. Please help us so we can help you. |
When i adding integration for solax, a see error ""
Log from HA:
|
Hello Robin, Thanks for your help. X3-Hybrid-G4, Wifi dongle 2.034.06 firmware.
|
@dohnalekp @jirisvozil could you please also supply the following:
I have a hunch that your data might have the same structure as the existing X3 integration, so please check here if all the values line up: https://github.com/squishykid/solax/blob/master/solax/inverters/x3_v34.py If they don't, you will need to supply the data mapping information |
`Curl Command curl response inverter model firmware logs from the home assistant instance |
Hi @squishykid,
|
I don't have much time right now, but I can confirm most of dohnalekp's findings. I just think, that the last one is : Total Feed-in Energy': (68, 'kWh', feedin_energy). I'll try to add something during the week. Thx, Jiri |
X3-Hybrid-G4
|
I have made a spreadsheet trying to match the numbers with the correct sensor. If someone would like to contribute I made it publicly editable. https://docs.google.com/spreadsheets/d/1-scQT3MN871zuhe2x-X6myknQDyWaCwh3igaLTdE2PY/edit?usp=sharing |
Hi @squishykid, |
Inverter Model Solax Mini X1-2.0
for those who don't know the password for the inverter it can be obtained on solaxcloud |
i checked in my solaxCloud but there is no 'Lock' icon Kind regards Peter |
|
Same issue. % curl -s -w '\n' -X POST http://192.168.xxx.xxx --data 'optType=ReadRealTimeData&pwd=XXXXXXXXXX' |
I am missing that password icon as well in cloud. |
Hi @dohnalekp , any luck solving the TimeoutError issue? I have the same inverter, same firmware, and facing the same issue. Curl also works for me and gets me a similar response. Thanks, Marek |
Home Assistant 2023.8.0 after upgrade installed solax 0.3.2 dependency (rather than 0.3.1) and my inverter connected successfully without any manual intervention 🎉 I think this issue is finally resolved. |
What I found out together with @NanoSector is just that the current integration just does a whole lot of requests, and because of this the inverter just doesnt respond because of unknown endpoints (since they are for other types of inverters). Sometimes the inverter just restores in time for the request that is meant for that type, so then it will work, so next reboot can still be a hit or miss |
Well, previous version never ever worked even once, now it worked, which was surprising and automatically attributed by me to updated version 🤷♂️ |
Like I am happy for you, but I want to temper your excitement. For context, the integration itself hasn't changed since 2023.7 so nothing has changed in 2023.8. So next restart of HA could break it again like before, or not. |
Another observation: yes, it doesn't start every time, but:
This is not a solution, but at least some improvement. |
I'm still on 2023.7 and both of those points are the same for me (I also mentioned the restarts/reloads fixing it before); what version have you upgraded from? |
2023.7, but maybe it was fixed a bit earlier, I just saw it getting stuck every single time and I was already in terminal ready to apply workaround right after upgrade. I was just a bit busy this time and noticed it booted successfully on its own. |
Still not working on latest version, x1boost. |
Integration reliably starts for me when restart is triggered, would be great if Home Assistant restarted integration a few times on its own. |
I think the discovery code in the solax library is the culprit, it seems to affect the dongle in some way, and then when the right class is up, the dongle fails to answer. the integration should offer the possibility to override the discovery and configure the right inverter class directly. A possible approach would be to offer a pulldown of the inverters in the config flow, and if none selected, revert back to discovery code. |
in the case where the Inverter type is already known. Some inverters at the end of the REGISTRY (e.g. X1HybridGen4) randomly crash because the discovery code issues too many incorrect requests before sending the correct one. This patch adds a variant of the entry point in which one can specify the name of the inverter type. This addresses home-assistant/core#66617 and home-assistant/core#99421
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
I don't think it was resolved yet |
I confirm, it wasn't. Solax integration is still unusable for X3 G4, out of the box. |
There are 2 open PRs in the upstream solax library that would make it possible to fix this issue: |
Would love to see this updated to support X3 G4 using the above open PRs in upstream Solax library |
There is a now a new PR in the upstream library that is ready to go: I also have a patch for HA to solve this specific issue, but it requires the upstream library to be updated. |
…home-assistant#66617). Adapt code to upstream solax-3.1.0
I don't think this is the right issue to ask such question @Elliottmonaghan, create a separate issue for this. This issue is about connection issues specifically. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
The problem
I can obtain the data by doing:
curl -d "optType=ReadRealTimeData&pwd=admin" -X POST http://192.168.1.100
{"sn":"SWXXXXXX","ver":"2.035.01","type":4,"Data":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,65591,65535,7907,0,22732,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0], "Information":[4.200,4,"XB32XXXXXXX",1,0.00,0.00,1.37,0.00,0.00,1]}
All the data is 0 cuase its at night. Can edit with real data in the moorning.
In the moorning with only 50W of real time power generation:
{"sn":"SWXXXXXX","ver":"2.035.01","type":4,"Data":[2385,6,55,1536,1721,2,2,39,39,5001,2,2427,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,11,0,214,0,0,0,0,0,0,65371,65535,7907,0,22911,0,0,21,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0], "Information":[4.200,4,"XB32XXXXXXX",1,2.19,0.00,1.37,0.00,0.00,1]}
If I configure SolaX Power with the ip address (192.168.1.100) and the password (admin) it states Failed to connect.
Take into account I am trying to connect to a Solax X1 Boost v3.2 Inverter not a Air_Mini which seems to work fine.
I might be doing something wrong as I am a total newbie but can't find the problem while I read it works perfectly from everyone with a Air_Mini. I am sure that the return information is different on the Air_Mini than on the X1 Boost v3.2 as the data doens't match.
After a quick check this is what I gathered from the data:
Decimal spots are removed so 10.50=1050, 0.5=5 and so on. Im not sure if the decimal spots problem is me problem or general problem. Im from Spain and we tend to use commas to separate decimals so not sure if inverter is mixing stuff up.
0:voltageTotal
1:ampsTotal
2:acpower
3:voltage1
4:voltage2
5:amps1
6:amps2
7:powerdc1
8:powerdc2
*9:always around 5000, 10 up 10 down aprox. grid frecuency?
*10:always 2. MPPT used?
11:yieldtotal
12:
13:dailyyield
*38:temperature???
*40:around 214 and 215
47:energy to grid? a range(0,X) number when placing power to grid. 64300 when taking energy from grid. 64300-65536= energy taken from grid?
48:0 or 65535. a sign? direction of the flow of power?
49:feedinenergytotal
51:consumeenergytotal
*54:temperature??
Any information that helps just ask. Thanks
What version of Home Assistant Core has the issue?
core-2022.2.6
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
SolaX Power
Link to integration documentation on our website
https://www.home-assistant.io/integrations/solax/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: