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.
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.
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?
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.
or if they read our message and change the behaviour (unlikely) 
Was this brought back to support?
You can submit 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.
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?
Yeah, that would be another good reason.
