[RF] Proposal fix for issue #2139 + Extra documentation #2157
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.
Description:
This pull request proposes a fix for issue #2139 and includes several improvements and enhancements to the RF module.
Changes:
#define
directives to allow users to choose which MQTT message to send for each RF signal received. Users can uncomment the desired line to enable the corresponding functionality.Impact:
These changes improve the flexibility and usability of the RF module, allowing users to customize their Home Assistant integration more easily. With this implementaion can be a broken retroconpatibilty
The enhanced logging and documentation will aid in troubleshooting and understanding the RF module's behavior.
Base for Future Work
The idea is to move the configuration to Home Assistant using MQTT Selectors. This will allow users to enable or disable modules, set the current frequency, and choose the type of message to send, all through MQTT Selectors.
Please review the proposed changes and provide feedback. Thank you!
Checklist: