Hi Nick, great work. I have an SG50RS inverter, and I can see the data from the inverter correctly, but what I can’t see is the information or data in kWh for the energy purchased or consumed from the grid and the energy sent to the grid or sold. Do I need to modify anything or can you provide me with any additional information?
Thank you very much.
Leandro from Argentina
@NickS this has proven to be a very popular topic and add-on, thank you. This is my first use of an MQTT broker and I think my issue is with that and not your add-on. I get authenticated but then I see this repeatedly. Looks like multiple errors wrapped up which doesn’t really help. Any thoughts?
2025-08-08 06:07:30 info: Detected device: SG50RS ()
2025-08-08 06:07:30 info: Updated 29 sensors
2025-08-08 06:07:30 error: MQTT error: AggregateError
2025-08-08 06:07:31 error: MQTT error: AggregateError
2025-08-08 06:07:32 error: MQTT error: AggregateError
2025-08-08 06:07:33 error: MQTT error: AggregateError
2025-08-08 06:07:34 error: MQTT error: AggregateError
2025-08-08 06:07:35 error: MQTT error: AggregateError
2025-08-08 06:07:36 error: MQTT error: AggregateError
2025-08-08 06:07:37 error: MQTT error: AggregateError
2025-08-08 06:07:38 error: MQTT error: AggregateError
2025-08-08 06:07:39 error: MQTT error: AggregateError
2025-08-08 06:07:40 info: Updated 11 sensors
2025-08-08 06:07:40 error: MQTT error: AggregateError
2025-08-08 06:07:41 error: MQTT error: AggregateError
Thank you
Hi,
i have the same problem…
i found the problem… it was only that i wrote in the wrong way the url
Hey Guys
ive got my sungrow sh10rt online via the addon. is there any guides or different examples on how to best visualise this info on a dashboard? is it possible to connect two inverters?
did you have any luck adding a second inverter?
Hello everyone! Work on SH25T-V11 and winet-s2 !!! Thank you very much!
did you ever found a solution? Sungrow forced me to upgrade to the latest firmware, and now, I have the same issue…
It worked perfectly before… 
The WINET firmware version: WINET-SV300.001.03.P021
The logs:
2025-10-20 15:18:46 warn: Reconnecting to Winet
2025-10-20 15:19:16 info: Connected to a Winet-S2 device with newer firmware
2025-10-20 15:19:16 info: Connected to Winet, logging in
2025-10-20 15:19:17 info: Authenticated successfully
2025-10-20 15:19:17 error: Invalid realtime message: {
data: {
result_code: 1,
result_msg: 'success',
result_data: { service: 'real', list: [Array], count: 19 }
},
[Symbol(level)]: 'error',
[Symbol(splat)]: [ { data: [Object] } ]
}
2025-10-20 15:19:17 warn: Reconnecting to Winet
I got this working with a SH3.6RS + battery.
However, I have 2 more inverters with Winet.
How would I go about adding those aswell?
Hi, With default password and user, neith.er with admin/ pw8888 was not working. Just get solved using the user/pw1111 credentials.
Use the user/pw1111 credentials.
Hi, got SH20T V11 with WiNet SV300.001.03.PO18 - it leads into this error:
2025-11-19 14:52:21 info: Connected to MQTT broker
2025-11-19 14:52:24 warn: Newer Winet versions require SSL to be enabled. Retrying
2025-11-19 14:52:28 error: Failed to fetch l18n properties required to start. connect EHOSTUNREACH 192.168.5.200:443 {
errno: -113,
code: ‘EHOSTUNREACH’,
syscall: ‘connect’,
address: ‘192.168.5.200’,
port: 443,
stack: ‘Error: connect EHOSTUNREACH 192.168.5.200:443\n’ +
’ at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1606:16)',
[Symbol(level)]: ‘error’,
[Symbol(splat)]: [
Error: connect EHOSTUNREACH 192.168.5.200:443
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1606:16) {
errno: -113,
code: ‘EHOSTUNREACH’,
syscall: ‘connect’,
address: ‘192.168.5.200’,
port: 443
}
]
}
Anyone any idea how to solve it?
Hello Thx for your impressive work.
In my case I’m an absolutely beginner in terms of MQTT and such.
I followed the instructions of the WiNet Extractor.
Therefore I installed Mosquitto Broker and added a user. The I configured the WiNet Extractor.
The log-File of WiNet Extractor showed:
I tried different ports ans switched SSL enabling nothing changed the connack error
node build/src/index.js
2025-11-20 13:36:34 warn: Newer Winet versions require SSL to be enabled. Retrying
2025-11-20 13:36:35 info: Fetched i18n properties.
2025-11-20 13:36:36 info: Connected to a Winet-S2 device with newer firmware
2025-11-20 13:36:36 info: Connected to Winet, logging in
2025-11-20 13:36:36 info: Authenticated successfully
2025-11-20 13:36:36 info: Detected device: SG50RT (A2141504207)
2025-11-20 13:36:36 info: Updated 39 sensors
2025-11-20 13:36:46 info: Updated 11 sensors
2025-11-20 13:36:56 info: Updated 9 sensors
2025-11-20 13:37:04 error: MQTT error: Error: connack timeout
2025-11-20 13:36:36 info: Authenticated successfully
2025-11-20 13:36:36 info: Detected device: SG50RT (A2141504207)
2025-11-20 13:36:36 info: Updated 39 sensors
2025-11-20 13:36:46 info: Updated 11 sensors
2025-11-20 13:36:56 info: Updated 9 sensors
2025-11-20 13:37:04 error: MQTT error: Error: connack timeout
2025-11-20 13:37:06 info: Updated 4 sensors
Has anyone managed to get the Sungrow AC22E-01 EV charger (or the new iHomeManager) working with the WiNet-S add-on in Home Assistant?
I can’t tell if the integration picks up the charger at all, or if it only supports inverters/batteries. If you’ve had it detected or working, what setup did you use?
Thanks!
I’m having the same problem but I have notice that I can’t even log into the dongles web interface anymore it’s like they’ve taken that function out of the dongle I stopped reading anything as of the 4th of December 2025 so I’m thinking they’ve done some sort of an update.
Hello everyone!
I’ve finally managed to connect my SH15T SBR128.
But now I’m not sure if I can use “WiNet Extractor” to perform actions on the SH15T???
I want to start charging my battery at 11:00 a.m. Can anyone help me with the automation?
That would be great 
Not sure if this has been answered or if any dev is happening here?
Is it possible to have 2 separate Winet devices? ie add another IP / login.
I have just added an additional grid tied inverter to the backup cct of an existing Hybrid inverter. Its at another location, but same network.
Would love to add it to this system?
Nick - Not sure if you still follow this thread but thank you very much for this addon. I was trying to work out how to get it to monitor both of my SH15T inverters and their batteries. I pointed it at my Sungrow Logger 1000 and it actually picked up all the inverters, batteries, and even a meter. Thank you!
I have had this working for some time but I keep getting entities either becoming unknown or changing names. The big one I’m missing at the moment is operating status. It’s still there on the app but the entity in HA is now unknown. I now have 44 entities (out of 131) that I’ve had to disable on the inverter and 5 (out of 12) on the battery. Is there a way to rectify this?
Hi, I’m pretty new on HA and MQTT and have an issue with integration of the Sungrow inverter via WiNet-S Extractor.
I have installed MQTT and activated one MQTT integration, added the User mqtt_svg, which I can use succesful in the MQTT Explorer.
The connection to the WiNet seems also to work fine, but the mqtt-user is not accepted. I tried the host “core-mosquitto” and the IP of HA-installation.
Hopefully something simple I don’t see. 
BTW: I’m connected by Wireguard VPN to the HA-installation on a RaspberryPi4.
Thanks in advance for any hint.
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
> cli
> node build/src/index.js
(node:91) [DEP0170] DeprecationWarning: The URL mqtt://mqtt_svg:<my-password>@core-mosquitto is invalid. Future versions of Node.js will throw an error.
(Use `node --trace-deprecation ...` to show where the warning was created)
2026-05-02 11:17:25 warn: Newer Winet versions require SSL to be enabled. Retrying
2026-05-02 11:17:27 info: Fetched i18n properties.
2026-05-02 11:17:28 error: MQTT error: Error: getaddrinfo ENOTFOUND mqtt_svg
2026-05-02 11:17:28 info: Connected to a Winet-S2 device with newer firmware
2026-05-02 11:17:28 info: Connected to Winet, logging in
2026-05-02 11:17:28 info: Authenticated successfully
2026-05-02 11:17:29 info: Detected device: SH10RT (A2310404xxx)
2026-05-02 11:17:29 info: Detected device: SBR096 (S2310215xxx)
2026-05-02 11:17:29 info: Updated 88 sensors
2026-05-02 11:17:29 error: MQTT error: Error: getaddrinfo ENOTFOUND mqtt_svg
2026-05-02 11:17:30 error: MQTT error: Error: getaddrinfo ENOTFOUND mqtt_svg
2026-05-02 11:17:31 error: MQTT error: Error: getaddrinfo ENOTFOUND mqtt_svg
Solved the issue. My MQTT-user password contains a hashtag ‘#’ as special character. This was not accepted by the WiNet-S addon.But it works with the MQTT-Explorer, therefore I was not expecting this.