Absurdly high reported power spikes from multiple Aeon Labs smart switches

(Posting in hardware since I don’t yet know if it’s a HASS z-wave issue or a device issue.)

I have several Aeon Labs (Aeotec) Gen 6 smart switches. Occasionally, any one of them can report an insane power draw, as shown below. The spikes can be reported whether or not the attached equipment is actually drawing any power. I know because I made some automations that check for power consumption changes, and I had to set a time threshold to prevent the spikes from triggering them.

Does anyone happen to know if this is a known issue with this hardware, or perhaps it’s an issue with openzwave?

Example attached image

I also have very unreliable power figures from my Nano dimmers and switches. I haven’t figured out why.

I have 3 of them and I’ve seen one reporting very small power draw (0.05A) but nothing like you and not from the other 2. It might be a bug somewhere in the firmware but it’s related to the unit you have.

Do you have persistence enabled for them?

I’ve noticed this too with mine, both the smart switches and the nano switches. They all report ridiculously high power usage numbers about once a day which is excruciatingly annoying. I don’t use home assistant either, so it’s not my HA set up. Did you ever figure out a solution?

I get the same with my Home Energy Meter Gen5 (https://aeotec.com/z-wave-home-energy-measure/) unfortunately.

The only solution that I came up with is the filter-component (https://www.home-assistant.io/components/filter/).

I haven’t played around with it though, but I guess the Range-filter and setting an upper_bound limit and replacing every “spike” with just some normal value should work.

1 Like

I’m observing the same with some of my aeotec nano switches. Most work fine, but there are 2 which randomly have high power figures once a day.

I’ve tried reseting the switches and re-adding to HA, but still experience the same issue. Have also installed the latest firmware.

Did anyone solve this, or is this something migrating to openZwave beta might fix?