But what will happen with the NodeID and the signing preferences then? If EEPROM is cleared if you update your gateway you have to restart all nodes using signing so the gateway gets updated then.
If you do it in a node, the gateway will assign it a new nodeId and that in turn messes up for the controller. I do not think wiping all EEPROM config on reprogramming is a good ide. The purpose of the EEPROM config is exactly to preserve certain parameters on power cycle/reprogramming.
@mainali
It would be easier if you showed the type of sensor, but basically, you would be constantly reading its output, and reflecting changes between HIGH and LOW (if it has digital output) or using analog thresholds.
@mainali In my view your can distinguish between controller and gateway by understanding each other main function
For the controller the main function is scene management while for the gateway the main function is a route between radio sensors and the controller.
Because raspberry is a multitasking thing it should be possible to run opneHAB and ethernet gateway on the same hardware simultaneously. But I'm not sure is it any existing case of a such.