@CamDavidsonPilon, thanks for your quick reply!
Can I ask why you’d rather use a remote MQTT broker? Just curious about use cases and features we might be missing
I want to be able to access the Pioreactor from devices that aren’t on the same network as the Pioreactor (i.e., cloud access). From what I understand, this isn’t possible in the existing setup. The desire to use HiveMQ as the broker is that I can do so securely, even though it’s remotely accessible outside of the network. Another piece is that I will primarily be interacting with the Pioreactor programatically, rather than through the web interface. It seemed like if I could swap out the broker with my own cloud-hosted one, that it would make it easy to integrate with my existing workflows.
The closest conversation (sorry, meant to link this in the original post) seems to be Project cloud database - #4 by CamDavidsonPilon.
I also noticed Writing Pioreactor scripts with Python | Pioreactor Docs.