You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure if this is an issue, but I find it interesting.
Tried the code on Wemos D1. Everything works no problems.
The module logs on on 192.168.1.107 and if I go to that ip I see the text of ḧumidifier control and everything works.
However, when I loaded the same code on a NodeMCU, that worked as well, but, when I happened to check my AP list, I noticed there was a new AP named AI-Thinkerxxxxxx, which ofcourse was my NodeMCU. I connected to that one, went to 192.168.4.1.. also got the "Humidifier Control" screen that was working perfectly albeit publicly accessible to everyone.
I checked again with the Wemos D1: no AP, just webserver on my LAN, checked NodeMCU again: AP AND webserver on my LAN, working simultaneously.
Interesting
The text was updated successfully, but these errors were encountered:
I am not sure if this is an issue, but I find it interesting.
Tried the code on Wemos D1. Everything works no problems.
The module logs on on 192.168.1.107 and if I go to that ip I see the text of ḧumidifier control and everything works.
However, when I loaded the same code on a NodeMCU, that worked as well, but, when I happened to check my AP list, I noticed there was a new AP named AI-Thinkerxxxxxx, which ofcourse was my NodeMCU. I connected to that one, went to 192.168.4.1.. also got the "Humidifier Control" screen that was working perfectly albeit publicly accessible to everyone.
I checked again with the Wemos D1: no AP, just webserver on my LAN, checked NodeMCU again: AP AND webserver on my LAN, working simultaneously.
Interesting
The text was updated successfully, but these errors were encountered: