-
Notifications
You must be signed in to change notification settings - Fork 46
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
Comments
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. |
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. |
I forked the repo and I'll see if I have time to create a two-step gateway option. |
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. |
On earlier versions (until 0.5) EnigmaIot works whit two ESP8266, one for
EspNow, one for mqtt (WiFi) connected by serial port.
Maybe you were referring to this
El sáb, 15 jun 2024, 21:02, rajtan ***@***.***> escribió:
… 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.
—
Reply to this email directly, view it on GitHub
<#51 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD7NRUMGDRRH655UKZGHZRTZHSFVZAVCNFSM6AAAAABJL5CF7WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZQGUZTGMJYG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
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.
The text was updated successfully, but these errors were encountered: