Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FR: Is there a way to seperate MQTT client from ESP-Now controller? #51

Open
JoostAB opened this issue Jan 3, 2023 · 5 comments
Open

Comments

@JoostAB
Copy link

JoostAB commented Jan 3, 2023

I was wondering if there is already a way implemented to seperate MQTT client from ESP-Now controller, so that I can build the gateway from two seperate esp's. That way the ESP-Now network can use it's own channel.
I searched the code but could not find it.

@dgcasana
Copy link

dgcasana commented Jan 3, 2023

At this moment the Esp-Now channel (WiFi) is already selected when configuring the gateway so you can use a different channel than your WiFi, I do not know if that is your question.
On the other hand in examples you have "GatewayDummy" in which you could implement for example an output to serial port, (in the first version 0.5 two esp8266 communicated per serial port were used one for Esp-Now and another for WiFi / mqtt).
An implementation with serial port output would be very good, I would connect it directly to my raspberry, removing load to mqtt (tasmota, zigbee2mqtt ...)

@JoostAB
Copy link
Author

JoostAB commented Jan 4, 2023

Problem is that the wifi channel can change. In that case the esp-now channel has to follow. I know a node will search for the controller if it can't connect on the old channel, but there will be a down-time. Also, with a lot of nodes the esp-now network will interfere with your wifi if it's using the same channel.
Why was that changed after 0.5?

@JoostAB
Copy link
Author

JoostAB commented Jan 4, 2023

I forked the repo and I'll see if I have time to create a two-step gateway option.

@rajtan
Copy link

rajtan commented Jun 15, 2024

I have not tried it with EnigmaIOT but did successfully test it with other esp-now test runs. You may use serial communication (may be softserial as well). You send the esp-now messages or the messaages to be published to serial port, which is connected to other microcontroller or computer, wherein you run a serial listening server. Upon successful transfer of message to the port (you may optionally add CRC) you simply publish it from the MQTT client on the other system.

@dgcasana
Copy link

dgcasana commented Jun 21, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants