Mike Marvin

The issue stems from how I'm doing those updates, like you've observed those sensors all update from the API every 15 minutes, but when the 1 minute sensors are active...

It's using an ESP32 so the data is sent over wifi, not ZigBee, and unfortunately the only way to get data locally is to flash a custom firmware onto the...

Again, reminder that the data isn't sent over ZigBee, it's Wifi. People have tried to intercept the data between the device and router but it is encrypted and we don't...

Unfortunately I'm not aware of a way to backfill data like that, other than directly interfacing with the backing Home Assistant database. Home Assistant tracks the history itself and all...

Not a bug, the 1 minute data is the same as in the app: the average power over a one minute interval. To convert to energy you just need to...

Hello, this is a tough one for me because it's not something I can reproduce and so it is not something I can test fixes for. I have started on...

My recommendation for alerting on laundry (or anything on a dedicated circuit) is to start the automation when the power usage is more than some value, then add a wait...

```yaml alias: Laundry - Dryer Complete description: "" trigger: - type: power platform: device device_id: f2582f2dfc4ed5c8ce6391bcaa9347f1 entity_id: sensor.dryer_2_1min domain: sensor above: 100 condition: [] action: - service: light.turn_on target: entity_id:...

I have 38 devices under the integration in Home Assistant so the numbers you're seeing might just be a fluke. I have a Vue 2 with 16 circuits, then a...

The warning will go away in the next release. It isn't a concern, just a heads up that the current code won't still work in 2025.