You can check kite document: https://kite.trade/docs/pykiteconnect/v4/#kiteconnect.KiteTicker

You can refer to the pykiteconnect documentation here.

You can checkout docs to know more about enabling debug logs.

You can enable debug logs as mentioned here and share the complete stacktrace to investigate.

Can you enable debug logs as mentioned here?

exit_order is for placing the exit order for CO. You need to use place_order to exit the order for regular order. There you can use the tag param to specify the source.

You may refer to the pykiteconnect documentation here.

You need to set debug=True in the ticker initialization.

It could be connection pool issue. You can set a custom connection pool while initializing. You can check out the pykiteconnect docs here.

You don't need to use generate_session for every run. You can directly set access_token kite.set_access_token("your obtained access token"), post successfully generating access toke…

You may refer to the documentation here.

https://kite.trade/docs/pykiteconnect/v4/#kiteconnect.KiteTicker.__init__

pykiteconnect comes with reconnect support. You don't have to do anything, library itself takes care of reconnection and re-subscribes after reconnect. You can check out documentation to know how to …

https://kite.trade/docs/pykiteconnect/v4/#kiteconnect.KiteConnect.place_order

But https://kite.trade/docs/pykiteconnect/v4/#kiteconnect.KiteTicker states:

What are the use cases of on_message callback while using websocket?

You may refer to the documentation to know more about the initialization of kite connect object and usage of timeout parameter.

You don't have to do it. pykiteconnect does it for you. You just need to enable reconnect here.

Unable to fetch close of last candle instead of "last_price"

An access token is available from generate_session API not profile. Go through the examples here.