Mapping wizard confusing when snooping fails

[haraldmeyer]

On a tenant with MQTT service not available, if snooping is activated but connection to MQTT service fails, the wizard looks like this:

[switschel]

That's on design.. if snooping is enabled nothing else should be define in the wizard.
Is your point that we shouldn't allow it for connectors which are not connected?

[haraldmeyer]

As discussed, current approach makes sense but better visual indicators that connector is not active.

[switschel]

@sagIoTPower We could add a new state in the mapping overview if snooping is enabled but connector is not connected.
Also in the snooping wizard we can add a note that a not connected connector is selected which could lead to no receiving any message.

[ck-c8y]

I reviewed the screensflo.
@haraldmeyer If you don't select a connector a warning is displayed.
There could be cases where you want to define the mapping or snooping first and lated assign a connector.
This is possible in the both steppers.

If no connectors is selected:

a warning is displayed:

[haraldmeyer]

Did you change something for this? In my case the problem was not that no connector was selected but that a failed connector was selected, which did not produce an error message.

[ck-c8y]

There could still be reason why you could choose a failed connector.

The connectors can be edited in two ways:

1. in the first part of the stepper
2. through the menu entry: Configuration, tab: Connector

So you could choose a failed connector in the stepper and then correct it in Configuration part.

We could exclude choosing failed connectors, but this leads to a stepper and workflow that is very restricted.