Sockets not stored in redis and onRedisDisconnect does not work

Node version: 10.15.3
Sails version (sails): 1.2.3
ORM hook version (sails-hook-orm): 2.1.1
Sockets hook version (sails-hook-sockets): 2.0.0
Grunt hook version (sails-hook-grunt): 4.0.0

It seems that socket connecting to sails are not saved in redis, despite having that set up in config/sockets.js

On a fresh Sails.js installation (generated with sails new and option empty, my config/sockets.js looks like this:

module.exports.sockets = {
    
  adapter: 'socket.io-redis',
  url: 'redis://127.0.0.1:6379',

  onRedisDisconnect: function () {
    console.log("FOO!!!");
 };

If I now add "socket.io-redis": "~5.2.0", to package.json and run npm install I can lift my Sails app without problems. However, Sails doesn't store anything in redis. If I connect a socket and look into redis (via redis-cli) - it is empty. There is not a single database with a single key. Nothing.

Additionally, if I stop redis, I'll get

error: Redis socket "admin sub" server went offline...
error: Redis socket "admin pub" server went offline...
error: Redis socket "sub" server went offline...
error: Redis socket "pub" server went offline...

but onRedisDisconnect is obviously not called, I never get the console.log

My adapter settings are definitely used by Sails: If I change them to something nonsense, I'll get an error ("Failed to lift app: Error: Redis connection to 127.999.0.1:6379 failed - getaddrinfo ENOTFOUND 127.999.0.1 127.999.0.1:6379").
Same goes if redis is not running, when I try to start Sails.

Reproduce the issue from config/sockets.js using the socket.io-redis dependency added in package.json, then inspect Redis with redis-cli while connecting a socket and stopping Redis. Compare the observed Redis state and disconnect behavior with the expected socket storage and onRedisDisconnect callback, using the reported error messages as checkpoints for completion.