Fixed IP seems not working

[Domosapiens]

@Grovkillen
Not sure if this an App problem or an ESPEasy problem

Using an old Vista PC. (WIN7 still not working)

Flash empty 4K goes well
Flash mega 20181101 goes well
Post flash action with no Admin password, Fixed IP and 2# SSID/Password
Post flash action seems to go well but ...
does not come out of the communication check wait loop at the end.

After termination and reboot:
the terminal shows ... not a valid wifi setting
terminal Settings command shows 0.0.0.0 as IP
terminal IP command accepts my input for a valid IP number.
terminal Save command
terminal Reboot command
After reboot
the terminal shows ... not a valid wifi setting
Settings command shows 0.0.0.0 as IP

Is the terminal IP command not working ??? and therefore the App not working with fixed IP?

Tried without the fixed IP
it does not come out of the communication check wait loop at the end.
After termination and reboot I need to use the terminal to discover the allocated IP,
to use that to change it to a fixed IP

[Grovkillen]

I got the same issue. Must look into that. Sometimes the flasher do not get a response in the serial and the only way forward is then to power toggle or press the reset button. Serial programming is not 100% accurate I have come to find out, at least not always responding accordingly. But I will fix the issue with the IP not being set.

[Grovkillen]

I have found the issue... before the ESP would interpret the blank DNS and GW settings as a variant of the set IP...

IP set to 192.168.1.123 would render a DNS and GW setting as 192.168.1.1

[Grovkillen]

We're working on it now... (adding commands for those settings within ESP Easy)

[Domosapiens]

Great that you found something ..... but
If you set Esp IP to 192.168.1.123 (assuming GW is 192.168.1.1)
Then what is wrong with "would render a DNS and GW setting as 192.168.1.1"
That's what I have now. Is my current setting wrong?

I have a local time server on 192.168.1.7. (fixed)
For what do I need a DNS when using fixed IP's?
Is this a local DNS to discover and access the ESP's by name?
Since latest releases ... Note: Leave empty for DHCP ... an empty ESP DNS field is not an option anymore.

[Grovkillen]

Your settings are correct but my flasher will not (currently) save it like that. Only the IP field will be filled, the others will be blank and your node will not be responsive. But we'll get this fixed very soon. Den mån 5 nov. 2018 10:48 skrev Domosapiens <notifications@github.com>:

…

Great that you found something ..... but If you set Esp IP to 192.168.1.123 (assuming GW is 192.168.1.1) Then what is wrong with "would render a DNS and GW setting as 192.168.1.1" That's what I have now. Is my current setting wrong? [image: client ip settings] <https://user-images.githubusercontent.com/35063211/47989858-4c2e4200-e0e6-11e8-9341-e72843ba5bbc.JPG> I have a local time server on 192.168.1.7. (fixed) For what do I need a DNS when using fixed IP's? Is this a local DNS to discover and access the ESP's by name? Since latest releases ... Note: Leave empty for DHCP ... an empty ESP DNS field is not an option anymore. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#11 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AZeBYgyi3BSepw9UNPL4_LOmbfoCkK99ks5usAligaJpZM4YM_xW> .

[Grovkillen]

Fixed in 0.02.004