Active Receiver Switching #936
Merged
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 6 commits
April 28, 2021 20:38
Switching of the active receiver module is available between the RF, RF2, RTL_433 and Pilight Gateway modules, allowing for changing of signal decoders without redploying the openMQTTGateway package. Sending a JSON message to the command topic of the desired receiver will change the active receiver module. Other minor adjustments/improvements 1 - Improved startup serial logging that includes - OpenMQTTGateway Version - OpenMQTTGateway Modules 2 - Trace logging of full Gateway module command topic - Enabled in RF, RF2, PiLight and RTL_433 3 - Updated RTL_433 Documentation to only include enabled ASK/OOK device decoders 4 - Trace logging of MQTT Callback topic
|
Just nodemcuv2-all-test failed, need to dig deeper into this |
Added valueAsASubject support for rtl_433_ESP - model and id keys are appended to message topic
|
Removed RF, RF2 and PiLight definition from build to reduce memory footprint of nodemcu build all. |
|
RF2 has been validated as being able to both receive and transmit ( ESP32 with CC1101 ). I just used two units and had one transmit the RF2 signal and the other setup to receive the RF2 signal. This should be good to go. |
1technophile
reviewed
May 9, 2021
added 3 commits
May 10, 2021 19:01
|
Thanks! |
|
Tks |
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.
Switching of the active receiver module is available between the RF, RF2, RTL_433 and Pilight Gateway modules, allowing for changing of signal decoders without redploying the openMQTTGateway package. Sending a JSON message to the command topic of the desired receiver will change the active receiver module. This will resolve issue #848
Other minor adjustments/improvements
1 - Improved startup serial logging that includes
2 - Trace logging of full Gateway module command topic to assist in determining command topic
3 - Updated RTL_433 Documentation to only include enabled ASK/OOK ( an oops from the original release )
device decoders
4 - Trace logging of MQTT Callback topic
Regression testing was completed with an ESP32 connected to a CC1101 transceiver and with a ESP32 connected to a RXB6 Receiver module. And RF, PiLight and RTL_433 were confirmed to be able to receive signals. I could not confirm RF2 was able to receive as I do not have an appropriate device to test with. Will need to watch this during the development phase in case it does not work correctly.
My Current Backlog
[x] Active switching between signal receivers ( RF, PiLight and RTL_433 ) and a bonus RF2
[ ] Home Assistant Discovery for RTL_433, including Black/White listing devices
[ ] FSK Modulation support for rtl_433_ESP ( waiting for feedback on the feature )
[ ] RTL_433 support for the RX127X Transceiver Chipset