Probably the 123SmartBMS is causing the issue.
I found a repository on GitHub for a service that you probably installed manually, and the issue seems to be that it doesn’t fully follow the specifications. As a result, VictronConnect isn’t receiving the expected response, which blocks the entire message queue. You can either ask the developers not to publish this path on D-Bus, or you can try to comment out this line in the script on your GX yourself:
We’ll work on handling these cases, but at the moment there are other priorities.