Scan interval

[xDAVIDx93]

Changing this line in the YAML

/homeassistant/custom_components/alphaess/const.py

SCAN_INTERVAL = timedelta(seconds=10)

Used to make most of the important sensors like instantaneous solar generation
instantaneous grid I/O
instantaneous battery I/O
Instant instantaneous load

Refresh every 10 seconds

After the most recent update though changing the yaml scan interval to 10 seconds and restarting Home Assistant does nothing everything refreshes at 1 minute still.

Any idea how we can fix this?

[Poshy163]

Odd, nothing was changed. ill look into it. tho its working locally on my build

[xDAVIDx93]

Odd, nothing was changed. ill look into it. tho its working locally on my build

Any extra steps I could take to ensure the scan interval I set is adhered to?

[xDAVIDx93]

Also just checking this is correct, right?

[Poshy163]

yes, that is correct,

are you able to try a scan time of like 20s? and see if that fixes anything?

[xDAVIDx93]

yes, that is correct,

are you able to try a scan time of like 20s? and see if that fixes anything?

Tried 20s everything still refreshing at 60s…

[Poshy163]

@xDAVIDx93 are you rebooting after making the modification to the code?

and after a reboot, does it still show as the seconds you set it to, rather than 60?

[xDAVIDx93]

@xDAVIDx93 are you rebooting after making the modification to the code?

and after a reboot, does it still show as the seconds you set it to, rather than 60?

Yes I’m rebooting and the update to the scan time sticks 👍 but isn’t being followed

[Poshy163]

Too easy, I got some time tonight, I'll have a look into it

[Poshy163]

@xDAVIDx93 are you running a single inverter/battery on the API or have you got 2 or more hooked up to the same API credentals?

[xDAVIDx93]

@xDAVIDx93 are you running a single inverter/battery on the API or have you got 2 or more hooked up to the same API credentals?

@Poshy163 Host and follower

[xDAVIDx93]

@Poshy163 any thoughts on leader/follower setups?

I mainly use this integration for monitoring (which is why I’m trying to get the scan interval down for a higher resolution) and I use axles modbus for control of my host. (Which also controls the follower but no monitoring of follower… 😢)

I can’t connect my follower because it’s modbus is in use communicating to host (we think) I’d love to be able to use both host and follower via modbus but that doesn’t seem possible at this stage….

[Poshy163]

@xDAVIDx93 im looking into it now, but the TLDR of it is, how we are handing calls atm is, make a request -> wait for response -> wait for all responses to load -> show data unfortunately with 2 batteries hooked up to the same account, the scan interval is useless as it takes about 50 or so secs to grab all the data from the openAPI (without being rate limited)

when this issue was opened, i opened a ticket with alpha to see if i could get a true answer for how much the API is rate limited (it used to be super strict back in the day). but all i got was a million different answers without giving me the answer.

atm, im feeling like ill have to rework how that original system works, as we do about 8 or so calls to the API per inverter, and trying to shrink the amount of time that takes without hitting the rate limit is hard

[xDAVIDx93]

@Poshy163 okay thanks 🙏

[Poshy163]

i think i have an idea, but might need to see what @CharlesGillanders thinks for it:

1. Split polling into fast and slow data paths.
2. Fast path every ~10-20s: only instantaneous power sensors (generation, load, battery I/O, grid I/O, current charge/discharge schedule).
3. Slow path every 10 mins: config, totals, daily aggregates, diagnostics.
4. Keep last known slow values cached and merge with fresh fast values before publishing.