modpoll 1.1.0__tar.gz → 1.2.0__tar.gz

{modpoll-1.1.0 → modpoll-1.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: modpoll
-Version: 1.1.0
+Version: 1.2.0
 Summary: A New Command-line Tool for Modbus and MQTT
 Home-page: https://github.com/gavinying/modpoll
 Author: Ying Shaodong
@@ -12,12 +12,12 @@ Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Provides-Extra: serial
-Requires-Dist: importlib-metadata (>=8.0.0,<9.0.0)
+Requires-Dist: importlib-metadata (>=8.3.0,<9.0.0)
 Requires-Dist: paho-mqtt (>=2.1.0,<3.0.0)
-Requires-Dist: prettytable (>=3.6.0,<4.0.0)
-Requires-Dist: pymodbus (>=3.5.4,<3.6.0)
+Requires-Dist: prettytable (>=3.9.0,<4.0.0)
+Requires-Dist: pymodbus (>=3.6.9,<3.7.0)
 Requires-Dist: pyserial (>=3.5,<4.0) ; extra == "serial"
-Requires-Dist: requests (>=2.28.1,<3.0.0)
+Requires-Dist: requests (>=2.32.0,<3.0.0)
 Project-URL: Documentation, https://gavinying.github.io/modpoll
 Project-URL: Repository, https://github.com/gavinying/modpoll
 Description-Content-Type: text/markdown
@@ -29,27 +29,27 @@ Description-Content-Type: text/markdown
 [![License](https://img.shields.io/github/license/gavinying/modpoll)](https://img.shields.io/github/license/gavinying/modpoll)
 [![Downloads](https://static.pepy.tech/badge/modpoll/week)](https://pepy.tech/project/modpoll)
 
+Show your love for this project by starring our repo 🌟, so we are encouraged to continue improving.
+
 > Learn more about *modpoll* usage at [documentation](https://gavinying.github.io/modpoll) site.
 
 ## Motivation
 
-The initial idea of creating this tool is to help myself debugging new devices during site survey. A site survey usually has limited time and space, working on-site also piles up some pressures. At that time, a portable swiss-knife toolkit is our best friend.
+The idea for creating this tool originated from my need to efficiently check new devices during site surveys. These surveys are often time-constrained and space-limited, with on-site work adding to the pressure. In such situations, a portable Swiss Army knife toolkit becomes a valuable companion.
 
-This program can be easily deployed to Raspberry Pi or similar embedded devices, polling data from modbus devices, users can choose to log data locally or publish to a MQTT broker for further debugging.
+This tool can be easily deployed on a Raspberry Pi or similar embedded devices, polling data from a Modbus network or connected devices. Users can choose to log the data locally or publish it to an MQTT broker for further troubleshooting.
 
-The MQTT broker can be setup on the same Raspberry Pi or on the cloud. Once data successfully published, users can subscribe to a specific MQTT topic to view the data via a smartphone at your fingertip.
+The MQTT broker can be set up either on the same Raspberry Pi or in the cloud. Once data is successfully published, users can subscribe to the relevant MQTT topics and conveniently view the data on their smartphones.
 
 <p align="center">
   <img src="docs/assets/modpoll-usage.png">
 </p>
 
-Moreover, you can also run this program continuously on a server as a Modbus-MQTT gateway, i.e. polling from local Modbus devices and forwarding data to a centralized cloud service.
+Moreover, you can also run this tool continuously on a server as a Modbus-MQTT gateway, i.e. polling from local Modbus devices and forwarding data to a centralized cloud service.
 
 In fact, *modpoll* helps to bridge between the traditional field-bus world and the new IoT world.
 
-> This program is designed to be a standalone tool, it works out-of-the-box on Linux/macOS/Windows.
-
-> If you are looing for a modbus python library, please consider the following great open source projects, [pymodbus](https://github.com/riptideio/pymodbus) or [minimalmodbus](https://github.com/pyhys/minimalmodbus)
+> 💡 **Tips:** This tool is designed to be a standalone executable application, which works out-of-the-box on Linux/macOS/Windows. If you are looking for a Modbus python library, please consider the following great open-source projects, [pymodbus](https://github.com/riptideio/pymodbus) or [minimalmodbus](https://github.com/pyhys/minimalmodbus)
 
 
 ## Feature
@@ -63,7 +63,7 @@ In fact, *modpoll* helps to bridge between the traditional field-bus world and t
 
 ## Installation
 
-This program tested on Python 3.8+, the package is available in the [Python Package Index](https://pypi.org/), users can easily install it using `pip` or `pipx`.
+This tool tested on Python 3.8+, the package is available in the [Python Package Index](https://pypi.org/), users can easily install it using `pip` or `pipx`.
 
 ### Using PIP
 
@@ -108,7 +108,7 @@ pipx upgrade modpoll
 Let's start exploring *modpoll* with *modsim* device, run the following command to get a first glimpse,
 
 ```bash
-modpoll \
+modpoll --once \
   --tcp modsim.topmaker.net \
   --config https://raw.githubusercontent.com/gavinying/modpoll/master/examples/modsim.csv
 ```
@@ -211,7 +211,7 @@ modpoll \
 
 ### Publish data to MQTT broker
 
-This is a useful function of this new *modpoll* tool, which provides a simple way to publish collected modbus data to MQTT broker, so users can view data from a smart phone via a MQTT client.
+This is a useful function of this new *modpoll* tool, which provides a simple way to publish collected Modbus data to MQTT broker, so users can view data from a smart phone via a MQTT client.
 
 The following example uses a public MQTT broker `mqtt.eclipseprojects.io` for test purpose. You can also set up your own MQTT broker locally using [mosquitto](https://mosquitto.org/download/).
 
@@ -224,7 +224,9 @@ modpoll \
 
 With successful data polling and publishing, you can subscribe the topic `modpoll/modsim` on the same MQTT broker `mqtt.eclipseprojects.io` to view the collected data.
 
-> The MQTT topic uses `<mqtt_topic_prefix>/<deviceid>` pattern, <mqtt_topic_prefix> is provided by `--mqtt-topic-prefix` argument, the default value is `modpoll/`  and <deviceid> is provided by the Modbus configure file.
+The MQTT topic uses `<mqtt_topic_prefix>/<device_name>` pattern, <mqtt_topic_prefix> is provided by `--mqtt-topic-prefix` argument, the default value is `modpoll`  and <device_name> is provided by the Modbus configure file.
+
+> ⚠️ **Note:** The `--mqtt-topic-prefix` argument is deprecated and will be removed in the future release. Use `--mqtt-publish-topic-pattern` and `--mqtt-subscribe-topic-pattern` instead. If both are used, `--mqtt-topic-prefix` argument will take precedence in order to keep backward compatibility. See [document](https://gavinying.github.io/modpoll/usage.html#Named%20Arguments) for details.
 
 
 <p align="center">
@@ -234,7 +236,7 @@ With successful data polling and publishing, you can subscribe the topic `modpol
 
 ### Write registers via MQTT publish
 
-The *modpoll* tool will subscribe to the topic `<mqtt_topic_prefix>/<deviceid>/set` once it successfully connected to MQTT broker, user can write device register(s) via MQTT publish,
+The *modpoll* tool will subscribe to the topic `modpoll/<device_name>/set` by default once it successfully connected to MQTT broker, user can write device register(s) via MQTT publish,
 
 - To write a single holding register (address at `40001`)
 
@@ -259,13 +261,13 @@ The *modpoll* tool will subscribe to the topic `<mqtt_topic_prefix>/<deviceid>/s
 
 ## Run with docker
 
-A docker image has been provided for user to directly run the program without local installation,
+A docker image has been provided for user to directly run the tool without local installation,
 
   ```bash
   docker run --rm helloysd/modpoll
   ```
 
-It shows the version of the program by default.
+It shows the version of the tool by default.
 
 Similar to the above *modsim* test, we can poll data with `docker run`, in order to avoid printing out received data, the argument `--daemon` or `-d` is recommended to use with docker.
 

{modpoll-1.1.0 → modpoll-1.2.0}/README.md

@@ -5,27 +5,27 @@
 [![License](https://img.shields.io/github/license/gavinying/modpoll)](https://img.shields.io/github/license/gavinying/modpoll)
 [![Downloads](https://static.pepy.tech/badge/modpoll/week)](https://pepy.tech/project/modpoll)
 
+Show your love for this project by starring our repo 🌟, so we are encouraged to continue improving.
+
 > Learn more about *modpoll* usage at [documentation](https://gavinying.github.io/modpoll) site.
 
 ## Motivation
 
-The initial idea of creating this tool is to help myself debugging new devices during site survey. A site survey usually has limited time and space, working on-site also piles up some pressures. At that time, a portable swiss-knife toolkit is our best friend.
+The idea for creating this tool originated from my need to efficiently check new devices during site surveys. These surveys are often time-constrained and space-limited, with on-site work adding to the pressure. In such situations, a portable Swiss Army knife toolkit becomes a valuable companion.
 
-This program can be easily deployed to Raspberry Pi or similar embedded devices, polling data from modbus devices, users can choose to log data locally or publish to a MQTT broker for further debugging.
+This tool can be easily deployed on a Raspberry Pi or similar embedded devices, polling data from a Modbus network or connected devices. Users can choose to log the data locally or publish it to an MQTT broker for further troubleshooting.
 
-The MQTT broker can be setup on the same Raspberry Pi or on the cloud. Once data successfully published, users can subscribe to a specific MQTT topic to view the data via a smartphone at your fingertip.
+The MQTT broker can be set up either on the same Raspberry Pi or in the cloud. Once data is successfully published, users can subscribe to the relevant MQTT topics and conveniently view the data on their smartphones.
 
 <p align="center">
   <img src="docs/assets/modpoll-usage.png">
 </p>
 
-Moreover, you can also run this program continuously on a server as a Modbus-MQTT gateway, i.e. polling from local Modbus devices and forwarding data to a centralized cloud service.
+Moreover, you can also run this tool continuously on a server as a Modbus-MQTT gateway, i.e. polling from local Modbus devices and forwarding data to a centralized cloud service.
 
 In fact, *modpoll* helps to bridge between the traditional field-bus world and the new IoT world.
 
-> This program is designed to be a standalone tool, it works out-of-the-box on Linux/macOS/Windows.
-
-> If you are looing for a modbus python library, please consider the following great open source projects, [pymodbus](https://github.com/riptideio/pymodbus) or [minimalmodbus](https://github.com/pyhys/minimalmodbus)
+> 💡 **Tips:** This tool is designed to be a standalone executable application, which works out-of-the-box on Linux/macOS/Windows. If you are looking for a Modbus python library, please consider the following great open-source projects, [pymodbus](https://github.com/riptideio/pymodbus) or [minimalmodbus](https://github.com/pyhys/minimalmodbus)
 
 
 ## Feature
@@ -39,7 +39,7 @@ In fact, *modpoll* helps to bridge between the traditional field-bus world and t
 
 ## Installation
 
-This program tested on Python 3.8+, the package is available in the [Python Package Index](https://pypi.org/), users can easily install it using `pip` or `pipx`.
+This tool tested on Python 3.8+, the package is available in the [Python Package Index](https://pypi.org/), users can easily install it using `pip` or `pipx`.
 
 ### Using PIP
 
@@ -84,7 +84,7 @@ pipx upgrade modpoll
 Let's start exploring *modpoll* with *modsim* device, run the following command to get a first glimpse,
 
 ```bash
-modpoll \
+modpoll --once \
   --tcp modsim.topmaker.net \
   --config https://raw.githubusercontent.com/gavinying/modpoll/master/examples/modsim.csv
 ```
@@ -187,7 +187,7 @@ modpoll \
 
 ### Publish data to MQTT broker
 
-This is a useful function of this new *modpoll* tool, which provides a simple way to publish collected modbus data to MQTT broker, so users can view data from a smart phone via a MQTT client.
+This is a useful function of this new *modpoll* tool, which provides a simple way to publish collected Modbus data to MQTT broker, so users can view data from a smart phone via a MQTT client.
 
 The following example uses a public MQTT broker `mqtt.eclipseprojects.io` for test purpose. You can also set up your own MQTT broker locally using [mosquitto](https://mosquitto.org/download/).
 
@@ -200,7 +200,9 @@ modpoll \
 
 With successful data polling and publishing, you can subscribe the topic `modpoll/modsim` on the same MQTT broker `mqtt.eclipseprojects.io` to view the collected data.
 
-> The MQTT topic uses `<mqtt_topic_prefix>/<deviceid>` pattern, <mqtt_topic_prefix> is provided by `--mqtt-topic-prefix` argument, the default value is `modpoll/`  and <deviceid> is provided by the Modbus configure file.
+The MQTT topic uses `<mqtt_topic_prefix>/<device_name>` pattern, <mqtt_topic_prefix> is provided by `--mqtt-topic-prefix` argument, the default value is `modpoll`  and <device_name> is provided by the Modbus configure file.
+
+> ⚠️ **Note:** The `--mqtt-topic-prefix` argument is deprecated and will be removed in the future release. Use `--mqtt-publish-topic-pattern` and `--mqtt-subscribe-topic-pattern` instead. If both are used, `--mqtt-topic-prefix` argument will take precedence in order to keep backward compatibility. See [document](https://gavinying.github.io/modpoll/usage.html#Named%20Arguments) for details.
 
 
 <p align="center">
@@ -210,7 +212,7 @@ With successful data polling and publishing, you can subscribe the topic `modpol
 
 ### Write registers via MQTT publish
 
-The *modpoll* tool will subscribe to the topic `<mqtt_topic_prefix>/<deviceid>/set` once it successfully connected to MQTT broker, user can write device register(s) via MQTT publish,
+The *modpoll* tool will subscribe to the topic `modpoll/<device_name>/set` by default once it successfully connected to MQTT broker, user can write device register(s) via MQTT publish,
 
 - To write a single holding register (address at `40001`)
 
@@ -235,13 +237,13 @@ The *modpoll* tool will subscribe to the topic `<mqtt_topic_prefix>/<deviceid>/s
 
 ## Run with docker
 
-A docker image has been provided for user to directly run the program without local installation,
+A docker image has been provided for user to directly run the tool without local installation,
 
   ```bash
   docker run --rm helloysd/modpoll
   ```
 
-It shows the version of the program by default.
+It shows the version of the tool by default.
 
 Similar to the above *modsim* test, we can poll data with `docker run`, in order to avoid printing out received data, the argument `--daemon` or `-d` is recommended to use with docker.
 

{modpoll-1.1.0 → modpoll-1.2.0}/modpoll/arg_parser.py

@@ -102,8 +102,23 @@ def get_parser():
     )
     parser.add_argument(
         "--mqtt-topic-prefix",
-        default="modpoll/",
-        help='Topic prefix for MQTT subscribing/publishing. Defaults to "modpoll/"',
+        default=None,
+        help="(DEPRECATED) Topic prefix for MQTT subscribing/publishing. Defaults to None",
+    )
+    parser.add_argument(
+        "--mqtt-publish-topic-pattern",
+        default="modpoll/<device_name>",
+        help='Topic pattern for MQTT publish. Use <device_name> as placeholder for the device names in Modbus config. Defaults to "modpoll/<device_name>"',
+    )
+    parser.add_argument(
+        "--mqtt-subscribe-topic-pattern",
+        default="modpoll/<device_name>/set",
+        help='Topic pattern for MQTT subscribe. Use <device_name> as placeholder for the device names in Modbus config. Defaults to "modpoll/<device_name>/set"',
+    )
+    parser.add_argument(
+        "--mqtt-diagnostics-topic-pattern",
+        default=None,
+        help="Topic pattern for MQTT diagnostics. Use <device_name> as placeholder for the device names in Modbus config. Defaults to None",
     )
     parser.add_argument(
         "--mqtt-qos",

{modpoll-1.1.0 → modpoll-1.2.0}/modpoll/main.py

@@ -10,6 +10,7 @@ from datetime import timezone
 from modpoll.arg_parser import get_parser
 from modpoll.modbus_task import (
     modbus_setup,
+    modbus_device_list,
     modbus_poll,
     modbus_publish,
     modbus_publish_diagnostics,
@@ -57,36 +58,59 @@ def app(name="modpoll"):
 
     # parse args
     args = get_parser().parse_args()
-    # sanity check
-    if args.mqtt_topic_prefix.endswith("/"):
-        args.mqtt_topic_prefix = args.mqtt_topic_prefix[:-1]
 
     # get logger
     setup_logging(args.loglevel, LOG_SIMPLE)
     global logger
     logger = logging.getLogger(__name__)
 
+    # setup modbus
+    if not modbus_setup(args, event_exit):
+        logger.error("Failed to setup modbus client(master)")
+        modbus_close()
+        mqttc_close()
+        exit(1)
+
+    # Overwrite topic pattern if topic prefix is specified for backward compatibility
+    if args.mqtt_topic_prefix:
+        logger.warning(
+            "(DEPRECATED): The `--mqtt-topic-prefix` argument is deprecated and will be removed in the future release. Use `--mqtt-publish-topic-pattern` and `--mqtt-subscribe-topic-pattern` instead. If both are used, `--mqtt-topic-prefix` argument will take precedence in order to keep backward compatibility."
+        )
+        if args.mqtt_topic_prefix.endswith("/"):
+            args.mqtt_topic_prefix = args.mqtt_topic_prefix[:-1]
+        args.mqtt_publish_topic_pattern = f"{args.mqtt_topic_prefix}/<device_name>"
+        args.mqtt_subscribe_topic_pattern = (
+            f"{args.mqtt_topic_prefix}/<device_name>/set"
+        )
+
+    # create mqtt subscribe topics
+    subscribe_topics = []
+    if args.mqtt_subscribe_topic_pattern:
+        if "<device_name>" in args.mqtt_subscribe_topic_pattern:
+            for device in modbus_device_list():
+                topic = args.mqtt_subscribe_topic_pattern.replace(
+                    "<device_name>", device.name
+                )
+                subscribe_topics.append(topic)
+        else:
+            subscribe_topics.append(args.mqtt_subscribe_topic_pattern)
+
     # setup mqtt
     if args.mqtt_host:
         logger.info(f"Setup MQTT connection to {args.mqtt_host}")
-        if not mqttc_setup(args):
+        if not mqttc_setup(args, subscribe_topics):
             logger.error("Failed to setup MQTT client")
+            modbus_close()
             mqttc_close()
             exit(1)
         if not mqttc_connect():
             logger.error("Failed to connect to MQTT host")
+            modbus_close()
             mqttc_close()
             exit(1)
     else:
         logger.info("No MQTT host specified, skip MQTT setup.")
 
-    # setup modbus
-    if not modbus_setup(args, event_exit):
-        logger.error("Failed to setup modbus client(master)")
-        modbus_close()
-        mqttc_close()
-        exit(1)
-
     # main loop
     last_check = 0
     last_diag = 0
@@ -123,19 +147,39 @@ def app(name="modpoll"):
         # Check if receive mqtt request
         topic, payload = mqttc_receive()
         if topic and payload:
-            device_name = re.search(
-                f"^{args.mqtt_topic_prefix}([^/\n]*)/set", topic
-            ).group(1)
+            topic_regex = args.mqtt_subscribe_topic_pattern.replace(
+                "<device_name>", "([^/\n]*)"
+            )
+            device_name = re.search(topic_regex, topic).group(1)
             if device_name:
+                logger.info(f"Received request to write data for device {device_name}")
                 try:
                     reg = json.loads(payload)
-                    if "coil" == reg["object_type"]:
-                        if modbus_write_coil(device_name, reg["address"], reg["value"]):
-                            logger.info("")
-                    elif "holding_register" == reg["object_type"]:
-                        modbus_write_register(device_name, reg["address"], reg["value"])
+                    object_type = reg["object_type"]
+                    address = reg["address"]
+                    value = reg["value"]
+                    if "coil" == object_type:
+                        if modbus_write_coil(device_name, address, value):
+                            logger.info(
+                                f"Successfully write coil(s): device={device_name}, address={address}, value={value}"
+                            )
+                        else:
+                            logger.warning(
+                                f"Failed to write coil(s): device={device_name}, address={address}, value={value}"
+                            )
+                    elif "holding_register" == object_type:
+                        if modbus_write_register(device_name, address, value):
+                            logger.info(
+                                f"Successfully write register(s): device={device_name}, address={address}, value={value}"
+                            )
+                        else:
+                            logger.warning(
+                                f"Failed to write register(s): device={device_name}, address={address}, value={value}"
+                            )
+                except KeyError:
+                    logger.error(f"No required key found: {payload}")
                 except json.decoder.JSONDecodeError:
-                    logger.warning(f"Failed to parse json message: {payload}")
+                    logger.error(f"Failed to parse json message: {payload}")
         if args.once:
             event_exit.set()
             break

{modpoll-1.1.0 → modpoll-1.2.0}/modpoll/modbus_task.py

@@ -410,6 +410,11 @@ def load_config(file) -> bool:
         return False
 
 
+def modbus_device_list() -> []:
+    global deviceList
+    return deviceList
+
+
 def modbus_setup(config, event) -> bool:
     global args
     args = config
@@ -494,7 +499,7 @@ def modbus_poll():
         modbus_print()
 
 
-def modbus_write_coil(device_name, address: int, value):
+def modbus_write_coil(device_name: str, address: int, value) -> bool:
     if not master:
         return False
     master.connect()
@@ -502,7 +507,7 @@ def modbus_write_coil(device_name, address: int, value):
     logger.debug(f"Master connected. Delay of {args.delay} seconds.")
     for d in deviceList:
         if d.name == device_name:
-            logger.info(
+            logger.debug(
                 f"Writing coil(s): device={device_name}, address={address}, value={value}"
             )
             if isinstance(value, int):
@@ -514,7 +519,7 @@ def modbus_write_coil(device_name, address: int, value):
     return False
 
 
-def modbus_write_register(device_name, address: int, value):
+def modbus_write_register(device_name, address: int, value) -> bool:
     if not master:
         return False
     master.connect()
@@ -522,7 +527,7 @@ def modbus_write_register(device_name, address: int, value):
     logger.debug(f"Master connected. Delay of {args.delay} seconds.")
     for d in deviceList:
         if d.name == device_name:
-            logger.info(
+            logger.debug(
                 f"Writing register(s): device={device_name}, address={address}, value={value}"
             )
             if isinstance(value, int):
@@ -567,27 +572,30 @@ def modbus_publish(timestamp=None, on_change=False):
             else:
                 payload[f"{ref.name}"] = ref.val
             if args.mqtt_single:
-                topic = f"{args.mqtt_topic_prefix}/{dev.name}/{ref.name}"
+                topic = f"{args.mqtt_publish_topic_pattern.replace('<device_name>', dev.name)}/{ref.name}"
                 if isinstance(ref.val, list):
                     for i, ref_val_entry in enumerate(ref.val):
                         mqttc_publish(
-                            topic + "/" + str(i), ref_val_entry, qos=args.mqtt_qos
+                            f"{topic}/{str(i)}", ref_val_entry, qos=args.mqtt_qos
                         )
                 else:
                     mqttc_publish(topic, ref.val, qos=args.mqtt_qos)
         if timestamp:
             payload["timestamp_ms"] = int(timestamp * 1000)
         if not args.mqtt_single:
-            topic = f"{args.mqtt_topic_prefix}/{dev.name}"
+            topic = args.mqtt_publish_topic_pattern.replace("<device_name>", dev.name)
             mqttc_publish(topic, json.dumps(payload), qos=args.mqtt_qos)
 
 
 def modbus_publish_diagnostics():
-    for dev in deviceList:
-        logger.debug(f"Publishing diagnostics for device {dev.name} ...")
-        payload = {"pollCount": dev.pollCount, "errorCount": dev.errorCount}
-        topic = f"{args.mqtt_topic_prefix}/diagnostics/{dev.name}"
-        mqttc_publish(topic, json.dumps(payload), qos=args.mqtt_qos)
+    if args.mqtt_diagnostics_topic_pattern:
+        for dev in deviceList:
+            logger.debug(f"Publishing diagnostics for device {dev.name} ...")
+            payload = {"pollCount": dev.pollCount, "errorCount": dev.errorCount}
+            topic = args.mqtt_diagnostics_topic_pattern.replace(
+                "<device_name>", dev.name
+            )
+            mqttc_publish(topic, json.dumps(payload), qos=args.mqtt_qos)
 
 
 def modbus_export(file, timestamp=None):

{modpoll-1.1.0 → modpoll-1.2.0}/modpoll/mqtt_task.py

@@ -42,9 +42,9 @@ def _on_connect(client, userdata, flags, reason_code, properties):
             logger.info("New session created")
             # Subscribing in on_connect() means that if we lose the connection and
             # reconnect then subscriptions will be renewed.
-            if "subscribe_topic" in userdata:
-                topic = userdata.get("subscribe_topic")
-                qos = userdata.get("subscribe_qos", 0)  # Default to QoS 0
+            topics = userdata.get("subscribe_topics", [])
+            qos = userdata.get("subscribe_qos", 0)  # Default to QoS 0
+            for topic in topics:
                 logger.info(f"Subscribe to topic: {topic} with QoS: {qos}")
                 client.subscribe(topic, qos)
     else:
@@ -87,7 +87,7 @@ def _on_log(client, userdata, level, buf):
     logger.debug(f"{level} | {buf}")
 
 
-def mqttc_setup(config: Any) -> bool:
+def mqttc_setup(config: Any, subscribe_topics: []) -> bool:
     global args, logger, mqttc, clean_start_or_session
     args = config
     logger = logging.getLogger(__name__)
@@ -99,11 +99,16 @@ def mqttc_setup(config: Any) -> bool:
 
         clean_start_or_session = args.mqtt_qos == 0
 
+        sub_topic = args.mqtt_subscribe_topic_pattern
+
         if args.mqtt_version == "5.0":
             mqttc = MQTTClient(
                 CallbackAPIVersion.VERSION2,
                 client_id=clientid,
-                userdata={"qos": args.mqtt_qos},
+                userdata={
+                    "subscribe_topics": subscribe_topics,
+                    "subscribe_qos": args.mqtt_qos,
+                },
                 protocol=MQTTProtocolVersion.MQTTv5,
             )
         else:
@@ -111,7 +116,10 @@ def mqttc_setup(config: Any) -> bool:
                 CallbackAPIVersion.VERSION2,
                 client_id=clientid,
                 clean_session=clean_start_or_session,
-                userdata={"qos": args.mqtt_qos},
+                userdata={
+                    "subscribe_topics": subscribe_topics,
+                    "subscribe_qos": args.mqtt_qos,
+                },
                 protocol=MQTTProtocolVersion.MQTTv311,
             )
 

{modpoll-1.1.0 → modpoll-1.2.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "modpoll"
-version = "v1.1.0"
+version = "v1.2.0"
 description = "A New Command-line Tool for Modbus and MQTT"
 authors = ["Ying Shaodong <helloysd@gmail.com>"]
 repository = "https://github.com/gavinying/modpoll"
@@ -12,11 +12,11 @@ packages = [
 
 [tool.poetry.dependencies]
 python = ">=3.8.2,<4.0"
-importlib-metadata = "^8.0.0"
-pymodbus = "~3.5.4"
+importlib-metadata = "^8.3.0"
+pymodbus = "~3.6.9"
 paho-mqtt = "^2.1.0"
-prettytable = "^3.6.0"
-requests = "^2.28.1"
+prettytable = "^3.9.0"
+requests = "^2.32.0"
 pyserial = { version = "^3.5", optional = true }
 
 [tool.poetry.extras]