Meter is not being discovered on MODBUS TCP #536
mayberryjp
started this conversation in
Connecting to the inverter
Replies: 1 comment 3 replies
-
@mayberryjp SmartLogger is NOT a supported configuration. If you want to get this integration working, you must rewire the meter to the primary inverter, plug the sDongle into the primary inverter and connect using Modbus TCP to the IP of the sDongle (that you've also enabled modbus tcp access upon). PS. Said as a person with 2 x SmartLogger 3000A's..... ended up having to remove the SmartLoggers and rewire my setup to use this intergration. Personal call on what you want/need more the data and ability to automate in Home Assistant or local SmartLogger vs FusionSolar in the cloud. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I have a smart meter it's connected and I can't see data on COM1. I can also see smart meter stats like grid power and return on the smartloggers local website. The meter is registered in the smart logger and everything looks normal. The battery and inverter are discovered fine by home assistant and the entities have data and work 100% as expected.
The problem is - Home Assistant can't discover the smart meter and I can't get any meter entities in home assistant.
Does anyone have any ideas? I've tried everything - removing and re-adding the meter, power cycling the smart logger, etc. Nothing is working. It seems to be a MODBUS TCP issue but i can't figure it out.
I am connecting via MODBUS TCP directly to the smart loggers management IP. There are all kinds of settings around logical address and communication address and slave IDs. it's not obvious to me how to figure out the meters slave ID. To discover the battery and inverter it is on slave ID 2.
thanks
Beta Was this translation helpful? Give feedback.
All reactions