-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Times for energy data collection #256
Comments
@signalkraft Another solution could be an option to disable automatic energy data request + a service for energy data request that user can call only when needed (maybe every day at 23.59 through an automation). In this way we can have the possibility to manually control energy data request and possibly to avoid api request limit exceeded error |
https://github.com/signalkraft/mypyllant-component/releases/tag/v0.9.0b2 Good idea, I disabled the update schedule by default now but left the setting on the old value for existing installations. You can unset the corresponding update interval option in the configure dialog of the integration, to get the same behavior and schedule your own updates with HA's built in update service: https://signalkraft.com/mypyllant-component/#seconds-between-energy-data-updates |
Just tested https://github.com/signalkraft/mypyllant-component/releases/tag/v0.9.0b2. Works, but at the first attempt to retrieve energy data through automation, i got error |
That's in the integration: https://github.com/signalkraft/mypyllant-component/blob/main/custom_components/mypyllant/const.py#L36 |
After several days that energy data were not available, now with the new request by automation, energy data are back. This is the automation that i'm using. I also reduced at only 4 energy values (i have an hybrid system):
|
Since update to HA 2025.1.1 everything works fine. |
Before requesting a new feature / a new sensor
Describe the feature you want
I retrieve my energy data every 6 hours - otherwise I get blocked. I've already tried a lot ...
Now I have the problem that the energy data is often missing at the end of the day. Because the data was retrieved at 8 pm, for example, the next data is not retrieved until 2 am. In this case, however, the meter has already reset to 0 and the values from 8 pm to 0 am are therefore missing.
Is it possible to set fixed times when the data is fetched? Even better: the most sensible cycles are automatically recognized. At 6 hours, for example, the last collection should be shortly before midnight.
Or it will be possible to transfer data to HA that lies in the past. However, I don't know how this could work ...
The text was updated successfully, but these errors were encountered: