Time-dependent scan_interval #15
Replies: 5 comments 1 reply
-
It would be really great and I would like to do it, but I lack the skill & time to implement that myself. |
Beta Was this translation helpful? Give feedback.
-
I think it would by highly disired feature. home_assistant_tgtg works good, but we are making use of it only when we actually want to order package from TGTG.
In other words, it would be nice to have posibility to turn off/on your sensor by switch on the Home Assistant dashboard. |
Beta Was this translation helpful? Give feedback.
-
Perhaps this could be provided by adding a "service" to the integration (https://developers.home-assistant.io/docs/dev_101_services) Looking at the source code for this integration, you could expose your update function ( ) as a service.The service could be used inside of automations and scripts. This could be used, for instance, to allow end users to set up time-based automations that define periods of time in which the update call happens more frequently that the standard Thank you for you work on this plugin btw, I was pleasantly surprised to come across it 🙏 |
Beta Was this translation helpful? Give feedback.
-
Has anybody made progress on this? Or maybe somebody knows a workaround for getting blocked with too much traffic? |
Beta Was this translation helpful? Give feedback.
-
Hi there, this integration is really great, it gave me great hopes but now I'm blocked behind the captcha too. Having a system to decrease the update frequency as described above would be amazing ! |
Beta Was this translation helpful? Give feedback.
-
I (at least personally) would have an use-case to have higher or lower scan intervals at certain times of the day.
Idea behind it is, that most of (my) tgtg offers will be updated only once a day within a certain time period (here from 8 pm to 8:20 pm). That update does not happen at exactly the same time on each day.
Getting alerted once it is available would be extremely helpful to snatch a good deal.
Toi prevent hammering the tgtg server(s) with useless requests, my idea would be, to define a default scan_interval of e.g. 900 s and a elevated scan_interval of e.g. 30 s which only will be considered if we are in a defined time window (e.g. "elevation_window: 2000-2030" maybe even with a list of windows).
What do you think about this idea?
Beta Was this translation helpful? Give feedback.
All reactions