Skip to main content
S
Simon0077-Bedrock
7-Bedrock
April 18, 2023
Question

Remote properties updated with delay when bound to an existing property

  • April 18, 2023
  • 1 reply
  • 6742 views

Hello,

 

I have a thing where I have binded a remote property from the Kepserver by creating a new property.

Also, I have the same property binded to a property we have created on template level to trigger subscriptions with that.

 

Now I'm facing that I have a delay in updating the values of the property which is binded to the other property. The property which was new created on the thing does not have this delay.

So, I have 2 times the same property from Kepserver binded to a thing, but the values are not updated at the same time.

 

The properties in the screenshot in category "AutoBinding" are in sync with the Kepserver, the upper properties are having the delay.

 

I have already tried with different Cache Options and different settings on the push type, but unfortunately without any success.

Also we have tried for the property from template level as persistent and not persistent but did not make any difference.

 

Has anyone an idea how that could be fixed or by what this could be caused?

 

Thanks,

Simon

 

ThingProperties.png

 

 

 

 

 

 

 

1 reply

P
PaiChung22-Sapphire I
22-Sapphire I
April 18, 2023

I have noticed that if you try to use a remote binding multiple times, Thingworx can experience issues with that, You could try doing 1 remote binding and then bind the other property using a local binding from that bound property and see if it behaves more consistent.

S
Simon0077-BedrockAuthor
7-Bedrock
April 19, 2023

Thanks for your reply!

Makes sense, I thought the same already.

 

I tried it in that way now, to bind the property remotely and did the other binding locally.

Unfortunately I had no success with that.

 

What is also strange for me is that the delay we are facing is pretty much, up to several seconds.

S
Simon0077-BedrockAuthor
7-Bedrock
April 19, 2023

What I forgot to mention, we see this behavior also when we do not have the property bound 2 times, it also occurs when the remote property is only bound 1 time to the property from the template

Terms & ConditionsAccessibility statement