Commit Graph
13 Commits
Author SHA1 Message Date
Northern Man 2e0d1708c3 Update to rtl_433_ESP 0.1.5 and support for LILYGO® LoRa32 V2.1_1.6.1 433 Mhz (#1371)
* Update to rtl_433_ESP 0.1.5

Includes support for LILYGO® LoRa32 V2.1_1.6.1 433 Mhz

* Fix lint issue

* Fix build and lint issues

* Add lilygo-rtl_433 to build.yml
2022-12-26 13:48:08 -06:00
Northern Man e8cb115602 Update to rtl_433_ESP v0.1.4 (#1316)
Minor tuning of rtl_433_ESP signal reception for CC1101 and sx127x
2022-11-10 06:19:59 -06:00
Northern Man fd8c3a79ae Updated docs for the Heltec ESP32 Board (#1301) 2022-10-23 19:34:59 -05:00
Northern Man 19d58e01e0 Defensive code for Heltec Display (#1296)
Added to Heltec board display code logic to reduce corruption of messages on the display

Two piece of defensive code were added

- Only display messages to the display when operating on Core 1 ( Default Arduino ESP32 CONFIG_ARDUINO_RUNNING_CORE )

- Only display one character/string at a time

In the event of failure, default to Serial output.

PS SSD1306 driver similar issues

https://github.com/ThingPulse/esp8266-oled-ssd1306/issues/326
https://github.com/ThingPulse/esp8266-oled-ssd1306/issues/352
2022-10-23 13:36:59 -05:00
Northern Man 8bc65d62dc Update of rtl_433_ESP to version 0.1.3 - Support for SX127X transceiver module (#1291)
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
2022-10-20 11:14:45 -05:00
Northern Man c570eead82 Delete main.ino.cpp (#1289) 2022-10-18 12:33:33 -05:00
Northern Man c45181ef7e Heltec SSD1306 Display Support (#1283)
My environment

[env:heltec-display]   ; Heltec ESP32 Board with SSD1306 display
platform = ${com.esp32_platform}
board = heltec_wifi_lora_32_V2
build_type = debug
monitor_filters = esp32_exception_decoder
board_build.partitions = min_spiffs.csv
extra_scripts = pre:scripts/omg_firmware_version.py
lib_deps =
  ${com-esp.lib_deps}
  ${libraries.wifimanager32}
  ${libraries.heltec}
;  ${libraries.m5stickcp}

build_flags =
  ${com-esp.build_flags}
  ${test_env.build_flags}
; *** OpenMQTTGateway Config ***
  '-UZmqttDiscovery'          ; disables MQTT Discovery
  '-DvalueAsATopic=true'
  '-DLOG_LEVEL=LOG_LEVEL_TRACE'
; *** OpenMQTTGateway Modules ***
  '-DZboardHELTEC="HELTEC"'
; *** Heltec Board Options ***
  '-DDEBUG_OLEDDISPLAY(...)=Serial.printf( __VA_ARGS__ )'
  '-DLOG_TO_LCD=true'         ; Enable log to LCD
  '-DLED_ERROR=2'
  '-DONBOARD_LED=25'          ; Onboard LED is GPIO 25 on the Heltec Board

monitor_port = /dev/cu.SLAB_USBtoUART
monitor_speed = 921600
upload_port = /dev/cu.SLAB_USBtoUART
upload_speed = 921600

1 - Set default LCD log level to WARNING
2 - Implemented a macro based displayPrint function that will be usable across different displays

- Added logo display when idle
- Fixed log-lcd mqtt function
- Enable OLED Display on Heltec Boards
2022-10-13 21:17:25 -05:00
Northern Man 8d902962e5 Update ZgatewayPilight.ino (#1202) 2022-04-17 05:52:18 -05:00
Northern Man 5c8fd626ec Version update for rtl_433_ESP (#1152)
Just some minor code cleanup

* Rework OOK Receiver sample and rename directory to OOK_Receiver
* Cleaned up diagnostic logging
* Added logging of device decoder return codes ( DEMOD_DEBUG & RTL_DEBUG=4 )
* Fixed some compiler warnings
2022-01-27 05:43:57 -06:00
Northern Man 9546f43cd6 Behaviour when MQTT and/or Wifi is not available (#1126)
* Behaviour when MQTT and/or Wifi is not available

I was looking into why all my OpenMQTTGateway devices were not responding after a recent power failure and am speculating that the ESP32 was able to restart faster than my Wifi and MQTT Server was able to restart and resume operations.  And was thinking that a generic ESP.restart may be a reasonable approach with repeated Wifi and/or MQTT connection failures.

As mentioned here https://community.openmqttgateway.com/t/behaviour-when-mqtt-and-or-wifi-is-not-available/1747

Added new variable maxRetryWatchDog, which is the maximum number of mqtt or wifi connection attempts before restarting gateway device.
2022-01-17 16:16:43 -06:00
Northern Man cf0f53507d Library Update - rtl_433_ESP and smartrc-cc1101-driver-lib (#1122)
Includes the following updates to rtl_433_ESP:

1 - Workaround for cc1101 module going deaf after 24 hours, issue #16.
- By default the workaround is enabled, define NO_DEAF_WORKAROUND to remove the workaround

2 - Improved process for updating from rtl_433 for GitHub, almost totally automated.
- FYI - Their is a shell script in the tools subdirectory which does most of the heavy lifting required

3 - Updated device decoders to latest release of rtl_433
- They are now in align with rtl_433 release 21.12

4 - Updated r_api.c to prioritize ook demodulators - feature from rtl_433

5 - Created contrib directory for other device decoders to be merged into code base as part of the rtl_433 update process

6 - Bump library version to 0.0.3

7 - Tuned signal receiver logic and now throw away the first received byte. On testing this appears to dramatically reduce the number of unparsed signals.

8 - Fixed README feedback from @DigiH and updated the wording for 'PUBLISH_UNPARSED'. Also removed serial logging of unparsed messages unless 'PUBLISH_UNPARSED' is set

9 - Fixed gitignore so that the clone of rtl_433 is no longer part of the repository.

10 - Added new DEFINITION to enable rtl_433 verbose mode for a single device decoder. RTL_VERBOSE=##
2021-12-23 17:37:27 -06:00
Northern Man 94a7792863 Support for BME280 Temperature Correction (#1062)
* Support for BME280 Temperature Correction

The Spark Fun BME 280 library has support for Temperature correction, and this pull request implements the ability to apply a correction via a compiler directive ( BME280Correction ).
2021-08-16 19:35:02 -05:00
Northern Man 7cd1e9a1ab The reset button function does not work if TRIGGER_GPIO = 0 (#770)
After a bit of a challenge getting the config correct, determined that the reset button option doesn't work on a ESP32 due to the definition logic
2020-10-01 13:10:12 -05:00