Replies: 37 comments 1 reply
-
After a restart from command interface (su) the webui is available again ... |
Beta Was this translation helpful? Give feedback.
-
I'll monitor and keep an eye out. Next time could you capture the # available memory? This is the usual culprit when things start getting slow. Perhaps there is a memory leak somewhere. Also did you have this problem with earlier builds? |
Beta Was this translation helpful? Give feedback.
-
Yes I will do, but how shall I capture the # available memory? It's not Free heap .... or? |
Beta Was this translation helpful? Give feedback.
-
yes it's free heap. grab it either from the MQTT hearbeat or via the webUI |
Beta Was this translation helpful? Give feedback.
-
see above ... Free heap was during webui freeze: 94296 bytes - after restart (now) 95.076 bytes |
Beta Was this translation helpful? Give feedback.
-
oops, missed that. I'll monitor here. very strange |
Beta Was this translation helpful? Give feedback.
-
My webui started to slow down again .... > 10 secs to respond and no memory problems. Could you please provide the correct download link ..... Thanks |
Beta Was this translation helpful? Give feedback.
-
take the branch called |
Beta Was this translation helpful? Give feedback.
-
I have done so. |
Beta Was this translation helpful? Give feedback.
-
weird, if you select the branch from the pull-down list and download the zip it will take the branch, |
Beta Was this translation helpful? Give feedback.
-
@proddy I then the looked at my mesh network and recognized that the ems-esp was now connected to my main router quite fare away with very poor signal and speed. When I restarted the gateway connected to the next mesh accesspoint (in 50cm distance) and everything works fine. Could it be that after a while wlan connection is somehow changed? I understood that there has been changes on network access since v3.xx. |
Beta Was this translation helpful? Give feedback.
-
that would explain it what you're seeing. I see from the first post the signal strength was 42% which is quite low. The ESP will automatically reconnect the WiFi if it loses a connection. The best way to spot this is to use Syslog and scan the log files for the re-connect messages. Another way is to look at the MQTT Heartbeat for the rssi (wifi signal strength) and see if this is dropping. For example, Home Assistant will keep a history or alternatively push this information into Grafana. In later v3 versions, I added Ethernet code, but that shouldn't affect the Wifi behavior. I don't know why your network is reconnecting and sending the ESP to another router node. I've had similar problems at home with the ESP32 which is literally 1 meter from my Unifi AC Pro wireless Access Point and EMS-ESP would still always connect to one of my other Access Points on another floor in my house. I could never figure out why. I guess I'll google it... |
Beta Was this translation helpful? Give feedback.
-
In v3.0.0b1 I haven't had this reconnection issue and in the v2.xx versions neither. Any changes done on wlan since b1? |
Beta Was this translation helpful? Give feedback.
-
The biggest change I could think of is the ESP32 libraries that got upgraded to 3.1.0 and uses the latest Arduino core libraries. That was pushed 2 weeks ago. See https://github.com/platformio/platform-espressif32/releases/tag/v3.1.0. You could try downgrading? Replace with |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
sure, no problem. I'll write down some steps tonight. Are you Windows, Linux or OSX? |
Beta Was this translation helpful? Give feedback.
-
WIN10 - Thanks .... |
Beta Was this translation helpful? Give feedback.
-
ok, if you VSC and Git installed, open VSC, click |
Beta Was this translation helpful? Give feedback.
-
It's the same if i push to my github. But if i rename the branch, the source assets are ok. |
Beta Was this translation helpful? Give feedback.
-
@proddy |
Beta Was this translation helpful? Give feedback.
-
Just a question before starting testing: I would like to avoid re-entering wlan and other settings. Can I take the factory_settings.ini out to keep my settings when uploading the bin-file after compilation? |
Beta Was this translation helpful? Give feedback.
-
you can just keep the platformio.ini as it is. The settings are stored in the ESP's filesystem and are persisted so when you re-flash it's only updating the application code. |
Beta Was this translation helpful? Give feedback.
-
@proddy |
Beta Was this translation helpful? Give feedback.
-
yes, absolutely. I do many updates each day. Have you changed any settings in platformio? Are you using VSC to upload or via the command line? |
Beta Was this translation helpful? Give feedback.
-
No, up to yet I used the bin-files from github. Just b1 I compiled myself. |
Beta Was this translation helpful? Give feedback.
-
@proddy yes you where right. I restarted all components on my Mesh Network yesterday (Router and all Mesh Repeaters) and since then the ems-esp connects to the nearest Mesh Repeaters (rssi 100). |
Beta Was this translation helpful? Give feedback.
-
@proddy I think we can close this issue. |
Beta Was this translation helpful? Give feedback.
-
before we do, did you change anything? Like use the -D compiler build flag? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Could someone explain what the checkbox "disable wifi sleep mode" do exactly? |
Beta Was this translation helpful? Give feedback.
-
I upgraded from v3.0.0b1 to v3.0.0b3 yesterday.
Now after approx. one day of operation the webui does not respond anymore. (empty white page - no error displayed)
MQTT is still working as well as the telnet session.
The command interface took approx. 5 secs to respond - that's not the normal bevavior:
ems-esp:/system$ show
Uptime: 000+22:40:46.701
SDK version: v3.3.4-432-g7a85334d8
CPU frequency: 240 MHz
Free heap: 94296 bytes
WiFi: Connected
SSID: xxxxxx
BSSID: DC:39:6F:BF:DC:ED
RSSI: -79 dBm (42 %)
MAC address: F0:08:D1:D7:E7:70
Hostname: ems-esp
IPv4 address: 192.168.178.71/255.255.255.0
IPv4 gateway: 192.168.178.1
IPv4 nameserver: 192.168.178.1
Ethernet: disconnected
Syslog: disabled
Beta Was this translation helpful? Give feedback.
All reactions