question

Same here with 2.91.

/var/log/dbus-mqtt/current shows:

@40000000633977463001833c -------- dbus_mqtt, v1.30 is starting up --------
@400000006339774630197424 INFO:logger:Loglevel set to INFO
@40000000633977463390d034 INFO:mosquitto_bridge_registrator:[InitBroker] Reading config file
@400000006339774633a9846c INFO:mosquitto_bridge_registrator:[InitBroker] Registering CCGX at VRM portal
@4000000063397747013a8d64 INFO:mosquitto_bridge_registrator:[InitBroker] Not updating config file and not restarting Mosquitto, because config is correct.
@400000006339774701473b7c INFO:mosquitto_bridge_registrator:[InitBroker] Registration successful
@400000006339774701ba19bc INFO:dbus_mqtt:[Scanning] service: com.victronenergy.hub4
@4000000063397747020cb62c INFO:dbus_mqtt:[Scanning] service: com.victronenergy.qwacs
@400000006339774702bc012c /opt/victronenergy/dbus-mqtt/dbus_mqtt.py:402: DeprecationWarning: The 'warn' function is deprecated, use 'warning' instead
@400000006339774702bc2454   logging.warn('[Scanning] {} does not provide an item listing'.format(service))
@400000006339774702c55bb4 WARNING:dbus_mqtt:[Scanning] com.victronenergy.qwacs does not provide an item listing
@400000006339774702e13c6c INFO:dbus_mqtt:[Scanning] service: com.victronenergy.settings
@400000006339774705d78d54 INFO:dbus_mqtt:[Scanning] service: com.victronenergy.pvinverter.pv_3010544110
@4000000063397747065475e4 INFO:dbus_mqtt:[Scanning] service: com.victronenergy.system
@4000000063397747085be28c INFO:dbus_mqtt:[Scanning] service: com.victronenergy.fronius
@400000006339774708a5f37c INFO:dbus_mqtt:[Scanning] service: com.victronenergy.temprelay
@40000000633977470916a70c INFO:dbus_mqtt:[Scanning] service: com.victronenergy.grid.cgwacs_ttyUSB0_di30_mb1
@400000006339774709d1d11c Traceback (most recent call last):
@400000006339774709d3f7e4   File "/opt/victronenergy/dbus-mqtt/dbus_mqtt.py", line 397, in _scan_dbus_service
@400000006339774709f268dc     items = self._get_dbus_value(service, '/')
@400000006339774709f3bcb4   File "/opt/victronenergy/dbus-mqtt/dbus_mqtt.py", line 533, in _get_dbus_value
@40000000633977470a15f284     return self._dbus_conn.call_blocking(service, path, None, 'GetValue', '', [])
@40000000633977470a16d12c   File "/usr/lib/python3.8/site-packages/dbus/connection.py", line 652, in call_blocking
@40000000633977470a429064     reply_message = self.send_message_with_reply_and_block(
@40000000633977470a454b9c dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Unknown / invalid method
@40000000633977470a464d6c 
@40000000633977470a46553c During handling of the above exception, another exception occurred:
@40000000633977470a4664dc 
@40000000633977470a4668c4 Traceback (most recent call last):
@40000000633977470a475edc   File "/opt/victronenergy/dbus-mqtt/dbus_mqtt.py", line 602, in <module>
@40000000633977470a6c3c5c     main()
@40000000633977470a6d51b4   File "/opt/victronenergy/dbus-mqtt/dbus_mqtt.py", line 584, in main
@40000000633977470a90c004     handler = DbusMqtt(
@40000000633977470a91c9a4   File "/opt/victronenergy/dbus-mqtt/dbus_mqtt.py", line 217, in __init__
@40000000633977470aa230dc     self._scan_dbus_service(service)
@40000000633977470aa2f42c   File "/opt/victronenergy/dbus-mqtt/dbus_mqtt.py", line 401, in _scan_dbus_service
@40000000633977470abd2734     self._introspect(service, device_instance, '/', publish)
@40000000633977470abe01f4   File "/opt/victronenergy/dbus-mqtt/dbus_mqtt.py", line 441, in _introspect
@40000000633977470adc6f04     self._introspect(service, device_instance, p, publish=publish)
@40000000633977470adde9ec   File "/opt/victronenergy/dbus-mqtt/dbus_mqtt.py", line 423, in _introspect
@40000000633977470af95574     value = self._dbus_conn.call_blocking(service, path, None, 'Introspect', '', [])
@40000000633977470afa3034   File "/usr/lib/python3.8/site-packages/dbus/connection.py", line 652, in call_blocking
@40000000633977470b23ebcc     reply_message = self.send_message_with_reply_and_block(
@40000000633977470b2508f4 dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Unknown / invalid method

Hi both, VictronConnect remote view, I think we call that VC-R in the VictronConnect manual, as well as the real-time mode of the VRM Dashboard, also use MQTT.

And that is used a lot: by thousands of users at a time.

So you could check if those things work for you.

And otherwise, I’d start searching elsewhere: perhaps you’re using the wrong mqtt broker in the farm? Or some perhaps making a mistake elsewhere. I’m quite sure many people are using MQTT, also on v2.91.

Hi @mvader (Victron Energy)!

My understanding is, that dbus-mqtt connects to the local mqtt broker running on VenusOS. As soon as it sees an empty payload on topic /R/<sysid>/system/0/serial it sends the serial to that topic and keeps on sending all available values to all topics.

The local mqtt broker has two bridges configured, one of them connects to mqtt<xx>.victronenergy.com and bridges all topics.

My assumption is, that once I have sent the keep alive to the named topic above, I should even see topics and values on the local mqtt broker.

Anyhow, I tried both, local mqtt broker and the mqtt<xx>.victronenergy.com but in both cases there is literally nothing happening accept the serial being sent back.

How can I troubleshoot this?

@stevie @mvader (Victron Energy)

I found the issue. I am using https://github.com/mitchese/shm-et340 to read my SMA SunnyHomeManager 2.0. This executable seems to send data to dbus that breaks dbus-mqtt.

I am aware, that Victron is not supporting this. I raised an issue with the developer of shm-et340.

Thanks for the information. Since I use the same script, it is quite likely exactly the same error.

How did you find out?

Hopefully the developer of shm-et340 finds a soloution.

@stevie @mvader (Victron Energy)

I found a solution to this issue. After ending up in the python code of python package "dbus", I got the impression that maybe the fact, shm-et340 being the last registration to dbus causes the issue. So I flipped the rc.local entries and it works!

Now my rc.local with shm-et340 & dbus-serialbattery looks like this:

root@raspberrypi2:~# cat /data/rc.local
#!/bin/bash
sleep 10
setsid /data/shm-et340 > /dev/null 2>/dev/null &
sh /data/etc/dbus-serialbattery/reinstalllocal.sh

Now I can see the topics being published after keepaliving dbus-mqtt like described in the git documentation.

@Dominik Feser Thanks for sharing this. Unfortunatelly I couldn't find /data/etc/dbus-serialbattery/reinstalllocal.sh. So I started playing with the rc.local, I found another even simpler way to fix my issue: I just increased the sleep time.

My rc.local now looks like this and MQTT / shm-et340 are working fine (together):

#!/bin/bash
sleep 25
setsid /data/home/root/shm-et340 > /dev/null 2>/dev/null &

@stevie you are probably not using dubs-serial battery at all ☺️

Glad shm-et340 now works with mqtt!