Moving sensor from one network to another may cause conflict
-
Hi
My question is about moving sensor from one 'MySensors network' (lets call it network A) to another (lets call it network B ), ie: a friend give you one of his sensors from his network. In this scenario, the sensor still use his network A id in the network B. This may cause conflicts with another sensor with the same id in the new network...
A solution would be to give a network some kind of hashcode to compare with a sensor at boot time (in gw.begin()). If hashcodes are different (the one stored in the controller/gateway and the one stored in the sensor), then the sensor need to reinitialize (reset EEPROM and reboot) before any other action. The hashcode may be a string of 8 characters for example.
Add a new sub-type for internal mesage like this :
I_NETWORK_HASHCODE with a value of 15 (?) with the comment "Hashcode used in the network to avoid conflict with others networks".What do you think about that ?
Suggested Topics
-
Motion Sensing sketch which is also a repeater
Troubleshooting • 18 Jan 2015, 10:07 • Dean 15 Mar 2015, 04:08 -
General advice
General Discussion • 8 Oct 2014, 18:43 • shawn_ky 17 Oct 2014, 06:27 -
Connect sensors directly to the Gateway (again)
Development • 12 Jan 2016, 09:01 • mortommy 1 Sept 2016, 12:58 -
Aluminium Case for MySensors
Hardware • 4 Mar 2015, 19:28 • allanvbcrew 5 Mar 2015, 09:14 -
Figaro TGS5042 Carbon Monoxide Sensor & Op Amp
Hardware • 30 Apr 2016, 11:01 • Samuel235 12 Sept 2017, 15:55 -
Secure node encrypted communication. AES-128
Development • 1 Apr 2018, 19:54 • monte 1 Apr 2018, 19:54 -
Network Gateway with Sensors/Actuators
My Project • 20 Jan 2015, 14:31 • lunarok 20 Jan 2015, 14:31