💬 Power Meter Pulse Sensor

[rejoe2]

@gohan How about

#define MY_TRANSPORT_WAIT_READY_MS 2000

This will start up your code so you won't miss any pulses until controller is ready.
You may ask for the last known Value in presentation(), then it will be fetched as soon as the controller is really there after startup. This could/should be combined with a bool pcReceived, so you may decide to either add the value received from controller to the counts the node meassured in between or just use the received value (starting from second time value is received from controller).

[gohan]

That actually is not that critical, as I am going to move to MQTT and that should be working anyway. Right now it is working on a UNO with NRF24, but my biggest issue is the WATT reading that it is missing

[gohan]

Any more suggestions on the Watt issue?

[hek]

Did you by any chance change SLEEP_MODE to true?

[gohan]

No, I get every pulse reported as soon as it is detected.

[gohan]

I think I found a problem: the WATT calculation is returning values over 172000 watts and since I put 10000 as the max value, it was not sending anything. I double checked my energy meter and indeed it is 1000 pulses per KWH and this is what I set in sketch

[gohan]

@hek I said I found the problem, I didn't say I know how to solve it 😅

[gohan]

Here is the log I get from node

7230 TSF:MSG:READ,0-0-250,s=1,c=2,t=24,pt=0,l=7,sg=0:1682675
rece

Received last pulse count from gw:1682675

11817 TSF:MSG:SEND,250-250-0-0,s=1,c=1,t=17,pt=5,l=4,sg=0,ft=0,st=OK:528
Watt:528

Watt:197065

21820 TSF:MSG:SEND,250-250-0-0,s=1,c=1,t=24,pt=5,l=4,sg=0,ft=0,st=OK:1682677
21913 TSF:MSG:SEND,250-250-0-0,s=1,c=1,t=18,pt=7,l=5,sg=0,ft=0,st=OK:1682.6770
Watt:196807

36824 TSF:MSG:SEND,250-250-0-0,s=1,c=1,t=24,pt=5,l=4,sg=0,ft=0,st=OK:1682679
36917 TSF:MSG:SEND,250-250-0-0,s=1,c=1,t=18,pt=7,l=5,sg=0,ft=0,st=OK:1682.6790
Watt:197368

51827 TSF:MSG:SEND,250-250-0-0,s=1,c=1,t=24,pt=5,l=4,sg=0,ft=0,st=OK:1682681
51920 TSF:MSG:SEND,250-250-0-0,s=1,c=1,t=18,pt=7,l=5,sg=0,ft=0,st=OK:1682.6810
Watt:196850

Am I the only one using this sketch?

[mickecarlsson]

Please post you sketch.

[gohan]

it is the one in https://www.mysensors.org/build/pulse_power

[mickecarlsson]

How is the pulse counter set up? Is it connected to the S0 port?
Edit:
If you are using S0 it is vital that you use a pull down resistor, if you dont’t have that you get false pulses.

[gohan]

I'm using the lm393 light detector. Domoticz is able to do a calculation from the pulses to give a Watt value and it is correct but it does it every 5 minutes and it is too slow for me

[sundberg84]

@gohan - is Domoticz updating anything (except switches) faster than 5 min? I dont think so...

[gohan]

If you send the watt reading faster it updates like the switch, anyway I need the watt values for node-red also

[gohan]

Could it be the Light sensor is triggering more interrupts from each pulse?

[henninne]

@niklaso

Hi Niklas,

I know this is a very old post, but its worth a try. How did you get out the daily Kwh usage? As default my sensor only gives Watts and Kwh (accumulated from start), I have tried to run a Scene in Vera UI7 where there are a function in the sensor called resetKWh(), but it looks like it doesn't do anything. Any tips would be great, thanks.

Henning

[smilvert]

@gohan I think it is a little tricky to update domoticz every minute but try update the sql-file, see the domoticz forum
https://www.domoticz.com/forum/viewtopic.php?t=10183

[gohan]

The main issue is the fact that the sensor is not calculating the instant power correctly

[DaTim69]

I created this kWh sensor with the TCRT5000 IR Barrier Line Track Sensor.
My powermeter is a ferarrismeter with 375 rotations per kWh.
I also had the problem with spikes in the power usage. But after long...too long investigation I solved the problem.
At my config it was a double issue.

Issue 1.
The problem is the pulse width of the rotation.
The pulse are at night ( low power) much wider that during the day when more power is consumed. At night the spikes in power usage where huge.

Issue 2.
Switching on/off the halogen light causes spikes and related to also strange power measurement.

Solution:
I added a second arduino mini pro as a pulse regulator between the TCRT5000 and the power meter arduino.
this arduino triggers on Rising and will always give a 100ms puls. Als debounce is handled (spikes).
I don't upload the sketch here, I'm a beginning programmer on arduino. It's made on " trail and error" but it functions as it supposed to do.
If someone wants a copy feel free to contact mee

[xydix]

@gohan Did you solve this?
I get very high watt usage as well. Sometimes like 40 000 - 130 000 watt if I check the serial monitor.
Of course, those values will never be sent to the controler.