-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Added support for Unix Domain Sockers for MQTT communication
- Created a new config option 'mqtt_borker_socket_path' where one can provide the socket path - The config option mutual exclusive to the normal TCP socket and will raise an exception if both are provided in the config file (or as env variable) - There is no default value for the UDS path, it must be provided in the config file - We keep the backward compatibility, thus if nothing is provided in the config file, the default MQTT values are used (localhost:1883) - Beside functionality added, this provides an optimization over the TCP connection (boserved on slow systems around 5%) - Updated the config schema to for the new option * Optimization made in the MQTT event loop (we moved from executing the event loop from 100ms to 300s) - Normally the keep alive message is send by the MQTT lib, in certain cases however this might not work unless you call mqtt_sync often and regular - We decreased the event loop execution frequency drastically (on slow systems we can see a decrease of CPU usage around 10%)
- Loading branch information
Florin Mihut
committed
Feb 21, 2024
1 parent
7f532fa
commit cb607f7
Showing
10 changed files
with
170 additions
and
29 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters