I’ve extended the timeout settings - please try again (with new version)
Version 1.0.8 released: Huawei FusionSolar Manager | Homey
If it fails again → please post a screenshot of the error
Same issue.. what happens is when i set local control it goes back after timeout to what it was before in my case max self….
Did some testing… regardless what i try to set in the list gives same problem.
I also experienced timeout errors earlier today when trying to activate charging the battery from the grid. I then tried to do the same from the FusionSolar app, which also resulted in a timeout.
Potentially a short update interval could cause this issue. When I had a custom solution using the ModBus app, I had frequent timeouts when reading settings too frequently.
After setting the update interval to 180 seconds, I was able to make adjustments.
This was odd.. i tried to jump around in the list and for some magical reason it changed to local control and i didnt even select it more then the first time.
Ill try it also and see what happens.
Acutualy that makes sense. Considering in my case i have 3 devices talking to the same modbus device (inverter). Wouldnt a 60 second setting create spam toward the unit?
I implemented three changes in 1.0.9:
Fix 1 — Poll paused during writes (_writeInProgress flag)
Both the SUN2000 and LUNA2000 drivers now set a _writeInProgress flag before executing any Modbus write. The poll cycle checks this flag at the start and skips execution if a write is queued or in progress. This prevents new read operations from being pushed onto the host queue, keeping it free for the write to execute immediately.
Fix 2 — Three write attempts with increasing delays
writeModbusRegister in modbus-client.js previously made only one retry. It now attempts the write up to three times — on failure, it waits 1500 ms before the second attempt and 3000 ms before the third. This handles the common case where Huawei inverters silently reject the first TCP connection.
Fix 3 — Increased write response timeout
A dedicated WRITE_TIMEOUT_MS = 10000 ms constant was introduced for write operations, separate from the existing RESPONSE_TIMEOUT_MS = 5000 ms used for reads. Control register writes on Huawei inverters (e.g. working mode, force charge/discharge) require more processing time on the device side before an acknowledgement is returned.
How modbus traffic works in the app and why a timout could occur:
All Modbus traffic is serialised through a withHostLock mechanism in modbus-client.js. Each unique host:port combination gets its own queue — when a device wants to read or write, it chains its operation onto the tail of that queue and waits for all previous operations to finish first. This means a SUN2000 and a LUNA2000 that share the same SDongle (same IP and port) will never open two simultaneous TCP connections to it, because the second device’s request simply waits until the first device’s connection is fully closed before starting. Devices on different IP addresses or ports each have their own independent queue and therefore never block each other at all.
At least for me it seems to work:
Last version semi works. It gets changed but i get timeout sometimes. Not all the times thow.
I’ve extended the timeout again and implemented logging for modbus write actions.
Please make sure to pause any other homey apps which access the same modbus device while testing.
Is the battery configured to use mode “maximize self consumption“?
Separate devices vs. FusionSolar Plant
Install the separate devices: SUN2000 (Modbus) for the inverter and LUNA2000 (Modbus) for the battery. The “FusionSolar Plant” device uses the cloud API and only shows aggregated yield data — it does not give you control over battery settings or detailed live values. The separate Modbus devices run fully local and give you everything.
It looks like
Does that mean you do not have an S Dongle and there is no Power Meter in your setup?
If that’s the case there is a separate driver required for EMMA-only installations within my app where specific modbus registers.
Could you please post some screenshots of the devices you’ve added? I need to know if all required Capabilities are visible in the EMMA device.
Thank you
I had both s dongle and smart meter before but when I installed EMMA it replaces them so only EMMA now.
