Replies: 21 comments
-
|
wow, that's not good. I'll look into it. Did you compile yourself or take the github release build? |
Beta Was this translation helpful? Give feedback.
-
|
Please send your configuration from help->support-info. |
Beta Was this translation helpful? Give feedback.
-
|
also did you come from v3.5.0b4? |
Beta Was this translation helpful? Give feedback.
-
the Github Release Build |
Beta Was this translation helpful? Give feedback.
-
yes |
Beta Was this translation helpful? Give feedback.
-
|
The file has Null Information |
Beta Was this translation helpful? Give feedback.
-
Free heap to low, i think due to mqtt queue and incomming mqtt commands. |
Beta Was this translation helpful? Give feedback.
-
Please disable this, sometimes this can give instabilities
Disable this, your log shows that the mqtt broker sends the publishes as command back, this makes much traffic and cost much ram. This works only on special settings of the mqtt broker, especially ioBroker-mqtt.
Funny, no boiler at this time. But uptime is low. |
Beta Was this translation helpful? Give feedback.
-
|
also I see all the MQTT publishes are failing, perhaps because of the hostname have a dot '.' ? I'll try it out here |
Beta Was this translation helpful? Give feedback.
-
|
also looks like all the MQTT settings are on. It's recommended to have both Clean Session and Retain set to disabled, unless you really know what you're doing and how MQTT works. |
Beta Was this translation helpful? Give feedback.
-
|
@proddy It's one minute uptime and 1800 mqtt publishes, the queue is constantly overflowing because ems-esp and mqtt broker playing ping-pong with the messages. The fails are only 1300, so 500 are send out, nearly 8 per second. |
Beta Was this translation helpful? Give feedback.
-
|
that's it! |
Beta Was this translation helpful? Give feedback.
-
|
also surprised it worked in 3.5.0b4 😳 |
Beta Was this translation helpful? Give feedback.
-
in 3.5.0b4 everything worked great |
Beta Was this translation helpful? Give feedback.
-
|
even if i copy your settings I cannot reproduce |
Beta Was this translation helpful? Give feedback.
-
|
Fallback to "version": "3.5.0b4" and it works again. Flash with USB and ESPTool (Windows) esptool.exe --port COM7 --chip esp32 erase_flash esptool.exe --chip esp32 --port COM7 --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 40m --flash_size detect 0x1000 bootloader_dio_40m.bin 0x8000 partitions.bin 0xe000 boot_app0.bin 0x10000 EMS ESP.bin EMS ESP version File System (Used / Free) greeting |
Beta Was this translation helpful? Give feedback.
-
|
I see lots of traffic in API calls and mqtt, about 40 publishes every minute. There's something special about your setup, perhaps the publish single option or an external app like iobroker? If you have time try the latest b5 again but disable mqtt and check memory. Then add mqtt but not HA. And check again. The only way to get to the root cause here is by process of elimination. Very old school! |
Beta Was this translation helpful? Give feedback.
-
Yes, I have IOBroker running via the API and MQTT for IOBroker too |
Beta Was this translation helpful? Give feedback.
-
|
When using publish to command topic make sure the ioBroker-mqtt does not publish on subscribe, connect etc. These settings are working: |
Beta Was this translation helpful? Give feedback.
-
|
@stmb-100 can we close this? |
Beta Was this translation helpful? Give feedback.
-
After updating to Development Build v3.5.0b5, all ENTITIES in the dashboard are set to 0 at regular intervals and a new scan begins.
log.txt
EMS-ESP Version
v3.5.0b5
Device (Platform / SDK)
ESP32 / v4.4.2
System Uptime
000+00:00:14.257
CPU Frequency
240 MHz
Heap (Free / Max Alloc)
91 KB / 39 KB
Flash Chip (Size / Speed)
4.096 KB / 40 MHz
Application (Used / Free)
1.864 KB / 56 KB
File System (Used / Free)
32 KB / 160 KB
Regards
Stefan
Beta Was this translation helpful? Give feedback.
All reactions