python: migrate applications to use IoT3 Core SDK #149
Commits on Sep 20, 2024
-
python/iot3/core: fix MQTT over Unix socket
Although the unix socket transport does not require a TCP port, paho-mqtt expexts that a valid TCP port be specified when connecting. Technically, specifying a port is not necessary in that case, so we could in theory change our call to connect_async() to not pass a port at al. However, that would make the code a bit more complex. So, to simplify things, just use a valid TCP port, i.e. one that is strictly greater than 0. We could have decided to use the default port, 1883, but that would be a bit misleading. Instead, we just use 1, which is odd enough that it will at least raise an eyebrow to an unsuspecting reviewer. Signed-off-by: Yann E. MORIN <[email protected]>
-
python/iot3/core: fix unsubscribing to all MQTT topics
The unsubscribe() method expects keyword arguments, not positional ones. Signed-off-by: Yann E. MORIN <[email protected]>
-
python: relax dependency on paho.mqtt
The vareious ITS clients (its-vehicle, its-iqm...) currently use the APIs of paho.mqtt 1.6.1, while the newly-introduce IoT3 Core SDK uses those of 2.1.0. In paho.mqtt 2.0.x, there was a breaking API change, so a client written against paho.mqtt 1.6.1 (or earlier) could not be used as-is with paho.mqtt 2.0.x. but in paho.mqtt 2.1.0, there was another API change that made it possible to use clients written against 1.6.1, without any modification, while also alowing clients written againt the 2.0.0 API as well. So we can accept anything from 1.6.1 onward, except for versions 2.0.x. Signed-off-by: Yann E. MORIN <[email protected]>
-
python/status: use iot3.core.mqtt
Signed-off-by: Yann E. MORIN <[email protected]>
-
python/iqm: no one ever join()s the authority threads
Signed-off-by: Yann E. MORIN <[email protected]>
-
python/iqm: use iot3.core.mqtt for queue-manager
Signed-off-by: Yann E. MORIN <[email protected]>
-
python/iqm: use iot3.core.mqtt for MQTT authority client
Signed-off-by: Yann E. MORIN <[email protected]>
-
python/iqm: drop custom MQTT client
Signed-off-by: Yann E. MORIN <[email protected]>
-
Signed-off-by: Yann E. MORIN <[email protected]>
-
python/vehicle: drop tracking from ITS message
Signed-off-by: Yann E. MORIN <[email protected]>
-
python/vehicle: don't instanciate dummy custom tracker
Signed-off-by: Yann E. MORIN <[email protected]>
-
python/vehicle: drop custom, dummy tracker
Signed-off-by: Yann E. MORIN <[email protected]>
-
python/vehicle: don't use abbrev() which is going to disapear
Signed-off-by: Yann E. MORIN <[email protected]>
-
python/vehicle: only start() clients once all have been created
Signed-off-by: Yann E. MORIN <[email protected]>
-
python/vehicle: insert trampoline on message reception
Signed-off-by: Yann E. MORIN <[email protected]>
-
python/vehicle: use iot3.core.mqtt
Signed-off-by: Yann E. MORIN <[email protected]>
-
python/vehicle: drop our custom MQTT Client
Signed-off-by: Yann E. MORIN <[email protected]>
-
Signed-off-by: Yann E. MORIN <[email protected]>
