Do as you think. I just suggested how it works on my D1mini without a problem for more than a year.
OK, I hooked up everything and Iām still getting "Entity is Non-numeric ", and I even tried a different uart, but that gave more problems.
Maybe itās my sensor setup. Did you configure anything differently??
You tried to switch Tx, Rx. Just do it in the configuration
I have it this way
uart:
tx_pin: D1
rx_pin: D2
baud_rate: 9600
stop_bits: 2
I tried connecting to a different set of pins designed for uart. The esp32 supposedly has 3 sets. The tx pin on pin 9 made the WiFi stop working when installed in the software, but pin10 which is rx was fine, but I switched it to both the tx and rx pins of the ttl to uart adapter. Everything resulted in the entity is non-numeric error. I even tried the resistor trick, still nothing.
I ordered some esp8266ās and a nodemcu esp32 to see if I can make anything different happen with everyone elseās known configurations.
I still would like to know if the code you used was dissimilar to the example for the pzem-017 example on the earphone website, or if you configured the sensor in a special way. Thanks!
I used an example from the ESPhome documentation
Connect pins IO22 and IO21 (D1, D2) as Tx pin D1 to TTL converter to Tx and Rx pin D2 to TTL to Rx. The TTL board is probably incorrectly marked
Found the solution! Turns out the pinout I had was not complete, and on the ESP32 there is a 3rd UART pair: Pins 16 (RX) and 17 (TX). Through a level shifter, I connected the ESP TX and RX to the TTL to UART adapterās TX and RX (respectively)ā¦yes, TX to TX, and RX to RX. A to A and B to B from the TTL to UART adapter and the PZEM-017. No resistor needed, so far 
According to the ESPHome debugger, the UART1 pair (pin 9 and 10) is used for the programmer and wifi, so that pair is a non-option, and it was causing the ESP32 to go into a bootloop and then safemodeā¦so thatās why I tried the UART2 option, and Iām super glad it worked!
This the fully correct Mini ESP32 pinout:
Hereās the final wiring schematic:
Code was almost exactly what ESPHome recommends, except the pin difference. I hope this helps someone in the future. Take care!
2 Likes
Hello,
I have a similar setup (ESP32 DEVKIT1). I have connected all the boards the same way as described, but I am receiving errors regarding CRC checks:
[17:51:08][W][modbus:121]: Modbus CRC Check failed! 9FBD!=9F32
[17:52:08][W][modbus:121]: Modbus CRC Check failed! 3745!=F610
I have connected the board on the UART2 (GPIO17 for TX and GPIO16 for RX). I have bought another pair of UART adapter and logic sifter, but the same issueā¦ Does anyone know, what could be the issue?
Many thanks.
Hi, Iām in the same situation. Setup with ESP-wroom-32, worked for about half a year and after updating Esphome sometime in December 2022, CRC errors started to increase. A correct value appears here and there, but only exceptionally. I havenāt found a solution yet 
I just setup a pair of these and seeing the same CRC errors
Any update on this?