strconv.Atoi: parsing "null"

[paytah232]

Hi,

Just got ownership of these (from my installer), and now the integration picks up the devices I have (over 2 plants). It gets the ps_id of my first plant (confirmed on the webpage), but then I immediately get the parsing "null" error, and that's as far as I get.

I'd really like any inclination into what I need to check or fix to get this working. It's the closest I've been in months, and I'm very keen to get there! Any help would be greatly appeciated!

Relevant logs below:

2026/01/30 03:49:38 INFO: Found SunGrow 6 devices
2026/01/30 03:49:38 INFO: Caching Sungrow metadata...
2026/01/30 03:49:38 INFO: Cached 1230 Sungrow data points...
PsId: required
JSON request:	{"ps_id":REDACTED}
2026/01/30 03:49:38 ERROR: strconv.Atoi: parsing "null": invalid syntax
Error: strconv.Atoi: parsing "null": invalid syntax
Usage:
  GoSungrow mqtt run [flags]
Aliases:
  run, 
Examples:
	GoSungrow mqtt run  
Flags: Use "GoSungrow help flags" for more info.
Additional help topics:
ERROR: strconv.Atoi: parsing "null": invalid syntax
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

[Paraphraser]

@paytah232 - can I say - as gently as possible - that going to the Issues tab and searching for "strconv.Atoi" would find a bunch of hits which, eventually would have led you to this gist.

I say "eventually" because there are so many comments on every issue in this repo that it would still take you a fair bit of reading time before the gist would stick out as something where you might find the answer. I acknowledge that.

Pick the "part" (or parts) of that gist which meet your requirements.

If it all sounds far too complicated - sorry, that's the best we can do until MickMake comes back or someone decides to fork the project and take responsibility for releasing updates.

There are no guarantees that the current set of patches (if you follow Part 1 of the gist) will actually solve your problem. The only way to know is to try.

One of the simplest debugging techniques is to stay away from Home Assistant until you have things working outside that environment. The fact that your crash is happening so early makes me suspect your configuration, by which I mean things like the Sungrow server, your credentials, your app key, or perhaps even your password if it has weird characters - exclamation marks seem to cause problems - or something else along those lines. It is much easier to sort out problems like that from the command line than it is from Home Assistant.

At the very least, get to the point where you can run:

$ GoSungrow api login
$ GoSungrow show ps tree

Any problems getting that far are usually "configuration".

Hope this helps.