Today installation of my Sungrow solar inverter SH10RT and battery SBR096 will start. What home assistant integration is currently the most functional and reliable? I found reports of people using the following:
Iām stuck at the installing add-on bit. I have added the repository but nothing happens after that. My other repository ewlink is working fine but this ones does not appear in the list after adding and has a red delete icon next to it for some reason.
Hi everyone,
I have just released v3.0.0 of GoSungrow, (appearing as v3.0.1 on HASSIO). This is a major update and took a little longer than I had expected - life gets in the way sometimes
The following is from my GoSungrow changelog, (for HA, there have been just a few stability changes):
It was originally intended for my needs, (seeing all data in HomeAssistant), but there seems to be a big interest in this tool. So Iāve spent some time working on the v3.0.0 release.
v3.0.0 changelog:
Support better api changes. This allows a much quicker change in my code when the api changes.
Support multiple devices. Previous versions only allowed query of one device.
Improve cli for queries. Now can fetch endpoints in either ālistā or ātableā formats, the latter showing point data in a similar fashion to pivot tables in spreadsheets.
Multiple output formats supported - not only csv, png and ascii, but markdown, xml, HTML, sql and plain MQTT.
Lots of bug fixes. :-).
I have now mapped out all the API calls. All the read-only endpoints are mapped out and fully tested. The write-only calls havenāt been tested fully. Itās tricky as their āAPIā changes regularly; however Iāve accommodated for quick changes in the v3.0.0 release.
Most endpoints contain repeated data. The main endpoints that house most of the data Iāve provided easy commands to access. Of course, all endpoints are accessible. So go for your life.
This is really nice, thanks alot! Got it working in a few minutes, really cool.
At a glance seems you are polling the webapi every 5mins? Iām a bit impatient is there a way to up this or is that the cloud output? Do you also have a list of sensor values that fit to the HA energy monitor? I was planning on just using this as itās so far been doing a great job for me
I present all the point data I see from three main endpoints. There are plenty of other endpoints but the three I chose contain 90% of them.
All the points data appear in the format ps_key.point_id The critical ones I have aliased to virtual entries. So in HA you can search for them using āvirtualā.
If you want to go deeper, download the GoSungrow tool to your PC and type:
GoSungrow show ps points
This will show up all points available for your unit.
Also check out the Lovelace yaml files as an example of output you can produce.
You can generate these files for your PsId using the command:
whatever the problem was yesterday has fixed itself overnight. Deleted and added repository back and now appearing in the list of addons. Strangely I also did many times yesterday with no luck.
Iām seeing the wrong data in the MQTT connection - log shows username:password rather than the host:port which is throwing an error. See red items in attached image.
The configuration automatically identified the correct MQTT host and port but they are not used. I have manually updated and restarted but same issue persists.
Looking at the logs when the add-on starts, it looks like the port begins with a carriage return as itās dropped to the next line in the logs but is actually shorter than any other entry.
Could this be what is causing the failure to get the port into the connection string?
Just done a restart on HA, the upgrade is in place but the log shows the same error on MQTT
Token File: /data/.GoSungrow/AppService_login.json
2022/12/21 22:43:29 INFO: Connecting to MQTT HASSIO Serviceā¦
**Error: parse "tcp://my-username:my-password": invalid port ā:my-passwordā after host
Usage:
GoSungrow mqtt run [flags]
Aliases:
run,
Examples:
GoSungrow mqtt run
Flags: Use āGoSungrow help flagsā for more info.
Additional help topics:
ERROR: parse ātcp://my-username:my-passwordā: invalid port ā:my-passwordā after host
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
Logs showing that the URL that isā trying to connect to is does not contain either the MQTT host or the MQTT portā¦ but does contain my-username and my-password as per config file.
Any chance you could update the debug mode logs to output more information on what is happening at the time of MQTT connection?
This looks like a name resolve issue.
Are you running the latest HA? Iām not sure if the older versions made use of the mosquitto-core hostname or not.
The latest version, (v3.0.3), you can control logging with MQTT commands. Have a look at the docs for examples.
You can create some Lovelace cards that contain select.gosungrow_option_mqtt_debug and select.gosungrow_option_loglevel. These will do what you expect them to do.
Ahh OK, so is MQTT connection in your add on directing comms to the mosquitto-core that would be hosted in HA?
I have a separate broker in a separate device?
In the config, Ive set the MQTT host, port, user and P/W.
