[Bug]: wait for setup devices forget devices that are published late

[sjorge]

NRCHKB Plugin Version

1.5.0-dev.2

Node JS Version

v16.14.2

NPM Version

8.5.0

Node-RED Version

2.1.3

Operating System

OmniOS

What happened?

All my devices have wait for setup, sometimes one of my devices would appear as a new device for homekit.

It took a while to track down while, occasionally one or two devices would get there setup payload published a bit later than the others. This device still shows up but it looks like some of the 'remembered' information about the device in that case gets discarded and new UUID and such are generated for the devices that get published a bit later.

This is rather annoying as it only happens every so often and it's very hard to trigger in my actual setup.

Doing it manually is easy as you can just insert a delay node for example for 10 seconds on one service and that would trigger it.

How to reproduce?

• setup 2 services with wait for setup
• publish a payload to them via a inject node (once at startup)
• add a delay node, say 10 sec or more to one of the two.

Expected behavior:

Even if a service gets the setup message a bit later than the other, it should still retain UUID's so it appears as the same device to homekit.

Additional comments?

Additional comments here, if any.

Relevant log output

No response

[caitken-com]

Hi @sjorge, is this resolved?

1. Have you set NR to only deploy modified nodes only?

[sjorge]

No, mine is set to do full deploys.

it’s still not resolved, the problem is not the node deployment but that when a setup payload is received later for a node it misses the boat so to speak and falls into the water.