Allow multiple UI clients to run simultaneously on the same local network without interference

[ivelin]

Currently when multiple clients open the UI and they are on the same local network, they sometimes conflict and aren't able to pull timeline from the same edge device. This happens mainly during discovery scan for a local edge device. Multiple UIs find each other in the peer room and try to connect as if they were edge devices, which goes into a loop. They are not able to distinguish edge devices from UI peers in the local network peer room.

[ivelin]

related to #408

[ivelin]

UPDATE: This comment is out of scope. Moving to a separate issue: #494

Another concern came up in our bi-weekly community call. There may be different roles of users with different level of access to the same edge device data. For example owner/admin sees all detections. Caregiver only gets medical emergency related notifications, but not all images&video.

[ivelin]

Note: This issue is different and simpler to solve than #408

[ivelin]

The idea of the solution is to detect the type of a peer (edge device vs UI app) during peer handshake. Consequently an UI app should treat differently edge device peers from other UI app pears. We may need to slightly extend the peer handshake protocol to properly authenticate a peer with its credentials and type (edge device vs UI app).

As a performance optimization and a step toward managing multi peer relationships, we can save in browser local storage each newly discovered peer ID and type. Once saved (cached) the information can be used to speed up subsequent local network discovery scans.

[ivelin]

🎉 This issue has been resolved in version 2.14.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release
• v2.14.0

Your semantic-release bot 📦🚀