Replies: 3 comments
-
CONF_TIMEOUT/DEFAULT_TIMEOUT is legacy from the original ha-nfl sensor. Since it's part of the schema, pulling it out would break backward compatibility. In reality, the sensor behaves as you suggested. It updates at 10 minute intervals until 20 minutes before game time, then updates every 5 seconds until the the game is over. |
Beta Was this translation helpful? Give feedback.
-
Ah, I see. Great stuff. Thank you for explaining. Keep up the great work. |
Beta Was this translation helpful? Give feedback.
-
Oh, you mean when you set up the sensor. I completely forgot about that. I’ll see what I can do there. Good call. |
Beta Was this translation helpful? Give feedback.
-
Hello,
Firstly, I have to thank the developers. Ha-teamtracker is great.
I'm not sure, but as I understand the interface, ha-teamtracker polls the servers every 120 seconds by default.
I base this off the field "Update Timeout (in seconds) 120" when setting up the integration.
My take:
Between games, 120 seconds is a bit too often. But during games, 120 seconds can be a bit too seldom.
Suggestion:
Have variable updates. Let's say, between games, poll the server once every 2 hours.
But during games update every 30 seconds.
Could even be that when we're getting close to game-start, the update interval should be something in-between. Perhaps 2 hours before game, poll every 2 minutes, to see if there are any changes.
Caveat: This setting might be a timeout, not an update interval. If so, this topic is a bit wrong. But perhaps relevant anyway? Not sure how updates are done.
Beta Was this translation helpful? Give feedback.
All reactions