Hi, A current project I am working on has a requirement for integration with a specific access controller and I would like to make it generic and publish as an open source module. For those that are curious the brand is called ISONAS ( very nice because its the only solution I was able to find where the keypad itself can store users ).
I am just after some initial feedback in regards to my design so that it follows the "Tryton way". The product comes with a full software suite to manage different users and accesses, and the integration can be achieved using simple plain text TCP/IP messages. We only want to achieve 2 things: 1. Create codes for users 2. record keypad events The solution I see so far is a code field on the party model and whether they are unable or disabled and simple one to many model to hold "events" at a keypad with a few fields: party - onetomany keypad reference - text datetime - date and time of event event description I was going to create a configuration to the module to define items such as destination IP/url of controller, and also key for encryption, however Sharoon had suggested that it is best practice to store this in the Tryton instance config file. I will probably also need to add the name of the user group as the ISONAS controller requires users to be assigned to a group. Interested to see if anybody else has integrated another Access controller and what design they have chosen. Cheers, Vincent Bastos
