debug OT version

[blb4github]

OT Debugging BLB4

HeishaMon.ino.elf.zip

[blb4github]

update experience: I rebooted, it did crash 2 times (after 40 minutes and after 12 minutes) after which I rebooted, now it is running for 22 hours. So, not completely reliable.

[CurlyMoo]

Can you try the build of the latest commit from the PR?

[blb4github]

Can you try the build of the latest commit from the PR?

you mean this one? https://github.com/IgorYbema/HeishaMon/suites/16508529249/artifacts/942955656

update: installed that version, running now 15 minutes without crash yet; fingers crossed... update2: it's now running for 9 hours without crash Update3 (20230929 14:23: this seems stable version! I did manually reboot after almost 24 hours without crash and it’s running now for 1 day and 14 hours stable!

[blb4github]

This seems stable version, see update above

[CurlyMoo]

I readding some of the commits in the PR. You can try that latest build.

[blb4github]

Sorry, where can I find that latest build?

[CurlyMoo]

The same way you found it the last time.

Op 30 sep. 2023 om 10:39 heeft blb4github @.***> het volgende geschreven:

 Sorry, where can I find that latest build?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[blb4github]

On my phone it was a bit difficult to find…. But installed 👍Op 30 sep 2023 om 10:56 heeft CurlyMoo @.***> het volgende geschreven: The same way you found it the last time.

Op 30 sep. 2023 om 10:39 heeft blb4github @.***> het volgende geschreven:



Sorry, where can I find that latest build?

—

Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you commented.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[blb4github]

Active now for 6,5 hours without crash

[geduxas]

I have latest heishamon build, also experience some random reboots.. don't use opentherm, also don't use any script.. uptime is random, from 27h to 6h.. so heishamon usually reboots 7-9times in week.

[CurlyMoo]

The latest regular build is not related to what we discuss in this issue.

[blb4github]

Active now without crash for more than 23 hours

[CurlyMoo]

Do you use all functionality on this device?

[blb4github]

Yes, S0, 1W, OT and rules. Op 1 okt 2023 om 10:17 heeft CurlyMoo @.***> het volgende geschreven: Do you use all functionality on this device?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[CurlyMoo]

I pushed a new commit

[blb4github]

Installed

[blb4github]

Running now without crash for 9:30u

update: still running, now for 20 hours

[CurlyMoo]

I did a new commit

[blb4github]

installed. what we're doing now is one by one adding the latest functionality since #298 to see where it goes wrong?

[CurlyMoo]

what we're doing now is one by one adding the latest functionality since https://github.com/Egyras/HeishaMon/issues/298 to see where it goes wrong?

Yes

[blb4github]

running now for 13 hours without crash

[CurlyMoo]

There is already a new commit

[blb4github]

installed

[blb4github]

I've seen a crash! it did run for approx 1:30u. I'll do a reboot. update: another crash 5 minutes after reboot. update2: so it now crashed every time after approx 5 minutes after reboot:

[blb4github]

I did reload the firmware and it's now running for almost 3 hours without crash.... Update: it did crash a little bit later. update2: it’s back now to the 5 minute runtime after which a crash occurs.

[CurlyMoo]

What commit was the one which crashes?

[blb4github]

heishamon 20231003 #337 Alpha-109f281. The one before didn't have any crash within 24 hours. Will it have any use to monitor output on Serial1?

[CurlyMoo]

I pushed a new commit which i hope fixes it.

[blb4github]

installed #338 (not #337, that one was crashing), running for 16 minutes now.

[CurlyMoo]

installed https://github.com/Egyras/HeishaMon/issues/337, running for 16 minutes now.

I assume you meant #338

[blb4github]

installed #337, running for 16 minutes now.

I assume you meant #338

yes, sorry, #338. #337 was crashing.....

338 is running now for 1:50u without crash

update: running now for 4:12u without crash... fingers crossed.... update: running now for 8:18u without crash...

[CurlyMoo]

I pushed a new commit. Feel free to run it when you are convinced enough about the stability of this last one.

[blb4github]

After running > 10 hours on #338 without crash I've installed #339

[blb4github]

Unfortunately it did crash with #339 arround 06:00u. I rebooted and it crashed again after approx 5 minutes

[CurlyMoo]

Can you try 338 again?

Op 5 okt. 2023 om 08:36 heeft blb4github @.***> het volgende geschreven:

 Unfortunately it did crash with #339 arround 06:00u. I rebooted and it crashed again after approx 5 minutes

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[blb4github]

Installed #338 againOp 5 okt 2023 om 08:51 heeft CurlyMoo @.***> het volgende geschreven: Can you try 338 again?

Op 5 okt. 2023 om 08:36 heeft blb4github @.***> het volgende geschreven:



Unfortunately it did crash with #339 arround 06:00u. I rebooted and it crashed again after approx 5 minutes

—

Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you commented.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[blb4github]

338 is running again for already 5 hours without crash.

[CurlyMoo]

Can you try the latest build which uses again another approach.

[blb4github]

installed #343 P.S. #338 has crashed as well. Is the other approach on #343 building on #338 or earlier?

[blb4github]

343 did crash after 2 hours. Rebooted now

[CurlyMoo]

Honestly, i believe the current fix is the way to go. So if it still crashes, i believe it must be another edge case.

[CurlyMoo]

I pushed a new commit. That includes all changed since 298. If this doesn't work, then i at least know it must be something else, because i'm sure that the current changes should just work.

[blb4github]

343 is running now without crash for 7 hours (after a reboot. Now installing #346

Update: #346 running now for 3 hours without crash

[blb4github]

346 is running now for 15 hours without crash, hopefully this one is and stays stable 👍👍

Are there already time based rules possible in this one?

[CurlyMoo]

Are there already time based rules possible in this one?

One day and month. Not minutes and seconds. That's another PR.

[blb4github]

Are there already time based rules possible in this one?

One day and month. Not minutes and seconds. That's another PR.

month = %month;

on %month = 10 then should work?

[CurlyMoo]

Yes

[CurlyMoo]

Ehm, no. Month is not an event, so you can only use it in existing code blocks.

[CurlyMoo]

I've created a final build with all changes from the last default heishamon also synchronised. If that also works fine, then the PR is done.

[blb4github]

Installed #351. #346 was running for > 16 hours.