[homematic] Expansion of virtual data channel for all window/door contacts #15641
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
Update StateContactVirtualDatapointHandler.java Signed-off-by: niclas18 <[email protected]>
Signed-off-by: niclas18 <[email protected]>
lsiepel
added
the
enhancement
|
This binding is apparently no more maintained. Let's assume your change is correct. |
querdenker2k
pushed a commit
to querdenker2k/openhab-addons
that referenced
this pull request
Oct 21, 2023
…tacts (openhab#15641) * make VirtualDatapoint belonging ContactSensor for more devices available --------- Signed-off-by: niclas18 <[email protected]>
querdenker2k
pushed a commit
to querdenker2k/openhab-addons
that referenced
this pull request
Oct 29, 2023
…tacts (openhab#15641) * make VirtualDatapoint belonging ContactSensor for more devices available --------- Signed-off-by: niclas18 <[email protected]> Signed-off-by: querdenker2k <[email protected]>
austvik
pushed a commit
to austvik/openhab-addons
that referenced
this pull request
Mar 27, 2024
…tacts (openhab#15641) * make VirtualDatapoint belonging ContactSensor for more devices available --------- Signed-off-by: niclas18 <[email protected]> Signed-off-by: Jørgen Austvik <[email protected]>
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.
The HomeMaticIP series includes, among other things, numerous different window and door contacts. The corresponding binding "homematic" from this repo establishes a connection to the headquarters of this product series (via an API). However, this only provides the current status (open or closed) for these sensors as a string, which is difficult to process. For example, for further integration via Openhab to Amazon Alexa, a special conversion rule is required (necessary for each sensor).
For this reason, a virtual controller was built into the add-on, which converts the strings from the API into a normal data channel (ON or OFF). This currently checks whether it is the
HMIP-SWDOmodel and then adds the corresponding data channel. However, in recent years there have been significantly more variants of these sensors on the market, for example theHMIP-SWDMmodel. However, these are not assigned the virtual channel, although they have the same API return and therefore a problem-free conversion is possible (tested myself, as I own both models).The manufacturer of HomeMatic products follows clear naming, so that all products with the model number
SWDshould also have this virtual data channel. This is why the simplification as stated in the PR.The problem has been reported in #4614, the german Openhab forum and other repos, among others.