Open open-stemware opened 3 weeks ago
This issue is bigger than the initial problem. There are five MQTT files that have their own client creation code that needs to be fixed and points to a design io issue. Can a single MQTT base class be created? Some of the variations are required because of different status reporting environments. The five files are
basecamp.py: Operator->Configure Command Destination cfsinterface/targetcontrol.py: Basecamp's remote ops (fixed in issue #76) remoteops/remoteops.py: Python process that runs on the remote target and communicates with targetcontrol.py remoteops/remoteprocess.py: Example Ada Fruit sensor interface remoteops/demo-targets/helloworld.py: Generates MQTT messages to drive SpaceStep's cubesat GUI demo
Issue #41 should also be fixed.
MQTT v5 changed the client API and the Operator->Configure Command Destination needs to be updated to comply with the new API. Issue #76 was written against the remote ops MQTT code and fixed in v1.16.