Best practices for multiple networks in close proximity

Go To Last Post
2 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm hoping someone could tell me the "best practices" when using the lwMesh with multiple networks in the region.

Use case I'm not sure how to handle.

This is home automation component and there is the possibility of having two apartments in close proximity where networks would be able to "see each other". These must operate as independent networks.

Assume you have a coordinator, and multiple add-on nodes. If the person in apartment "a" wants to add a node, how does it avoid being added on in apartment "b" also?

Solution 1 - each network has it's own network ID. How does a new node know what the ID is and does he set if there is no user interface. (simple sensor - no keyboard, lcd or usb)

Solution 2 All networks share the same ID, but the coordinator filters responses based on known device ids

Solution 3 - you have a special part of the program for "lean mode" where the coordinator would switch to a know network id, the new node would start up with the known id, look for a new message with the new network id to use as the payload. After confirmation, both devices would switch to the broadcast network id.

Solution x - there must be some best practices for this type of situation

Last Edited: Fri. Oct 16, 2015 - 01:47 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

That really depends on what kind of UI is available on the devices.

For example, if you have just one button:
1. Each coordinator selects a random PAN ID and security key.
2. When new device is added, a button must be pressed on both sides. This will initiate transfer of the security information. At this stage you might also assign a unique network address to the devices.

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.