MQTT Null Messages and Device Reports on ZPC Service Stop/Start or Restart

[sohail-shareef]

I noticed that when I stop the ZPC service, null messages appear on MQTT. Technically, these messages should only appear when a node is removed, but they are the same when the ZPC service is stopped.

Similarly, when I start the service, all previously added Z-Wave devices report their information again on MQTT.

Upon restarting the service, both types of reports occur, making it difficult for our application to determine whether a device has been removed or added.

Why is this behavior occurring? Is there a way to stop this reporting?

I am attaching logs

Reports when ZC service restart.txt
Reports when ZPC service start.txt
Reports when ZPC Service stop.txt

[rzr]

Thanks for reporting, this will be investigated, is it a regression ?

[sohail-shareef]

Thanks for responding and It is common in all the versions. Everytime devices are deleting and adding.

[sohail-shareef]

Any update on this?

[rzr]

Not really it looks, it looks like the attribute resolver was intentionally designed that way, as a fallback option can your application detect some mqtt "restart" publication to filter out those init states ?

[sohail-shareef]

Currently we are relying on protocol controller status but the MQTT messages are in thousands if i add 50 nodes in real world these nodes are common. We don't understand how much we should ignore these messages.
Is there any possible alternate solution on this.