"Automatic Round Start" to false ignored

[arthurdent75]

The Problem

Setting "Automatic Round Start" does not seem to take effect

Version

15.2.1

Logfile

[0d00h00m25s] 2023-04-30T23:39:57 <INF> [MAIN] Device info: CPU cores: 2, Chip revision: 301
[0d00h00m25s] 2023-04-30T23:39:57 <INF> [MAIN] SD card info: Name: SA16G, Capacity: 14772MB, Free: 14757MB
[0d00h00m27s] 2023-04-30T23:39:59 <INF> [MAIN] Initialization completed successfully! Starting flow task ...
[0d00h00m30s] 2023-04-30T23:40:02 <INF> [LOGFILE] Set log level to ERROR

Expected Behavior

If I set "Automatic Round Start" to false, the round should not start at boot

Screenshots

No response

Additional Context

No response

[caco3]

Thanks for reporting it.

The implementation seems to be correct, the flow does not start.
But I see 2 minor issues:

1. The log message is misleading
2. the image stays on "initializing"

We will address this in the next release.

[arthurdent75]

Thank you for your quick response.
The real issue for me is that I can't complete the setup.
I get the "busy" message trying to set up the reference images because the round is on (as per #2357)
The round never ends, so I cannot proceed.
That's why I tried to turn off the round on startup, but I keep getting the same "busy" message.

[caco3]

ah, right, yep, that is an issue!

There are 2 temporary workarounds:

1. enable autostart and wait for the round to complete, you can disable it again afterwards.
2. downgrade to 15.1.1 for the setup and then upgrade back to 15.2.1

[arthurdent75]

• enable autostart and wait for the round to complete, you can disable it again afterward.

I've waited hours... it never ends... 🤷

• downgrade to 15.1.1 for the setup and then upgrade back to 15.2.1

I'll try this one. Thanks!

[caco3]

I've waited hours... it never ends... 🤷

did you restart between?

[arthurdent75]

did you restart between?

Many times

[caco3]

I just pushed a fix to rolling which fixes the problem during setup mode. See #2373

You can try it out, see next comment.

[github-actions]

You can try the latest Automatic Build of the the rolling or any other branch. It might already contain a fix for your issue.
See the documentation for additional information.

[caco3]

With #2376 the log also shows the correct behaviour