Home power monitoring with PZEM-004 & home assistant for under 30$! Part 1

AS THIS IS THE MOST IN DEMAND ENTRY. I’M CONSTANTLY UPDATING IT.
IF YOU HAVE ANY QUESTIONS PLEASE ASK. 

UPDATES

  • 2019.07.14: hmm must have missed Dr ZZz talking about the PZEM ealier this year https://youtu.be/_djX-7c2kg4?t=3995
  • 2019.06.03: This setup has been rock solid for over a year without any changes. 👌
  • 2019.04.26:  from Sendorm is a cleaner way to power the system without a separate usb power adapter
  • 2019.04.16:To simplify the process of the code below I have put it online at https://github.com/halfforked/PowerMeter/tree/master
  • 2018.09.09 – Post split in multiple pieces see part 2 as well

ALTERNATIVES* (added 2019.03.02) 

 

The standard disclaimer: Please do not attempt anything seen here if you’re not comfortable with breakers and mains power.

Home assistant home power monitoring
The unboxing 📦.

At this point I had BRUH room sensors in every room (except bathroom) and outside.

The next step was to have whole house monitoring. Which was finally done this morning.

A couple weeks back I received my PZEM-004. Without a clue on how to hook it up to hassio. I figured there had to be a way.

I was ready to reflash a nodemcu with original programming if I had to. I wanted house wide power monitoring but couldn’t get many ready made products in Japan nor wanted to pay 200-500USD for them. For example this awesome looking SENSE unit reviewed a while back by BRUH.

Sure I won’t have the detection software that will figure out the various appliances for me, which would be very nice, but realistically at sub 30$ I’m quite happy.

The PZEM-004 with display, split coil current transformer (CT) with a usb wire for power set me back a tiny 2116JPY (20USD) [nodemcu was 3USD]

PZEM004 home power monitoring
[a SPLIT COIL IS IMPORTANT, as it will be much easier to open the coil around the wire than to remove the wire to put it through the coil]
This unit has a limit of 100Amps, but as this leaning house has a average-small 30Amp breaker box, this would be ample.

This is what I bought. PZEM-004 link here. I commented that it does make a buzzing noise when powered, if it’s an issue in tiny-house-Japan. Of course if you want an even cheaper one, get it without the display. (Although I don’t recommend it as with display it’s easier to test)

TESTING:

  • Using a cable with a plug on one end and bare cable on the other (i.e. like a cut extension cord).  I used a cable bare on both ends and temporarily attached a plug to one end.
  • Connect the bare cable ends into the PZEM-004 as per the instructions on the unit
  • Connect the coil (if not already attached) and put ONE of the two wires in the extension cable through it again as per the instructions on the unit.  (not both wires as the currents will cancel each other out)
  • Power the PZEM004 via the included USB cable. I opted to use a double USB charger with one side powering the NodeMCU and the other powering the PZEM004 plugged into a power strip with a switch. (I’m guessing you could *maybe* power the PZEM004 from the VIN pin of the NodeMCU as this is the same as connecting to the USB plug directly)

UPDATE 2019.04.26 from Sendorm

One thing to add, I am powering the pzem-004t TTL from the nodemcu VU pin and it is working perfectly. It seems a separate usb power adapter is not necessary after all.

https://community.home-assistant.io/t/whole-house-power-monitoring-single-phase-for-under-30/68793/9

  • USING a power strip with a switch at OFF, plug in the “plug” end of the cut extension cable.
  • Clearing away any other debris, things around, turn on the power strip.
  • You should be getting a reading on the PZEM004 (if you have a screen)
Hassio home power monitoring
VDD to 5v USB or maybe the VIN NodeMCU Picture from https://mysku.ru/blog/china-stores/38717.html

Providing power to the PZEM004 to TEST it worked without a hitch with a cable to the mains. I used a cable with a plug on the end and bare wires on the other. The bare wires powered the PZEM004 and splitting cable into the two wires carefully preserving the rubber the coil was attached to ONE of the wires. After the setup I plugged the cable into the wall and power readouts appeared on screen. TEST successful.

Whole house power monitoring

How to get it to play nicely with TASMOTA? (then Home Assistant)

  • [update 2019.09.11] I use the nodeflasher, it’s old but just works well for me, and flash TASMOTA v6.6.0 onto a nodeMCU. There is no fussing around with Arduino or anything anymore
    NodeFlasher
    TASMOTA v6.6.0 this sonoff.bin (standard)

    [original] Flash tasmota on the NodeMCU or Wemos. The Sonoff basic doesn’t have the pins necessary to connect with. (I flashed with the ARUDINO IDE as I wanted to select the WIFI AP mode and Enter a name for this NodeMCU as “powermeter“)
    **If using the Arduino IDE be sure not to use ESP8266 version 2.4.X I would downgrade to 2.3.0 for now (2018.09.09) link

  • Make sure the PZEM-004 is disconnected or the switch is off. Using the picture on the back of the unit connect the PZEM RX -> NODEMCU TX and the PZEM TX-> NODEMCU RX pins.

That pretty much takes care of the physical connection.

  • Connect to the tasmota firmware at the IP address on your network
  • Set to generic
  • Set the pins you chose (in my case see below)
  • Enter the MQTT server info
PZEM004 tasmota home assistant
Node TX -> PZEM RX // Node  RX-> PZEM TX  and as for D7 the DHT-22 also known as the SI7021

And that should be it for Tasmota-NodeMCU (Wemos).

When switching on the power again, the PZEM and the USB powered NodeMCU should be working together and logging into the NodeMCU you should see the following. (WITHOUT THE TEMPERATURE INFO)

Home assistant power monitoring diy
The temperature info is not there without installing a DHT22

Next, how to extract the Tasmota’s PZEM004T information. Without any more steps the MQTT is receiving the following data.

How to check house power consumption

To find this out I got lucky as this NodeMCU was a former BRUH Multisensor. Checking the logs and was able to find the JSON code to extract this information. I tested many ways to get the information from the PZEM MQTT messages. In the end after I got my results I stumbled on this page. https://github.com/arendst/Sonoff-Tasmota/issues/1595

UPDATE 2019.04.16: To simplify the process of the code below I have put it online at https://github.com/halfforked/PowerMeter/tree/master

Screenshot of my configuration.yaml file about the powermeter settings. See above for link to github

By entering the above as MQTT entities the data will be properly extracted to Home Assistant.

Real time power usage hassio
After setting up a card this is what my setup looks like.

One problem I encountered was the slow update time of the information. The humidity and temperatures were updating by the second whereas the power updates were every 300 seconds.

[UPDATE 2019.09.11]

  • OPTION 1 – On TASMOTA firmware v6.6.0 go to MENU – CONFIGURATION – CONFIGURE LOGGING – Telemetry Period and change the value to 10
  • OPTION 2 – Changing the following TELEPERIOD setting is the original way. See below
img_7197
“Teleperiod 10” for 10 second interval updates

Changing that to 10 seconds made everything so much better and usable. By entering “Teleperiod 10” to update every 10 seconds.

UPDATE 2019.05.05: If “Teleperiod 10” for 10 second interval updates is still too slow for your liking there is the possibility to update the Tasmota code as commenter SeByDocKy

Finally, I recompiled the last tasmota firmware and made the two following changes in the sonoff.ino (around line 1204)
if ((payload >= 0) && (payload 0) && (Settings.tele_period < 10)) Settings.tele_period = 10; // Do not allow periods < 10 seconds
Works fine for Teleperiod 1

SeByDocKy‘s link: see the comments (I didn’t have time to test it myself, see comments for any issues that may arise)

This is an interesting workaround. However having said that I will be leaving the tasmota code untouched for the time being as 10 seconds doesn’t bother me so much. Plus I’m curious as to why there would be a 10 second minimum in tasmota in the first place. Long term usage to be the final test perhaps.

Congrats the safe part is done.

Just FYI this seems to be a good link to check for bugs with the PZEM.  https://github.com/olehs/PZEM004T/issues

Part 2

42 thoughts on “Home power monitoring with PZEM-004 & home assistant for under 30$! Part 1

    1. @zacaruca the kWh and power factor (etc) were all part of the tasmota firmware presets.
      I’ve edited the post to reflect that.
      Thanks for the question.

      Like

    1. Thanks for you request.
      I’ve uploaded a screenshot of my settings in my configuration.yaml file for the power meter.
      Please note I named it “powermeter” also the temperature and humidity are not needed unless you have that sensor.

      Like

    1. From what I’m told
      Update 2019.04.26 from Sendorm
      One thing to add, I am powering the pzem-004t TTL from the nodemcu VU pin and it is working perfectly. It seems a separate usb power adapter is not necessary after all.

      I think this is what you’re asking

      Like

    1. Hi.
      You could get the pzem-004 w/o display. I do mention that but personally I wanted to be able to test it before integrating it into hassio.
      As for powering the unit.
      I personally use a dual 100->5v USB adapter. Some people have reported success with powering the pzem via the 5v pin on the nodemcu/wemos d1mini

      Like

      1. Thanks a lot … I will reproduce your project for my main electricy input but also for my electric water tank and my futur solar panel energy optimizer :). If you can extend a bit the grafana integration, can be great 🙂

        Liked by 1 person

      2. Hi I received my PZEM-004T and I can confirm it can be directly powered via the “Vin” of a nodeMCU. Thanks to your blog, it took me 2min to have information in Home Assistant. Anyway, I am a bit frustrated by the 10s limitation of Telemetry information sent by Tasmota…. I would like to have about 1s…. Thinking to flash with ESPurna firmware instead which offer 1s and 6s options…

        Liked by 1 person

      3. Finally, I recompiled the last tasmota firmware and made the two following changes in the sonoff.ino (around line 1204)

        if ((payload >= 0) && (payload 0) && (Settings.tele_period < 10)) Settings.tele_period = 10; // Do not allow periods < 10 seconds

        Works fine for Teleperiod 1

        🙂

        Liked by 1 person

    1. Updated! Thanks for the feedback and mods. As I mention in the post, I will not be attempting this as 10 seconds is tolerable for me, but it might be useful for others~!

      Like

      1. I understand…. Personally, since I will install soon some solar panels, I will have three PZEM-004T+D1mini combo: one for the main electricity input, the second for my main electrical water tank and the third from the solar panel DC/AC converter. The Electrical water will be controled via a 4000W SCR. The idea is to send the maximum power to the water tank when the solar panel are producing. It’s cheaper to stock power in hot water rather than into battery. If course when the water tank will be hot enough, then power will be send to battery. So I need fast updated from these three devices to run the power distributor optimizer algorithm ran in home assistant

        Liked by 1 person

      2. Hi,

        I noticed something strange … with my system…. Now after 24h/30h of usage, my system “freezes” whatever the teleperiod value 😦 ….I have to reboot via the associated panel switch…
        I don’t know if it’s from the PZEM-004T or my NodeMCU… Maybe linked with the fact that the PZEM-004T is directly powered via the NodeMCU….. I am investigating :(…

        Like

      3. Ok it comes from my NodeMCU ….. It freezes after a couple of minute right now. Maybe when powering the PZEM-004T, he draws too much for NodeMCU circuit… then “freeze”….. Or maybe sensitive to the EMI around…. (My system is directly into my main electrical panel with a lot of AC wires around)

        Like

      4. I had the same issue with 2.4.x
        It was the first thought to my mind.
        Can you give more details about the file?
        Which tasmota version also which package?

        Like

      5. It’s last tasmota version modified for Timeperiod >=1 s and linked with Core lib V2.3.0….. Unfortunatly it’s still freezing time to time 😦 …
        I tried to play with the Dynamic Sleep option…. Still not perfect… 😦
        If it’s not perfect…. I will go for espurna firmware instead

        Like

  1. HI,

    VERY IMPORTANT MSG….. I KILLED TWO PZEM-004T V2.0 (TTL) TRYING TO ADD A DHT22 SENSOR ON THE 3.3V, GND & D5 OF THE NODEMCU !!!!!!! SEEMS AS SOON THE DHT22 IS ALSO POWERED BY THE NODEMCU, IT KILLS THE CURRENT SENSOR OF THE PZEM-004T…. ONLY VOLTAGE WORKS AFTER…….. SO DON’T TRY TO ADD A DHT22 ON THE SAME NODEMCU OR USE ANOTHER POWER SOURCE!!!!! THE PROBLEM NOW ONLY PZEM-004T V3.0 ARE SOLD AND IT’S NO MORE TTL BUT MODBUS SO NOT YET TASMOTA COMPATIBLE

    Liked by 1 person

      1. YEs 😦 …. I have no more sensor now 😦 ….
        How you connected your DHT11 on the NodeMCU ? The DHT11 is working in 3.3V or 5V ? for you

        Like

      1. I use a double USB adapter. One USB port powers the PZEM-004T with provided cable. The other port provides power to the nodemcu via microUSB.

        My DHT22 temp/hum sensor is powered from the nodemcu 3v3 pin.

        Like

  2. So only the double USB powering….. is different from my setup…
    Really I don’t understand what’s happened for my case… 😦

    Like

    1. Ok I think I have the answer for my problem… In fact, PZEM-004T are not killed but my Wemos D1 mini instead.

      Why ? Because, every pin of the 8266 should run @3.3V… and basically with the PZEM and the DHT2, the RX & TX pins received some fatal 5V.
      So definitively, it’s strongly advise to modify the PZEM by adding a 1Kohms in order to transform the +5V TTL of the PZEM into a 3.3V. Then… use the 3V3 pin of the D1 mini to power the PZEM. In this situation, the DHT2 should run perfectly as well.

      Like

      1. Previously in the comments there was a question about having to modify the pzem.

        I did not modify and followed this.

        “ALTERNATIVE: No modification required on the PZEM-004T. Rather than using the 3.3V output from the Wemos D1 Mini to power the PZEM-004T serial interface, use the same 5V buck converter output (also used to supply power to the display and the Wemos D1 Mini) as VDD on the PZEM-004T serial interface. This eliminates the need for the resistor and the need to modify the PZEM-004T in any way at all.”

        Like

      2. Some updates… few days later…
        got some good news and some bad one…
        Good news: the system is reworking… with a new nodeMCU….
        Bad news: the system freezes when the teleperiod is too low…
        With 10s, it’s ok ….. for 5s it’s freezing….. Now testing 9s…. if ok for at least 24h, I will test 8s….

        Liked by 1 person

      3. Good to know it’s up and running.
        New nodemcu, did you modify the pzem or leave it untouched.
        About your system freezing I’m not sure if the risk/benefit from going down from 10s to 9s or 8s is worth it.

        Like

      4. Yes I modified the PZEM-004T with a 1Kohms resistant. Both the PZEM-004T & the DHT22 are powered via the two 3V3 pins of the nodeMCU.
        Testing 9s… seems ok, at least no freeze after 12h… Will see tmr if the 24g test will be successful. If yes going down to 8s… and so on 🙂

        Liked by 1 person

      5. 8s worked for the 24h test … so now testing 7s 🙂

        By the way, I think the future will be zap Tasmota for ESPhome….
        It will be direct for Home assistant.

        Liked by 1 person

  3. Great read thanks
    Where you get the case.
    was it supplied or 3d printed
    cheers just ordered the parts

    Like

    1. Hi Marty,
      Thanks for the comment.
      I assume you’re talking about the PZEM-004t case. I ordered the one with case, USB cable and, split coil. (The complete package)

      Like

Leave a Reply to SeByDocKy Cancel reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s