The indi protocol does allow blobs to be enabled/disabled, - normally on the indiserver port, giving the option of using an out of band solution. I've implemented this by sending the appropriate enable/disable command from the client via MQTT, and applying it at the remote end. So if disabled (the default) blobs will not be published to MQTT.
Tried ok with blobs generated by simulated telescope/ccd, but not specifically tested large blobs for size. It's on my list to create test drivers to exercise the package, so I'll bear that in mind, thanks. I did find when reading an input stream in Python I got asyncio.LimitOverrunError exceptions so I read data in chunks of 32K at a time, but that had nothing to do with mqtt.
Hi, just completed a Python project sending INDI protocol over MQTT, and storing data to redis, see
, together with a web client that displays the redis stored data allowing control of the attached instruments. The web client is documented at
So far only tested with simulated drivers, I'd be interested in any feedback from anyone who cares to try them out.