Inconsistent relationship between two router devices (shown as sibling on one card, child on the other)

[wenstarner]

Hi,

I’ve noticed what looks like an inconsistency in how device relationships are displayed in the network view.

In the attached screenshot, there are two router devices:

1. Plug (Bathroom)
2. 3. Plug (Kitchen)

Both devices show the Coordinator as their parent.

However:

• On the Plug (Bathroom) card, Plug (Kitchen) appears under “Siblings (1)”.
• On the Plug (Kitchen) card, Plug (Bathroom) appears under “Children (1)”.

So the same pair of devices are displayed as siblings from one side and parent/child from the other, even though they both list the Coordinator as their parent.

Expected behaviour

I would expect the relationship between these two devices to be represented consistently, for example:

• Either both see each other as siblings (same parent),
• Or there is a clear parent/child relationship that is reflected identically on both cards.

Actual behaviour

• Device A (Plug (Bathroom)) lists device B (Plug (Kitchen)) as a sibling.
• Device B (Plug (Kitchen)) lists device A (Plug (Bathroom)) as a child.

This makes it hard to understand the actual network topology.

Steps to reproduce

1. Have two Router devices on the network that both use the same Coordinator as parent.
2. Open the detail view / card for Router 1.
3. Note how Router 2 is categorised (sibling/child).
4. Open the detail view / card for Router 2.
5. Compare how Router 1 is categorised.

Additional information

• Both devices are shown as Router.
• Each device lists Parent (1): Coordinator.
• The relationship discrepancy is visible in the screenshot.

Please let me know if this is expected based on how neighbour tables are interpreted, or if you need any extra diagnostics (logs, export, etc.).

[Nerivec]

Unfortunately, relationships handling is far more complicated than it should be, and does not always reflect what you would expect from the naming. Here's an example (quote from the spec):

After joining is complete, a joining or rejoining router device will no longer have a parent child relationship with the device it has joined or rejoined to; rather, both devices will have a ‘relationship’ of 'sibling' (0x02).

On top of this, this is tied to how devices report this information, and quite a few mislabel relationships (or don't update properly after some status changes). This is especially true for anything Tuya or Tuya-derived.