Idea:
When a connection was established, the slave sends a message to the server containing the settings (keys) he needs (maybe includes a fancy description etc). Then the master responds with the settings it knows. It also adds those settings to an internal database, so the server knows which slave and which plugin needs what device. Also, the master provides a config interface (probably a webpage), where all of those entries can be edited in a nice way. When a setting changes, the master sends a message to the slave, notifiyng it of the changed setting.
Idea:
When a connection was established, the slave sends a message to the server containing the settings (keys) he needs (maybe includes a fancy description etc). Then the master responds with the settings it knows. It also adds those settings to an internal database, so the server knows which slave and which plugin needs what device. Also, the master provides a config interface (probably a webpage), where all of those entries can be edited in a nice way. When a setting changes, the master sends a message to the slave, notifiyng it of the changed setting.