Try updating from v2.1.8 to any future beta (if available) and then roll back to v2.1.8.
If you would like to document the solution for future reference or need help interpreting a specific changelog, please provide more details on what the firmware issue was. ts1022 firmware fixed