-
-
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
Feature Request: bitmask_sensor #520
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. |
It would be nice if we had a sensor that takes a raw payload and applies a given bitmask to it. Eg heating or cover actuators often use status communication objects where multiple (binary and numeric) states are encoded to one payload.
One bitmask_sensor object could spawn multiple binary_sensor / sensor entities in HA if multiple bitmask-name combinations are configured for one GA.
Maybe in the future these bitmasks could also be configured with GAs directly in other devices instead of DPT1 GAs (eg for operation_mode_frost_protection_address etc. or future options like cover_moving) see #484
The text was updated successfully, but these errors were encountered: