Conflict with HA built-in Modbus integration - cannot use modbus: in configuration.yaml

[Nedrans]

Hi! I'm using this integration together with the built-in Modbus integration in HA to control my Östberg HERU ventilation unit. But when I add a modbus: block in configuration.yaml, both integrations crash with this error:

Setup failed for 'modbus': Integration failed to initialize.
Setup failed for custom integration 'sigen': Could not setup dependencies: modbus

Is there any way to use both at the same time? The HERU uses a completely separate IP address from my Sigenergy system.

Environment

• Home Assistant version: Core 2026.6.4
  Supervisor 2026.06.2
  Operating System 18.0

• Sigenergy ESS version: Version 1.2.5

[TypQxQ]

Hi! I'm using this integration together with the built-in Modbus integration in HA to control my Östberg HERU ventilation unit. But when I add a modbus: block in configuration.yaml, both integrations crash with this error:

Setup failed for 'modbus': Integration failed to initialize.

Setup failed for custom integration 'sigen': Could not setup dependencies: modbus

Is there any way to use both at the same time? The HERU uses a completely separate IP address from my Sigenergy system.

Environment

• Home Assistant version: Core 2026.6.4

                                      Supervisor 2026.06.2
  
                                      Operating System 18.0 
  

• Sigenergy ESS version: Version 1.2.5

Thank you for bringing this up.
Could you provide logs and config so I can try to replicate your problem?
Thanks!

[Nedrans]

Thank you for responding so quickly!
I will unfortunately or fortunately have to say that it was all on me. I was trying to use number/numbers in my manual modbus configuration, and after removing it and only using sensors (and instead using "action: modbus.write_register" in an automation), both integrations now coexist without any issues.
I tried turning yours on after I got mine to work perfectly just to gather logs and well. It just worked perfectly.

It turns out that the invalid number entity type was causing the entire Modbus integration to crash on startup, which in turn prevented your integration from loading since it depends on Modbus. So there was never actually a conflict between the two integrations.

So, sorry about that, and thank you for a great integration!