Goodwe rest sensor for multiple json elements

Tags: #<Tag:0x00007f77fb24d518>

After zillion tries, I can’t seem to get the template configuration correct.
I hope someone has more experience?

	"code": 1,
	"result": [{
			"inventersn": "xxxxxxxx",
			"desc": "",
			"vpv1": "353.40",
			"vpv2": "261.40",
			"ipv1": "0.90",
			"ipv2": "0.90"

sensor.yaml file:

# Goodwe Solar data
- platform: rest
  name: goodweinverter
  json_attributes: true
  value_template: '{{ value_json.code}}'
  scan_interval: 300

- platform: template
      value_template: '{{ states.sensor.goodweinverter.attributes}}'
      entity_id: sensor.goodweinverter
      value_template: '{{ states.sensor.goodweinverter.attributes.result[0]["inventersn"]}}'
      entity_id: sensor.goodweinverter
      value_template: '{{ states.sensor.goodweinverter.attributes["vpv1"]}}'
      unit_of_measurement: "V"
      entity_id: sensor.goodweinverter

2018-06-23 19:02:01 ERROR (MainThread) [homeassistant.components.sensor.template] Could not render template goodweinverter_inventersn: UndefinedError: ‘mappingproxy object’ has no attribute ‘result’

The first entry within the rest platform, showing “1” is ok.
I can’t get the other value’s out in correct sensors.

I guess for the rest sensor the relation of the value template is directly for the template sensor.
Looking at the JSON data: “code” is on the same level, so I changed the sensor to “result[0]”

# Goodwe Solar data
- platform: rest
  name: goodweinverter
  value_template: '{{ value_json.result[0]}}'
  scan_interval: 300
    - inventersn
    - vpv1

- platform: template
      friendly_name: 'inventersn'
      value_template: '{{ states.sensor.goodweinverter.attributes["inventersn"] }}'
      friendly_name: 'vpv1'
      value_template: '{{ states.sensor.goodweinverter.attributes["vpv1"] }}'
      unit_of_measurement: "V"

Before adding json_attributes in the rest sensor, it complained:

homeassistant.exceptions.InvalidStateError: Invalid state encountered for entity id: sensor.goodweinverter. State max length is 255 characters.

With this feedback, I think the data-set capture is correct.
I’ve added two attributes to the rest sensor: “inventersn” and “vpv1”, and the error is gone.
next the template sensor need to be configured correctly.

I stopped using the API’s as it doesn’t give me all the details I would like.
Now I scrape the Goodwe Sems portal with the following code:

1 Like

Does this still work ? I am looking to use it within my setup but unsure how to go about it? A simple guide would be brilliant! Good work so far!

Does it work? Yes. Can it be done better. Definitely :slight_smile:
Check this Guide on how to run the code :wink:

1 Like


Can you post a copy of your sensor configuration in the configuration.yaml?

I got it to work!

Clone the repo ( somewhere.
Edit the file to have your user and password for the SEMS portal.
I also added some print statements for debugging.
Also change:
mqtt_host = "localhost"
and add after line client =mqtt.Client(mqtt_client_name):
client.username_pw_set('homeassistant', password='hello')

In automation.yaml:

# needed by gsps_beta
  password: hello # this starts an embedded MQTT server
  discovery: true
  discovery_prefix: homeassistant

Now you can run the python file:

It should add a gazillion sensors to home assistant. I hope they can somehow be grouped.

I now run the python file using crontab every 5 mins:
crontab -e
in my current (to be fixed) case: */5 * * * * /opt/homeassistant/bin/python /home/homeassistant/.homeassistant/custom_components/ >> /var/log/ 2>&1

1 Like

Did you install this on Hassio or just Home Assistant? I am running Hassio so i am unable to use the script as it doesnt allow for using imports.

I’m using home assistant.
Unfortunately the script itself runs outside of home assistant and I just call it using Python.
Home assistant just runs the MQTT bus that the script connects to.

I’ve just ran the script within VSC and it connected with HA, and i can see on MQTT.FX that it was sending all the info through. However i cannot see the new sensors which should have appeared?

I added username and password for MQTT.
And print statements for some output.

For the new sensors, you need home assistant to listen to the MQTT and have autodiscovery on.
The config:

  password: hello # this starts an embedded MQTT server
  discovery: true
  discovery_prefix: homeassistant

enables this with an MQTT server embedded in home assistant.

Managed to get it working now on my Mac running it on visual studio. Need to try and work my Nuc so i can run this as a cron task within the server instead of my manually deploying

I’m now trying to convert @sprk-nl’s code into a custom home assistant component. It will not use the MQTT stuff anymore then.
Any comments or ideas I should take into account?

I noticed that it pulls through the information, but without cross checking the info and the web page its hard to tell where the information has come from! If i can help let me know

Done for now. Seems to work. Nothing polished yet.

1 Like


1 Like

Just tried it, and all working this end.

How often does this sensor update, and is it possible to change the refresh time?

Nice to see it is working.

I don’t have a clue how often it updates. If I look in my grafana dashboard which shows the data that home assistant exports to influxdb, i have a data point around every 2/3 minutes for this day. If you have a clue how to control it, please let me know.

Hi there,
Nice to see this progress on a Goodwe integration.
I have also received info about native access instead of web scraping for which I’ll update the code… Soon ish