#Configurable update interval for EDL21
1 messages · Page 1 of 1 (latest)
Because the device sends messages every 3-5 seconds and we currently only write state every minute
Now I'm not in favor of just setting it to 3 and calling it a day, but to make it not configurable is meh if we do have dsmr
why?
Okay so id argue that automations based on energy are nice. However, for a local solution I think a minute could be considered a low interval. For example if a device is starting right at that moment and have a peak in power, it'd show that for a minute
Some won't care, some would
And currently we're kinda forcing everyone to pick a minute
If the device is updating every 5s we should get the information at that interval
Especially with a interval of 1 minutes we loose 12 states
3-5 seconds from what I understand
I would go with the upper bound of 5s which is a big improvement over the 1 minute
But again the user can write an automation that fires each x seconds to update it
Nope, it's push based
They are throttled on purpose
If it's pshed based why are we throttleing?
Because they push a lot
and?
Same with DSMR
I don't get it why we should ignore data if it is pushed to us.
I think HA is performant enough to handle nowadays this frequent data
I get it if we are polling the data but data pushed to us, I would always accept it
I mean, check out frencks response in the comment linked in the main post
That is our stance for as long as I know
but that comment is about polling and you said this is a push based integration.
Couldn’t we let the user decide?
Sure, they can. They can implement any polling logic they see fit. We have services and documentation for that available, using the homeassistant.update_entity service.
This is from his comment. So is the integration a polling one or a pushed based one?
Can we manually poll data? Some push integration are supporting it
If not then Frencks comment makes no sense as it's speaking about polling or maybe it's outdated (maybe it was polling back then)
From what I can tell it was always pushing
Let's ask Frenck tomorrow but I my opinion we should accept any data pushed to us
It is very weird that we have a push metering device providing 5s and we throttle it to 1 min
5s isn't that high
Just reading this, we had a discussion with Frenck in the past on adjusting values as we would go 'under' the factory defaults (DSRM + Climate) so users need to follow {% include common-tasks/define_custom_polling.md %}?