mjmeli/ha-duke-energy-gateway

sensor.duke_energy_usage_today_kwh >>> Not Working

tteck opened this issue · 14 comments

tteck commented

It hasn't been reporting since around 3 pm est. according to HA's energy dashboard
No errors in log
sensor.duke_energy_current_usage_w is working

Mine hasn't stopped reporting here. I'm surprised this one would give out because it just makes a new REST call every 60 seconds. Have you tried restarting your HA instance in case something got in a bad state?

tteck commented

It must be my gateway!? I've reset everything. Even on my phone it's not updating 1hr, 15min, usage

That's really strange that it isn't working yet the live usage is working. Hopefully you can figure it out.

I have the exact same issue

Trying to restart gateway now. HA restart didn’t help.

Got it working again after restarting and pairing the gateway.

tteck commented

What do you mean by pairing?

Most of the time when I pull the power on the gateway I have to re-pair the meter to the gateway. The app usually prompts me for it but you can go in the smart meter information in the app and choose pair gateway if it’s not already connected.

But now I appear to have lost the current energy sensor.

tteck commented

Had to push the reset next to the Ethernet port, repair to the meter and all's well now, including the current usage sensor.

tteck commented

Screenshot 2022-02-25 6 14 00 PM
Looks like the decimal point moved?
Maybe not. It may not be picking up past data

I have dual setup on different docker servers.
Two HA (V2022.2.6 & 2021.12.4) instances.
Two physical locations with two different meters.
Both "Current Usage" sensors went offline, one late 2/24/22 at 15:28 and the other on 2/25/22 around 03:00.
Both "Usage Today" sensors appear to still be working as designed.
I have not done any troubleshooting yet. Holding stable to see if any more forensic data is needed.

Attached are highlights of the log file.
duke-errors-20220228.txt

After a couple more HA restarts and Duke Energy app force closes and now both sensors are working.

Since this appears to be a Duke API/gateway problem that also happens on the app, has anyone contacted Duke about it?