Skip to main content
H
HN_AAU1-Visitor
1-Visitor
December 19, 2019
Solved

Thing shape subscription cannot change property values

  • December 19, 2019
  • 2 replies
  • 1825 views

Hi Forum
I have a weird problem in thingworks. I have a thing shape with a data change subscription. The script needs to update a property value and as usual i write "me.<property> = <something>" but for some reason the property does not get updated. If i copy paste the code into a service and execute the service it works just fine. I have a logger message in my script and can see that the subscription is triggered but the data is not updated.

Even more strange, when i make the subscription trigger the service (that i know work) i can see that the service has run, but again no update to the property.... whaaat.... if i then right after trigger the service manually the property updates.

 

I have no clue why this happens. It used to work on 8.4.x since then i have updated to 8.5.0 and now i have this mess. 

 

Hope someone can help me.

Best answer by Radu

Hi,

 

Does the thing that you're testing these properties on implement the thing shape mentioned? Is the subscription enabled? From what you're saying, the code is not the problem, but the subscription. Try inserting a logger message inside the subscription, and see if it appears if you manually change the variable data.

2 replies

R
Radu15-MoonstoneAnswer
15-Moonstone
December 19, 2019

Hi,

 

Does the thing that you're testing these properties on implement the thing shape mentioned? Is the subscription enabled? From what you're saying, the code is not the problem, but the subscription. Try inserting a logger message inside the subscription, and see if it appears if you manually change the variable data.

H
HN_AAU1-VisitorAuthor
1-Visitor
December 20, 2019

Hi

Okay this is strange... it was the simple mistake that the subscription wasn't enabled (they really should be enabled by default) so just enabling it, it all works as it should. Thanks for the help.

 

But one thing i really don't understand is why my logger messages in the subscription still appeared in the script log!? This means that the code is actually still executed while disabled, it just doesn't have any privileges?!

It is even more strange that the logger messages appeared when the code was executed indirectly from a service called by the subscription. This fact makes this kind of stuff near impossible to debug and should really be changed/updated by the developers. spent around 2 hours trying to figure out why the code ran but not doing anything. 

 

Thanks for the help tho. I completely forgot about the enable flag. 

Terms & ConditionsAccessibility statement