Silly question - old FW 2.73 on Cerbo GX and missing devices in HA

[kucerazdenek]

I am managing two victron installations in HA, one is mine, Cerbo GX FW 2.93, everything works smoothly, no issues. Few days ago, vendor installed PV to my neighbors in very same configuration as I have (1x Fronius, 3x Victron Multiplus 3000, Cerbo GX, Pylontech batteries). All devices have recent FW except Cerbo which vendor forgot to upgrade and currently is on FW 2.73. When I installed victron integration and did the scan on my neighbor installation, I am missing following devices in HA (even they are shown in Cerbo Remote Console)

• ID 30 - victronenergy.grid
• ID 227 - victronenergy.vebus

Rest, (ID 225 - pylontech, ID 20 - pvinverter and ID 100 - settings) works fine. I know vendor has to update Cerbo to newer FW, but would like to kindly ask you if someone had similar experience and I can expect that after FW upgrade it will work correctly, or this might be caused by some other issue. Attaching debug log from victron integration, it just states that no registers found for those devices (ID 30, ID 227) home-assistant_victron_2023-06-12T18-16-52.628Z.log

In VRM Console I see them correctly:

[sfstar]

Thank you for opening this issue. (and providing the level of detail) When I originally started work on this integration I made the assumption that nobody would be having 2 GX devices they wanted to integrate into the same home assistant instance (with this being a local integration and 1 GX device enabling almost infinite future extensions to a given system). However, this assumption was clearly wrong since you opened this issue (no worries 😉)

If you don't mind me asking Is the connection to your neighbours installation in essence "local" (either on the same lan, point-to-point or using a vpn to create a "local" network over te internet?

Since the integration isn't (currently) completely compatible with this use case I believe that your issue might be stemming from your own installation also exposing a grid device on modbus ID 30 and a vebus endpoint on 227. Could you check if the ID 30 and id 227 are the overlapping between the instances? (And if so, whether there are any other overlapping ID's). It's my assumption that the 2 installations use different modbus unit (slave) id's for all other devices but the vebus and grid meter endpoints. Since, the integration uses the unit id to register an entity ID this would result in an entity_id clash meaning that the entities coming from the 2nd configuration instance wouldn't be able to be registered and would therefore be missing.

[kucerazdenek]

Thanks for reply. I have to apologize for a bit misleading/confusing description. Of course there are physically two HA instances (one is serving my house, second one my neighbor's) and I am just switching between them in Home Assistant mobile application with three-finger gesture. Both installations uses (according to VRM Control Panel) very same ID for all devices (20, 30, 100, 225, 227) My question was rather pointing to the fact, that on Cerbo GX FW 2.73 integration scan returns "no registers found for unit ID 30 and 227", while on 2.93 works perfectly. Because it is not easy to push vendor to visit the site, would be helpful to know in advance, if those issues are caused by old FW version or if there is some underlying other issue which needs to be resolved.

Today I found following in your readme, thus wondering if it might be the case with FW 2.73 (08/2021)

This might (depending on your firmware and connected devices) cause odd behaviour where some but not all devices connected to your GX device will be correctly detected by this integration.

[kucerazdenek]

It definitely was caused by 2.73 FW