VMB7IN data read in Home Assistant with Velbus-TCP

I am working with a VMB7IN module in combination with Home Assistant.

Since upgrading to firmware build 2306, the pulse counter/energy values are no longer being read correctly in Home Assistant.
In earlier tests, this still worked perfectly with build 1822, which is fully supported by the current Home Assistant Velbus integration.
Therefore, I would like to downgrade the VMB7IN module back to build 1822.

Would it be possible to obtain the .vmb file for VMB7IN firmware build 1822?

I will of course take care of performing a correct and safe downgrade using VelbusLink.
Thank you in advance for your assistance!

@cereal
Is this something you’ve seen?

@SergeVG
Can you find the version of Velbuslink that offers the firmware version you need?

I Have found the problem. When using two velbus integrations on home assistant, there can be a conflict in names when the modules on different integrations have the same adress 00 to FF on the bus.

Which begs the obvious question…

What reason do you have for needing two (I assume different) Velbus integrations?

Is there something missing in one that is available in the other?

The building is to big for one velbus. I have in total more than 200 modules knowing that a keypad can use up to 6 adresses, I am running out of adresses with 255 possibilities.

Oh I see.

Two networks of Velbus, rather than two different integration solutions.

That’s very interesting, are you saying that the cause of the issue was that the VMB7IN modules on both networks had the same base address?

I’m not sure, but in the first integration, I have the names from the first Velbus. In the second integration, I have the names from both the first and the second Velbus. It seems there’s a conflict in the entity names, and after reloading, the energy data doesn’t show up. Maybe the problem is something else. I called Velbus support, and they said the Home Assistant integration isn’t theirs. They suggested using two Signum modules and connecting each to a separate Home Assistant installation.with the remote home assistant integration.