@NeverDie Simple said: Buffer messages at nodes until they receive an acknowledge that the message was delivered succesfully. Retry sending the message after some time if the acknowledge does not arrive.
The principle is simple, but the devil is in the details

@NeverDie said in Why I quit using MySensors for actuators:

Now, suppose you include a byte in the payload as a counter.

Let's go all the way then and implement 'guaranteed delivery', not a diagnostic counter that only tells you your connection sucks...

@NeverDie said in Why I quit using MySensors for actuators:

we're more likely to notice an actuator fault than a sensor fault?

Judging from recent measurements I'm quite sure this is the cause. Especially a wireless actuator switched by a wireless sensor requires 2 succesful message transmissions. If one of them fails you will notice immediately.

To make things worse, sensors often only transmit a new value if it changed w.r.t. the previous one. If an isochronal sensor skips a sensor value at the gateway, we'll never know if it just didn't send the value because it was identical to the previous one, or if a new value wasn't received.

@Sushukka said in ACS712 strange values when measuring 3D printer power consumption:

                /|
               / |
              |   \
      /------/    |
----/             \----

Cool ASCII-art Next time you could just attach a screenshot

I had a quick look at emonlib and it appears to measure the true RMS value; it takes a number of samples and sums the squared values: https://github.com/openenergymonitor/EmonLib/blob/master/EmonLib.cpp#L187
It is designed for specific hardware and applies some correction that might not match your sensor.
On the other hand, if your other (resistive) loads match the reference power meter the algorithm seems to work

Did you consider that your power meter could be off for reactive loads?

@Sushukka The getVPP function samples for 1 second and returns the maximum peak-peak voltage of these samples.
For purely resistive loads it is correct to multiply this peak-peak voltage by 0.707 to get the RMS value.

If your load looks like the blue graph (reactive load, taken from the link in my previous post) you have to integrate the surface area to get the true RMS value (that's why true RMS multimeters are in general more expensive and are advertised as such). I think the emon lib does exactly that, but I would have to check.

As a test you could run a sketch which samples the voltage from the ACS712 as fast as possible and outputs these values to the serial port. Recent Arduino versions contain a 'serial plotter' which then graphically show the power usage.
A test sketch could be as simple as:

void setup() { 
 Serial.begin(115200);
}

void loop() {
 Serial.println( analogRead(A0) );
}

Flash it, select serial plotter in the tools menu and watch the output.

@pihome Make sure all nodes and gateway use the same version; 2.x is not compatible with 1.x !

@pihome did you update all nodes and gateway to 2.1.1, or only the gateway ?

@gohan said in MyWindSensor:

since it isn't a pulse counter sensor but it gives a voltage to read it is probably why it isn't cheap

A simple pro-mini can do the same; only costs a few €...
Looks like it's full metal, so probably a lot more durable than the plastic ones that tend to agree rapidly in the sun...

@gohan @Bert-Ramselaar sorry, I'd better not browse the forum on my phone anymore

@Bert-Ramselaar HI and welcome to the forum!
I modified your post slightly to include code tags, which improves readability.
Could you give some more info on your project (which sensor did you use? And did I mention that we simply looooove pictures )?