You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if a mapping with wildcard is defined and a connector selected which doesn't support it no feedback is given to the user.
The only feedback is that the connector does not show up in the list even after the mapping is activated.
We could improve the feedback...
by adding log entries to the microservice logs
showing a error/warning in the UI if mapping is activated
As this is a limitation of MQTT service we would not invest much effort into this as it is a temporary issue until wildcards are supported by MQTT service.
The text was updated successfully, but these errors were encountered:
Currently if a mapping with wildcard is defined and a connector selected which doesn't support it no feedback is given to the user.
The only feedback is that the connector does not show up in the list even after the mapping is activated.
We could improve the feedback...
As this is a limitation of MQTT service we would not invest much effort into this as it is a temporary issue until wildcards are supported by MQTT service.
The text was updated successfully, but these errors were encountered: