OpenUV data stops updating at peak value. Still under daily quota of 50

Configuration
1

Setup Open UV yesterday. Added sensor.openuv_current_uv_index and sensor.openuv_max_uv_index to an Entities card on my dashboard. Works as expected until the current_uv_index matches or gets close to max_uv_index (yesterday it matched the daily max exactly when it stalled, today was slightly under). Then the data just stalls for the rest of the day until something forces it to update like an HA restart.

Calling OPENUV.UPDATE_DATA under Developer Tools > Services updates the data on the dashboard but cannot figure out why it stops updating automatically. By proxy this confirms I have not reached my daily quote of 50 request. I also manually verified by checking my openuv account and I’m not even at 20 requests for the day and can see it go up when I make those manual calls. Wasn’t even close yesterday either.

Screen Shot 2020-09-04 at 2.23.33 PM
Screen Shot 2020-09-04 at 2.23.33 PM834×383 51 KB

Screen Shot 2020-09-04 at 2.31.04 PM
Screen Shot 2020-09-04 at 2.31.04 PM1292×820 32.8 KB

Thoughts on why it’s not updating? Bug? Configuration?

2

Actually it looks like restarts and even calling OPENUV.UPDATE_DATA don’t always update the value despite the fact that I can call the API myself via curl and get the updated value at any time. Is the integration caching it somewhere and only allowing it to get updated at certain intervals even when calling OPENUV.UPDATE_DATA?

3

Reviewed the documentation and implemented this automation to force updates. Seems to have fixed it. https://www.home-assistant.io/integrations/openuv/

automation:
  - alias: Update OpenUV every 30 minutes during the daytime
    trigger:
      platform: time_pattern
      minutes: '/30'
    condition:
      condition: and
      conditions:
        - condition: sun
          after: sunrise
        - condition: sun
          before: sunset
    action:
      service: openuv.update_data
4

Question on the: minutes: ‘/30’ line.

When I create the automation my automations.yaml file shows: minutes: “30”

Why ‘/30’ versus “30”? Why the slash?

5

Never mind, I just found this:

Time pattern trigger

With the time pattern trigger, you can match if the hour, minute or second of the current time matches a specific value. You can prefix the value with a / to match whenever the value is divisible by that number.