Can you extend the timeout before an entity becomes unavailable (Open Media Vault integration)

Configuration
1

I am using the open media vault HACS integration, and the default polling time is set to 60 seconds. Keeping it like this means the hard disks connected to OMV never get a chance to spin down (known issue).

So I have set the polling interval to 7200 seconds, or 2 hours. This works fine, but I can now see gaps in my entities history, where they go unavailable after 1 hour.

Is there a way to extend this so the entities don’t go unavailable until 2 hours ? (or maybe more in the future if I extend the polling time further).

2

No takers ?

3

Short answer, no.

Long answer, you’d have to change the integration. Either keeping your own modified version of it, or submitting a PR (pull request) to change the behaviour for everybody.

4

The only other way I thought of doing this is to wrap every entity in another template, but that would be a royal pain. I guess I just have to live with the gaps.

5

@Tinkerer got me thinking, so I started digging around the OMV code. The plugin doesn’t seem to be actively developed anymore, but I think I found a line in the file omv_controller.py that should do the job.

Go to line 84 and it should look like this:-

self.hass, self.force_hwinfo_update, timedelta(seconds=3600)

I’ve changed it to this, which I am testing now:-

self.hass, self.force_hwinfo_update, timedelta(seconds=7200)