The issue was only discovered 2 days ago, so well after that release was made.
There is a patch available on the link provided above, I’ve got a PR ready for the next release I just need to fix the tests later today and it’ll be merged in.
2 Likes
@muppet3000 I have set my datalogger to upload every minute to growatt server. However home assistant only updates the data every 2 minutes. I checked the code and the scan_interval is set to 1minute. It only updates every minute if I change the throttle to 55 seconds.
Do you see the same behaviour?
I can’t say I’ve tried to test it. I didn’t know you could configure the datalogger to upload more often, how did you do that?
Mine is set to 5 minutes (what it seems to come with as default), if you can tell me how to change it maybe I can try at my end?
When you follow this document (I have the dongle that is on page 2). You can connect to a webserver on the dongle. You can input your wifi details on the main page, but on one of the other pages (Advanced I think) you can set the upload interval. You can set it to 1 minute.
If this is not clear, I can get you some more detailed information when my inverter is awake again.
Is there anyway of connecting to the webserver once the dongle is connected to my router?
I’ve browsed all my connected devices on my router and can’t seem to connect to anything that connects to a webserver.
From my experience it seems that the webserver is only running when the dongle is not connected to the router.
You only need to select the wifi SSID and enter the password (and change the upload interval 
). You save the settings and restart the dongle. It will automatically start uploading again to your growatt account.
Thanks.
I have the older dongle which isn’t wifi, it communicates via RF to a little hub box which is connected to my network via an ethernet cable. That said, I bet it’s all the same webserver etc. so if I just try and hit the IP of the hub box I may have the same luck!
Will try it at some point this week maybe.
As for your problem with polling frequency, it used to be configurable via the configuration.yaml, but, I bet since it was updated to use the graphical GUI it’s not used anymore. I should be able to investigate. If it’s no longer configurable we’ll need to add it back in again via the UI.
In the code a scan_interval of 1 minute is defined.
But there is also a throttle defined with the same time as the scan_interval.
From my experience these settings conflict. The sensor is instructed to update every minute, but it is not allowed by the throttle.
An example:
1 minute → sensor wants to update, throttle prevents update because it can only update when the sensordata is older then 1 minute. At this moment the sensordata is exactly 1 minute old so it will not update.
2 minute → sensor wants to update, sensordata is now 2 minutes old. It is allowed to update now.
When I change the throttle time to 55 seconds, the sensor updates every minute. Because when the sensor wants to update at the 1 minute mark it is older then 55 seconds and allowed by the throttle for updating.
I hope you understand my story.
1 Like
Muppet3000 Thanks for all your hard work on this subject. I had everything working and then BOOM!!! nothing… Do you know if this fix will be on the next update?
Hi, sorry, I have seen your message, I just haven’t had any time recently to do anything with it.
The latest release should have resolved this for everyone.
Thank you very much.
Now I’d put one shelly em on the batteries line, so I’m able to have “situation under control” …
Only to have a base line for automation and script based on energy available…
Thanks.
Many thanks to the code owners for this fix!
I do have a question however; I have 4 lifetime sensors provided through this integration;
- sensor.plantid_lifetime_energy_output
- sensor.plantid_lifetime_total_energy_input_1
- sensor.plantid_lifetime_total_energy_input_2
- sensor.pv_total_lifetime_energy_output
The first three reset each day to zero and come back to their previous value once the sun starts shining, the last one is the only one that simply keeps increasing and does not reset to zero.
I would like to be able to use both per-side/string values as input for the Energy panel, but given that they reset each day it is impossible, as they register hundreds or even thousands of kWhs produced each morning.
I’ve tried a template value to be used to ignore the 0 values but it doesn’t seem to work.
Is there any chance that these lifetime values could be captured with the integration without the daily reset?
Hi @marcelg you’re not the first person to have seen this.
Would you mind posting the above message on this ticket: https://github.com/home-assistant/core/issues/56500
Also if you can tell me on that ticket what type of system you have, I’m trying to work out if this affects specific systems.
1 Like
Done! Many thanks! If you need to know more details or need me to try something, just let me know. I cannot write code, but I’d gladly help!
Thanks, I may need to borrow some credentials at some point to confirm the ‘fix’ that I have in mind. But lets get it all confirmed by the others that are having the same issue, otherwise I may be looking at two different “bugs”.
Hi, I have the same question as you, how can I see the values of the Eastron meter (model SDM230) in HA, in the integration with Growatt they do not appear. It would be essential to be able to include smart plug automatisms. You have been able to integrate it directly with HA through Modbus Integration. All the best.
1 Like
are you using a growatt inverter? what entities did you use to achieve this?
1 Like