Getting Wrong NIFTY values sometimes when using sockets

APIs, Automation, Algos & Code
1

When we try to get value for 13 NIFTY from subscribed data, I am sometimes getting value around 7788 instead of a value around 25255 .
This could be a bug.
It would have been better if you used unique numbers instead of depending on marketfeed.NSE and marketfeed.IDX values.
In the list of instruments subscribed some are equity and some are indexes. But 13 is only in indexes. So it might be a bug.

2

might be related Websocket API not working since market close yesterday

3

My bug here. When I added instruments I added using sql. It has 13 in both equities and indexes.
I think it is possible for everyone to get confused if unique values are not used.

4

that’s correct. You are getting accurate data with [0, “13”] subscription?

1 Like
5

Hello @Garlapati_Srikanth

Understood your point. However, these Security IDs are provided by Exchange which is standard. There is a column to filter out exchange and instrument itself, so that correct Security ID can be fetched.