-
Notifications
You must be signed in to change notification settings - Fork 29
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
GoodWe 55000DNS the target machine actively refused it #31
Comments
I get similar errors with a Goodwe 5000DNS and 3000XS Any fix for these loggers? |
Figuring out what Wi-Fi kit you have and the Serial Number of it might help you. Documentation says you might find the Wifi Kit S/N on one of the sides of the Inverter and it should be 8 Digits long and start with a 6. I can not find mine but you might have more luck. Then in the Config file add your ip and then your SN. "192.168.1.101,60012334" |
I would also like to get this working on my 3000XS. Any progress @Uksa007 ? What i don't understand is how i should interpret the S/N that is talked about in this repository. I installed the app 'PV Master' but it didn't support my inverter. When i filled in the serial number it said i had to use the 'SolarGo' app. This app found my inverter, but couldn't read it (not supported, only for inverters without display it said). By using Wireshark i saw that the app did a discovery for inverters was done by a broadcast on 48899. |
Ok, i tried this Python script and it discovered my wifi-module. But it gives me |
I didn't have any luck getting the wifi module to reply on any of the know ports, most of them UDP. I ended up using a script to pull the data from the SEMS portal. |
Using this on a GW5048D-ES NONE of the following works: ip + full SN |
2019-06-15 11:24:03,779 ERROR Could not open socket
2019-06-15 11:24:03,779 ERROR [Errno 10061] No connection could be made because the target machine actively refused it
2019-06-15 11:24:03,780 ERROR Error connecting to logger with IP: 192.168.1.2 and SN , trying next logger.
The text was updated successfully, but these errors were encountered: