Speed of Data Update

[snaven1]

Fantastic piece of work. I have essentially implemented all the functionality with reasonable success. I am using Mickmate's Energy Dashboard code. I have had to make a small number of changes to the code to pick up on certain parameters. Not an issue! My major concern is that the information (data) being provided on the energy status graphic is so out wack from the ISolar Cloud app provided by Sungrow, that it is almost useless. This comes about because the downloading of the data from ISolar portal environment to mqtt server then onto home assistant takes in the order of minutes. I have being observing the rate of update of data within the mqtt server (using mqtt explorer) and updates can take up to 10 minutes. Of course, the actual system has moved on from this already inaccurate figure. So for example .... Tracking parameter p13149 (purchased power), on Isolar app this figure will be changing and updating all the time. On GoSungrow energy dashboard it may update once every 5 minutes ( hard to ascertain the exact wait time ). I assume that Mickmates code is using the command line API interface code to extract the data and then send onto the Home Assistant Mqtt server. I have examined the config.json file that represents that config file for the command line interface, however does not seem to have any polling options that I am aware of. Any assistance would be greatly appreciated.

[NoNameSwede]

+1

[TaxmanNo1]

Hello @MickMake I have a problem in the energy dashboard in Home Assistant, which is probably related to the delay described.

On many days (not always) all the previous day's values ​​(yield, feed-in and so on) are entered with the opposite sign in the period 0 - 1 a.m., which of course then leads to completely wrong values ​​in the dashboard. Will there be a solution for this?