433mhz, infrared IR to and from MQTT on ESP8266

Thanks mate!

1 Like

Hi, I successfully upload the code and its working fine. I have a RF motion and door sensor.

I want to make automation that if motion detect show “Motion Detected” if no motion show “Stand By” and if door is close show “Door Close” if open show “Door Open”.

Can somebody help me to make automation?
I receive code from motion sensor “9069033” and receive two code form door sensor close code “9242062” and open code “9242058”.

Thanks in advance,

Hi,

Your request is unclear. Do you want an action performed when any of the events (motion detected, door closed, door open) is fired? Or do you want a sensor that will display the messages that you mentioned? Also, what’s happening if there is motion detected and the door is open?

Could you post the binary sensors for open door and motion sensors? Do you have an automation to reset PIR sensor (as PIR sensors do not send an “off” code, each time a motion is detected the same code is received thus HA won’t be able to consider it as a trigger)?

Does the sonoff bridge support both 433 and 315mhz?

If not is there a good solution for getting both working?

On sonoff RF bridge I don’t think so. On ESP8266 or ESP32 you can have both working, more info on this request:
https://github.com/1technophile/OpenMQTTGateway/issues/140

OpenMQTTGateway compatible with ESP32, I have opened a specific thread for this chip:

1 Like

Hi @Florian,

Could you also provide a compiled binary for ESP32 dev module? I think that NodeMCU flasher can work also with ESP32.

There are a lot of compiling errors on 0.6 with Arduino 1.8.5.

Thanks

I assume you meant to address @1technophile instead of me :wink:

Right :slight_smile:

Hi there,

I guess I should open another topic, but it’s closed related :-). Thanks again @1technophile and contributors to make the code compatible with the esp32. Since I’m mostly interested in BLE the esp32 is perfect. I did the little modification to the advertisedDevice.haveRSSI() so it reports the devices on a room topic and it’s working fine with the mqtt_room component.

I know that the code is still in “beta” but I can see that from time to time the esp32 disconnect/connect again to the MQTT. How may I help to debug this (btw, using version 0.6.1)?

Hi,

Could you indicate the following info please:
-time between disconnections
-version of your mqtt broker
-does it disconnect to the wifi also?
-did you experienced mqtt disconnection with another device?

Hello all,
im struggling a strange problem with gateway… actually i have 2 problems:
1-when i first starts my nodemcu it will only connect to broker if i open the serial monitor. after connection establish to the broker i can close the Serial mon and it will continue to work as it should.
2-After node establish the connection it will fire the what seems the last command was on memory so every time it start it will trigger my rf relay, if i will restart the broker it will send the last rf command also im using rf433 to mqtt and mqtt to rf433
can anyone point me for a solution?

hi,

Still in the early stages of testing, but at first I was using a Mosquitto version 1.4.8 running on a virtualbox ubuntu 16.04 vm. Now I’m using my “production” Mosquito (same version) and across the internet and it seems stable. No disconnection oth the wifi was observed before. It seemed to disconnect about once a minute or two.

btw… I’m using a no-ip domain as my mqtt broker and it’s working fine so far.

On a side note, it seems that the esp32 gets a little hot comparing to the esp8266, isnt it?

Hi, could you try some basics config like:
basic pubsub example from pubsubclient library and a local broker

Here my feedback with my DOIT ESP32 board:

  • last ESP32 arduino env sync
  • libraries as stated in the wiki
  • mosquitto v3.1.1 on a local network
  • connected to MQTT via IP adress
  • using RF, RF2 and BT gateways

ESP32 getting tidy I think <30°

Working without disconnection since 1 hour

Hi,

My esp32 is running at 33c, so perhaps it’s not that hot :-). The connection with my mqtt server seems somewhat stable. I left it running yesterday and it was ok for about 15hrs and then disconnected and stay offline. My guess is that it couldnt handle the IP change, but not sure. What should happen if you use a FQDN instead of a IP in configuration? Should it try to resolve the name at every connection attempt?

Hi,

really don’t know how a FQDN influence this, I searched what it is but don’t catch the impact, could you give me some inputs?

Hi,

Sure. What I meant is that I have a dyndns domain so i can access my homeserver from outside using a “Fully Qualified Domain Name” (FQDN) which is simple what we know as domain name. So, inside my user_config.h configuration instead of using a “define mqtt_server 192.x.x.x”, I have something like “define mqtt_server myhome.homelinux.net”. The problem with my domain name, is that my dsl ip changes from time to time, so now myhome.homelinux.net may resolve (“translate”) as one ip, and one hour from now, may resolve to another ip.

When the esp32 starts, it resolves the domain to a IP. Later in the day my IP changes and the connection to the MQTT drops. My question is, when this happens, what the device try to do? It try to connect to the same IP as it first resolved or it try to resolve the domain name again?

Hi @clyra,

Do you connect a router behind the xdsl modem?

If not, may I suggest using a DDNS service for internet connection to resolve on your public IP and dnsmasq for resolving to router’s WAN IP connected behind the modem (as most probably the xdsl modem is locked up)? You could do this with basically any DD-WRT compatible router.

Although it ends up in a double NAT environment (and it would be a little more difficult to setup DDNS), you can access the MQTT broker with the same myhome.homelinux.net address on both internet and LAN.

Hi @Petrica

Sorry for my bad english… I do have a DDNS service and I can connect from outside (my esp32 is at my workplace).

But I’m trying a new approach now. I’m running a MQTT at the remote location and did a MQTT bridge connection from my lan to this location (there I have a fixed IP). So far so good…

I’m finally starting to get into this and following the wiki on your github.

I think I’ve got everything sorted out except one thing (so far…). Maybe it’s not even an issue.

I keep seeing references to #ifdef related to which module you are using (ESP8266, ESP32 or Arduino).

The only thing I can’t find is where the module type is actually defined. Does it automatically figure out what the module is that it’s loaded onto or am I missing where it’s defined?

I’ve looked and looked and can’t find it anywhere.