Polling automation issue

Configuration
1

On the following page, section 3 is theoretically about setting a custom polling interval, but it doesn’t explain how to set that interval. I cannot find any obvious way to set that interval:

This is to set a custom polling frequency for the HACS iSolarCloud integration in an attempt to mitigate the “unavailable” flags that may be related to the polling frequency.

Can someon explain how to set teh interval for this polling frequency automation?

Chers,
Gaetano.

2

Hmmm, I just checked the calls included in my plan and I can make 2000 per hour, which is roughly 1 call every 2 seconds if my maths are mathing… that should be way sufficient… so perhaps it isn’t the automation frequency that is the problem.

It would still be nice for those guidelines to reflect how to set a custom polling interval.

3

I guess the reason the automation instructions on that link you posted simply says “Define any trigger and condition you like” is that people might want different triggers other than time-based ones.

In your case, you can use a time pattern trigger and have it update your entity every x seconds/minutes:

  triggers:
    - trigger: time_pattern
      # You can also match on interval. This will match every 5 minutes
      minutes: "/5"

EDIT: Had a quick look at that integration’s issues. Have a read through this one & don’t set your automation to poll more frequently than every 5 minutes.

4

Thanks gain Shadow. I have set up 2 triggers, one that refreshes the sensor every 5 minutes, and one that sends the message if the value is between two numeric vaues Wait and see I guess.

PS the sensors are still unvailable.
PS the author says that he added the interval feature in v 0.6.0, but the latest version is 0.2.2 - oooooh, there are two integrations available. I am using this one: sungrow-hass/scripts at main · KRoperUK/sungrow-hass · GitHub, I may just need to try the other one…

5

And both integrations have the same display name, just a different logo.

1 Like
6

So far, so good with the Bugjam integration, but it has much fewer sensors, a dozen compared to the 73 in this integrations.