Skip to main content
H
H061013-Aquamarine
13-Aquamarine
March 3, 2026
Question

Property quality GOOD on disconnected device

  • March 3, 2026
  • 1 reply
  • 109 views

Hi all,
We're running Thingworx 10 as SaaS with Thingworx Kepware server 6.18 on-prem. I sometimes notice that devices that are disconnected in kepware (e.g. powered off), still have properties in Thingworx that show good quality. When I run GetPropertyDiagnostics on any of the properties, the results shows CurrentQuality as BAD.
It also seems like the behavior is not always the same, most often the disconnection will change the property quality & values as expected.
As Push Type we use 'Pushed based on deadband', when I change this to 'always', the property quality changes and values are set back to 0 (so the expected behavior) but with ten thousands of properties the impact on our environment will be too high.
Is there any other way to ensure that a disconnected machine is always seen in thingworx without using a workaround like a lifebit?

1 reply

A
abandal12-Amethyst
12-Amethyst
March 10, 2026

Hello @H0610,

 

Based on the information you provided, it seems like Kepware is correctly marking the tag quality as Bad when the device disconnects. The difference in behavior appears when deadband is enabled on the ThingWorx side. In this case, ThingWorx may filter out updates where the value remains unchanged, even though the quality has changed. This results in the quality not updating as expected on the ThingWorx platform.

 

To ensure the correct behavior on the ThingWorx side, you may want to review:

  • Whether ThingWorx deadband is configured to consider value changes only, which may cause quality-only updates to be skipped.
  • Property processing settings in your ThingWorx model (e.g., caching, filtering, subscription timing).
  • Any platform logic or services that may be overriding or delaying quality updates.
  • Are you seeing any errors/warnings in the logs?
Terms & ConditionsCookie settingsAccessibility statement