guystewart
(Guy Stewart (Victron Community Manager))
21
Great info and lateral thinking, thanks for writing it up.
Would you be willing to go a step further and take some screenshots or even a screen recording of that process?
I think that might be the final solution for people such as yourself where the “official working solution” has this gap for some people.
Presumably those now stuck with the phantom sensors tried deleting them from the device list before the feature was added that removed them from the dashboard at the same time, so are now between the worlds.
I had that idea too, but I don’t know, how to create sensors with a specific VRM-id… I know there are python-functions you can call (I looked them up in the dbus-mqtt-devices source code). For me it worked good, because my ghost IDs were close to the beginning, IF you have e.g. a ghost-ID of 2048, then my solution wouldn’t be practical.. In theory it should be possible witch command line commands in the console also… But You have to perform several steps to really create and “activate” a new sensor so for me it was the easiest to use dbus-mqtt-devices. Maybe we can ask freaknt to implement a feature to specify a VRM-id upon creation of a device in his code, so it would be much easier to use for high VRM-IDs…
sorry that I didn’t took screenshots during my actions. But I wasn’t sure if it’s working at all
And also, I suppose, the process might be different with different sensor types and/or versions of dbus-mqtt-devices. So I think, people with this ghost devices already played around with dbus-mqtt-devices or node red and will find it’s way to try to remove their ghost sensors itself. As an addition to the above, I used MQTT-Explorer to send the mentioned messages. But I assume, everyone using dbus-mqtt-devices and venus will use MQTT-Explorer to check their setups anyhow.
So if there are more people having problems to get rid of their ghost devices, I’ll try to help here and we’ll see, if a “tutorial” will be necessary.
