Skipping update due to missing data: from_time - OPEN UV

[DomAlu24]

The problem

For some time now, the Open UV integration hasn't been updating only the protection window binary sensor, and this message appears in the logs:

`Registratore: homeassistant.components.openuv Fonte: components/openuv/binary_sensor.py:54 Integrazione: OpenUV (documentazione, problemi) Prima occorrenza: 21 ottobre 2024 alle ore 07:45:10 (16 occorrenze) Ultima registrazione: 09:50:22

Skipping update due to missing data: from_time`

What could this mean? The update works fine for all the other sensors.

What version of Home Assistant Core has the issue?

2024.10.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

OpenUV

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Registratore: homeassistant.components.openuv
Fonte: components/openuv/binary_sensor.py:54
Integrazione: OpenUV (documentazione, problemi)
Prima occorrenza: 21 ottobre 2024 alle ore 07:45:10 (16 occorrenze)
Ultima registrazione: 09:50:22

Skipping update due to missing data: from_time

Additional information

No response

[home-assistant[bot]]

Hey there @bachya, mind taking a look at this issue as it has been labeled with an integration (openuv) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of openuv can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign openuv Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

openuv documentation openuv source _{^{(message by IssueLinks)}}

[andreasbrett]

The protection endpoint of the OpenUV API returns from_time = null and to_time = null when there are no protection windows that fit the requested from and to params (= searching for windows where UV is between from and to).

# https://api.openuv.io/api/v1/protection?lat=31.79&lng=-7.09&from=3&to=4
{
  "result": {
    "from_time": null,
    "from_uv": 0,
    "to_time": null,
    "to_uv": 0
  }
}

# https://api.openuv.io/api/v1/protection?lat=31.79&lng=-7.09&from=1&to=2
{
  "result": {
    "from_time": "2024-11-20T09:12:45.435Z",
    "from_uv": 1.0964,
    "to_time": "2024-11-20T14:22:45.435Z",
    "to_uv": 1.9879
  }
}

I think the integration should not error out in those cases but rather set the binary_sensor to false.

[de-Techneut]

Also seeing this error last few weeks.

Logger: homeassistant.components.openuv
Source: components/openuv/binary_sensor.py:54
integration: OpenUV (documentation, issues)
First occurred: 12:58:53 (1 occurrences)
Last logged: 12:58:53

Skipping update due to missing data: from_time

[Phoenix-DH]

I habe the same, and also those:

`Logger: homeassistant.helpers.entity Source: helpers/entity.py:1288 First occurred: February 9, 2025 at 2:00:10 PM (28 occurrences) Last logged: 1:00:10 PM

Update of binary_sensor.openuv_protection_window is taking over 10 seconds Update of sensor.openuv_current_uv_index is taking over 10 seconds `

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[jonwaland]

still an issue, core-2025.5.2

[ivanvmoreno]

This can indeed be replicated by setting the starting and ending UV protection window indexes to the same value (e.g., 3:3). This was solved by increasing the range to, e.g., (3:7).

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[jonwaland]

bump as this shouldn't be an error