Potential Scale Factor Error/Configuration Problem
I have being using IotaWatt since installing it in February and things have been going fine. Today I noticed a major scale factor problem Today, when using the dryer. I am seeing 9000 W from the dryer when there is only 5700 W total reported for the mains connections! Obviously something is wrong here. Also, I am almost 100% sure that the power numbers used to make sense so something has changed.
First my system:
Standard US split phase 220 Vac
ECS25200-C2 current transformers on mains
SCT013-000 current transformer on 220 Vac dryer outlet setup checked “Double”
Now some data. Using outputs assigned to current for these inputs I am seeing:
Main 1: 27 A
Main 2: 21 A
Dryer: 38 A
Given normal dryer currents and a 30 Amp 220 Vac breaker circuit I don’t think 38 A is correct for the dryer current. Also, current in a 220 Vac load can’t be higher than both mains current readings with only standard utility interface/no solar, etc. It is as if the IotaWatt is doubling the measured current figure.
Because the dryer is a 220 Vac load, the setup option “Double” is checked. If I set the channel to not double the current (uncheck the box) the historic data from before the setup change doubles to 76 A and the present current stays as 38. When I put it back to “Double” checked the old current goes back to 38 and the current from when “Double” was not checked goes to a believable 19 A.
I thought the “Double” check mark would only change the power calculation by a factor of 2. That is, power = 2voltagecurrent. I don’t see why it would change the measured current value at all. Whether the “Double” check box is checked or not checked and whether it should be or not I would assume that the Amps reading would always be the same. Am I missing something here or is there a bug in the FW?
I note in the log that 3 weeks ago IotaWatt FW on my device updated. Line in log says:
IoTaWatt 4.x, Firmware version 02_04_02 to FW
and the previous verions was 02_04_00. There are no error messages in the log.
Is it possible that FW 02_04_02 introduced an error in the current reading when the setup option “Double” is checked?? If not that, what could be going on here?