search

freakent / dbus-mqtt-devices

A driver for Victron VenusOS GX devices to support use of dbus-mqtt/flashmq-mqtt
MIT License
111 stars 24 forks source link

Custom name missing after CCGX reboot #15

Closed gharshaw closed 2 years ago

gharshaw commented 2 years ago

@freakent Hi Martin, After further investigation, the re-registration is not overwriting the local /data/conf/settings.xml file after a reboot and a re-registration. The GUI shows the default name, again the settings.xml still has custom name. I have to re-enter the custom name in the GUI for it to take effect.

Thoughts? Thanks, Gene

freakent commented 2 years ago

Gene, can you provide the service type and the status message you are registering with?

gharshaw commented 2 years ago

Martin,

device/<nr001/Status { "clientId": "nr001", "connected": 1, "version": "v2.3", "services": { "t1": "temperature", "t2": "temperature", "t3": "temperature", "t4": "temperature", "t5": "temperature", "tk1": "tank", "tk2": "tank", "tk3": "tank", "tk4": "tank" } }

freakent commented 2 years ago

In the topic name you have <nr001, is that a typo?

freakent commented 2 years ago

Seems like a regression error. I'll have to do more testing and create a fix.

gharshaw commented 2 years ago

Appreciate it! Question: Does your service update the D-Bus or does a Victron Service? The reason I ask is that looking at Dbus-spy the Custom Name is populated with the "default" Custom name image

freakent commented 2 years ago

Victron provides a library called velib.

freakent commented 2 years ago

I found the problem. The fix will go out in the 0.5 release hopefully over the weekend.

If you are looking in dbus-spy, the persistent settings are under com.victronenergy.settings.

freakent commented 2 years ago

Fixed in release v0.5.1