noname
noname
401 error seems to be authorization issue. Its working fine for me. 
Can you check header - from this point to see if it has access token  link in my case: 
always use WebSocket's to get Realtime data as most brokers will have restrictions on number of pings you can make.
@Anirudh-1213 i think Zerodha is forcing to use TOTP from Sep 23rd so you need to use TOTP code as mentioned in defect 45. (https://github.com/jugaad-py/jugaad-trader/issues/45) https://support.zerodha.com/category/your-zerodha-account/login-credentials/login-credentials-of-trading-platforms/articles/enable-device-lock
were you able to resolve the issue?
@avlsi it's because console class expects 'x-csrftoken' in header. so add below 2 lines in Console class 
looks like login session didn't execute correctly.
Hello @vijay-arwapally , I think you need to apply 2 changes. 1.  replace with import urllib.parse  2. In the python package of zerodha - KiteTicket class / file...
Its working for me.. I just updated Kite to latest version without any modification to enc_token. def on_ticks(ws, ticks): # Callback to receive ticks. print(ticks) #print(kws.is_connected()) logging.debug("Ticks: {}".format(ticks)) def on_connect(ws,...
@ashishanand7 if this has not resolved, then try these steps - https://github.com/jugaad-py/jugaad-trader/issues/44#issuecomment-1200493371 > this issue persists. i tried to fix but going nowhere.