Phantom devices

[berkinet]

When creating a new Indigo Hubitat device, In the available HE device list, I see a few HE devices that no longer exist. That is, they did exist in HE at some point, but were removed. These devices do not appear in the HE device list and are not published from the HE MQTT app. I have rebooted both devices several times. Obviously, something, somewhere, is caching the information.

This is certainly not a big problem. But, it seemed worth reporting.

[berkinet]

Looking at the MQTT stream, it seems these phantom services are being propagated by the HE MQTT plugin. I will check with Kevin.

[autolog]

Have you gone in and edited the MQTT App settings to remove the devices?

[berkinet]

Have you gone in and edited the MQTT App settings to remove the devices?

Yes.

[berkinet]

After emailing Kevin, I shut everything down (HE, broker (Mosquitto), MQTT Explorer, and the HE plugin and then restarted. Problem gone.

[FlyingDiver]

Those discovery messages might have been tagged as "retained", so the MQTT broker was saving them and re-transmitting. Restarting the broker would have cleared that.

[berkinet]

Those discovery messages might have been tagged as "retained", so the MQTT broker was saving them and re-transmitting. Restarting the broker would have cleared that.

In that case, would the option to control retention, if it exists, be somewhere in the HE MQTT app?

[autolog]

In that case, would the option to control retention, if it exists, be somewhere in the HE MQTT app?

Yes, retention is specified by the App doing the publishing AFAIK.

[FlyingDiver]

I can sorta see why they might want to discovery messages to be retained, so a client gets an immediate list of devices without waiting for them to advertise themselves again.

If they do that, then they should also be sending out a (retained) message when they shut down to cancel the previous message. It's possible that the broker is sending those shutdown messages again but the plugin isn't acting on them.

Or, it's just broken.

[autolog]

.... It's possible that the broker is sending those shutdown messages again but the plugin isn't acting on them.. Or, it's just broken.

Quite possible on both counts

[FlyingDiver]

.... It's possible that the broker is sending those shutdown messages again but the plugin isn't acting on them.. Or, it's just broken.

Quite possible on both counts

I was referring to the HE app.