Skip to content
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

Open
1 of 3 tasks
blueJack92 opened this issue Dec 31, 2024 · 6 comments
Open
1 of 3 tasks

Times for energy data collection #256

blueJack92 opened this issue Dec 31, 2024 · 6 comments

Comments

@blueJack92
Copy link

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 ...

@gio-dot
Copy link

gio-dot commented Jan 3, 2025

@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

@signalkraft
Copy link
Owner

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

@gio-dot
Copy link

gio-dot commented Jan 5, 2025

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 Quota Exceeded on https://api.vaillant-group.com. I have to say that during this period even the official app get me often "data retriving not yet available.." warning.
Just a question: the 10800s timeouts after quota exceeded is decided by Vaillant server or by mypillant integration?

@signalkraft
Copy link
Owner

Just a question: the 10800s timeouts after quota exceeded is decided by Vaillant server or by mypillant integration?

That's in the integration: https://github.com/signalkraft/mypyllant-component/blob/main/custom_components/mypyllant/const.py#L36

@gio-dot
Copy link

gio-dot commented Jan 5, 2025

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):

  1. Ecotech energy on domestic hot water
  2. Ecotech energy on heating
  3. Arotherm energy on domestic hot water
  4. Arotherm energy on heating

image

description: Update myVAILLANT energy data
triggers:
  - trigger: time
    at: "23:50:00"
  - trigger: time
    at: "18:00:00"
  - trigger: time
    at: "12:00:00"
  - trigger: time
    at: "06:00:00"
conditions: []
actions:
  - action: homeassistant.update_entity
    metadata: {}
    data:
      entity_id:
        - >-
          sensor.seve_device_0_arotherm_consumed_electrical_energy_domestic_hot_water
mode: single




@zschaler
Copy link

zschaler commented Jan 7, 2025

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):

  1. Ecotech energy on domestic hot water
  2. Ecotech energy on heating
  3. Arotherm energy on domestic hot water
  4. Arotherm energy on heating

image

description: Update myVAILLANT energy data
triggers:
  - trigger: time
    at: "23:50:00"
  - trigger: time
    at: "18:00:00"
  - trigger: time
    at: "12:00:00"
  - trigger: time
    at: "06:00:00"
conditions: []
actions:
  - action: homeassistant.update_entity
    metadata: {}
    data:
      entity_id:
        - >-
          sensor.seve_device_0_arotherm_consumed_electrical_energy_domestic_hot_water
mode: single

Since update to HA 2025.1.1 everything works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants