Connecting to 192.168.0.100

Blynk Servers Local Blynk Server
1

this morning I got an issue :slight_smile:

[21992] Connecting to alex69
[24496] Connected to WiFi
08:36:58.958 -> [24496] IP: 192.168.0.10
08:36:58.958 -> [24496] 
08:36:58.958 ->     ___  __          __
08:36:58.958 ->    / _ )/ /_ _____  / /__
08:36:58.958 ->   / _  / / // / _ \/  '_/
08:36:58.958 ->  /____/_/\_, /_//_/_/\_\
08:36:58.958 ->         /___/ v0.5.4 on NodeMCU
08:36:58.958 -> 
08:36:58.958 -> [24503] Connecting to 192.168.0.100
[29503] Connecting to 192.168.0.100
[34504] Connecting to 192.168.0.100
[39505] Connecting to 192.168.0.100
[44506] Connecting to 192.168.0.100
[49507] Connecting to 192.168.0.100
[54508] Connecting to 192.168.0.100
[59509] Connecting to 192.168.0.100
[64510] Connecting to 192.168.0.100
[69511] Connecting to 192.168.0.100

I must say that this nodeMCU ran well yesterday, I stopped it at midnight.(it is my blynk test MCU)

I have another node MCU ( MCU in prod ) working on my local blynk server for a month with the same sketch, another IP address and another Blynk auth.

I wonder why the IP is 192.168.0.10 at first, because I wrote an fix IP
IPAddress ipMCU56 (192, 168, 0, 56);

I suspect mac address and DHCP leases, am I wrong ?

2

I reply to myself

it was a DHCP issue

I have a TP-LINK repeater witch was configured with DHCP on “auto” by default !
changed to OFF resolved that issue
:smile:

3

If you’ve specified a static IP address for your NodeMCU then DHCP leases shouldn’t come into the equation.

Are you sure you’ve no accidentally updated the code on this test NodeMCU (maybe via a OTA upload)? Do you have some sort of scheduled HTTP OTA update process that ran at midnight and re-flashed the wrong .bin file to your NodeMCU?

Pete.

1 Like
4

thank you Pete.
yes I am sure, and this nodemecu is on my USB port. :wink:
since I changed DHCP to off, nodemecu came online at 192.168.0.56.
I think the problem is between my ISP box DHCP and the Dlink DHCP auto .
now all works fine.

1 Like
5

Put manual IP outside the DHCP pool to stop IP conflicting

6

… and use only one DHCP server in the local network.

1 Like
7

:smile:

read my messages!

I know all of that :wink:

I said that the reapeter was DHCP auto by default,
anyway, DHCP pool is outside the DHCP local server.
I discovered the limit of the plug and play !
:smile:

8

192.168.0.56 is already out of the DHCP pool.
the 1st DHCP server is 10 to 50
and the second was 100 to 2xx
the second DHCP server is disable, so now, everything works well
:wink:

2 Likes