5 Replies Latest reply on Feb 7, 2017 4:34 AM by mnudel RSS
    mnudel Explorer

    What is the use of "Push threshold" parameter of a remote property? (Edge Micro-Server)

    The aim is to introduce a dead-band on a number of properties in order to eliminate noise. However, having experimented with the remote property options I've concluded that using "Push threshold" parameter is not a feasible solution for my application.

     

    Take an integer property for instance. Set a push threshold of 2. Allow the property to increase, where each increase is lower than a push threshold. What you will notice in the Composer is that the integer property won't change at all, although the actual value had increased considerably.

     

    For example, after each scan the property on the Edge changes as follows: 1, 3, 5, 6, 8, 10, 12, 13, 15 ... 100.

    The platform would store only the initial value, 1. If after that 100 changes to 103, only then the property on the platform end will get updated to 103. As you can see - a lot of lost data points.

     

    I was hoping that the push would be based on a current Edge value and a value which is stored on the platform. Referring to example above - 1, 5, 8, 12, 15, etc.

    However this is not the case.

     

    Push threshold is simply the difference between current and previous values in . As you can see the latter can lead to inaccurate data being stored in the database.

     

    Hence the question, what's the point? Is there an alternative solution to my problem? Thanks!