iobroker.modbus 6.4.0 → 7.0.0

package/LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2015-2024 Bluefox <dogafox@gmail.com>
+Copyright (c) 2015-2025 Bluefox <dogafox@gmail.com>
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/README.md

@@ -9,12 +9,23 @@
 [![Translation status](https://weblate.iobroker.net/widgets/adapters/-/modbus/svg-badge.svg)](https://weblate.iobroker.net/engage/adapters/?utm_source=widget)
 [![Downloads](https://img.shields.io/npm/dm/iobroker.modbus.svg)](https://www.npmjs.com/package/iobroker.modbus)
 
-**This adapter uses Sentry libraries to automatically report exceptions and code errors to the developers.** For more details and for information how to disable the error reporting see [Sentry-Plugin Documentation](https://github.com/ioBroker/plugin-sentry#plugin-sentry)! Sentry reporting is used starting with js-controller 3.0.
+**This adapter uses Sentry libraries to automatically report exceptions and code errors to the developers.** For more details and for information how to disable the error reporting, see [Sentry-Plugin Documentation](https://github.com/ioBroker/plugin-sentry#plugin-sentry)! Sentry reporting is used starting with js-controller 3.0.
 
 Implementation of ModBus Slave and Master for ioBroker. The following types are supported:
 - Modbus RTU over serial (master)
 - Modbus RTU over TCP (master)
 - Modbus TCP (slave, master)
+- Modbus TCP with SSL/TLS (master)
+
+## SSL/TLS Support
+For secure connections to devices that require SSL/TLS encryption (such as the Kostal KSEM Smart Energy Meter on port 802), you can select "TCP with SSL/TLS" as the connection type. This provides the following configuration options:
+
+- **SSL Certificate file path**: Path to your SSL certificate file in PEM format
+- **SSL Private key file path**: Path to your SSL private key file in PEM format  
+- **SSL CA Certificate file path**: Path to CA certificate file in PEM format (optional)
+- **Reject unauthorized certificates**: Uncheck to allow self-signed certificates
+
+Note: Certificate files must be accessible by the ioBroker process and in PEM format.
 
 ## Settings
 ### Partner IP Address
@@ -49,7 +60,7 @@ Like addresses from 3 to 20 will be aligned to 0 up 32.
 If this option is active, the addresses will not be aligned.
 
 ### Do not use multiple registers
-If slave does not support "write multiple registers" command, you can activate it to get warnings, when the multiple registers will be written.
+If slave does not support "write multiple registers" command, you can activate it to get warnings when the multiple registers will be written.
 
 ### Use only multiple write registers
 If slave only supports "write multiple registers" command, you can activate so the registers will be written always with FC15/FC16 command.
@@ -195,7 +206,7 @@ This variable can be then later used in any formula for other parameters. E.g.,
 
 The following description was copied from [here](http://www.chipkin.com/how-real-floating-point-and-32-bit-data-is-encoded-in-modbus-rtu-messages/)
 
-The point-to-point Modbus protocol is a popular choice for RTU communications if for no other reason that its basic convenience. The protocol itself controls the interactions of each device on a Modbus network, how device establishes a known address, how each device recognizes its messages and how basic information is extracted from the data. In essence, the protocol is the foundation of the entire Modbus network.
+The point-to-point Modbus protocol is a popular choice for RTU communications if for no other reason that its basic convenience. The protocol itself controls the interactions of each device on a Modbus network, how the device establishes a known address, how each device recognizes its messages and how basic information is extracted from the data. In essence, the protocol is the foundation of the entire Modbus network.
 
 Such a convenience does not come without any complications, however, and Modbus RTU Message protocol is no exception.
 The protocol itself was designed based on devices with a 16-bit register length.
@@ -292,13 +303,13 @@ One can then swap bytes and/or words to analyze what potential endianness issues
 ## Export / Import of registers
 With export / import functionality, you can convert all register data (only of one type) to a TSV (Tab separated values) file and back to easily copy data from one device to another or to edit register in Excel.
 
-You can share your schemas with other users in [modbus-templates](https://github.com/ioBroker/modbus-templates) or you can find some register schemas there.
+You can share your schemas with other users in [modbus-templates,](https://github.com/ioBroker/modbus-templates) or you can find some register schemas there.
 
 ## Test
 There are some programs in folder `test` to test the TCP communication:
 - Ananas32/64 is a slave simulator (only holding registers and inputs, no coils and digital inputs)
 - RMMS is master simulator
-- mod_RSsim.exe is a slave simulator. It can be that you need [Microsoft Visual C++ 2008 SP1 Redistributable Package](https://www.microsoft.com/en-us/download/details.aspx?id=5582) to start it (because of SideBySide error).
+- mod_RSsim.exe is a slave simulator. It can be that you need [Microsoft Visual C++ 2008 SP1 Redistributable Package](https://www.microsoft.com/en-us/download/details.aspx?id=5582) to start it (because of Side-By-Side error).
 
 ## Todo
 - [ ] Parse files on https://github.com/ioBroker/modbus-templates and allow to import them directly from adapter
@@ -307,6 +318,13 @@ There are some programs in folder `test` to test the TCP communication:
 	### **WORK IN PROGRESS**
 -->
 ## Changelog
+### 7.0.0 (2025-10-06)
+* (copilot) Improved Modbus error handling and fault tolerance - continue polling working devices even when others fail
+* (copilot) Fixes memory leak
+* (copilot) Added option to disable connection error logging to avoid log spam when devices are unavailable
+* (bluefox) Show values directly in configuration
+* (bluefox) Implemented TLS connection (master)
+
 ### 6.4.0 (2024-11-22)
 * (bluefox) Moved GUI compilation to vite
 * (bluefox) Added error message if the response length is invalid
@@ -422,7 +440,7 @@ There are some programs in folder `test` to test the TCP communication:
 * (bluefox) fixed the configuration dialog for "input registers" in slave mode
 
 ### 3.3.0 (2021-04-16)
-* (Apollon77) Allow usage of write-only (no poll) states
+* (Apollon77) Allowed usage of write-only (no poll) states
 * (Apollon77/TmShaz) F Write multiple registers
 * (prog42) create states of type string with default value of type string
 
@@ -500,7 +518,7 @@ There are some programs in folder `test` to test the TCP communication:
 * (bluefox) Refactoring
 
 ### 3.0.0 (2019-05-15)
-* (Apollon77) Support for nodejs 12 added, nodejs 4 is no longer supported!
+* (Apollon77) Support for Node.js 12 added, Node.js 4 is no longer supported!
 
 ### 2.0.9 (2018-10-11)
 * (Bjoern3003) Write registers was corrected
@@ -621,7 +639,7 @@ There are some programs in folder `test` to test the TCP communication:
 ## License
 The MIT License (MIT)
 
-Copyright (c) 2015-2024 Bluefox <dogafox@gmail.com>
+Copyright (c) 2015-2025 Bluefox <dogafox@gmail.com>
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal