Lilygo_T3_V1.61, locking up

Boards
1

Hi,
I’ve been running OMG on Lilygo for a week of two, getting familiar with it. I was concerned that it was somewhat unstable and suspected my WiFi and Internet (because they are not 100%), but after reading https://community.openmqttgateway.com/t/rtl-443-mqtt-topic-remove-id-add-timestamp/2459/8 I added Steph’s changes.
Today I caught the error:

[1947528][E][WiFiClient.cpp:422] write(): fail on fd 51, errno: 11, "No more processes"
[1947558][E][WiFiClient.cpp:422] write(): fail on fd 51, errno: 113, "Software caused connection abort"
*wm:[2] [EVENT] WIFI_REASON:  200
W: MQTT connection...
[1947575][E][WiFiClient.cpp:242] connect(): connect on fd 50, errno: 118, "Host is unreachable"
W: failure_number_mqtt: 1
W: failed, rc=-2
W: MQTT connection...
N: Connected to broker
[1960053][E][WiFiClient.cpp:422] write(): fail on fd 51, errno: 11, "No more processes"

Which may be one of several possible causes of hangups, but at least that’s a start.

So here’s my question, how can I track the number of processes? Or more generically (if it’s memory related) find what is using memory?
Dave

2

Soo, I’ve pulled the latest from github with out the changes. It has run twice as liong as I was getting (45 minutes).

I’ll leave it alone till tomorrow.

3

interresting
I’m not seeing errors

would suggest to just set “#define UTCtimestamp true” in User_config.h
without other modifications and see if your problem is back

4

you aren’t alone with similar problem : LilyGO devices stop responding after a few hours

5

The gateway publish its freememory and other parameters to hom/OpenMQTTGateway/SYStoMQTT
Could you share what you have here before the freeze?

6

it’s been a lot more stable with the ‘vanilla’ version.

feee memory
feee memory1632×400 18.5 KB

I’ll try adding “#define UTCtimestamp true” shortly.
Dave

7

I added the UTCtimestamp, and it seems stable, Free memory still around 110,000 Bytes.

The graph above showed the rapid decline I was getting back on the 25th (localtime). The one between 3 and 6 PM would have included a WiFi/Internet dropout, but it seems like the lockup is under 40,000 Bytes. What would need that much?

8

here’s a couple of the SYStoMQTT messages from MQTT Exporer, just before and after I did the re-build, but I’m not sure how I can go back to the earlier crashes.

{"uptime":1210,"UTCtime":"2023-05-26T23:52:26Z","version":"version_tag","discovery":true,"env":"lilygo-rtl_433","freemem":109884,"mqttport":"1883","mqttsecure":false,"minfreemem":48324,"tempc":53.33333,"freestack":3132,"rssi":-51,"SSID":"paddys_tavern","BSSID":"0C:0E:76:AC:37:FF","ip":"192.168.1.8","mac":"D4:D4:DA:82:F1:74","actRec":3,"mhz":433.92,"RTLRssiThresh":-90,"RTLRssi":-105,"RTLAVGRssi":-99,"RTLCnt":1629,"RTLOOKThresh":15,"modules":["LilyGo_SSD1306","WebUI","rtl_433"]}

{"uptime":10,"UTCtime":"1970-01-01T00:00:10Z","version":"version_tag","discovery":true,"env":"lilygo-rtl_433","freemem":110668,"mqttport":"1883","mqttsecure":false,"minfreemem":106400,"tempc":53.33333,"freestack":5996,"rssi":-53,"SSID":"paddys_tavern","BSSID":"0C:0E:76:AC:37:FF","ip":"192.168.1.8","mac":"D4:D4:DA:82:F1:74","actRec":3,"mhz":433.92,"RTLRssiThresh":-82,"RTLRssi":-99,"RTLAVGRssi":0,"RTLCnt":1,"RTLOOKThresh":15,"modules":["LilyGo_SSD1306","WebUI","rtl_433"]}
________________ Rebuild with UTC time _________________
{"uptime":73944,"version":"version_tag","discovery":false,"env":"lilygo-rtl_433","freemem":110576,"mqttport":"1883","mqttsecure":false,"minfreemem":32228,"tempc":53.33333,"freestack":3132,"rssi":-54,"SSID":"paddys_tavern","BSSID":"0C:0E:76:AC:37:FF","ip":"192.168.1.8","mac":"D4:D4:DA:82:F1:74","actRec":3,"mhz":433.92,"RTLRssiThresh":-89,"RTLRssi":-90,"RTLAVGRssi":-98,"RTLCnt":104056,"RTLOOKThresh":15,"modules":["LilyGo_SSD1306","WebUI","rtl_433"]}

Would earlier stuff be in the HA database?
Dave

9

Could you share the configuration that you are using and has issues?

10

I’ve put Steph’s ‘add timestamp’ code in to ZgatewayRTL_433.ino. For the last 50 minutes free memory is sitting around 106-108 thousand Bytes.
So, all seems OK now.
One thing that may have changed was when I tried to go back to ‘original’ code I ended up with the latest ‘development’ code.

Thanks
Dave

11

So, I made the changes at 3:43, all still looking stable.

free memory 20230528
free memory 202305281632×400 18.3 KB

After some investigation I think I started out using the pre-compiled binaries (esp32dev-rtl_433) that I downloaded on 8th April, and when I saw Steph’s timestamp changes I moved to VSCode and cloned the repository.
I see now that esp32dev-rtl_433-libraries.zip is a few hundred byes bigger, so there must have been a change there. Sorry I don’t know enough about github to look at what they were and what might be relevant.

All good now, so thanks for the support.

Dave

1 Like