Make node-session TTL configurable / don't expire for ABP nodes

[frederikvannieuwenborg]

No description provided.

[proemke]

Suggestion:
If no sessiondata for the abp device is available in redis, check the postgres database (only if the 7 MSB of the devaddr are equal to seven LSB of the NetID).
This way it is also easy to modify the database directly to add/modify/delete devices by a simple script.

This way it will also be possible to automatic add new devices with a valid combination of keys and id's (NetID, network and application) to the database. All ABP devices should have the same keys, and can be identified by their devaddr, deveui.

[radekvozak]

Hi guys - I have a question here. Default TTL by creating node session is getting from what.. I see TTL about 7000 min? I have a little bit problem with ABP devices sending data in long interval. After expiration of TTL it does not work (keys are expired)... f.e. after one week. OTAA - no problem of course. The configurable TTL would be very nice. Like if OTAA generated session - TTL expiration time like it is, if ABP - user can set up TTL expiration time (1day - 1year?). What do you think? @brocaar @frederikvannieuwenborg @edjeed

@edjeed Btw - save session data to postgres - I think it is not good idea. Redis is much more quicker then postgres and load this info for big network could be problem in future.

[brocaar]

This will be fixed in 0.17.1 by adding support to configure the node-session TTL.