Only sensor.homevue_123_1min and sensor.homevue_totalusage_1min are working.

[NoSadBeHappy]

I didn't update anything, and nothing auto updated, but all of my sensors have stopped giving any data on the minute data point.

Home assistant, one example.

Prometheus scrape, only two sensors available.

[NoSadBeHappy]

Let me know if you need anything else. I am happy to help resolve this issue, I just don't know what logs you would need.

[NoSadBeHappy]

Update: after restarting home assistant, it now works as intended. It seems to have all stopped working 10 minutes after midnight yesterday, at least thats when data stopped being recorded by prometheus. I am running home assistant on docker, so let me know what logs I can send to help fix the issue.

[FredericG-BE]

I had the same issue: all 1 minute sensors (except for total consumption) were unavailable until I restarted HA.
Thanks for the excellent work!

[NoSadBeHappy]

Yeah. Also, quick update, it has still been happening. I have temperarly solved this problem for now by automatically restarting HA every couple days in the middle of the night.

[matthojo]

I have found just reloading the integration is enough to get this working again.

[NoSadBeHappy]

Thank you, yes I fegured this out recently, forgot to update this issue.

[chrwei]

I have the same, or a similar, issue, except it rarely works on startup or restarting HA doesn't fix it. in fact, restarting is a sure way to trigger it. Reload does make it work again, and the time it takes to stop working seems rather random. All I'm seeing in the logs is my automations complaining that the sensor is unavailable

[sdwhwk]

I can concur on that. 1min sensors quit working yesterday for me and resetting stopped working completely (for a while that would work when it stopped working a few days ago). I uninstalled/reinstalled the integration in HACS and HA just a few minutes ago and when it repopulated the sensors, all but the two 1min that the OP stated didn’t. So now all I have are the daily and monthly sensors with minute total and main.

[NoSadBeHappy]

@sdwhwk try restarting the integration, and/or HA.

[sdwhwk]

That brought them back. Let’s see how long they stay up.

[chrwei]

reloading the integration seems to be required after a reboot, and occasionally otherwise, possibly after internet loss?

I added this automation, runs every 15 minutes, keeps it from been unavailable for very long.

Add/remove/edit the sensors to whichever of yours is most commonly unavailable. "balance" is the most common for me, but sometimes it's one of the mains instead. Edit the target sensor too, doesn't matter which one you use, it's just so the reload service can locate the integration.

alias: Check Emporia
description: Check Emporia Vue for reload
trigger:
  - platform: time_pattern
    minutes: /15
    enabled: true
condition:
  - condition: or
    conditions:
      - condition: state
        entity_id: sensor.panel1_123_1min
        state: unavailable
      - condition: state
        entity_id: sensor.panel1_123_1min
        state: unavailable
      - condition: state
        entity_id: sensor.panel_2_balance_1min
        state: unavailable
action:
  - service: homeassistant.reload_config_entry
    data: {}
    target:
      entity_id: sensor.panel1_123_1min
mode: single

[sdwhwk]

Thanks, will try this tonight! On the target, do you just put that one entity or all the others also?

[chrwei]

just the one, and it doesn't matter which one, it can even be some other circuit or interval, it's only so the service can find the integration to restart. Seems odd an odd way to do it, but it's the easiest way. there's also a way to do it by integration ID, but that's not easy, and not supported by the Visual editor.

[NoSadBeHappy]

Just reporting back, just today it broke again. Hasn't for a month or so, but today I realised that I set up the automation listed above, but i didn't change the entity id for the target to be correct for my setup. (oops) Anyways, still an issue, and thank you for the help chrwei!