Aeon Smartswitch Reporting Wrong Watts

Have several of these running and they all seem to report correctly. This one in particular runs continuously and now shows 11820 watts even though the device plugged into it is only pulling like 50 watts or so. I have tried unplugging it and turning it on and off, but it still shows the incorrect wattage. I haven’t tried removing and adding it again, maybe that would fix it.

Anyone else have this issue?

Try a “configure node now” from the settings tab of the module as it might correct it!

Thanks, but didn’t change anything. I will try to remove and add it again when I get a chance and see if that fixes it.

It’s probably not an issue with the Smartswitch.

The Smartswitches report every second, if you have several of them that’s alot of Z-Wave traffic and from what MCV has determined the Z-Wave packets are colliding, getting corrupt and providing inaccurate information when delivered.
Some of the side effects are:
Battery devices reporting wattage.
Powerline devices reporting a battery.
Some devices reporting watts even when off.
Watt values not changing.

MCV has stated ths is out of their control and waiting on a Sigma fix…
Out of curiosity, are you using the Enegy Profiling plugin or one of the later FW’s that removed it on install?

JOD.

I had these bugs with wattage appearing and batteries appearing long before I had any form power monitoring solution.

I just received my FREE aeon smartswitch. Amazon has a special this month which includes the smartswitch for free when you buy a Vera2. I filled out the form, and I got the smartswitch about a week later…Super quick!!!

Well, I hooked it up to my vera2 running 1.1.1183 and it paired perfectly.

But, the usage is only displaying 0W with lights plugged in and turned on.

I can’t seem to find anything to help in the forums.

Any advice?

Thanks!

If I remember it took a couple hours for it to start reporting when I first set them up.

Regarding the OP, that particular switch just out of the blue started reporting correctly the other day. I think the difference was that the device that is attached to it went from running 24 hours a day to only about 16. I guess the break time it gets is allowing it to work correctly.

Mine took a few days before it started reporting.
Check the settings tab after clicking the wrench. Does It say the manufacturer is Mios or Aeon? :wink:

JOD.

It says MIOS for the manufacture. DOH!

Not Aeon, MIOS! Sorry about that!

Amen. This is still UI2+Vera1, but over the last month, I have one outdoor relay switch and one Leviton on/off switch both sprout batteries–which look like they could stand to be replaced some day soon…

–Richard

i have the same smartswitch and i’m having problems too

in one moment the smartswitch is measuring ok, but in other it is measuring a wrong wattage
i attached two pics showing this

I have Vera 2, FW 1.1.1245

Amen. This is still UI2+Vera1, but over the last month, I have one outdoor relay switch and one Leviton on/off switch both sprout batteries–which look like they could stand to be replaced some day soon…

–Richard[/quote]
Since I got my smartswitch, I have had a GE dimmer and GE outlet start to show watts on the dashboard. Sounds like the collisions/data corruption might have something to do with it.

You didn’t put manual power consumption numbers in, by any chance?

(You can clear the energy stuff in the Advanced tab and the wattage will disappear from the dashboard.)

I do not have manual power consumption entered for either device. The watts on the dashboard started appearing for the outlet first and just started appearing for the dimmer within the last couple days. Nothing has been changed in the configuration over the last couple days.

It is also interesting to note that in the Advanced tab of the power outlet, there is a variable for KWH with a value in it. The value is less than the current reading on the smartswitch, which could be the value for the KWH usage of the smartswitch when the wattage first started appearing on the power outlet. There is no KWH field on the dimmer at this time.

I imagine that excluding and re-including the devices would fix the issue, but it is not a big issue at this time.