Anyone experiencing the "not accurate" issue:
We experienced the same and found the cause.
We were both doing active scans with scanning credentials,
and were using the lspush in the logon script.
When lspush was run using the logon script, all TPM information disappeared in lansweeper.
When a sceduled en manual scan was run using the scanning credentials, TPM info reappeared.
This might be related:
https://www.lansweeper.com/knowledgebase/event-id-5605-generated-during-scanning/
Our solution/workaround was to drop the lspush from logon script,
and move to lspush using a sceduled task to trigger at logon, but using admin credentials.