[FEATURE] Polling intervals

[craiger112]

Hey,

is it possible to set the polling intervals to less than 30 seconds? This long interval is too long for my home automation needs.

Best regards from Rügen

[moehrem]

Hi @craiger112 ,

Technically possible. But may you please describe a usecase for my better understanding?

I think that a request of the same data over and over again is not helpful. It might even lead to API restrictions from Divera.
Due to several reasons I even think about totally avoiding useless polling by using webhooks. Thus requesting data only in case of active alerts.

Thank you for further infos!

[craiger112]

Hey,

Sure, no problem! I control various lights and switches via automation. If the alarm is triggered at Divera and, in the worst-case scenario, the lights only turn on 30 seconds later, that's too long for me. If things go well, I'll already be in my car on my way to the fire station within those 30 seconds. A check with a 10 or 15-second delay would be much better.

Unfortunately, I haven't been able to get the webhook integration working, otherwise I would use it.

[moehrem]

Hi @craiger112 ,

I thought so :)
Thats exactly my usecase - but thats not what this integration is used for. I try to support giving data from local actors and sensors to Divera. To have alarm data available is more of a side effect.
DiveraControl lets you communicate to Divera by creating & changing alarms, vehicle data, creating news, etc. Its not meant to be used as a personal alarm trigger for home automations, but more for triggers used in your fire station. And at a firestation a 30s delay is acceptable, as long as we're talking about voluntary fire fighters.

For personal use have a look at the integration from @fwmarcel here: https://github.com/fwmarcel/home-assistant-divera
Though I am not sure about there polling interval settings.

I'll check the minimum acceptable polling interval with Divera. Maybe we can lower it a little without getting in trouble.

Cheers!

[moehrem]

Hi @craiger112 ,

got an answer from Divera:
There is no fixed limit for polling intervals, but an internal monitoring. So any excessive polling will raise an alert, which may result in locking your api-key.

Guess we have some room lowering the polling interval. I may do so with any upcoming update, but I have not decided about the exact values yet.

[craiger112]

Hey thanks for the answer! I will look soon