* Correct string handling for type key in NAMING_KEYS
Extend class structure RTL_433device and modify code to create correct state topic in discovery message to support sensors, that send type key as well as sensors, that don't. Actually only TPMS sensors use type=TPMS.
* Try to correct format failure.
* Remove trailing spaces
* [FSK] Add Lilygo Heltec environment with FSK modulation
Enable RTL_433 frequency and active receiver change with WebUI
Add FSK environment for Heltec and Lilygo
Update to rtl_433_ESP 0.3.0
Resolves issue with sx127x chipset and receiving higher frequencies
Includes support for receiving FSK signals, requires compiler directive OOK_MODULATION=false to switch to FSK mode
Adds unit of measure for rtl_433/battery_ok devices RTL_433_ESP Battery Auto Discovery Missing Unit of Measurement #1644
Updates value template for rtl_433/battery_ok in openHab mode
Resolves out of stack space crash lilygo-rtl_433 crash after chacon remote control button pressed #1655
* Bump ESP32 platform to v6.1.0 and ESP8266 to v4.1.0
* Fix ESP32 not connecting to Ethernet
And remove check updates as it is now done every hour
* Do not define LED pins if not explicitly stated
* OLED need to be reset for Heltec Lora 32 V2
* Fix issue with SSD1306 saving
* [RTL_433 Discovery] Add Govee water sensor Status entity
Add Govee water status sensor auto discovery as a binary_sensor, the entity will detect Water Leak Event and go back to Off state after 60seconds
* Format and comment
* https://github.com/1technophile/OpenMQTTGateway/issues/1380
CC1101 TXPower selection
* Creates the possability the define SDA/SCL Pins correct through a compiler switch from the platformio.ini
Sample:
'-DBME280_PIN_SDA=0'
'-DBME280_PIN_SCL=2'
This also changes the topic structure when using the macro valueAsATopic=true, it adds as sub-topics the `type, subtype, and channel` when they exist.
The id is the last subtopic to facilitate filtering, as it may change when replacing the batteries.
Co-authored-by: NorthernMan54 <19808920+NorthernMan54@users.noreply.github.com>
The main features of the upgrade to 0.1.3 of rtl_433_ESP are
1 - Change Transceiver Library to RadioLib
2 - Add support for SX127X transceiver module ( I used the 433 Mhz version of this Heltec module for development ).
3 - Added automatic calibration of the RSSI Signal detection Threshold
4 - Removed dependency on loop for start and end of signal detection, and moved to a ESP32 Task
5 - Moved received signal decoding to a ESP32 Task
6 - Identified Blueline PowerCost Monitor decoder as source of significant memory overhead and disabled.
7 - Multi Receiver support has been validated with RF, RF2 and PiLight
* Make number of RF2 repeats configurable
* Reduce number of repeats
Number of repeats in NewRemoteTransmitter is by default 16, which takes
quite some time to send.
It actually runs 2^R repeats, where R is the configured amount.
86f1c8486c/NewRemoteTransmitter.cpp (L20)
* PR #934
* Active Receiver Switching
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
* Regression testing
* Adding valueAsASubject support to rtl_433_ESP
- model and id keys are appended to message topic
* Increased memory size for receiver switching in blocking build all
Co-authored-by: Northern Man <sgracey@Heisenberg.local>
Received signals are published to the subjectRF2toMQTT topic (/RF2toMQTT). However, echos of mqtt messages are published to the topic subjectGTWRF2toMQTT (/433toMQTT). That seems quite inconsistent.
* 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
* Add ability to specify repeats for raw Pilight strings
* Updated RF Pilight doc to add raw transmission tut
Added information about transmitting raw messages using the MQTTtoPilight topic, including using the new repeats functionality. Fixed some scattered English mistakes.
Relay ok
Button press ok
RF reception 433toMQTT ok
To have the RF reception you need to connect D0 of SYN470 to GPIO4 of ESP8285. Instruction to follow. Do not do that if you are not confortable with soldering and don't have an electrical background.
