search

letscontrolit / ESPEasy

Easy MultiSensor device based on ESP8266/ESP32
http://www.espeasy.com
Other
3.22k stars 2.2k forks source link

Problems with the current mega version #1238

Closed micropet closed 1 year ago

micropet commented 6 years ago

Good Morning all. The current mega version is not really working yet. Board Wemos D1 without external hardware compiled with Arduino 1.8.5. I get:

19802 : WIFI : Connected! AP: SMC (C8:0E:14:05:BC:C6) Ch: 11 Duration: 3777 ms 19803 : EVENT: WiFi#ChangedAccesspoint 19824 : WIFI : DHCP IP: 192.168.0.201 (ESP-201-1) GW: 192.168.0.3 SN: 255.255.255.0 duration: 23 ms 19835 : EVENT: WiFi#Connected 19934 : MQTT : Intentional reconnect 24958 : MQTT : Failed to connect to broker 32012 : Current Time Zone: DST time start: 2018-03-25 02:00:00 offset: 120 minSTD time start: 2018-10-28 03:00:00 offset: 60 min 32013 : EVENT: Time#Initialized 32020 : EVENT: Clock#Time=Fri,08:37 32023 : MQTT : Intentional reconnect 37047 : MQTT : Failed to connect to broker 37056 : MQTT : Intentional reconnect 42078 : MQTT : Failed to connect to broker 42085 : MQTT : Intentional reconnect 47109 : MQTT : Failed to connect to broker 47115 : WD : Uptime 1 ConnectFailures 0 FreeMem 12256 47116 : MQTT : Intentional reconnect 52139 : MQTT : Failed to connect to broker 52141 : MQTT : Intentional reconnect 57164 : MQTT : Failed to connect to broker 57170 : MQTT : Intentional reconnect 62195 : MQTT : Failed to connect to broker 62202 : MQTT : Intentional reconnect 67228 : MQTT : Failed to connect to broker 67237 : MQTT : Intentional reconnect 72261 : MQTT : Failed to connect to broker 72269 : MQTT : Intentional reconnect 77292 : MQTT : Failed to connect to broker 77297 : WD : Uptime 1 ConnectFailures 0 FreeMem 12560 77298 : MQTT : Intentional reconnect 82321 : MQTT : Failed to connect to broker 82327 : WIFI : AP Mode Disabled for SSID: ESP-201_1 82328 : WIFI : Set WiFi to STA 82344 : EVENT: WiFi#Disconnected 82347 : WIFI : Disconnected! Reason: 'Assoc leave' Connected for 1 m 2 s 82347 : WIFI : Connecting SMC attempt #0 83546 : WIFI : Connected! AP: SMC (C8:0E:14:05:BC:C6) Ch: 11 Duration: 1198 ms 83565 : WIFI : DHCP IP: 192.168.0.201 (ESP-201-1) GW: 192.168.0.3 SN: 255.255.255.0 duration: 19 ms 83577 : EVENT: WiFi#Connected 83676 : MQTT : Intentional reconnect 83751 : MQTT : Connected to broker with client ID: ESPClient_5C:CF:7F:0B:68:52 83753 : Subscribed to: ESP-201/# 83754 : EVENT: MQTT#Connected 84617 : EVENT: Time#Set done.

ets Jan 8 2013,rst cause:4, boot mode:(1,7)

wdt reset

TD-er commented 6 years ago

What version is this? (file used to flash, or preset used to build yourself)

And did you also test a reset/restart of the node after flashing and setup of wifi?

micropet commented 6 years ago

Self-compiled. The wifi settings are still saved because the device was still online until yesterday. Reset and poweroff was done.

Oh, after about 15 times Poweroff it works. I have to watch that now.

TD-er commented 6 years ago

That's really strange. Maybe it is trying to fast and deciding to give up too soon?

TD-er commented 6 years ago

What version did you compile? 'normal' or one of the others? The normal uses core 2.4.0, which fixes some issues wrt. wifi. You can see the used core version in the info page.

micropet commented 6 years ago

This one:

Firmware Build | 20101 - Mega (core 00000000) GIT version | (custom) Plugins | 71 [Normal] [Testing] [Development] Build Md5 | 4d44355f4d44355f4d44355f4d44355f Md5 check | fail ! Build time | Apr 13 2018 11:26:14 Binary filename | ThisIsTheDummyPlaceHolderForTheBinaryFilename...

At the moment it is running. I'll try another Wemos D1 right away

Is Md5 check | fail OK?

TD-er commented 6 years ago

Yep, since you don't "sign" your builds with the proper MD5sum, like we do with the daily builds.

The 71 plugins indicate "dev" build, but "core 0000..." looks like staging version of core. (Arduino ESP8266 core 2.4.x) If you could try the pre built version of "normal" version. That one uses core 2.4.0 The dev and test versions are built with core 2.3.0, since the 2.4.x version uses too much memory, what will lead to all kinds of issues. In the tests I ran yesterday, I had sometimes issues with saving settings, since the memory was full.

micropet commented 6 years ago

I think that the normal version does not have all the plugins I need.

MH-Z19, VEML6040, SDS011 ....

The Arduino IDE uses Core 2.4.0. I have the ESP8266 sources from here: https://github.com/esp8266/Arduino/commits/master

TD-er commented 6 years ago

I'm not sure about the VEML6040, but the other two are included in the normal version. You can also add others by setting defines. But I really have to look into the memory usage.

v-a-d-e-r commented 6 years ago

@TD-er : A lot of problems now with last night changes. Pls check PM in forum....

TD-er commented 6 years ago

I will later this evening.

wdonker commented 6 years ago

Same problem (as mentioned in post 1) with mega-20180414. And when I reinstall 20180407 (which was ok before) the MQTT connection keeps failing. The log complains about settings CRC so maybe 20180414 broke something there:

INIT : Booting version: mega-20180407 INIT : Warm boot #1 FS : Mounting... FS : Mount successful, used 76555 bytes of 957314 CRC : program checksum ...OK CRC : Settings CRC ...FAIL CRC : SecuritySettings CRC ...OK

micropet commented 6 years ago

Nothing has changed here. The device connects very slowly to the network and it takes a long time until an MQTT connect takes place.

The web server is also rarely reachable.

TD-er commented 6 years ago

How do you connect to the MQTT broker? Hostname or IP?

wdonker commented 6 years ago

My ESP connects using IP. I flashed an empty bin to clear the settings and reflashed 20180407. It's working ok now.

TD-er commented 6 years ago

And the same for the last version? The CRC settings were corrupted (only the unused settings and the checksum) in the last few builds, which was corrected in the 20180413 build. The problem was that there were some settings added at the position of the checksum. So the checksum was incorrect and save would corrupt the settings again. In the last 2 builds, the checksum would be correct again and a simple save in those builds would make the checksum match again.

micropet commented 6 years ago

I use IP for MQTT Server too.

wdonker commented 6 years ago

I tried to do a factory reset and after that upgrade to 20140414 but that did not work. Then I flashed a blank bin and reflashed 20140414 and now it seems to work ok. It still mentioned setting CRC incorrect (also after reboot) and I once saw the Wifi disconnect because of 'async leave' again but it reconnected ok.

Part of the log: INIT : Booting version: mega-20180414 56 : INIT : Warm boot #2 57 : FS : Mounting... 82 : FS : Mount successful, used 75802 bytes of 957314 368 : CRC : program checksum ...OK 376 : CRC : Settings CRC ...FAIL 405 : CRC : SecuritySettings CRC ...OK . . 8275 : MQTT : Intentional reconnect 8315 : MQTT : Connected to broker with client ID: ESPClient_EC:FA:BC:83:22:CD 8316 : Subscribed to: domoticz/out . . 64738 : MQTT : Connection lost 64739 : WIFI : Disconnected! Reason: 'Assoc leave' Connected for 1 m 0 s 64739 : WIFI : Connecting xxxxxxxxxxxx attempt #0 66111 : WIFI : Connected! AP: xxxxxxx Ch: 13 Duration: 1370 ms 69656 : WIFI : DHCP IP: 192.168.178.235 (ESP-Easy-0) GW: 192.168.178.1 SN: 255.255.255.0 duration: 3545 ms 69803 : MQTT : Connected to broker with client ID: ESPClient_EC:FA:BC:83:22:CD

Zixim commented 6 years ago

i use hostname for mqtt, it never connects. if i switch over to ip address, it connects instantly. This is on R20100 with Build time Mar 30 2018 16:13:45

TD-er commented 6 years ago

@Zixim Do you have a DNS server? In the info page you can see what is being used as DNS server. Do other computers on the network use the same DNS and can they resolve the hostname you try to resolve?

My modem/router is my DNS server and that one is able to serve hostnames on my network as DNS. So "domoticz" resolves to 192.168.1.24 in my network, on every computer. Some other routers demand some kind of postfix to the hostnames like "domoticz.box" or some vendor specific string.

TD-er commented 6 years ago

@wdonker the "Assoc leave" means the node itself sent a disconnect and that's what ESPeasy does as a timeout when it set the AP active and nothing is connected to it. The question remains why ESPeasy decided to activate the AP mode. Was it the first boot after flashing?

wdonker commented 6 years ago

I think it was the first boot after flashing but after reboot it happens again (only once it seems).

Edit: it looks like ESPEasy thinks it is changing from AP to STA when it never was AP.

INIT : Booting version: mega-20180414 55 : INIT : Warm boot #4 57 : FS : Mounting... 81 : FS : Mount successful, used 75802 bytes of 957314 369 : CRC : program checksum ...OK 377 : CRC : Settings CRC ...FAIL 405 : CRC : SecuritySettings CRC ...OK 511 : INIT : Free RAM:19256 512 : INIT : I2C 512 : INIT : SPI not enabled 527 : WIFI : Set WiFi to AP+STA 1415 : WIFI : AP Mode ssid will be ESP_Easy_0 with address 192.168.4.1 1416 : WIFI : Connecting xxxxxxxxxx attempt #0 1539 : WD : Uptime 0 ConnectFailures 0 FreeMem 14088 1678 : DHT : Temperature: 21.20 1678 : DHT : Humidity: 43.20 4503 : WIFI : Connected! AP: xxxxxxx (80:29:94:F5:90:E4) Ch: 13 Duration: 3086 ms 8243 : WIFI : DHCP IP: 192.168.178.235 (ESP-Easy-0) GW: 192.168.178.1 SN: 255.255.255.0 duration: 3740 ms 8357 : MQTT : Intentional reconnect 8393 : MQTT : Connected to broker with client ID: ESPClient_EC:FA:BC:83:22:CD 8394 : Subscribed to: domoticz/out 28476 : Current Time Zone: STD time start: 2018-10-28 03:00:00 offset: 60 min 31539 : WD : Uptime 1 ConnectFailures 0 FreeMem 13264 39760 : Ram usage: Webserver only: 5040 including Core: 0 42325 : Ram usage: Webserver only: 4776 including Core: 0 45477 : Ram usage: Webserver only: 4776 including Core: 0 48631 : Ram usage: Webserver only: 3200 including Core: 0 51788 : Ram usage: Webserver only: 3200 including Core: 0 54948 : Ram usage: Webserver only: 3200 including Core: 0 58112 : Ram usage: Webserver only: 3200 including Core: 0 61272 : Ram usage: Webserver only: 3200 including Core: 0 61539 : WD : Uptime 1 ConnectFailures 0 FreeMem 12976 62304 : DHT : Temperature: 21.20 62304 : DHT : Humidity: 43.10 64427 : Ram usage: Webserver only: 3200 including Core: 0 65436 : WIFI : AP Mode Disabled for SSID: ESP_Easy_0 65437 : WIFI : Set WiFi to STA 65453 : MQTT : Connection lost 65453 : WIFI : Disconnected! Reason: 'Assoc leave' Connected for 1 m 0 s 65454 : WIFI : Connecting xxxxxxxxxx attempt #0 65436 : WIFI : AP Mode Disabled for SSID: ESP_Easy_0 65437 : WIFI : Set WiFi to STA 65453 : MQTT : Connection lost 65453 : WIFI : Disconnected! Reason: 'Assoc leave' Connected for 1 m 0 s 65454 : WIFI : Connecting xxxxxxxxxx attempt #0 66828 : WIFI : Connected! AP: xxxxxxxxxx (80:29:94:F5:90:E4) Ch: 13 Duration: 1372 ms 70596 : WIFI : DHCP IP: 192.168.178.235 (ESP-Easy-0) GW: 192.168.178.1 SN: 255.255.255.0 duration: 3768 ms 70842 : Ram usage: Webserver only: 3232 including Core: 0 70896 : MQTT : Connected to broker with client ID: ESPClient_EC:FA:BC:83:22:CD 70897 : Subscribed to: domoticz/out

Zixim commented 6 years ago

@TD-er I posted the answers to all of your questions on the forum : https://www.letscontrolit.com/forum/viewtopic.php?f=6&t=5170

In short : i use the exact same setup/config in other devices/firmwares, and everything works.

micropet commented 6 years ago

This is how it looks right now:

12899 : EVENT: System#Wake 12920 : WIFI : Set WiFi to AP+STA 12923 : WIFI : Error while starting AP Mode with SSID: ESP-201_1 IP: 192.168.0.250 12924 : WIFI : Connecting SMC attempt #0 12930 : OTA : Arduino OTA enabled on port 8266 12942 : EVENT: System#Boot 12951 : ACT : 12965 : ACT : Publish ESP-201/IP,0.0.0.0 12976 : ACT : timerSet,1,60 12987 : ACT : 13017 : WD : Uptime 0 ConnectFailures 0 FreeMem 13120 13049 : DS : Temperature: 19.25 (28-ff-b8-ea-b4-16-3-ed) 13051 : EVENT: DS18b20#Temperature=19.25 16717 : WIFI : Connected! AP: SMC (5C:49:79:45:39:ED) Ch: 1 Duration: 3792 ms 16718 : EVENT: WiFi#ChangedAccesspoint 16827 : WIFI : DHCP IP: 192.168.0.201 (ESP-201-1) GW: 192.168.0.3 SN: 255.255.255.0 duration: 109 ms 16838 : EVENT: WiFi#Connected 16938 : MQTT : Intentional reconnect 21961 : MQTT : Failed to connect to broker 28568 : Current Time Zone: DST time start: 2018-03-25 02:00:00 offset: 120 minSTD time start: 2018-10-28 03:00:00 offset: 60 min 28569 : EVENT: Time#Initialized 28593 : EVENT: Clock#Time=Sun,11:18 28612 : MQTT : Intentional reconnect 33634 : MQTT : Failed to connect to broker 33645 : MQTT : Intentional reconnect 38667 : MQTT : Failed to connect to broker 38678 : MQTT : Intentional reconnect 43700 : MQTT : Failed to connect to broker 43708 : WD : Uptime 1 ConnectFailures 0 FreeMem 12224 43709 : MQTT : Intentional reconnect 48731 : MQTT : Failed to connect to broker 48736 : MQTT : Intentional reconnect 53757 : MQTT : Failed to connect to broker 53768 : MQTT : Intentional reconnect 58790 : MQTT : Failed to connect to broker 58801 : MQTT : Intentional reconnect 63823 : MQTT : Failed to connect to broker 63834 : MQTT : Intentional reconnect 68856 : MQTT : Failed to connect to broker 68866 : MQTT : Intentional reconnect 73888 : MQTT : Failed to connect to broker 73896 : WD : Uptime 1 ConnectFailures 0 FreeMem 12160 73897 : MQTT : Intentional reconnect 78918 : MQTT : Failed to connect to broker 78942 : DS : Temperature: 19.25 (28-ff-b8-ea-b4-16-3-ed) 78944 : EVENT: DS18b20#Temperature=19.25 78993 : WIFI : AP Mode Disabled for SSID: ESP-201_1 78994 : WIFI : Set WiFi to STA 78998 : EVENT: Rules#Timer=1 79009 : ACT : Publish ESP-201/IP,0.0.0.0 79024 : ACT : Publish ESP-201/MAC,5C:CF:7F:0B:68:52 79035 : ACT : Publish ESP-201/Time,11:18:50 79047 : ACT : Publish ESP-201/Uptime,1 79060 : ACT : Publish ESP-201/RSSI,0 79072 : ACT : Publish ESP-201/SSID,-- 79083 : ACT : Publish ESP-201/BSSID,00:00:00:00:00:00 79095 : ACT : Publish ESP-201/CH,0 79106 : ACT : Publish ESP-201/SYSHEAP,13992 79117 : ACT : 79126 : ACT : timerSet,1,60 79153 : EVENT: WiFi#Disconnected 79172 : WIFI : Disconnected! Reason: 'Assoc leave' Connected for 1 m 2 s 79173 : WIFI : Connecting SMC attempt #0 80208 : WIFI : Connected! AP: SMC (5C:49:79:45:39:ED) Ch: 1 Duration: 1034 ms 80590 : WIFI : DHCP IP: 192.168.0.201 (ESP-201-1) GW: 192.168.0.3 SN: 255.255.255.0 duration: 381 ms 80601 : EVENT: WiFi#Connected 80702 : MQTT : Intentional reconnect 80769 : MQTT : Connected to broker with client ID: ESPClient_5C:CF:7F:0B:68:52 80771 : Subscribed to: ESP-201/# 80772 : EVENT: MQTT#Connected 81267 : EVENT: Time#Set

TD-er commented 6 years ago

So it takes in your setup about 60+ seconds to connect?

It is really strange to see it setting AP+STA in the beginning.

What build do you use? normal_esp8266_4096? Then I can build a test version for you to test.

TD-er commented 6 years ago

I've made a build to test here

wdonker commented 6 years ago

It is really strange to see it setting AP+STA in the beginning.

Maybe that is because the Wifi mode on first connecting is AP. I would expect ESPEasy to do a WifiStart first (and set mode to STA) but I do not think it does. My test build (based on mega 20180414 normal 4096) shows this log:

INIT : Booting version: (custom) 251 : INIT : Warm boot #2 253 : FS : Mounting... 277 : FS : Mount successful, used 75802 bytes of 957314 284 : CRC : No program memory checksum found. Check output of crc2.py 287 : CRC : Settings CRC ...FAIL 315 : CRC : SecuritySettings CRC ...OK 422 : INIT : Free RAM:18456 423 : INIT : I2C 423 : INIT : SPI not enabled 436 : WIFI : Mode = WIFI_AP 436 : WIFI : Set WiFi to AP+STA 1323 : WIFI : AP Mode ssid will be ESP_Easy_0 with address 192.168.4.1 1324 : WIFI : Connecting WLAN_WIM attempt #0 1442 : WD : Uptime 0 ConnectFailures 0 FreeMem 13280 4402 : WIFI : Connected! AP: WLAN_WIM (80:29:94:F5:90:E4) Ch: 13 Duration: 3077 ms 8244 : WIFI : DHCP IP: 192.168.178.235 (ESP-Easy-0) GW: 192.168.178.1 SN: 255.255.255.0 duration: 3842 ms 28373 : Current Time Zone: DST time start: 2018-03-25 02:00:00 offset: 120 minSTD time start: 2018-10-28 03:00:00 offset: 60 min 31442 : WD : Uptime 1 ConnectFailures 0 FreeMem 12912 61442 : WD : Uptime 1 ConnectFailures 0 FreeMem 12912 65361 : WIFI : AP Mode Disabled for SSID: ESP_Easy_0 65362 : WIFI : Set WiFi to STA 65377 : WIFI : Disconnected! Reason: 'Assoc leave' Connected for 1 m 0 s 65377 : WIFI : Mode = WIFI_STA 65378 : WIFI : Connecting WLAN_WIM attempt #0 66359 : WIFI : Mode = WIFI_STA 67765 : WIFI : Mode = WIFI_STA 67818 : WIFI : Connected! AP: WLAN_WIM (80:29:94:F5:90:E4) Ch: 13 Duration: 2438 ms 71487 : WIFI : DHCP IP: 192.168.178.235 (ESP-Easy-0) GW: 192.168.178.1 SN: 255.255.255.0 duration: 3669 ms 91442 : WD : Uptime 2 ConnectFailures 0 FreeMem 15296

TD-er commented 6 years ago

I just changed the Setup procedure of the wifi. The persistent settings were disabled after the event handlers were initialized. This could lead to the situation I described here: #1250 Could you test the build I attached, or just build it yourself, based on the Pull Request? I can merge it so it is just in the main branch.

TD-er commented 6 years ago

OK, I've got one of the devices myself that will start with AP+STA So, this is not a fix, but now I have something to debug.

micropet commented 6 years ago

Your test_ESP8266_4096 looks good:

12031 : EVENT: System#Wake 12050 : WIFI : Connecting SMC attempt #0 12065 : EVENT: System#Boot 12072 : ACT : 12085 : ACT : Publish ESP-201/IP,0.0.0.0 12098 : ACT : timerSet,1,60 12107 : ACT : 12126 : EVENT: WiFi#Disconnected 12141 : WIFI : Disconnected! Reason: 'Unspecified' 12148 : WD : Uptime 0 ConnectFailures 0 FreeMem 13576 12179 : DS : Temperature: 22.62 (28-ff-b8-ea-b4-16-3-ed) 12181 : EVENT: DS18b20#Temperature=22.62 15119 : WIFI : Connected! AP: SMC (5C:49:79:45:39:ED) Ch: 1 Duration: 3067 ms 15120 : EVENT: WiFi#ChangedAccesspoint 16016 : WIFI : DHCP IP: 192.168.0.201 (ESP-201-1) GW: 192.168.0.3 SN: 255.255.255.0 duration: 897 ms 16027 : EVENT: WiFi#Connected 16127 : MQTT : Intentional reconnect 16194 : MQTT : Connected to broker with client ID: ESPClient_5C:CF:7F:0B:68:52 16207 : Subscribed to: ESP-201/# 16216 : EVENT: MQTT#Connected 16314 : Current Time Zone: DST time start: 2018-03-25 02:00:00 offset: 120 minSTD time start: 2018-10-28 03:00:00 offset: 60 min 16315 : EVENT: Time#Initialized 16335 : EVENT: Clock#Time=Sun,14:31 41447 : EVENT: Clock#Time=Sun,14:32 42148 : WD : Uptime 1 ConnectFailures 0 FreeMem 12728 72718 : WD : Uptime 1 ConnectFailures 0 FreeMem 11720 72767 : DS : Temperature: 22.62 (28-ff-b8-ea-b4-16-3-ed) 72769 : EVENT: DS18b20#Temperature=22.62 72848 : EVENT: Rules#Timer=1 72860 : ACT : Publish ESP-201/IP,192.168.0.201 72879 : ACT : Publish ESP-201/MAC,5C:CF:7F:0B:68:52 72897 : ACT : Publish ESP-201/Time,14:32:32 72923 : ACT : Publish ESP-201/Uptime,1 72945 : ACT : Publish ESP-201/RSSI,-59 77961 : ACT : Publish ESP-201/SSID,SMC 82978 : ACT : Publish ESP-201/BSSID,5C:49:79:45:39:ED 87995 : ACT : Publish ESP-201/CH,1

micropet commented 6 years ago

The web server responds very slow. 15-04-_2018_14-42-48.zip

micropet commented 6 years ago

That does not look right:

4548057 : ACT : Publish ESP-201/BSSID,00:00:00:00:00:00

TD-er commented 6 years ago

That 00:00....00 is the return value of the %bssid% when disconnected. If you have a better suggestion what to use as string to indicate disconnected, be my guest. My idea was that this is still parseable as MAC address and clearly an error state

wdonker commented 6 years ago

OK, I've got one of the devices myself that will start with AP+STA So, this is not a fix, but now I have something to debug.

I changed ESPEasy.ino and added a setWifiState(WifiStart); just before setWifiState(WifiTryConnect);

and now it starts with mode WIFI_STA. Not sure if this really fixes the issue...

TD-er commented 6 years ago

@wdonker Why not use the implementation I submitted in my pull request? The main problem is that the core library itself is caching connection settings and is trying to (re)connect. This reconnect fails before ESPeasy is attempting to connect and thus the wifi state is already in "connection failed" state and thus selecting AP mode. When you set your wifistate to wifi start right before connecting, it may help only a few nodes and probably not even every boot. I did try using wifiReset() at that same line. which does somewhat the same and that didn't help also. One of my nodes continued to set AP+STA at boot.

wdonker commented 6 years ago

I did not use your PR because you wrote it would not be the fix and just assumed a wifistart would be logic as a first action. I think it is better I leave the issue up to you since my knowledge of the core library is not good enough. Sorry if I distracted you from really solving the issue ;-)

Edit: I now see you updated the PR, had not seen that before....

TD-er commented 6 years ago

I was hoping the issue of the inadvertently started AP mode was resolved by my last additions of the PR. That's why I created test builds.

micropet commented 6 years ago

My idea was that this is still parseable as MAC address and clearly an error state

No. That is okay. I just did not know what it means.

wdonker commented 6 years ago

@TD-er: I tried again using your PR and it works ok on my NodeMCU.

micropet commented 6 years ago

Have just tried the current version. Where does the address 195.186.4.101 come from? They do not exist in my System.

12769 : INFO : Plugins: 71 [Normal] [Testing] [Development] (core 00000000) 12770 : EVENT: System#Wake 12790 : WIFI : Connecting SMC attempt #0 12796 : OTA : Arduino OTA enabled on port 8266 12809 : EVENT: System#Boot 12817 : ACT : 12830 : ACT : Publish ESP-201/IP,0.0.0.0 12842 : ACT : timerSet,1,60 12853 : ACT : 12881 : WD : Uptime 0 ConnectFailures 0 FreeMem 15184 12912 : DS : Temperature: 19.81 (28-ff-b8-ea-b4-16-3-ed) 12914 : EVENT: DS18b20#Temperature=19.81 16573 : WIFI : Connected! AP: SMC (5C:49:79:45:39:ED) Ch: 1 Duration: 3782 ms 16575 : EVENT: WiFi#ChangedAccesspoint 16785 : WIFI : DHCP IP: 192.168.0.201 (ESP-201-1) GW: 192.168.0.3 SN: 255.255.255.0 duration: 211 ms 16796 : EVENT: WiFi#Connected 16896 : MQTT : Intentional reconnect 16942 : MQTT : Connected to broker with client ID: ESPClient_5C:CF:7F:0B:68:52 16944 : Subscribed to: ESP-201/# 16946 : EVENT: MQTT#Connected 20793 : Host unreachable: 195.186.4.101 41017 : Host unreachable: 195.186.4.101 42881 : WD : Uptime 1 ConnectFailures 0 FreeMem 13552 57146 : Current Time Zone: DST time start: 2018-03-25 02:00:00 offset: 120 minSTD time start: 2018-10-28 03:00:00 offset: 60 min 57147 : EVENT: Time#Initialized 57169 : EVENT: Clock#Time=Mon,01:02 72880 : WD : Uptime 1 ConnectFailures 0 FreeMem 13552 73053 : DS : Temperature: 19.81 (28-ff-b8-ea-b4-16-3-ed) 73055 : EVENT: DS18b20#Temperature=19.81 73097 : EVENT: Rules#Timer=1 73107 : ACT : Publish ESP-201/IP,192.168.0.201 73122 : ACT : Publish ESP-201/MAC,5C:CF:7F:0B:68:52 73139 : ACT : Publish ESP-201/Time,01:02:45 73156 : ACT : Publish ESP-201/Uptime,1 73171 : ACT : Publish ESP-201/RSSI,-61 73186 : ACT : Publish ESP-201/SSID,SMC 73202 : ACT : Publish ESP-201/BSSID,5C:49:79:45:39:ED 73217 : ACT : Publish ESP-201/CH,1 73235 : ACT : Publish ESP-201/SYSHEAP,11216 73252 : ACT : 73262 : ACT : timerSet,1,60 88033 : EVENT: Clock#Time=Mon,01:03

Zixim commented 6 years ago

195.186.4.101 looks like an ntp server

TD-er commented 6 years ago

Yep, the NTP uses randomly 0.pool.ntp.org ... 3.pool.ntp.org, which on itself is selecting random hosts from a big pool. Quite a few from these are unreachable, that's why I made them retry from the next in the pool within a few seconds. Maybe I could add a bit more info in the log to indicate it is a NTP request failing.

By the way, I see you're using core "000000", which is core 2.4.x 'staged'. Please keep in mind that version may change at once, since it is not a "stable" link.

micropet commented 6 years ago

OK. A small note that it is an NTP server is good.

micropet commented 6 years ago

Can it be that there are problems with the reading in of the configuration?

I had flashed a new wemos, added a few sensors and a few rules.

Then I flashed a second new Wemos and loaded the configuration of the first one.

There were no rules and sensors taken over. Only the MQTT controller and the device name were there.

Grovkillen commented 6 years ago

I think you're on to something here @micropet

micropet commented 6 years ago

What do you mean, Grovkillen ?

Zixim commented 6 years ago

he means you're right 👍

Grovkillen commented 6 years ago

Yes, and maybe this has something to do with the bumped build made 5 days ago: https://github.com/letscontrolit/ESPEasy/commit/2ee51363ddc47342306e00d518da5bd51cbe4b02#commitcomment-28596737

micropet commented 6 years ago

Thank you.

I work with the google translator. Since I do not always get the subtleties.

Zixim commented 6 years ago

hah...my brain just read "Since I do not always get the subtitles." and i was like...hey, I want subtitles for github also !

but way off topic. 😜

micropet commented 6 years ago

I do not know if it has anything to do with Grovkillen's changes, but the webserver is running fast again. The WIFI connect is also there immediately. Now I'm watching if the MQTT connect stays stable.