-
-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new Device: DPT converter #395
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please make sure to update to the latest version of xknx (or Home Assistant) and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions. |
Yes, this would be a really good idea. Even in the commercial KNX world I have very rarely seen this feature, which could be very helpful indeed |
We could implement a device wich converts payloads from one DPT to another.
Some actuators seem to send percentages as DPT 9 instead of the typical DPT 5 or temperatures as DPT 14 instead of 9.
A converter device could have one input GA and value_type and one output GA and value_type. For every received telegram on the input GA the value would be sent out on the output GA in a different encoding. If the value exceeds the outgoing max/min values or precision we'd need some kind of defined behavior (raise an error or send max/min or round...).
We could even accept some kind of template language (like HA does - there is for sure a nice python package for this) to do basic transitions of the value like
+ - / *
and< > =
for DPT 1 output.What do you think?
The text was updated successfully, but these errors were encountered: