Feature/mqtt v 3 #1752
Closed
Feature/mqtt v 3 #1752
Conversation
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
added 21 commits
April 23, 2021 14:45
-This Implementation allows the use of MQTT v. 3.1.1 - Configure a Broker with URL xor a Combination of IP, Port, Basepath, ConnectionType - Add an optional Last Will - Use TelemetryComponent to configure on the fly your openems components with differenty payloads and topics to publish and subscribe values depending on a key:Value pair - Publish: set up a Key:value concatination to publish channel values mapped to a key - Subscribe: Subscribe a Key within a topic and write the Value to the mapped Channel - Within every configuration it is possible to set multiple payloads and topics where each topic gets 1 payload - map the same payload to different topics - each configuration entry of publish/subscribe -> set up priority, QoS, RetainFlag, Payload, TimeInterval for push / refresh subscription - add an optional timestamp to the payload of each publish / subscribe config entry
When the "OtherComponent" is configured, telemetry/Command component will sort the Channels of the other component by ne id and display them in the Configuration
At the beginning of developing the MqttBridge I wanted to do something with the different connections But since this feature is not needed within the Publish/Subscribe Manager, different Connections can be removed -> only 2 instead of 6 Connections are now needed by the MqttManager. Since there will be only 2 connections now instead of 6 -> Executor Max Time could be reduced
We noticed, that some OpenEMS Components add some of their channel later on, after instatiation (SMA PV Invert for example) That's why we added a method to check for that
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hallo Stefan,
Hallo Community,
Unsere Implementierung von MQTT der Version 3.1.1 ist hier,
Hier wird es möglich, individuelle Payloads, und topics für einzelne OpenEMS Komponenten anzugeben und zu pushen.
Außerdem können virtuelle Werte subscribed und in Channel geschrieben werden.
Dies ist außerdem die Grundlage für den später folgenden "Optimizer" der der unseren Fahrplan der FleXa analysiert und aufteilt sowie dann optimierte Steuerung von einzelnen komponenten ermöglicht
Bei Fragen stehe ich zur Verfügung :)