Proxysql2 don't closes old clients coneections

Ubuntu 20.04, proxySQL 2.0.18-percona-1.1, XtraDB 5.7.33-36-57 - Percona XtraDB Cluster (GPL).
A pool of connections via python is used.
Now unused connections are live up to mysql-wait_timeout = 28800000. On proxySQL 1.4 connections were died when the time was coming time wait_timeout=500 (interactive_timeout=500) (variation and global ariation) on the backend for the same backend.

Proxysql processlist:
mysql> select * from stats.stats_mysql_processlist where user=‘user’ order by time_ms desc;
±---------±----------±-------------------±--------±----------±---------±----------±-----------±-----------±---------±---------±--------±--------±-----±-------------±--------------+
| ThreadID | SessionID | user | db | cli_host | cli_port | hostgroup | l_srv_host | l_srv_port | srv_host | srv_port | command | time_ms | info | status_flags | extended_info |
±---------±----------±-------------------±--------±----------±---------±----------±-----------±-----------±---------±---------±--------±--------±-----±-------------±--------------+
| 1 | 811 | user | db_main | 10.0.3.52 | 42674 | 0 | NULL | NULL | NULL | NULL | Sleep | 6395795 | NULL | NULL | NULL |
| 0 | 812 | user | db_main | 10.0.3.52 | 42676 | 0 | NULL | NULL | NULL | NULL | Sleep | 6395792 | NULL | NULL | NULL

Proxysql runtime variables:
mysql> select * from runtime_global_variables where variable_name like ‘%mysql-wait_timeout%’;
±-------------------±---------------+
| variable_name | variable_value |
±-------------------±---------------+
| mysql-wait_timeout | 28800000 |
±-------------------±---------------+

XtraDB variables:
mysql> show variables like ‘wait_timeout%’;
±--------------±------+
| Variable_name | Value |
±--------------±------+
| wait_timeout | 500 |
±--------------±------+

mysql> show variables like ‘interactive_timeout%’;
±--------------------±------+
| Variable_name | Value |
±--------------------±------+
| interactive_timeout | 500 |
±--------------------±------+

How to return proxySQL2 the same behavior of proxySQL1 that took into account the wait_timeout parameter on the backend?

In ProxySQL, change mysql-wait_timeout to match that of wait_timout.