# Which one is accurate?

**URL:** <https://community.homey.app/t/which-one-is-accurate/144497>\
**Category:** Energy\
**Tags:** zigbee\
**Created:** [October 24, 2025, 5:01pm UTC](https://community.homey.app/t/which-one-is-accurate/144497 "2025-10-24T17:01:19Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![cloudpulse\_01](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cloudpulse_01/32/143041_2.png) [@cloudpulse\_01](https://community.homey.app/u/cloudpulse_01)\
**Post date:** [October 24, 2025, 5:01pm UTC](https://community.homey.app/t/which-one-is-accurate/144497/1 "2025-10-24T17:01:19Z")

</div>

Hello team,

I am currently new to Homey and connected my socket via Zigbee2MQTT. I am getting funny results when it comes to Power consumption between Home Assistant and Homey. Does anybody have an explanation ?

The Energy seems to be correct though (kWh) only the Power is incorrect. It looks like Homey is not reporting the peaks in the graph because if I read the metrics like from Homey I can see the peak to 1600W.

 ![IMG_0273](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/b/1bda0797e9e7958bdb37db7c5870915b294a5ae9.png)

 ![IMG_0274](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/5/a560d96055f65c16c3e9e6d602159df172c0e888.jpeg)

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 24, 2025, 6:03pm UTC](https://community.homey.app/t/which-one-is-accurate/144497/3 "2025-10-24T18:03:14Z")

</div>

Homey starts averaging values very quickly, which will remove transients peaks. Home Assistant will keep the actual data for multiple days (which is configurable, with the default being 10 days) and only then start to average.

---

<div class="post-metadata">

**Author:** ![cloudpulse\_01](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cloudpulse_01/32/143041_2.png) [@cloudpulse\_01](https://community.homey.app/u/cloudpulse_01)\
**Post date:** [October 25, 2025, 7:45am UTC](https://community.homey.app/t/which-one-is-accurate/144497/4 "2025-10-25T07:45:54Z")

</div>

> [@robertklep](#):
>
> only then start to avera

thank you for your answer Robert. How can I determine then at what level of Power goes my device if I am not in front of the screen and wants to read graphs?

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 25, 2025, 8:00am UTC](https://community.homey.app/t/which-one-is-accurate/144497/5 "2025-10-25T08:00:55Z")

</div>

> [@cloudpulse\_01](#):
>
> How can I determine then at what level of Power goes my device if I am not in front of the screen and wants to read graphs?

You can’t with Homey, because it simply removes the actual data very quickly and replaces it with the averaged values.

The only way will probably be to use an app to export your data to an external database and use an external visualiser (like Grafana) to show proper charts. Or keep on using Home Assistant.

---

<div class="post-metadata">

**Author:** ![cloudpulse\_01](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cloudpulse_01/32/143041_2.png) [@cloudpulse\_01](https://community.homey.app/u/cloudpulse_01)\
**Post date:** [October 25, 2025, 8:38am UTC](https://community.homey.app/t/which-one-is-accurate/144497/6 "2025-10-25T08:38:12Z")

</div>

or if they read our message and change the behaviour (unlikely) 😃 Was this brought back to support?

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 25, 2025, 8:42am UTC](https://community.homey.app/t/which-one-is-accurate/144497/7 "2025-10-25T08:42:51Z")

</div>

You can [submit a support request](https://support.homey.app/hc/en-us/articles/360015784034-Submitting-a-support-request) if you feel that this is a bug, but it’s by design and I doubt it will be changed.

One of the reasons is that Homey has limited storage, and aggressively averaging and compressing data is the only way to prevent that storage from filling up.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [October 25, 2025, 2:26pm UTC](https://community.homey.app/t/which-one-is-accurate/144497/8 "2025-10-25T14:26:54Z")

</div>

In five years I’ve never seen anything over 70MB for insights (Pro 2019). Is that a bigger number on a Pro 2023?  
(oh, once it was 425MB \> backup failed \> support said nothing was found in the logs \> restoring a backup appeared to be the only fix)

In my case it can be increased to 400MB if I could control the limit myself.  
Maybe the agressive averaging is an eMMC saving choice?

 ![Screenshot_20251025_161535_Firefox](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/5/85167888d0387fd032aab51c9b68052cd659344e.jpeg)

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [October 25, 2025, 3:11pm UTC](https://community.homey.app/t/which-one-is-accurate/144497/9 "2025-10-25T15:11:37Z")

</div>

> [@Peter\_Kawa](#):
>
> Maybe the agressive averaging is an eMMC saving choice?

Yeah, that would be another good reason.
