I’ll assume this was directed at me, but if not just ignore it lol
No real updates, It’s been working great for months so I haven’t touched it much lol.
I saw you mention you are now using a RS485 to TCP/IP modbus gateway?
Yes, I’m now using a USR-W610 bridge to take the RS485 signal to Modbus TCP/IP over wifi. The USR-W610 can do a lot actually, with RS232 or RS485, WiFi or ethernet, etc, but I’m keeping it simple in my setup.
an you comment on that part as my electrical panels are in a utility room that does have a ethernet switch; but not a physical host.
So I was hoping to daisy chain 6 of the PZEM-16 off the modbus to monitor […]
If you have wifi there, you could use the W610 to take in the serial signal and let HA consume it over the network. Daisy chaining modbus isnt a problem. The PZEM-16s all come from the factory with the same node address, so I would recommend using a USB<->serial adapter (RS485) to connect it to your laptop and change the node address on each one to be unique. It’s not too difficult and the PZEM manual actually does a decent job explaining the register map.
Ha, I’m not sure how much detail there is!
I have 2 PZEM-016s, which I configured separately to have unique node addresses. Each with a split core CT over one of the incoming phases. The modbus connection of one is daisy chained to the second, which is chained to the USR-W610’s RS485 port. The W610 is connected to my WiFi network. Home Assistant is configured to read the W610’s IP address as a modbus TCP/IP node. This is the configuration inside HA for the modbus network:
# USR-W610 WIFI BRIDGE
host: !secret modbus_tcpip_bridge_ip
I can’t remember why the port isn’t the standard modbus TCP/IP port (502), maybe I changed it in the W610 configuration. I’m not home now to check.
And this is the configuration for the sensors (to long to post in the comment).