i'm using mqtt thing with some data from mqtt server in thingworx. i made two alerts in mqtt thing one is for above 50 and one is for below 50. when sensor data come from mqtt server and it is either above 50 or below 50 this alerts does not trigger. but when disconnected from mqtt server and set the thing property by manually above 50 or below 50 it triggers alerts. strange but is happening with me. please help with this.
Solved! Go to Solution.
anyone is going to help me or not, Now days PTC site also not working , i wanted to start my online instance of thingworx but it was not working, also community giving answers to questions are very slow, i wonder if anyone really using thingworx or not..? i am not getting answers to my questions on community. its really bad experience for user of thingworx.
What is your ThingWorx platform version? The issue looks to be this https://www.ptc.com/en/support/article?n=CS275831 If that is the case, you may either grant visibility to the system user or upgrade to the fixed version.
I apologize for the delay in the response and thank you for your time and patience.
thank you for replying me.
i saw the the link you gave. in that article it says "Add Visibility for the System User on ThingworxPersistenceProvider.
i added visibility for whole group and organization for ThingworxPersistenceProvider but still problem exists.
my Thingworx version is 8.2.1-b140.
Thanks posipova, it solved the problem.
can you explain me why it is so..? i didn't understand the visibility setting for persistence provider..? why we have to give visibility for persistence provider and some runtime permission for mqtt thing..?
Processing of messages when it arrives at the MQTTThing client is done as "System" user. There are certain operations during message processing that require the "ThingworxPersistenceProvider" to be visible to the "System" user. The fact that "ThingworxPersistenceProvider" does not have any visibility permissions set on it OOTB causes the issue being reported where DataChange events on properties that have alert definitions or bindings etc. set on them do not trigger those alerts or evaluate bindings.
in Article - CS275831 which you suggested me, says that this problem is been resolved in TW version 8.1 and above. still, this problem is there.