When Autostart is disabled, the Web UI always shows the "Initialization" image.

[caco3]

The Feature

Instead we should show another image mentioning "Ready"

[caco3]

Note: in case the autostart is disabled, the REST API "flow_start" also does not work. It simply returns WARNING: Flow start triggered by REST API, but flow is not active

@Slider0007 @jomjol Is this on purpose?

[Slider0007]

Note: in case the autostart is disabled, the REST API "flow_start" also does not work. It simply returns WARNING: Flow start triggered by REST API, but flow is not active

@Slider0007 @jomjol Is this on purpose?

The API only responds how the actual autoflow task is designed and with this design it's not possible to restart the round if autostart is disabled. An updated autoflow task is needed...

[slovdahl]

Note: in case the autostart is disabled, the REST API "flow_start" also does not work. It simply returns WARNING: Flow start triggered by REST API, but flow is not active

I noticed this too while debugging https://github.com/jomjol/AI-on-the-edge-device/discussions/2390#discussioncomment-6430819. I wanted to disable the automatic flow and only triggering it manually, but it didn't work. I never tried triggering a flow through MQTT though, but maybe that would not work either?

[caco3]

I never tried triggering a flow through MQTT though, but maybe that would not work either?

no it wouldn't

[Lackmake]

Its also not possible to set a new reference image with autostart disabled, Just getting a notice like "Device is busy, please wait until round is finished" or something like that even though the device isnt actually busy

[BobKooistra]

Note: in case the autostart is disabled, the REST API "flow_start" also does not work. It simply returns WARNING: Flow start triggered by REST API, but flow is not active @Slider0007 @jomjol Is this on purpose?

The API only responds how the actual autoflow task is designed and with this design it's not possible to restart the round if autostart is disabled. An updated autoflow task is needed...

Then I think the documentation is incorrect. It says: "The main reasons to set it to false (autostart disabled) is when you want to trigger it manually using the REST API or MQTT-API or for debugging.". But if set to false, the trigger with the REST API will NOT work. I wanted to control the flow completely myself at regular intervals from outside with the REST API. Is this possible in another way or should I set the interval to 1.440, for example (1 x per 24 hours) so that the autoflow starts automatically and I trigger the other flows myself?

[caco3]

should I set the interval to 1.440, for example (1 x per 24 hours) so that the autoflow starts automatically and I trigger the other flows myself?

I think this could work, just try it. Maybe you even can set the interval higher so it literally never triggers.