Skip to main content
U
Ujwal171-Visitor
1-Visitor
March 16, 2020
Solved

live data in timeseries chart

  • March 16, 2020
  • 8 replies
  • 3343 views

I have three properties in my Thing and it is continuously updating for every second. I want to show these updated values in Time series chart every second. which service should I use? I used query property history but it takes lot of time to get the result since the data is updating every second.

Best answer by Constantine

Hello @Ujwal17,

 

Just in case you're still looking for ideas -- try to cache N of your recent updates in an INFOTABLE property (not persistent and not logged), and use GetProperties service in your mashup instead of QueryPropertyHistory. Set "Automatically update" property on this service, so that it uses WebSockets to push data into the mashup instead of using Auto Refresh widget.

 

This way you should be able to display updates to a few dozen readings in your mashup every second without much performance overhead on the server side.

 

/ Constantine

8 replies

raluca_edu
raluca_edu17-Peridot
17-Peridot
March 16, 2020

Hi,

 

The only idea I have in this situation is to keep QueryPropertyHistory and in your mashup you can use Auto Refresh widget to execute the service every x sec. Don't know if this will work if you want to get data every 1 sec.

 

Hope it helps,

Raluca Edu

P
PaiChung22-Sapphire I
22-Sapphire I
March 16, 2020

the big question you need to look at is, does it make sense to get data every second yes or no?

Even if the data is updating once a second, to respond to that, you can automate that server side.

Is there a need to see the data updated every second on a screen, is that a requirement because a user is always looking at the screen and must react instantaneous.

Else you can still do as described, but I recommend slower updates on screen.

U
Ujwal171-VisitorAuthor
1-Visitor
March 17, 2020

Data in every second on mashup is what our client wants .

Can you help me to understand about how to automate server side?? 

S
slangleyCommunity Manager
Support
March 25, 2020

Hi @Ujwal17.

 

If you have found a solution to your issue, please post it here for the benefit of others on the community.  If you are still searching for a solution, please provide answers to the questions from the previous post.

 

Regards.

 

--Sharon

S
slangleyCommunity Manager
Support
April 3, 2020

Hi @Ujwal17.

 

If the previous response allowed you to find a solution, please mark it as the Accepted Solution for the benefit of others on the community.

 

Regards.

 

--Sharon

C
Constantine18-OpalAnswer
18-Opal
March 29, 2020

Hello @Ujwal17,

 

Just in case you're still looking for ideas -- try to cache N of your recent updates in an INFOTABLE property (not persistent and not logged), and use GetProperties service in your mashup instead of QueryPropertyHistory. Set "Automatically update" property on this service, so that it uses WebSockets to push data into the mashup instead of using Auto Refresh widget.

 

This way you should be able to display updates to a few dozen readings in your mashup every second without much performance overhead on the server side.

 

/ Constantine

Terms & ConditionsAccessibility statement