puuu / mqtt433gateway Goto Github PK

The code says "const int RECEIVER_PIN = 12; //avoid 0, 2, 15, 16"

Why is this? I'm testing the code with a Esp-01 and want to use Gpio2.

Hello, appreciate that this is not being actively maintained but hoping that you can help ?

I have installed the code and it works faultlessly when receieving codes - when I try and post a code over MQTT it is received fine and I have checked the content being passed to the rf.send routine - but nothing seems to happen - any idea what could be wrong or how I can check it.

I have used the same ESP8266 module and transmitter without fail with the rcswitch library so I know all the hardware is fine.

MQTT message details below:

topic: rf434/send/quigg_gt9000
message: {"id": 525572, "unit": 0, "on": 1}

Thanks

Would be cool to restart the device per MQTT command.

Hi puuu
when building with platformio 5
fw_version.py gives error :ModuleNotFoundError: No module named 'platformio.managers.lib':
it works in pio 4 but not pio 5
plase can you help
with thanks phill

Hi,

I am trying to compile the latest master branch for the d1_mini board, but it fails in the following errors:

lib/WebServer/ConfigWebServer.cpp: In member function 'void ConfigWebServer::onFirmwareUpload()':
lib/WebServer/ConfigWebServer.cpp:242:36: error: no matching function for call to 'UpdaterClass::printError(ArduinoSimpleLogging::LogTarget&)'
Update.printError(Logger.info);
^
lib/WebServer/ConfigWebServer.cpp:242:36: note: candidate is:
In file included from /home/mvandam/.platformio/packages/framework-arduinoespressif8266/cores/esp8266/Arduino.h:248:0,
from /home/mvandam/.platformio/packages/framework-arduinoespressif8266/libraries/ESP8266WiFi/src/WiFiClient.h:25,
from /home/mvandam/.platformio/packages/framework-arduinoespressif8266/libraries/ESP8266WiFi/src/ESP8266WiFi.h:39,
from /home/mvandam/.platformio/packages/framework-arduinoespressif8266/libraries/ESP8266WebServer/src/ESP8266WebServer.h:29,
from lib/WebServer/ConfigWebServer.cpp:30:
/home/mvandam/.platformio/packages/framework-arduinoespressif8266/cores/esp8266/Updater.h:75:10: note: void UpdaterClass::printError(Stream&)
void printError(Stream &out);
^
/home/mvandam/.platformio/packages/framework-arduinoespressif8266/cores/esp8266/Updater.h:75:10: note:   no known conversion for argument 1 from 'ArduinoSimpleLogging::LogTarget' to 'Stream&'
lib/WebServer/ConfigWebServer.cpp:247:36: error: no matching function for call to 'UpdaterClass::printError(ArduinoSimpleLogging::LogTarget&)'
Update.printError(Logger.info);
^
lib/WebServer/ConfigWebServer.cpp:247:36: note: candidate is:
In file included from /home/mvandam/.platformio/packages/framework-arduinoespressif8266/cores/esp8266/Arduino.h:248:0,
from /home/mvandam/.platformio/packages/framework-arduinoespressif8266/libraries/ESP8266WiFi/src/WiFiClient.h:25,
from /home/mvandam/.platformio/packages/framework-arduinoespressif8266/libraries/ESP8266WiFi/src/ESP8266WiFi.h:39,
from /home/mvandam/.platformio/packages/framework-arduinoespressif8266/libraries/ESP8266WebServer/src/ESP8266WebServer.h:29,
from lib/WebServer/ConfigWebServer.cpp:30:
/home/mvandam/.platformio/packages/framework-arduinoespressif8266/cores/esp8266/Updater.h:75:10: note: void UpdaterClass::printError(Stream&)
void printError(Stream &out);
^
/home/mvandam/.platformio/packages/framework-arduinoespressif8266/cores/esp8266/Updater.h:75:10: note:   no known conversion for argument 1 from 'ArduinoSimpleLogging::LogTarget' to 'Stream&'
lib/WebServer/ConfigWebServer.cpp:254:36: error: no matching function for call to 'UpdaterClass::printError(ArduinoSimpleLogging::LogTarget&)'
Update.printError(Logger.info);
^
lib/WebServer/ConfigWebServer.cpp:254:36: note: candidate is:
In file included from /home/mvandam/.platformio/packages/framework-arduinoespressif8266/cores/esp8266/Arduino.h:248:0,
from /home/mvandam/.platformio/packages/framework-arduinoespressif8266/libraries/ESP8266WiFi/src/WiFiClient.h:25,
from /home/mvandam/.platformio/packages/framework-arduinoespressif8266/libraries/ESP8266WiFi/src/ESP8266WiFi.h:39,
from /home/mvandam/.platformio/packages/framework-arduinoespressif8266/libraries/ESP8266WebServer/src/ESP8266WebServer.h:29,
from lib/WebServer/ConfigWebServer.cpp:30:
/home/mvandam/.platformio/packages/framework-arduinoespressif8266/cores/esp8266/Updater.h:75:10: note: void UpdaterClass::printError(Stream&)
void printError(Stream &out);
^
/home/mvandam/.platformio/packages/framework-arduinoespressif8266/cores/esp8266/Updater.h:75:10: note:   no known conversion for argument 1 from 'ArduinoSimpleLogging::LogTarget' to 'Stream&'

I've also tried the esp12e board, which fails on the exact same error.

Current version: v0.2.0
Build with:
    ArduinoJson: 6.11.5
    ArduinoSimpleLogging: 0.2.2
    ESPiLight: 0.16.2
    PlatformIO: 4.1.0a1
    PubSubClient: 2.7
    Syslog: 2.0.0
    WebSockets: 2.2.0
    WifiManager: 0.15-beta
    espressif8266: 2.2.3
Chip ID: b1c7d9

even since update dosnt seem to be transmitting received signals

Is this supports Acu-Rite 00606TX Outdoor Temperature Sensor?
https://github.com/mikepparks/pilight-protocols

Currently, I'm using the RFLink Gateway for these sensors, but would be nice to use standalone MQTT gateway.

Hi

I have tried to compile this project and I got those errors

{
"resource": "arduino projects/MQTT433gateway-master/lib/MQTT/MqttClient.cpp",
"owner": "generated_diagnostic_collection_name#1",
"severity": 8,
"message": "argument of type "const char (String::)() const" is incompatible with parameter of type "void *"",
"startLineNumber": 40,
"startColumn": 14,
"endLineNumber": 40,
"endColumn": 20
}

{
"resource": "arduino projects/MQTT433gateway-master/lib/MQTT/MqttClient.cpp",
"owner": "cpp",
"severity": 8,
"message": "cannot convert 'String::buffer' from type 'const char* (String::)()const' to",
"startLineNumber": 40,
"startColumn": 34,
"endLineNumber": 40,
"endColumn": 34
}

{
"resource": "arduino projects/MQTT433gateway-master/lib/MQTT/MqttClient.cpp",
"owner": "cpp",
"severity": 8,
"message": "cannot convert 'String::buffer' from type 'const char* (String::)()const' to type 'void*'",
"startLineNumber": 40,
"startColumn": 34,
"endLineNumber": 40,
"endColumn": 34
}

{
"resource": "arduino projects/MQTT433gateway-master/lib/MQTT/MqttClient.cpp",
"owner": "generated_diagnostic_collection_name#1",
"severity": 8,
"message": "expression must be a modifiable lvalue",
"startLineNumber": 41,
"startColumn": 7,
"endLineNumber": 41,
"endColumn": 10
}

{
"resource": "arduino projects/MQTT433gateway-master/lib/MQTT/MqttClient.cpp",
"owner": "cpp",
"severity": 8,
"message": "invalid use of member function (did you forget the '()' ?)",
"startLineNumber": 41,
"startColumn": 11,
"endLineNumber": 41,
"endColumn": 11
}

{
"resource": "arduino projects/MQTT433gateway-master/lib/MQTT/MqttClient.cpp",
"owner": "generated_diagnostic_collection_name#1",
"severity": 8,
"message": "identifier "fwJsonVersion" is undefined",
"startLineNumber": 91,
"startColumn": 28,
"endLineNumber": 91,
"endColumn": 41
}

I'm new at this, I'll try to debug and correct this but your help would be much appreciated

thanks in advance :)

I have just tried to install platformIO on Atom and on VSCode, as well as just the core (all on a MAC) without success. Not sure whether this is the right forum, but just the core installation following the manual results in permission errors (despite using sudo and having verified that I indeed have python 2.7) and VScode and Atom both report back the error: Error: Detected unknown package ..... with any of the packages (nodemcu, nodemcu2, huzzaah, etc) [I actually tried them all]; searching the wisdom of the internet revealed that this is an error for which there is a bounty; I have also checked that no updates are available; "pio platform lists" does not reveal any info, here the complete output:

espressif8266 ~ Espressif 8266
==============================
Espressif Systems is a privately held fabless semiconductor company. They provide wireless communications a
nd Wi-Fi chips which are widely used in mobile devices and the Internet of Things applications.

Home: http://platformio.org/platforms/espressif8266
Frameworks: arduino, esp8266-nonos-sdk, esp8266-rtos-sdk, simba
Packages: framework-esp8266-rtos-sdk, toolchain-xtensa, framework-simba, tool-esptool, tool-mkspiffs, tool-
espotapy, framework-arduinoespressif8266, sdk-esp8266, framework-esp8266-nonos-sdk
Version: 1.5.0

(just as some posts where recommending to find a number that would allow to specify the package in terms of nodemcuv2@XXXXX)
what am I missing? Any and all help will be appreciated

Hi,

Is there a way that oregon sensors will be supported?

pilight supports it, but I can't find it in the web interface

https://wiki.pilight.org/oregon

Hi,

First of all this is a great project, I really like it.
May I miss something or the program intentionally not forwarding decoded switch messages to MQTT?
For example I see the following on the logs:

rf signal received: {"id":89,"temperature":21.61,"humidity":49.00,"battery":1,"channel":1} protocol= tfa status=0 repeats=1 deviceID=89
rf signal received: {"id":89,"temperature":21.61,"humidity":49.00,"battery":1,"channel":1} with protocol tfa deviceID=89
Publish MQTT message: rf434/recv/tfa/89 retain=1 .. {"id":89,"temperature":21.61,"humidity":49.00,"battery":1,"channel":1}
rf signal received: {"id":6,"unit":5,"state":"off"} protocol= conrad_rsl_switch status=0 repeats=1 deviceID=6
rf signal received: {"id":198,"temperature":16.16,"humidity":48.00,"battery":1,"channel":3} protocol= tfa status=0 repeats=1 deviceID=198

Is it possible to forward the Conrad switch messages to the MQTT - to let the homeassistant process it?

Thanks,
Denes

Attempting to build webpage...
WindowsError: [Error 2] The system cannot find the file specified:
File "C:\python27\lib\site-packages\platformio\builder\main.py", line 124:
env.SConscript(item, exports="env")
File "C:\Users\phill.platformio\packages\tool-scons\script..\engine\SCons\Script\SConscript.py", line 541:
return _SConscript(self.fs, *files, **subst_kw)
File "C:\Users\phill.platformio\packages\tool-scons\script..\engine\SCons\Script\SConscript.py", line 250:
exec file in call_stack[-1].globals
File "C:\Users\phill\Desktop\build\MQTT433gateway-0.2.0\MQTT433gateway-0.2.0\scripts\build_web.py", line 34:
build_web()
File "C:\Users\phill\Desktop\build\MQTT433gateway-0.2.0\MQTT433gateway-0.2.0\scripts\build_web.py", line 29:
check_call(["npm", "install"])
File "c:\python27\lib\subprocess.py", line 185:
retcode = call(*popenargs, **kwargs)
File "c:\python27\lib\subprocess.py", line 172:
return Popen(*popenargs, **kwargs).wait()
File "c:\python27\lib\subprocess.py", line 394:
errread, errwrite)
File "c:\python27\lib\subprocess.py", line 644:
startupinfo)

I am currently using openhab2 and the mqtt2 add-on to use the MQTT433gateway.

Currently I have to write the whole json into my configuration files.

If I could just send the commands via "rf434/send/clarus_switch/C5/27" instead of "rf434/send/clarus_switch" it would make the configuration much easier.

please if possible could you rebuild the project I'm getting errors all-over. spffs are no longer used
all so could i as what do i need to install to build it
with thanks and happy new year
phill

I'm trying to get you code to work with a 3-pack of Telldus Slim RF outlets.
I begun with trying to sniff the codes, and this is what I get:

pulses: 132 possible protocol: arctech_switch
RF signal arrived [arctech_switch][52381518] (3) {"id":52381518,"unit":15,"state":"off"}
pulses: 132 possible protocol: arctech_screen
RF signal arrived [arctech_screen][52381518] (3) {"id":52381518,"unit":15,"state":"down"}
pulses: 132 possible protocol: arctech_contact
RF signal arrived [arctech_contact][52381518] (3) {"id":52381518,"unit":15,"state":"closed"}

pulses: 132 possible protocol: arctech_switch
RF signal arrived [arctech_switch][52381518] (0) {"id":52381518,"unit":15,"state":"on"}
pulses: 132 possible protocol: arctech_screen
RF signal arrived [arctech_screen][52381518] (0) {"id":52381518,"unit":15,"state":"up"}
pulses: 132 possible protocol: arctech_contact
RF signal arrived [arctech_contact][52381518] (0) {"id":52381518,"unit":15,"state":"opened"}

for off and on respectively. So i tried to set it up in my config file like this:

switch:
  - platform: mqtt
    name: "arctech_switch"
    command_topic: "rf434/send/arctech_switch"
    payload_on: '{"id":52381518,"unit":15,"on":1}'
    payload_off: '{"id":52381518,"unit":15,"off":1}'

But it is not really working as it should, the outlets isn't turning either on or off. This is what I get when I subscribe to the topic:

Client mosqsub|2882-hassbian received PUBLISH (d0, q0, r0, m0, 'rf434/send/arctech_switch', ... (32 bytes))
{"id":52381518,"unit":15,"on":1}
Client mosqsub|2882-hassbian received PUBLISH (d0, q0, r0, m0, 'rf434/recv/arctech_switch/52381518', ... (38 bytes))
{"id":52381518,"unit":15,"state":"on"}
Client mosqsub|2882-hassbian received PUBLISH (d0, q0, r0, m0, 'rf434/recv/arctech_screen/52381518', ... (38 bytes))
{"id":52381518,"unit":15,"state":"up"}
Client mosqsub|2882-hassbian received PUBLISH (d0, q0, r0, m0, 'rf434/recv/arctech_contact/0', ... (34 bytes))
{"id":0,"unit":0,"state":"closed"}

It looks like the last line with arctech_contact is not getting the correct id and unit. Do you have any idea of what could be wrong or could be done?
Or maybe it is more of question to the PiLight guys/guy?

Hi.
Just so you know that your prebuild scripts (I don't know what they doing, just get the exact version string?)
are purely based on git repo and don't work when someone just downloads zipped dir (as many people often do, since this is an option).

Not only the scripts not work, it prohibits the whole project to build. Maybe put them as optional, or maybe that they end gracefully when they don't find git repo.

I am trying to improve my current setup for fan speed control by using this gateway. ATM I use pilight USB nano which works.

I have 4 ceiling fans, each of them has 6 speeds, plus stop and a light buttons. I have recorded all the raw codes of each button for each fan, so i have a json file that maps the devices, their speeds and their respective raw code.

In pilight the raw command can be send pilight-send -p raw -c "RAWCODECOMMAND", in my case they look like this

pilight-send -p raw -c "370 370 370 370 370 370 370 370 370 370 370 670 370 730 370 670 370 670 370 670 370 670 370 370 370 11590"

That toggles the fan light for example.

So for sending a raw command using the gateway i am using this mqtt publish command:

mosquitto_pub -V mqttv311 -u homeassistant -P password -h localhost -t "rf434/send/RAW/" -m "370 370 370 370 370 370 370 370 370 370 370 670 370 730 370 670 370 670 370 670 370 670 370 370 370 11590"

But seems like is not interpreted correctly by the gateway. When I move the transmitter to the current pilight nano setup and fire the raw code mentioned above, the gateway listening on raw codes reads this:

Set debug flag protocolRaw: 1
RAW RF signal (34): c:0122324563636363636222222222222327;p:1469,1105,430,176,754,4772,585,11409@
RAW RF signal (28): c:0101010110100012111000003104;p:552,210,807,380,11407@
RAW RF signal (32): c:01221202222002110130300001230204;p:454,304,157,790,11380@
RAW RF signal (30): c:012013311110011011100000000104;p:574,168,765,441,11408@
RAW RF signal (25): c:0101012202023000000000104;p:559,183,441,816,11414@
RAW RF signal (28): c:0111210113210014230000000105;p:544,194,312,673,899,11427@
RAW RF signal (26): c:01010222022013000320000104;p:548,189,329,747,11424@
RAW RF signal (28): c:0101020021000023200000111104;p:548,192,332,939,11429@
RAW RF signal (26): c:01201300311000000000000104;p:545,198,704,339,11446@
Webserver: debug PUT
Set debug flag protocolRaw: 0

What is the correct way of sending raw codes via mqtt?

I am using a nodemcu board. Firmware was compiled with visual studio (platformio).
The transmitter is XKFST module powered by the nodemcu 3.3V pin.

I have 2 MQTT433gateways in ~20m distance.

When sending
{"systemcode":24,"programcode":1,"on":1}
from first one

I receive this
{"systemcode":25,"programcode":1,"state":"on"}
on second gateway.

Is this a correct behaviour? If not: how could I debug this further?

Hi,

I installed MQTT433gateway with an RXB6 receiver. Once I figured out that the data pin was mislabeled on my module I am getting something out of it.

But I'm not sure how to go about debugging reception.

I have some 4 button 433.92MHz remotes - they are supposed to be Sonoff compatible.

When I press buttons on the one remote the log shows:

rf signal received: {"id":"B15","unit":47,"state":"off"} with protocol rev2_switch deviceID=B15
rf signal received: {"id":"B15","unit":47,"state":"off"} with protocol rev2_switch deviceID=B15
(etc).

It doesn't matter which button I press - the display is the same. How do I distinguish the buttons?

I also have some 433.92MHz PIRs, but the gateway doesn't show anything when they go off.

So how do I get started with debugging?

Thanks,
Steve

Hi @puuu thank you for this great project.
I'm working on a new protocol for my 433 MHz doorbell. I want to use an ESP8266 running MQTT433gateway to test my new protocol.
When I tried to manually compile the (unmodified) source code, I ran into this error message:

...
|-- <SystemTools>
|-- <WifiManager> 0.15.0
|   |-- <DNSServer> 1.1.1
|   |   |-- <ESP8266WiFi> 1.0
|   |-- <ESP8266WebServer> 1.0
|   |   |-- <ESP8266WiFi> 1.0
|   |-- <ESP8266WiFi> 1.0
Building in release mode
KeyError: 'PROJECTLIBDEPS_DIR':
  File "/home/pi/.platformio/penv/lib/python3.7/site-packages/platformio/builder/main.py", line 164:
    env.SConscript(item, exports="env")
  File "/root/.platformio/packages/tool-scons/script/../engine/SCons/Script/SConscript.py", line 597:
    return _SConscript(self.fs, *files, **subst_kw)
  File "/root/.platformio/packages/tool-scons/script/../engine/SCons/Script/SConscript.py", line 286:
    exec(compile(scriptdata, scriptname, 'exec'), call_stack[-1].globals)
  File "/home/pi/adding_doorbell/original_MQTT433gateway/MQTT433gateway/scripts/fw_version.py", line 53:
    generate_file()
  File "/home/pi/adding_doorbell/original_MQTT433gateway/MQTT433gateway/scripts/fw_version.py", line 50:
    build_with=escape_string(get_dependencies_json())))
  File "/home/pi/adding_doorbell/original_MQTT433gateway/MQTT433gateway/scripts/fw_version.py", line 40:
    return json.dumps(get_dependencies(), separators=(',', ':'), sort_keys=True)
  File "/home/pi/adding_doorbell/original_MQTT433gateway/MQTT433gateway/scripts/fw_version.py", line 30:
    lib_storage = os.path.join(env['PROJECTLIBDEPS_DIR'], env['PIOENV'])
  File "/root/.platformio/packages/tool-scons/script/../engine/SCons/Environment.py", line 405:
    return self._dict[key]
============================================================ [FAILED] Took 254.97 seconds ==============

Environment    Status    Duration
-------------  --------  ------------
esp12e         FAILED    00:04:14.975
esp12e_160     IGNORED
nodemcu        IGNORED
nodemcuv2      IGNORED
d1_mini        IGNORED
huzzah         IGNORED
======================================================= 1 failed, 0 succeeded in 00:04:14.975 ==========

I also found this rjwats/esp8266-react#56
so I just tried to change PROJECTLIBDEPS_DIR to PROJECT_LIBDEPS_DIR on line 30 of ./scripts/fw_version.py and that worked:

Building .pio/build/esp12e/firmware.bin
Creating BIN file ".pio/build/esp12e/firmware.bin" using ".pio/build/esp12e/firmware.elf"
Retrieving maximum program size .pio/build/esp12e/firmware.elf
Checking size .pio/build/esp12e/firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
RAM:   [=====     ]  54.2% (used 44428 bytes from 81920 bytes)
Flash: [=====     ]  49.9% (used 520785 bytes from 1044464 bytes)
==================================== [SUCCESS] Took 2400.67 seconds ====================================

Environment    Status    Duration
-------------  --------  ------------
esp12e         SUCCESS   00:40:00.673
esp12e_160     IGNORED
nodemcu        IGNORED
nodemcuv2      IGNORED
d1_mini        IGNORED
huzzah         IGNORED
===================================== 1 succeeded in 00:40:00.673 =====================================

I use these:

platformio --version
PlatformIO, version 4.3.3

cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

uname -a
Linux domotica 4.19.75+ #1270 Tue Sep 24 18:38:54 BST 2019 armv6l GNU/Linux

I didn't want to create a pull request yet, since I expect that is was running without problems using "PROJECTLIBDEPS_DIR" in your configuration.

What do you think?

Kind regards,
woutput

I have a problem to get code from rf remote. I got code when pressing button:

pulses: 50 possible protocol: arctech_switch_old
pulses: 50 possible protocol: arctech_switch_old
pulses: 50 possible protocol: arctech_switch_old
pulses: 50 possible protocol: arctech_switch_old

I tried to get code from another rf remote. These what I got:

pulses: 50 possible protocol: rev3_switch
RF signal arrived [rev3_switch]/[33] (0) {"id":33,"unit":13,"state":"on"} (1)
pulses: 50 possible protocol: ev1527
RF signal arrived [ev1527]/[] (0) {"unitcode":1031337,"state":"opened"} (1)
pulses: 50 possible protocol: rev3_switch
RF signal arrived [rev3_switch]/[33] (2) {"id":33,"unit":13,"state":"on"} (102)
pulses: 50 possible protocol: ev1527
RF signal arrived [ev1527]/[] (2) {"unitcode":1031337,"state":"opened"} (102)

And I got code from 433Mhz door sensor as these:

pulses: 50 possible protocol: rsl366
pulses: 50 possible protocol: arctech_switch_old
pulses: 50 possible protocol: rsl366
pulses: 50 possible protocol: arctech_switch_old

What should I do to get them work?

Thanks.

I have setup this on a nodemcu and it's receiving messages. But the messages are not published to the broker.
Only the state and version are published correctly.
I think I'm missing something maybe someone knows the answer?

First; thanks for this awesome piece of software. It was exactly what I have been looking for / wanting to put together myself for a few months. But I would never have been able to get even close to this project :)

That being said, today I downloaded the source in an attempt to debug a bit of MQTT / ESPilight as I was experiencing some trouble in trying to turn an arctech dimmer completely off (which is a different issue, I might try to debug it myself and send a pull request or file another issue).
After installing the Platformio IDE and the necessary libraries I was able to compile the project. Though when uploading it (succesfully) to my NodeMCUv2 board the following error appeared:

ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v614f7c32
~ld

I tried uploading the binary file via the WebUploader sketch, as well as directly form the commandline with PlatformIO. Also did a clean install of PlatformIO on my other laptop and tried with a D1 mini R2 board as well. All yield the same boot loop as result.

While trying to figure this out by myself, I tried the following code which did work and after uncommenting the settings line started boot looping again.

#include <ESP8266httpUpdate.h>
#include <ESP8266mDNS.h>
#include <FS.h>
 
#include <ArduinoSimpleLogging.h>
#include <WiFiManager.h>
 
#include <ConfigWebServer.h>
#include <MqttClient.h>
#include <RfHandler.h>
#include <Settings.h>
#include <StatusLED.h>
#include <SyslogLogTarget.h>
#include <SystemHeap.h>
#include <SystemLoad.h>
 
WiFiClient wifi;
 
// Settings settings;
ConfigWebServer *webServer = nullptr;
MqttClient *mqttClient = nullptr;
RfHandler *rf = nullptr;
SyslogLogTarget *syslogLog = nullptr;
StatusLED *statusLED = nullptr;
SystemLoad *systemLoad = nullptr;
SystemHeap *systemHeap = nullptr;
 
void setup() {
    Serial.begin(115200);
    Serial.println("Hello world!");
    // Logger.addHandler(Logger.DEBUG, Serial);
}
 
void loop() {
    Serial.println("Hello world!");
    delay(1000);
}

Both laptops run Ubuntu 17.10, PlatformIO: Home 0.9.5·Core 3.5.3b1
Source from master branch on git; commit 5418b4e (HEAD -> master, tag: v0.1.0, origin/next, origin/master, origin/HEAD)

Hi

When I send a few (about 10) MQTT messages to turn off different ligthts on a short-term, my esp8266 stops responding. I get a temporary ping time time out and some of the RF pulse are not being send anymore.

This happens all the time when I start an activity to control about 10 (KaKU) lights.

Hey @puuu !

I've recently bought a sonoff rf bridge which I modded to use the direct mod which gives me in effect an esp8266 and some rf hardware in a nice plastic box.

I saw your engagement in the openmqttgateway project and after that I noticed this project too and now I'm not sure which one to choose if I don't need any bluetooth, IR and sensor fucntionality (if that was the case I'd choose the openmqttgateway instantly).

Both projects share the same rf library for pilight and this project is already using the mqtt convention that I am looking for.

You seem to know both projects very well and as both seem well maintained and intensively documented projects in which lot's of effort is put, I'm not sure which is the one that suits best to my sonoff rf bridge.

Can you shine a little light on the main differences? Is it mostly the additional functionality for sensors and other RF libraries that can be used with the openmqttgateway or is there more functionality I need to know of before I make a choice?

(And off course thanks so much for creating the pilight arduino RF library!)

I have the MQTT433gateway flashed on a nodemcu V3 and am trying to get it working with my rf wall plugs.
I do receive rf messages from the remote and also from some other devices, so the receiver is working.
However I did not manage to get any signs of life out of my transmittor.

I first tryed using the mosquitto broker and published mqtt messages using mosquitto_pub.
I sent the following mqtt message:

mosquitto_pub -h 192.168.1.??? -p ???? -t rf434/send/arctech_switch -m "{"id": 2660354, "unit": 0, "state": "off"}"

I do get responds on the serial of the nodemcu V3 saying:

Message arrived [rf434/send/arctech_switch] {"id": 2660354, "unit": 0, "state": "off"} with protocol arctech_switch
rf send {"id": 2660354, "unit": 0, "state": "off"} with protocol arctech_switch

But I don't see any "rf signal arrived" after that and I would have expected that.
Furthermore, when I sent some rubish message I get exactly the same response such as sending:

mosquitto_pub -h 192.168.1.??? -p ???? -t rf434/send/no-way -m "hello"

gives response on the serial:

Message arrived [rf434/send/no-way] {"hello"} with protocol no-way
rf send {"hello"} with protocol no-way

Therefore I think I have the mqtt message wrong or something.

I then tryed sending mqtt messages using the python paho client.

I sent the following message using this code:

import json
import paho.mqtt.client as mqtt

message = {
    'id': 2660354,
    'unit': 0,
    'on': 1
}

client = mqtt.Client()
client.connect("192.168.1.???", ????)
client.publish("rf434/send/quigg_gt9000", payload=json.dumps(message))

But then I get an exeption on the serial interface:

Message arrived [rf434/send/quigg_gt9000] {"on": 1, "id": 2660354, "unit": 0}
rf send {"on": 1, "id": 2660354, "unit": 0} with protocol quigg_gt9000

Exception (3):
epc1=0x40001f1c epc2=0x00000000 epc3=0x00000000 excvaddr=0x40249300 depc=0x00000000

ctx: cont 
sp: 3fff1170 end: 3fff1860 offset: 01a0

>>>stack>>>
3fff1310:  feefeffe feefeffe feefeffe 401074e5  
3fff1320:  000000ed 3fff2c9c feefeffe feefeffe  
3fff1330:  feefeffe feefeffe feefeffe 00000001  
3fff1340:  401070b8 0000000c 00000000 401070a2  
3fff1350:  ffffffff 00000020 feefeffe feefeffe  
3fff1360:  feefeffe feefeffe feefeffe 401074e5  
3fff1370:  40107264 00289802 00000001 00000000  
3fff1380:  00000802 00000030 00000004 00000001  
3fff1390:  401070b8 0000000c 00000000 401070a2  
3fff13a0:  00000000 00000000 fffffc01 00000001  
3fff13b0:  3fff13d0 3fff13c0 00000004 00000000  
3fff13c0:  00000000 00000003 0000000f 00000010  
3fff13d0:  00000800 00000000 3fff1498 00000001  
3fff13e0:  00000000 00000001 00289802 40210e30  
3fff13f0:  00000001 00000000 00000000 00000000  
3fff1400:  00000001 00000001 00000000 00000001  
3fff1410:  00000000 00000000 00000001 00000000  
3fff1420:  00000000 00000001 00000000 00000001  
3fff1430:  00000000 00000001 00000000 00000000  
3fff1440:  00000000 00000000 00000000 00000000  
3fff1450:  00000000 000886c0 00085e41 0008f002  
3fff1460:  00082da3 0008d254 00083775 000808e6  
3fff1470:  0008ec27 0008a9d8 00084bb9 0008b3fa  
3fff1480:  0008ca1b 00087f8c 0008643d 0008956e  
3fff1490:  0008119f 4010701c 00000000 3ff00000  
3fff14a0:  00080000 00000013 00000022 3fff13f8  
3fff14b0:  3fff542c 3fff5267 00000005 3fff1770  
3fff14c0:  3fff1720 3fff542c 3fff4a34 40205ae6  
3fff14d0:  3fff1500 0000000c 00000000 401070a2  
3fff14e0:  ffffffff 00000020 3fff0830 3fff1770  
3fff14f0:  3fff1740 3fff0640 00000000 40205b38  
3fff1500:  01f4044c 044c01f4 044c01f4 044c01f4  
3fff1510:  01f4044c 01f4044c 044c01f4 01f4044c  
3fff1520:  044c01f4 044c01f4 01f4044c 044c01f4  
3fff1530:  044c01f4 01f4044c 044c01f4 01f4044c  
3fff1540:  044c01f4 01f4044c 044c01f4 044c01f4  
3fff1550:  044c01f4 044c01f4 044c01f4 044c01f4  
3fff1560:  1b580bb8 3fffc6fc 00000001 401074e5  
3fff1570:  00000259 3fff329c 3fff0830 00000030  
3fff1580:  00000000 3fff0640 3fff3d74 00000001  
3fff1590:  401070b8 0000000c 00000000 401070a2  
3fff15a0:  ffffffff 00000020 0000001f 401048f9  
3fff15b0:  4000050c 00000000 0000001f 00000022  
3fff15c0:  3fffc200 4010701c 3fffc258 4000050c  
3fff15d0:  40203a94 00000030 00000018 ffffffff  
3fff15e0:  40201311 00000000 0000005f 0000007f  
3fff15f0:  0000007e 6000001c ff000000 007d3020  
3fff1600:  0000002f 3fff53c1 80808080 3fff077c  
3fff1610:  0000005f 3fff077c 3fff53c0 00000030  
3fff1620:  0000007e 6000001c ff000000 007d3020  
3fff1630:  0000002f 3fff53c1 80808080 3fff077c  
3fff1640:  00000020 3fff077c 3fff1770 00000030  
3fff1650:  3ffeb67c 00000006 00000000 3ffee808  
3fff1660:  40245e90 00000000 00000001 00000030  
3fff1670:  00000000 4010078f 00000000 3fff1954  
3fff1680:  00000010 3fff1770 00000000 3fff1954  
3fff1690:  00000030 3fff1720 00000000 4010053d  
3fff16a0:  40106fd0 00000208 0000fa00 3fff1770  
3fff16b0:  00000010 00000001 3ffe9149 3fff1770  
3fff16c0:  00000030 3fff1720 3fff1720 40201f28  
3fff16d0:  3fff1740 00000023 3fff1720 40201f77  
3fff16e0:  3fff1954 00000362 3fff1720 40201fad  
3fff16f0:  3fff1740 3fff1770 3fff1720 40201ffe  
3fff1700:  0000000a 3fff1770 3fff077c 40201ec8  
3fff1710:  3fff1740 3fff1770 00000000 40217933  
3fff1720:  3fff5244 0000002f 00000023 3fff1770  
3fff1730:  3fff1763 3fff1740 3fff077c 40217a63  
3fff1740:  6e6f227b 31203a22 6922202c 203a2264  
3fff1750:  30363632 2c343533 6e752220 3a227469  
3fff1760:  007d3020 3fff17e0 3fff077c 40217a00  
3fff1770:  3fff53b4 0000000f 0000000c 402047f7  
3fff1780:  00000000 3fff17c2 3fff53cc 0000000f  
3fff1790:  0000000b 3fff50ac 0000001f 00000017  
3fff17a0:  3fff069b 3fff06be 3fff06bd 00000002  
3fff17b0:  00000039 3fff067c 0000003c 3fff1800  
3fff17c0:  3fff1800 00008239 3fff067c 40218170  
3fff17d0:  3fff1800 00000001 00000017 40205786  
3fff17e0:  33346672 65732f34 712f646e 67676975  
3fff17f0:  3974675f 00303030 3fff067c 4020569c  
3fff1800:  01650101 015a0084 3fff0664 4021750a  
3fff1810:  1342024b 05a000e9 09e80c03 402157e8  
3fff1820:  044e0182 02d9005b 3fff0664 3fff0830  
3fff1830:  3fffdad0 00000000 3fff067c 40218040  
3fff1840:  3fffdad0 00000000 3fff0828 40202b38  
3fff1850:  feefeffe feefeffe 3fff0840 40203e94  
<<<stack<<<

I decoded this error using ESPexceptionDecoder:

Exception 3: LoadStoreError: Processor internal physical address or data error during load or store
Decoding 44 results
0x40249300: chip_v6_unset_chanfreq at ?? line ?
0x401074e5: ESPiLight::interruptHandler() at ?? line ?
0x401070b8: interrupt_handler at ?? line ?
0x401070a2: interrupt_handler at ?? line ?
0x401074e5: ESPiLight::interruptHandler() at ?? line ?
0x40107264: printf at ?? line ?
0x401070b8: interrupt_handler at ?? line ?
0x401070a2: interrupt_handler at ?? line ?
0x40210e30: createCode at quigg_gt9000.c line ?
0x4010701c: interrupt_handler at ?? line ?
0x40205ae6: ESPiLight::createPulseTrain(unsigned short*, String const&, String const&) at ?? line ?
0x401070a2: interrupt_handler at ?? line ?
0x40205b38: ESPiLight::send(String const&, String const&, unsigned int) at ?? line ?
0x401074e5: ESPiLight::interruptHandler() at ?? line ?
0x401070b8: interrupt_handler at ?? line ?
0x401070a2: interrupt_handler at ?? line ?
0x401048f9: ets_timer_disarm at ?? line ?
0x4010701c: interrupt_handler at ?? line ?
0x40203a94: uart_write_char at ?? line ?
0x40201311: HardwareSerial::write(unsigned char) at ?? line ?
0x40245e90: SHA1Final at ?? line ?
0x4010078f: ppProcessTxQ at ?? line ?
0x4010053d: realloc at ?? line ?
0x40106fd0: millis at ?? line ?
0x40201f28: String::changeBuffer(unsigned int) at ?? line ?
0x40201f77: String::reserve(unsigned int) at ?? line ?
0x40201fad: String::copy(char const*, unsigned int) at ?? line ?
0x40201ffe: String::String(char const*) at ?? line ?
0x40201ec8: String::~String() at ?? line ?
0x40217933: transmitt(String const&, char const*) at ?? line ?
0x40217a63: mqttCallback(char const*, unsigned char const*, unsigned int) at ?? line ?
0x40217a00: mqttCallback(char const*, unsigned char const*, unsigned int) at ?? line ?
0x402047f7: ClientContext::_consume(unsigned int) at ?? line ?
0x40218170: std::_Function_handler ::_M_invoke(std::_Any_data const&, char*, unsigned char*, unsigned int) at ?? line ?
0x40205786: PubSubClient::loop() at ?? line ?
0x4020569c: PubSubClient::loop() at ?? line ?
0x4021750a: LED::setState(bool) at ?? line ?
0x402157e8: Heartbeat::beatStep() at ?? line ?
0x40218040: loop at ?? line ?
0x40202b38: loop_wrapper() at core_esp8266_main.cpp line ?
0x40203e94: cont_norm at cont.o line ?

Could someone explain what i am doing wrong, or sent me a valid sintax for sending an rf message using ether mosquitto or python paho?

Thank you for your help!

Hi,

Congratulation, this is a really cool project I like it.
Unfortunately I'm unable to build it from source on Win 10 Atom.io + Platformio (latest, fresh installation both).
I'm sure a few small steps are missing from the build instructions but at the moment I have to depend on released binaries.

Thanks,
Denes

Build log attached: build.log

Being working on this now two months, i still cannot get the software to send a single rf signal via mqtt. I suspected the rf transmitter, but going now through the third different one i have doubts now on the fw.

I have tried the default release, as well as my own build binary. I have a couple of issues using the settings as changing the mqtt password, resulted in admin password defaulted so no RF. So i put all my passwords, topic, etc in settings.h

So far from reading the log i can see MQTT433gateway connects to the MQTT broker successfully, i can confirm this on the mosquitto server debug log seeing several messages from the device:

1530014897: Sending PINGRESP to rf434
1530014900: Received PINGREQ from DVES_375428
1530014900: Sending PINGRESP to DVES_375428
1530014900: Received PINGREQ from DVES_14C4FE
1530014900: Sending PINGRESP to DVES_14C4FE
1530014906: Received PUBLISH from DVES_375428 (d0, q0, r0, m0, 'sonoff/switch/lounge/tele/STATE', ... (156 bytes))
1530014906: Received PUBLISH from DVES_375428 (d0, q0, r0, m0, 'sonoff/switch/lounge/tele/SENSOR', ... (160 bytes))
1530014906: Sending PUBLISH to e9f3c689-6ac0-45de-aed5-cf41262004e8 (d0, q0, r0, m0, 'sonoff/switch/lounge/tele/SENSOR', ... (160 bytes))
1530014912: Received PINGREQ from milight-hub-1493872
1530014912: Sending PINGRESP to milight-hub-1493872
1530014912: Received PINGREQ from rf434
1530014912: Sending PINGRESP to rf434
1530014915: Received PINGREQ from DVES_375428
1530014915: Sending PINGRESP to DVES_375428
1530014915: Received PINGREQ from DVES_14C4FE
1530014915: Sending PINGRESP to DVES_14C4FE
1530014924: Received PINGREQ from mqtt_3672cb7d.1352a4
1530014924: Sending PINGRESP to mqtt_3672cb7d.1352a4

Now when i send any message via mqtt, the gateway doesn't log anything. Looking at others peoples issues here the received message should be something like:

Message arrived bla bla
rf send bla bla

This is a simple command made from the payloads from the wiki to test i use:

mosquitto_pub  -h ha.lan -u homeassistant -P password -t "rf/send/impuls/" -m '{"systemcode":24,"programcode":2,"on":1}'

or

mosquitto_pub  -h ha.lan -u homeassistant -P password -t "rf/send/impuls" -m '{"systemcode":24,"programcode":2,"on":1}'

Message is published as i can see it my subscribe terminal. But yet the serial terminal or web console don't log anything at all. The second command topic without slash crashes the nodemcu as you can see in the serial log

Loading config file.
Applying config settings.
Change status LED config: pin=16 activeHigh=0
configPassword: password
*WM: 
*WM: AutoConnect
*WM: Connecting as wifi client...
*WM: Using last saved values, should be faster
*WM: Connection result: 
*WM: 3
*WM: IP Address:
*WM: 10.10.0.30
Configure logging.
RfHandler Instance created.
Configure WebServer.
Starting webserver and websocket server.
WebServer instance created.
Configure rfProtocols.
Configure rfEchoMessages.
Try to (re)connect to MQTT broker
MQTT connected.
MQTT subscribe to topic: rf/send/+
MQTT subscribed.
MQTT instance created.
MDNS service registered.
Change status LED config: pin=16 activeHigh=0
Current configuration:
{
  "deviceName": "rf434",
  "mqttBroker": "10.10.0.152",
  "mqttBrokerPort": 1883,
  "mqttUser": "homeassistant",
  "mqttRetain": false,
  "mqttReceiveTopic": "rf/recv/",
  "mqttSendTopic": "rf/send/",
  "rfEchoMessages": false,
  "rfReceiverPin": 12,
  "rfTransmitterPin": 4,
  "rfReceiverPinPullUp": true,
  "rfProtocols": [],
  "serialLogLevel": "debug",
  "webLogLevel": "debug",
  "syslogLevel": "",
  "syslogHost": "",
  "syslogPort": 514,
  "ledPin": 16,
  "ledActiveHigh": false
}
Listen on IP: 10.10.0.30
Websocket client 0 connected

Exception (9):
epc1=0x40229f03 epc2=0x00000000 epc3=0x00000000 excvaddr=0x566e6b32 depc=0x00000000

ctx: cont 
sp: 3fff1e10 end: 3fff2050 offset: 01a0

>>>stack>>>
3fff1fb0:  3fff1fe0 00000001 0000000e 402188a2  
3fff1fc0:  3fff6e9c 3fff6ae0 00000000 40219032  
3fff1fd0:  732f6672 2f646e65 75706d69 4000736c  
3fff1fe0:  00000001 3fff0dc4 3fff69b0 4020a20d  
3fff1ff0:  401065e0 00000000 00001388 3fff1020  
3fff2000:  00000000 00000000 3fff6ae0 3fff1020  
3fff2010:  3fff0dc0 3fff0dc4 3fff7e24 4020f1a9  
3fff2020:  00000000 00000000 3fff0db8 4022b59d  
3fff2030:  3fffdad0 00000000 3fff1019 40211100  
3fff2040:  feefeffe feefeffe 3fff1030 402134b0  
<<<stack<<<

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x4010f000, len 1384, room 16 
tail 8
chksum 0x2d
csum 0x2d
v00000000
~ld
Load Settings...
Loading config file.
Applying config settings.
Change status LED config: pin=16 activeHigh=0
configPassword: password
*WM: 
*WM: AutoConnect
*WM: Connecting as wifi client...
*WM: Using last saved values, should be faster
*WM: Connection result: 
*WM: 3
*WM: IP Address:
*WM: 10.10.0.30
Configure logging.
RfHandler Instance created.
Configure WebServer.
Starting webserver and websocket server.
WebServer instance created.
Configure rfProtocols.
Configure rfEchoMessages.
Try to (re)connect to MQTT broker
MQTT connected.
MQTT subscribe to topic: rf/send/+
MQTT subscribed.
MQTT instance created.
MDNS service registered.
Change status LED config: pin=16 activeHigh=0
Current configuration:
{
  "deviceName": "rf434",
  "mqttBroker": "10.10.0.152",
  "mqttBrokerPort": 1883,
  "mqttUser": "homeassistant",
  "mqttRetain": false,
  "mqttReceiveTopic": "rf/recv/",
  "mqttSendTopic": "rf/send/",
  "rfEchoMessages": false,
  "rfReceiverPin": 12,
  "rfTransmitterPin": 4,
  "rfReceiverPinPullUp": true,
  "rfProtocols": [],
  "serialLogLevel": "debug",
  "webLogLevel": "debug",
  "syslogLevel": "",
  "syslogHost": "",
  "syslogPort": 514,
  "ledPin": 16,
  "ledActiveHigh": false
}
Listen on IP: 10.10.0.30
Websocket client 0 connected

So clearly the second command should be the correct one as the gw seems to receive it, but something is not working.

Can you clarify if not even having the transmitter connected to the gw should still try send the code right and of course log it right?

I'm running on a ESP-01. I've checked that the SPIFFS is working with the CheckFlashConfig-sketch:

18:42:58.258 -> Flash real id:   001440E0
18:42:58.258 -> Flash real size: 1048576 bytes
18:42:58.258 -> 
18:42:58.258 -> Flash ide  size: 1048576 bytes
18:42:58.258 -> Flash ide speed: 40000000 Hz
18:42:58.258 -> Flash ide mode:  DOUT
18:42:58.258 -> Flash Chip configuration ok.

But MQTT433gateway fails to save settings from the web gui:

Open settings file for write failed!
Ideas?

I'm trying to log into my gateway with an iPhone but can’t access the Frontend (back to http auth. Dialog).

Any idea how to solve this?

the topic does not work "rf434/recv/RAW/"

It seems like the compiled binaries use the default PubSubClient payload limit of 128 bytes, which is insufficient for sending RAW codes for some of my remotes. It would probably make sense to increase this limit.

Hello, I have a problem with sending mqtt from node red to MQTT433gateway protocol clarus.
The subject I send to is rf434 / send / clarus_switch
or rf434 / send / rev2_switch
the code received from the remote control is
"rf signal received: {" id ":" A3 "," unit ": 4," state ":" on "} with protocol clarus_switch deviceID = A3"
and tries to send with such syntax {"id": "A3", "unit": 4, "state": "on"} what am I doing wrong? What is the correct syntax for MQTT433gateway to pick up mqtt from node red?
I tried in many ways but I always get some error : "transmitting failed: message is invalid" , "message is not a proper json object" or insufficient number of arguments, what is the correct syntax ?
When i send
"id": "A3",
"unit": 4,
"state": "ON"
it returns me such an error: pilight(3): clarus_switch: insufficient number of arguments
transmitting failed: message is invalid

hey there
after few hour of no transmission first transmission is ignored

I run it on a nodemcu with rxb6 receiver

any ideas
thanks

Hi,

can you please release a current version?
As i can see, the last release is very old.

thanks

Hi I'm trying to upload the MQTT433gateway sketch I have all the relevant libraries but i seems to be getting errors when compiling any ideas..

In file included from sketch/src/ESPiLight.cpp:22:0: sketch/src/pilight/libs/pilight/protocols/protocol.h:26:26: fatal error: ../core/json.h: No such file or directory #include "../core/json.h" ^ compilation terminated.
Thanks in advance Andy

Hi i have some strange issues with the MQTT433gateway.
When using an RXB6 with the NodeMCU 2 i don't receive anything if i switch to another cheap chinese rx module it works. but i really wanna use the RXB6 for better reception clear messages from my 433 devices. i have checked all the wiring and it is good.
If switch to raw mode i get something? See:

rfESP_a39b1c/recvRaw c:00122314;p:1430,1034,757,1705,6029@ rfESP_a39b1c/recvRaw c:011234;p:5012,3736,3086,1389,10979@ rfESP_a39b1c/recvRaw c:012324506;p:283,4212,1014,3464,545,3921,8722@ rfESP_a39b1c/recvRaw c:01001010002;p:993,3550,15592@ rfESP_a39b1c/recvRaw c:012344;p:1130,3497,993,400,6926@ rfESP_a39b1c/recvRaw c:012234;p:1679,3477,1061,737,6642@ rfESP_a39b1c/recvRaw c:01234;p:1270,929,3543,671,8384@ rfESP_a39b1c/recvRaw c:011234115;p:3602,991,3487,699,3863,6021@ rfESP_a39b1c/recvRaw c:00102;p:950,3529,12936@ rfESP_a39b1c/recvRaw c:0123456;p:1959,868,3637,1007,1255,3994,6437@ rfESP_a39b1c/recvRaw c:012323224;p:386,3957,791,3580,13357@ rfESP_a39b1c/recvRaw c:01010102;p:817,3536,8474@ rfESP_a39b1c/recvRaw c:010101002;p:819,3542,13322@ rfESP_a39b1c/recvRaw c:01010102;p:896,3476,8392@ rfESP_a39b1c/recvRaw c:010101002;p:876,3487,13337@ rfESP_a39b1c/recvRaw c:01010102;p:870,3504,8437@ rfESP_a39b1c/recvRaw c:010101002;p:834,3514,13343@ rfESP_a39b1c/recvRaw c:01010102;p:847,3521,8427@ rfESP_a39b1c/recvRaw c:010101002;p:833,3523,13363@ rfESP_a39b1c/recvRaw c:01010102;p:842,3525,8441@ rfESP_a39b1c/recvRaw c:010101002;p:825,3507,13344@ rfESP_a39b1c/recvRaw c:01010102;p:849,3517,8451@ rfESP_a39b1c/recvRaw c:010101002;p:836,3517,13343@ rfESP_a39b1c/recvRaw c:01010102;p:844,3519,8449@ rfESP_a39b1c/recvRaw c:01010100101012;p:1010,3476,6032@ rfESP_a39b1c/recvRaw c:00102;p:1028,3504,6018@ rfESP_a39b1c/recvRaw c:010101001010123;p:1027,3464,1346,8213@ rfESP_a39b1c/recvRaw c:01010100101012;p:1016,3498,6020@ rfESP_a39b1c/recvRaw c:0100101012;p:994,3508,5984@ rfESP_a39b1c/recvRaw c:01010100101012;p:982,3517,6014@ rfESP_a39b1c/recvRaw c:01010100102;p:955,3520,8061@ rfESP_a39b1c/recvRaw c:010102010101345607;p:998,3518,4478,519,3036,2116,3885,6037@ rfESP_a39b1c/recvRaw c:01010100101012;p:989,3509,5979@ rfESP_a39b1c/recvRaw c:01234567;p:3095,1583,4480,265,882,679,1400,9353@ rfESP_a39b1c/recvRaw c:0101012;p:1068,3472,6024@ rfESP_a39b1c/recvRaw c:0101002;p:796,3563,13315@ rfESP_a39b1c/recvRaw c:01010102;p:861,3500,8440@ rfESP_a39b1c/recvRaw c:010101002;p:857,3515,13284@ rfESP_a39b1c/recvRaw c:01010102;p:917,3455,8368@ rfESP_a39b1c/recvRaw c:010101002;p:917,3448,13261@ rfESP_a39b1c/recvRaw c:01010102;p:906,3458,8371@ rfESP_a39b1c/recvRaw c:010101002;p:886,3479,13299@ rfESP_a39b1c/recvRaw c:01010102;p:900,3462,8387@ rfESP_a39b1c/recvRaw c:010101002;p:879,3493,13299@ rfESP_a39b1c/recvRaw c:01010102;p:895,3478,8404@ rfESP_a39b1c/recvRaw c:010101002;p:894,3459,13291@ rfESP_a39b1c/recvRaw c:01010102;p:885,3493,8399@ rfESP_a39b1c/recvRaw c:010101002;p:881,3484,13297@ rfESP_a39b1c/recvRaw c:01010102;p:885,3501,8399@ rfESP_a39b1c/recvRaw c:01234;p:1248,404,3582,2210,14301@ rfESP_a39b1c/recvRaw c:0101010010101234405;p:1045,3460,1798,3010,4639,5990@ rfESP_a39b1c/recvRaw c:010101001010123;p:1069,3413,3226,6365@ rfESP_a39b1c/recvRaw c:0101001010123;p:1053,3477,4786,11786@ rfESP_a39b1c/recvRaw c:0100101223134;p:1071,3460,3035,434,6588@ rfESP_a39b1c/recvRaw c:010100101234;p:1040,3435,680,3817,6076@ rfESP_a39b1c/recvRaw c:010101002;p:1084,3456,7996@ rfESP_a39b1c/recvRaw c:001010123;p:992,3462,4492,12012@ rfESP_a39b1c/recvRaw c:010101201010123245640278749:44;;p:1063,3458,3043,2473,787,1407,3282,379,914,183,500,8436@ rfESP_a39b1c/recvRaw c:01002;p:873,3497,13306@ rfESP_a39b1c/recvRaw c:01010102;p:910,3462,8377@ rfESP_a39b1c/recvRaw c:010101002;p:896,3427,13221@ rfESP_a39b1c/recvRaw c:01010102;p:980,3382,8307@ rfESP_a39b1c/recvRaw c:010101002;p:952,3409,13237@ rfESP_a39b1c/recvRaw c:01010102;p:942,3424,8368@ rfESP_a39b1c/recvRaw c:010101002;p:923,3374,13264@ rfESP_a39b1c/recvRaw c:01010102;p:931,3430,8350@ rfESP_a39b1c/recvRaw c:010101002;p:921,3430,13256@ rfESP_a39b1c/recvRaw c:01010102;p:922,3422,8358@ rfESP_a39b1c/recvRaw c:010101002;p:915,3436,13261@ rfESP_a39b1c/recvRaw c:01010102;p:925,3445,8360@ rfESP_a39b1c/recvRaw c:010101002;p:909,3435,13258@ rfESP_a39b1c/recvRaw c:01010102;p:938,3437,8369@ rfESP_a39b1c/recvRaw c:00120203456;p:2919,4193,1790,492,2792,3409,13156@ rfESP_a39b1c/recvRaw c:012123;p:808,3348,1162,7951@ rfESP_a39b1c/recvRaw c:0010101230405;p:1124,3425,653,3047,4796,5966@ rfESP_a39b1c/recvRaw c:012202302024567;p:1092,4419,3433,608,900,3628,1598,15036@ rfESP_a39b1c/recvRaw c:01210321442156;p:425,3422,1078,4028,4409,1817,14774@ rfESP_a39b1c/recvRaw c:0010123;p:1066,3418,1472,15127@ rfESP_a39b1c/recvRaw c:010123001014516;p:1088,3420,349,4242,685,3867,13136@ rfESP_a39b1c/recvRaw c:0010102;p:1073,3448,5963@ rfESP_a39b1c/recvRaw c:010100101012;p:1090,3406,5809@ rfESP_a39b1c/recvRaw c:0102010020201343456;p:1098,3564,3445,2548,337,553,7709@ rfESP_a39b1c/recvRaw c:01234256789;p:4320,358,3277,4615,3014,959,1101,3746,1511,5379@ rfESP_a39b1c/recvRaw c:01123;p:2171,171,1083,10522@ rfESP_a39b1c/recvRaw c:0101023045;p:1122,3395,728,3803,382,14153@ rfESP_a39b1c/recvRaw c:00123;p:3457,235,1120,7957@ rfESP_a39b1c/recvRaw c:01234;p:2275,3627,1413,1060,5958@ rfESP_a39b1c/recvRaw c:001023;p:1147,3412,851,12730@ rfESP_a39b1c/recvRaw c:01123;p:4739,4541,669,6418@ rfESP_a39b1c/recvRaw c:0100102;p:1087,3403,7986@ rfESP_a39b1c/recvRaw c:0101010010101223456;p:1102,3399,2875,207,3597,560,6451@ rfESP_a39b1c/recvRaw c:012303004;p:1097,4298,217,3411,12462@ rfESP_a39b1c/recvRaw c:012334;p:343,3670,2953,919,8412@ rfESP_a39b1c/recvRaw c:01002;p:863,3474,13275@ rfESP_a39b1c/recvRaw c:01010102;p:924,3423,8363@ rfESP_a39b1c/recvRaw c:010101002;p:939,3416,13221@ rfESP_a39b1c/recvRaw c:01010102;p:982,3373,8279@ rfESP_a39b1c/recvRaw c:010101002;p:962,3395,13209@ rfESP_a39b1c/recvRaw c:01010102;p:955,3410,8340@ rfESP_a39b1c/recvRaw c:010101002;p:942,3427,13235@ rfESP_a39b1c/recvRaw c:01010102;p:949,3425,8349@ rfESP_a39b1c/recvRaw c:010101002;p:910,3447,13231@ rfESP_a39b1c/recvRaw c:01010102;p:936,3431,8341@ rfESP_a39b1c/recvRaw c:010101002;p:933,3425,13250@ rfESP_a39b1c/recvRaw c:01010102;p:939,3429,8341@ rfESP_a39b1c/recvRaw c:010101002;p:931,3417,13234@ rfESP_a39b1c/recvRaw c:01010102;p:944,3419,8345@ rfESP_a39b1c/recvRaw c:01231405;p:2925,746,1062,1490,418,5238@ rfESP_a39b1c/recvRaw c:01234;p:3325,4215,546,3684,6617@ rfESP_a39b1c/recvRaw c:01234;p:522,2147,1775,1174,5850@ rfESP_a39b1c/recvRaw c:01010120101012;p:1108,3392,6170@ rfESP_a39b1c/recvRaw c:00102;p:1140,3383,7913@ rfESP_a39b1c/recvRaw c:010120101013;p:1093,3389,562,5518@ rfESP_a39b1c/recvRaw c:010101002;p:1115,3361,7912@ rfESP_a39b1c/recvRaw c:01213;p:4627,1267,3452,10369@ rfESP_a39b1c/recvRaw c:010101001010123;p:1115,3365,4038,12529@ rfESP_a39b1c/recvRaw c:00101010010102;p:1112,3355,5672@ rfESP_a39b1c/recvRaw c:010101001010123;p:1110,3385,2743,6819@ rfESP_a39b1c/recvRaw c:01010100101012344567108936:;;p:1116,3373,2520,2968,1966,556,442,2779,732,1349,1814,6906@ rfESP_a39b1c/recvRaw c:010101002;p:901,3460,13236@ rfESP_a39b1c/recvRaw c:01012;p:960,3388,5779@ rfESP_a39b1c/recvRaw c:010101002;p:957,3401,13179@ rfESP_a39b1c/recvRaw c:01012;p:1021,3334,5823@ rfESP_a39b1c/recvRaw c:010101002;p:1007,3368,13203@ rfESP_a39b1c/recvRaw c:01012;p:982,3376,5791@ rfESP_a39b1c/recvRaw c:010101002;p:977,3394,13231@ rfESP_a39b1c/recvRaw c:01012;p:971,3387,5807@ rfESP_a39b1c/recvRaw c:010101002;p:963,3401,13212@ rfESP_a39b1c/recvRaw c:01012;p:979,3382,5786@ rfESP_a39b1c/recvRaw c:010101002;p:977,3390,13215@ rfESP_a39b1c/recvRaw c:01012;p:976,3387,5791@ rfESP_a39b1c/recvRaw c:010101002;p:970,3385,13203@ rfESP_a39b1c/recvRaw c:012345;p:977,3379,3830,589,1157,15382@ rfESP_a39b1c/recvRaw c:0100101234;p:1148,3326,4540,2205,7388@ rfESP_a39b1c/recvRaw c:012322323456789;p:469,4062,1133,3391,841,3697,298,4713,978,10605@ rfESP_a39b1c/recvRaw c:0100101010010123;p:1137,3345,618,9255@ rfESP_a39b1c/recvRaw c:010101010101203;p:1143,3340,2427,5895@ rfESP_a39b1c/recvRaw c:010120103;p:1139,3354,493,7923@ rfESP_a39b1c/recvRaw c:01232323425;p:4532,983,1121,3405,631,5872@ rfESP_a39b1c/recvRaw c:01010100102;p:1140,3367,7896@ rfESP_a39b1c/recvRaw c:01234;p:4736,710,4031,1263,5801@ rfESP_a39b1c/recvRaw c:01221212134;p:277,3392,1126,3018,6445@

I have tired the RXB6 with another sketch (OpenMQTTGateway) and i am receiving fine.

There is another MQTT-Gateway project under active development.

https://github.com/1technophile/OpenMQTTGateway

I believe that both projects address the same idea.
They both developed in different directions

Differences to the MQTT433Gateway

1. Supports officially ESP32 and ESP8266
2. Supports other hardware, BLE, IR, direct Sensors, RFM69, GSM, etc.
3. Programming structure keeps it open for other Protocols as well (Zigbee, Zwave, Enocean)

Differences of this project to the OpenMQTTGateway

1. User interface for configuration (now very newbie friendly)
2. Uses the an own version of the pilight lib and hence supports many 433 MHz devices

I think both projects would benefit from each other and we might have at the end an ultimate Foo2MQTT-Gateway system, which ideally is even newbie friendly enough for non-programmers.

Hi,
after recompiling and flashing, the gateway can't connect to the MQTT Broker.

1. Set-up
   Mosquito Broker on a HASS.IO-based HA RPi Server
   Wemos d1mini for the gateway v0.1.0-19-ge818a313
   Firmware build was the current version from GIT
2. Error Message in the logs
   From the Gateway:
   Try to (re)connect to MQTT broker
   MQTT connect failed!
   From the Mosquito mqtt Broker log:
   1541889226: Socket error on client , disconnecting.
   1541889231: New connection from 192.168.3.129 on port 1883.

I use a login for MQTT but tried as well without login and anonymous login without success.
Reversing back to 1.0.0 works with the given login credentials.

please add more protocols
with thanks phill

Hi, i had the problem, that i could only rarely get MQTT Messages from some devices even if they are really nearby. The Problem is, that these devices only send the messages 2 times (sometimes only one time?), and due to noise i often get only one message with valid checksum. But the "status" is set only to VALID if there are 2 messages in short time. Why? After changing VALID to FIRST in line 104 in RfHandler.cpp i get enough MQTT messages from the device even from a far range.