Python MQTT Client The Loop and Callbacks Explained

when we assign a callback function why we are not including the parameters when it is called?

Thank You for great material!

I have had trouble taking in parts of Steve's videos. Whilst this is largely due to my inadequacies I don't think it is helped by the editing of the audio that seems to have removed the natural speech breaks and therefore one doesn't have time to understand the point being made before moving on to the next issue. I know that one can stop and rewind but that also has its drawbacks. Overall very good but a bit slower and a few more examples would be great.

Thanks for the videos steve. How can I wait to do an action on a flask server after I publish a message to a raspberry pi? Currently, the raspberry pi responds to the server with a confirmation the pump was turned on once the action was taken. The flask app on the server imports a script i wrote to handle callbacks...so I can view the message received from the pi. I am just confused as to how I can return the callback value to the flask app. Normally I have been writing the values to a text file and accessing them via the flask app. But I just use arbitary time pauses to wait until the message from the pi is written into the text file... is there a better way to do this?

how to make a client not to disconnect from the broker and keep listening to broker

Which thread call the callback functions? Is it the same thread that runs loop() in the background (if using loop_start()), or is it the main thread?

Steve how to send data or message from one system to another system using mqtt protocol