433mhz, infrared IR to and from MQTT on ESP8266

Petrica · January 2, 2018, 8:13pm

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

Florian · January 2, 2018, 9:00pm

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

Petrica · January 2, 2018, 9:05pm

Right

clyra · January 17, 2018, 6:20pm

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)?

1technophile · January 17, 2018, 7:35pm

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?

potzkin · January 18, 2018, 12:15pm

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?

clyra · January 18, 2018, 12:38pm

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?

1technophile · January 18, 2018, 9:46pm

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

clyra · January 19, 2018, 1:43pm

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?

1technophile · January 19, 2018, 5:28pm

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?

clyra · January 19, 2018, 6:20pm

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?

Petrica · January 19, 2018, 8:55pm

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.

clyra · January 20, 2018, 1:19am

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…

finity · January 20, 2018, 6:51am

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.

Petrica · January 20, 2018, 7:11am

Hi @finity

The sketch can be used to power up different hardware.

You define specific hardware module in Arduino IDE -> Tools -> Board

finity · January 20, 2018, 7:13am

I get that but is that the only place that the definition comes from is when you compile it for your specific board?

The definition isn’t defined in the actual code?

finity · January 20, 2018, 7:17am

And while I’m here…

I came up with another question.

I would like to use the gateway for 315mHz stuff too.

I’ve followed the github issues thread and created all the required files and made the changes to the main file.

the only thing there I dont follow is 1technophile’s comment here:

I will try first to connect both emitter data pins together. Regarding receiver i think you will have to duplicate the gateway and connect each receiver to different pins; produve several instance of myswitch depending on the pin.

What does he mean by that?

I see in both RF files they use the same pins. I think I can confidently assume that you can’t do that (or can you? ). If not which pins can I use instead?

Petrica · January 20, 2018, 7:17am

It will compile depending on your board (and what modules you select in user_config.h) by including only those elements.

Afterwards, you need to pay specific attention to the pins for your actual board.

finity · January 20, 2018, 7:18am

Alright! I’ll give it a try.

Thanks!

finity · January 20, 2018, 7:21am

@Petrica

And it seems that we are playing reply leapfrog.

Did you notice the post of mine right above your last one about 315mHz stuff?