Only EMMA-A02 is detected over Modbus TCP; inverter/battery/optimizer devices are missing #1204
Unanswered
mulle78de
asked this question in
Setting up the integration
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have integrated my EMMA into Home Assistant using the huawei_solar integration.
The integration works and I can see about 70 sensors plus the EMMA device itself.
However, I do not see any sub-devices that belong to the EMMA’s Modbus slave chain.
My system topology looks like this:
Plant
├─ EMMA-A02 (Master, WLAN Modbus TCP)
│ ├─ SUN2000-10K-MAP0 (slave)
│ │ ├─ LUNA2000-10KW-C1 + LUNA2000-7-E1 (battery stack)
│ │ └─ 21 x Optimizers
│ └─ SmartGuard-63A-T0
I would like to access the inverter, the battery and the optimizers as individual devices in HA — not only the EMMA-level sensors.
Question:
Do I need to install a Huawei Smart Dongle WLAN-FE A-05 on my SUN2000-10K-MAP0 inverter (which is currently a Modbus slave behind the EMMA) in order to expose the inverter over Modbus-TCP and make it available to Home Assistant?
Right now, the inverter does not show any Modbus-TCP or dongle configuration options in FusionSolar. I can only change the RS485 bus baud rate, which suggests that EMMA is the only active Modbus master.
I would like to confirm whether the integration can access slave devices behind EMMA at all, or whether a Smart Dongle on the inverter is required for full access to inverter/battery/optimizer registers.
I've seen issues/943, that in general it should be possible to have all devices over EMMA Modbus TCP connection.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions