Temperature sensors not appearing in my VRM Device list

[gharshaw]

Is it just my account or should the temperature sensors be appearing in the VRM device list as they do show on the VRM dashboard?

[freakent]

Please can you provide more information and some screenshots? It's not clear to me what you mean by VRM dashboard vs device list.

[gharshaw]

My temp and tank sensors that are published to the dbus appear correctly on the VRM dashboard however only the tanks appear on the VRM device list.

I am unable to remove the temp sensors from VRM since they are not on the device list. I'm curious if this is the case for all using this device driver

Regards Gene

[freakent]

You are correct. I just checked my test set up where I have ruuvi tags and a the temperature simulator running. The device list only shows the Ruuvi tags.

I'm not sure exactly why that is. There are some differences in the dbus values but I can't see anything obvious. It could be that VRM is explicityly looking for the name Ruuvi somewhere. A simulated tank sensor is being listed so it can't be an issue with the driver, but something in services.yml.

At the end of the day, I can't see that this is really that useful. You should be sending a disconnect (connect=0) with a Last Will message when the device disconnects from MQTT. The GX device will then spot disconnected devices and give you the option of removing them.

[freakent]

dbus whilst devices are connected over MQTT

dbus after devices have disconnected and Last Will message sent

[gharshaw]

As you see in my screenshot my IN temp sensor states it has not updated in 5 days although it is updating on my CCGX. I think it might be corrupted in VRM. Do you think sending the last will message will remove it from VRM and on a new connection will recreate it on VRM?

[freakent]

I would use dbus-spy to see what is in the dbus. You might find it easier to clean up the dbus by hand.

But you should ensure you have a Last Will message set in your code.

[gharshaw]

I am using node-red. I just shut it down cleanly and it did not send a last will or disconnect. According to node-red documents it should have. Do you have any experience with the node-red mqtt nodes?

Regards

[freakent]

I do know NodeRed well (see my other popular project) although it's been a while so I have to rely on my memory.

The last will message is sent by the client (in this case NodeRed) to the MQTT broker when the client connects. If the client disconnects unexpectedly then the broker sends the last will message to the topic it was intended for.

There is a good article here:

http://stevesnoderedguide.com/configuring-the-mqtt-publish-node

Also take a look at the samples in the test-data folder. They are written in python but you should be able to understand the Mqtt last will set up.

[gharshaw]

Thanks for the additional info. I have the lastwill and disconnect working now by updating the close and will message configuration in the NR MQTT broker config. After making this change and forcing a close it seems to have corrected the VRM update issue