Victron Bus System Connection get lost when using dbus-mqtt-devices

[PanicMan]

Version

0.6.5 (current)

What version of VenusOS are you running on your GX device

3.21 (current release)

Does this issue occur during installation or at runtime ?

Runtime

Is there a Discussion thread for this issue? Please paste a link.

No response

What is the issue you are actually experiencing?

Hello, thank you very much for the code and the detailed description! I have the whole thing running on an MP2 5000 GX (Large OS), also have an OpenHab Smarthome and am quite familiar with MQTT. I get the grid data from an LG ESS 10 system and wanted to feed it to my Victron System, which runs in parallel. However, I get errors in the system when I run it on it. I connected an MPPT 450/100 charge controller via VE.direct and a battery system via BMS.CAN (500kbits), which has been running for a few weeks without any problems.
But as soon as I start supplying the MQTT Grid Meter with data, which happens every 10s, I get errors in the system and the charge controller stops charging: Solar Charger - MPPT 450/100: Error code: #67 - No BMS ... VE. Bus system: low battery alarm. Then the CCGX is rebooting...
As soon as I stop sending the MQTT data to the local broker, the whole thing works again. What could be the reason? Is this going to overload the system and prevent the BMS data from reaching the charge controller?
Tried to check the system load with "top", around 50-60%... Seems to be ok...
Thanks a lot!
Greetings Jack

If this is not installation related, what does the status payload look like that you are publishing to the driver to register your device?

{"clientId":"grid01","connected":1,"version":"v0.1","services":{"g1":"grid"}}

Relevant log output

@4000000065db140d27fb34e4 *** starting dbus-mqtt-devices ***
@4000000065db141118a7b6d4 dbus_mqtt_devices v{} 0.6.5
@4000000065db141118a7e1cc INFO:logger:Loglevel set to INFO
@4000000065db141118ce2e7c INFO:dbus_mqtt_devices:-------- dbus_mqtt_devices, v0.6.5 is starting up --------
@4000000065db14111e58baec INFO:device_manager:Using portalId c0619ab41a28
@4000000065db14122a19466c INFO:mqtt_gobject_bridge:[Init] Connecting to local broker
@4000000065db14122e5ab8dc INFO:device_manager:[Connected] Result code 0
@4000000065db14901d2a58c4 INFO:device_manager:Received device status message {'clientId': 'grid01', 'connected': 0, 'version': 'v0.1', 'services': {'g1': 'grid'}}
@4000000065db14901d61147c WARNING:device_manager:tried to remove device grid01 that is not registered
@4000000065db14902c6f8e94 INFO:device_manager:Received device status message {'clientId': 'grid01', 'connected': 1, 'version': 'v0.1', 'services': {'g1': 'grid'}}
@4000000065db14902c7e9254 INFO:device:**** Registering device: grid01, services: {'g1': 'grid'} ****
@4000000065db14902c885e24 INFO:device:Registering Service grid for client grid01
@4000000065db14902c91e3a4 INFO:device_service_config:About to open config file
@4000000065db1491114856dc INFO:device_service:Registering service grid for client grid01 at path com.victronenergy.grid.mqtt_grid01_g1
@4000000065db1491137dc0f4 INFO:settingsdevice:Setting /Settings/Devices/mqtt_grid01_g1/ClassAndVrmInstance does not exist yet or must be adjusted
@4000000065db149116e16624 INFO:vedbus:registered ourselves on D-Bus as com.victronenergy.grid.mqtt_grid01_g1
@4000000065db149117c9e1c4 INFO:device_service:Registered Service com.victronenergy.grid.mqtt_grid01_g1 under DeviceInstance 1
@4000000065db14911817b78c INFO:device_manager:publish {'portalId': 'c0619ab41a28', 'deviceInstance': {'g1': 1}} to device/grid01/DBus, status is 0

--- Here I manually send the disconnect Status from Node-Red ---

@4000000065db184202f652dc INFO:device_manager:Received device status message {'clientId': 'grid01', 'connected': 0, 'version': 'v0.1', 'services': {'g1': 'grid'}}
@4000000065db18420609efc4 INFO:device_service:Unregistered mqtt_grid01_g1 from dbus
@4000000065db1842061899ac INFO:device:Removed Service g1 from client grid01
@4000000065db18420634c49c INFO:device_manager:**** Unregistering device grid01 ****

[freakent]

Hi Jack,
There is a good chance that since you are running this on a CCGX you are simply running out of system resources. Take a close look at /var/log/dmesg. Somewhere you might see messages about system being low on resources and the OS forcing a reboot.

I experienced this same problem on my ccgx so I stopped using the driver, but I also experienced this after adding 4 ruuvi tags to my system so I can't blame the driver. I guess it just doesn't take much to cause reboots on a CCGX. This weekend I replaced my own CCGX with an Ekrano.