Sensor for H1-3.0-E address 40010

[PaulRumsby]

Hi

Is it possible to create a sensor in Home Assistant that reads the value of the meter 1 code, which I believe is register 40010? I have searched through the forum and internet but cannot find anything on this so maybe its not possible. I want to write an automation that will trigger if the meter 1 code becomes disabled, as it did recently with a CT data logger firmware update, and reset it to 1=CT. Hope this makes sense...

I have a I have an H1-3.0-E inverter connected to Home Assistant via RS485 and the Fox ESS-Modbus integration by nathanmarlor.

Any help would be really appreciated.

Paul.

[calum]

If you're suggesting it be included in the foxess_modbus integration, best to raise it as a feature suggestion on Github.

EDIT: Modpoll can read it on my H1 here, so there's nothing in theory stopping it being added to an integration in HA.

Code: Select all

root@netscan:~/modpoll/x86_64-linux-gnu# ./modpoll -m tcp -p 502 -a 247 -t 3 -0 -1 -c 1 -r 40010 192.168.0.41
modpoll 3.10 - FieldTalk(tm) Modbus(R) Master Simulator
Copyright (c) 2002-2021 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.

Protocol configuration: MODBUS/TCP, FC4
Slave configuration...: address = 247, start reference = 40010 (PDU), count = 1
Communication.........: 192.168.0.41, port 502, t/o 1.00 s, poll rate 1000 ms
Data type.............: 16-bit register, input register table

-- Polling slave...
[40010]: 1

[PaulRumsby]

Hi Calum,

Thanks for the response and advice. I'll add it as a feature request but also try creating a sensor using the HA modbus integration. Since my original post I have been doing some more searching and seen similar sensors using modbus. Thanks again.

Paul

[calum]

Bear in mind that the foxess_modbus integration has its own modbus implementation. If you set up separate sensors that use the built in HA modbus library to talk to the same interface (ie the RS485 adapter connected to your inverter), there is the likelihood that the data requests that each one sends can collide with each other and you can end up in a mess.

[PaulRumsby]

Calum,

That's really good advice, thanks for saving me some pain. Feature request it is then.

Paul