Support for changing CC1101 Receive and Transmit Frequency#847
Support for changing CC1101 Receive and Transmit Frequency#8471technophile merged 8 commits into1technophile:developmentfrom NorthernMan54:CC1101-Mhz
Conversation
|
Thanks for the PR, could you update the docs also please : |
Legion2
left a comment
There was a problem hiding this comment.
In the Somfy module the frequency variable should also be used to reset frequency after transmision. Also do a search with an text editor to find all usages of CC1101_FREQUENCY.
|
@Legion2 'In the Somfy module the frequency variable should also be used to reset frequency after transmission' I was looking at this and am thinking would need a global variable for this. Any other thoughts on how to share the value between modules? |
|
Yes, the value must be shared, I think the best place is the config_RF.h, which is already shared. |
|
@Legion2 support for Somfy going back to the global receive frequency has been added. I don’t have the device so I can’t do a physical test, but the build worked. I also named the global variable receiveMhz as that made the most sense. Any other comments or feedback? |
ELECHOUSE_cc1101.SpiStrobe(CC1101_SIDLE); // Idle receiver prior to setting a new frequency
|
Thanks guys |
|
Tks very much gentlemen |
…from #847 (#851) Tks to @LSatan workaround no longer needed LSatan/SmartRC-CC1101-Driver-Lib#65
* Update to SmartRC-CC1101-Driver-Lib@^2.5.4 and removal of workaround from #847 Tks to @LSatan workaround no longer needed LSatan/SmartRC-CC1101-Driver-Lib#65 * Default to value as subject for rtl_433 and receiver switching * Default to not publishing unparsed signals * Fix for missing String for uint64_t * Fix is only required when value a subject is defined and not PiLight Co-authored-by: Northern Man <sgracey@Heisenberg.local>
* Update to SmartRC-CC1101-Driver-Lib@^2.5.4 and removal of workaround from 1technophile#847 Tks to @LSatan workaround no longer needed LSatan/SmartRC-CC1101-Driver-Lib#65 * Default to value as subject for rtl_433 and receiver switching * Default to not publishing unparsed signals * Fix for missing String for uint64_t * Fix is only required when value a subject is defined and not PiLight Co-authored-by: Northern Man <sgracey@Heisenberg.local>
…ile#847) * Support for changing CC1101 Receive and Transmit Frequency * Docs * Resolve feedback * Update Somfy module to use Global receiveMhz ELECHOUSE_cc1101.SpiStrobe(CC1101_SIDLE); // Idle receiver prior to setting a new frequency
…from 1technophile#847 (1technophile#851) Tks to @LSatan workaround no longer needed LSatan/SmartRC-CC1101-Driver-Lib#65
* Update to SmartRC-CC1101-Driver-Lib@^2.5.4 and removal of workaround from 1technophile#847 Tks to @LSatan workaround no longer needed LSatan/SmartRC-CC1101-Driver-Lib#65 * Default to value as subject for rtl_433 and receiver switching * Default to not publishing unparsed signals * Fix for missing String for uint64_t * Fix is only required when value a subject is defined and not PiLight Co-authored-by: Northern Man <sgracey@Heisenberg.local>
Adds the following
1 - Adds a new field on received messages, the MHz of the message ( only visible when compiled for CC1101 ) “mhz”: 303
2 - Add a new message, to set receiver frequency ( optional, default to 433.92 ). Ie { “mhz”: 303.0 }
3 - Add a optional field to transmit message “mhz”
4 - after transmission of a message, the receiver will go back frequency specified in # 2
5 - at this time these changes would only work on the zgatewayrf module.
6 - If an issue occurs while parsing the JSON message an error is transmitted over Mqtt
Sample message to control a Hampton Bay Fan
To change receiver frequency
Message Received from a GE Fan Remote on 315Mhz
Response to setting an invalid frequency
PS Two thumbs up on your usage of compiler definitions, makes customizing a build really easy