I have the same issue with some Heatit ZM Single Relay that control the lights. They report some crazy high energy usage, and it seems to be because the relay sometimes reports an erroneous energy value (effect or watt is correct). It corrects itself on the next reading, but the consumption adds up in the energy tab.
I talked with the producer and they say it is a known problem with the SDK and not possible to fix without replacing the unit. Can you make some error correction in the software for this problem @Emile?
I have added screenshots below of the energy tab and the accumulated energy consumption of one of the relays.
I have a Smart Meter which measures all my Data, PV, Battery, Grid Power etc. I have excluded this from energy tab because of wrong and only PV reading. Furthermore, I am now trying to split this values apart by using advanced device capabilities. PV is working fine, but is there any way I could say the AVD is measuring the power? And Battery?
Really Interesting!!!
So based on the information from @Magnus_Engseth, we can bury the rumor that the incorrect energy data is coming from the devices, right?
What we know, this problem only seems to occur with Z-Wave and Zigbee devices from different manufacturers.
Z-Wave again?
@Emile and @Robin, these incorrect energy data, wherever they may come from, have no effect on the Power by the Hour app from @Gruijter, as far as I can tell. So it should be possible to fix this problem in the energy dashboard somehow, shouldn’t it?
I included a filter that ignores very unlikely values. But I can understand Athoms position; the source data should be correct. ‘Fixing’ errors somewhere else is always less effetctive and prone to newly introduced errors (what if the filter filters out a very unlikely value, but in fact it was a real value?)
One day I proposed to add an “extremes” or a “very unlikely values” filter, with a possibility to disable it for individual sources.
If Athom wants the Energy thing to be successful, they should not solely rely on correctness of data by 3rd party devices imho.
Users will point the finger to Athom, not to the users’ faulty devices.
I agree with you, Robin. But I still doubt that so many Z-Wave and Zigbee devices from various manufacturers provide incorrect data.
So what could be the reason for these false data being sent to Homey?
Faulty Z-Wave and Zigbee chips?
Faulty Z-Wave and Zigbee software/firmware?
Interferences?
I can’t imagine it.
And if I understand the information from Magnus correctly, it’s a problem with the Homey SDK.
@robertklep, have you ever noticed such faulty data of Z-Wave and/or Zigbee devices in Home Assistant? Or have you ever noticed about this issue in the HA communities you are active in?
Pls. have a quick look at the peaks in second screenshot of the post #661 from @Magnus_Engseth, to understand what we are talking about.
I apologize for mentioning you here without being asked. But I would be very interested to know whether this problem also occurs in HA. If so, then we can be highly sure that the problem is caused by the devices and not by a Homey.
Thanks in advance!
I don’t have any power measuring Z-Wave/Zigbee devices myself so I don’t have any personal experience with this, in HA or otherwise.
Looking at the peaks in the second graph of post #661, could this be caused by Homey’s averaging of Insights data?
If not (or unlikely), can you give me some device brands and model names of Zigbee devices for which this happens? I can check the z2m code to see if there’s any special handling of power/energy-related clusters.
Athom has most likely added the energy dashboard as a selling point and to be competitive. The topic of energy monitoring and saving is becoming increasingly important. That’s why Athom is also now selling their own Homey Energy Dongle.
But there are problems with the Energy Dashboard and energy data from various Z-Wave and Zigbee devices. @Robin has consistently pointed the problem towards the devices. According to the information from Magnus, it now seems to be a Homey SDK problem after all.
So what exactly is the problem now?
Thank you @robertklep for your feedback and for being so helpful.
I don’t know if it’s caused by Homey’s Insights data, but I guess not.
In my post #557 I mentioned some manufacturers and devices, but mainly Z-Wave devices, sorry.
The information I got from the manufacturer of the heatit device was: “it’s the specific version of the SDK for Z-wave that is the reason for the problems”
I don’t understand why we can’t select energy meters by our self, because I mis the water tab and a lot of energy meters for electricity. So there is a lot of work I would like to see that this will be in a short time.
@Kai_Engvik Have you been able to fix this? I’m using MQTT hub to import meter data from an “AMSleser”-device and have the exact same problem, the power is shown, but not energy use.
Regarding water: If you have a supported water meter and it does not show up in the Energy tab, then go to the water meter’s advanced settings (in the device tile) and check that the ‘this device measures the energy consumption of the house’ toggle is enabled.
I don’t have these option, but watermeter is a watermeter, why are there some that will not work with homey energy. The other electric meters are from Tuya some work and some don’t. I have the option on the electric meters but they don’t show up in energy tab.
I don’t know why your specific water meter data is not shown in the Energy tab. I do agree with you that, as a principle, it should not matter what water meter you use for it to show up in Energy.
I do know however, that some total energy/P1 meters, though compatible with Homey, did not provide data to the Energy tab either. The Homey app of those P1 meters needed to be updated in order to provide the data elements as expected by the Energy tab. This may also be the case for your water meter. You might want to reach out to the app developer.
For your Tuya devices, perhaps you could ask your question in the respective Tuya forum section.
FYI I think i got it working now, by setting “meter_power.imported” with “capability”: “meter_power.imported”, chosing “yes” for “cumulative energy measuring” and “include in total energy”, and adding “meter_power.imported” in the text box for “Meter capability for imported energy”. But I agree, the tab has limited usability…