VZM30-SN failing with erroneous overcurrent condition and active/periodic power/current monitoring is failing

Product Support
, , ,
1

Hey everyone, I’ve got a bunch of blue dimmers installed, first time installing an on/off. Turned it on and it seemed to work great! Then I came back upstairs later and it’s flashing red every few seconds. The switch is wired to a 70CFM ceiling fan with a 1.2A rating. Not sure on the motor HP, but it’s a Nutone 695-R03 if that helps.

I checked Home Assistant and for some reason when I turn the switch on, the current and power reported don’t update. Then a minute later when they do the switch reports exactly 21.81A and goes into this loop of flashing red, back to normal, flashing red.

To be clear, I don’t think this is actually a real ~22A load, because I’m on a 15A circuit and haven’t tripped it yet with this fan on a dumb switch.

Anyone seen this before?

2

What firmware are you on? There were reports last year of issues with bathroom fans, unresponsiveness and inaccurate energy reporting.

The current production fw is 1.03.

3

Supposedly 1.03 I think. It’s a hex string but it ends with a 3. If I can flash over it I’ll try that to see if there’s maybe just a bad FW flash

Edit: current fw is 0x01100103

4

Digging thru Zigbee clusters, it seems the switch was manufactured on Dec 24, 2025 and FW is 1.03

5

Is there a way to reflash the latest OTA on my switch? The switch turns on, runs for a bit and then shuts down blinking red (or LED off entirely). Until this point, active and periodic power reporting do not happen, but at the time of failure I get a bunch of (mostly bogus) info.

At failure time I get 600-ish% RH, -30°F, and 21.81A (always that number). The power number looks accurate at about ~120W (the fan is rated for 1.2A).

Reconfiguring, factory reset and attempting to manually change the divisor of the metering cluster (which reads 15880) all fail to resolve the issue

6

Swapped out the switch for another VZM30-SN and power reporting works perfectly. Switch isn’t crashing out either.

Not sure what’s up with the original, but unless I can reflash it I think I need to warranty it. Will test on another load later

7

Hmmm, I just posted a very similar issue with a Matter/Thread VTM30-SN.

8

Just replied to you over there :slight_smile:

I think there’s either a component that’s marginal on the switch or FW is really freaking out over these bogus readings but I would reach out to support and get a replacement. Wish I had a better solution that didn’t involve waiting a few weeks but at least they seem to want to make it right!

9

I’m running into the exact same thing.

I’ve talked to support a lot of this and done so much troubleshooting on them and once they start throwing this error there just doesn’t seem to be a way around it. Support has replaced my switch multiple times now. I’m on switch number 3, and every single one of them has started doing this eventually.

At this point, I honestly feel like the model either has serious firmware bugs that need worked out, or they’ve just got defective hardware. I’ve never had issues like this with any of the other inovelli switches or dimmers.

10

It may well be. I don’t have their firmware or internal specs but my outside opinion is that there’s a current divisor that is wrong somewhere given power looks good but current is off by a factor of 22