Thanks for all the quick responses, sorry for the radio silence from my side (unfortunate private stuff).
As you replied I also thought the same, I investigated versions of the board (v2,v3 etc), rf (srx, cheap ali devs) etc etc.
So I have been working on stripping and creating a lightweight version of openMQTTgateway 0.8 only for 433 RF2 srx882 kaku, NodeMCU v2. It still hasn’t broke and works as I expected the full version would. At the moment Receiving works fine, I am now working on sending messages via MQTT and RF (hope to finish this week). If you like and give permission I will publish the code and or hand it over for further publication and or analysis.
I have no problem with forks you can let it published,
If you find something usefull for OMG main repository and users you can submit a pull request, you will so contribute your turn to the project.
Especially if you succeed in making work RF and RF2 together for sending and receiving it will be great to incorporate your code.
Or if you have other finds pull requests are welcome.
My apologies for the late response, the past few days were very busy (private and business), that meant I coudn’t work on this project. I will come online and back when I finished the first setup and got this stable.
Thanks for the tips, been working on the combination of receiving and sending RF signals. Somehow it’s not stable right now (stripping all access code). I will look into the combination and incorperating pilight for more protocols later.
Current issue is when starting to receive MQTT messages and sending these via RF2 the RF2 Receiving stops processing of receiving RF signals (some kind of race that degradates functionalities). When I get this working I will come online
I’ve been banging my head up against a wall with this one too. I’ve tried everything to get the SRX882 going. It doesn’t appear to work with the RFSwitch Receive simple sketch. I’ve connected vcc, gnd and data, as well as shorting CS to VCC to no avail. I’ve used D2 and D3 as inputs and as ZgatewayRF and ZgatewayRF2.
I think I’m going to have to put a scope on it to see what’s going on.
Well. I just like platformIO (atom) more because it’s loading needed boards allone. Otherwise be prebuilt images, like espeasy or tasmota would be awesome. But there is then of cause the setup problem.
I might have just to bite throu it and try it again with this aweful Heltek ESP32 WiFi kit
It should be possible to use several i2c sensors on one i2c bus. If using the same kind of sensor you may run into a situation where both use the same bus ID and you will have to change one of them… Been there, done that. (it was a while ago, and I don’t remember the details but shouldn’t be difficult to find how).
What would be a good way to define an efficient script for handling the different RF codes which my gateway will be receiving?
Currently i have multiple scripts, one for each service (1 for RM pro to turn on/off RF devices, 1 for the xiaomi vacuum platform, etc.) and each of them has a long list of if/else statements in lieu of a switch case. Each “if” sends the desired data template to the service based on the received RF code.
I’m just wondering if this will become cumbersome as more RF commands are added.
