For now, we have a new type of command "Read Request": https://dev.iridi.com/KNX/en#Sending_commands

It is about this that we formulated a request to the developers, how we can provide a detailed filter for visitors (there is no such module now).

The language division also turned out to be very important for our clients (we received complaints from local markets), there used to be one forum, but with different topics, and this turned out to be very inconvenient.

As you can see, we came to this situation in a completely deliberate way and now the issue of convenience can be solved only by changing the tool or in the hope that the third-party platform will continue to develop.

Yes, now it's clearer.

We have deliberately divided the forums by product and language. It was a big problem (and there were complaints from users) when I look for information on the i3pro product (for example, information about ONVIF cameras), and they show me a selection on i3ite or on an outdated i2control platform. Therefore, we made the search independent, and it only works within the forum in which you are located.

How would you recommend changing this to keep the search relevant to the product?

Hello Dennis

Your post was not deleted, it was under moderation.

I don't quite understand your search query. You created one forum and conducted a search in it, but this works great for us, or does it not?

Give an example, what do you want to find on our forum, but it does not show the result?

For this case, the best would be to use the JS template, as I described above. For simplicity, you can draw a popup template in the editor, but clone and define links later in the script. Then changing the popup in one place will automatically change the behavior in the entire project.

I really don't understand you ((

Create a separate project with the desired popup and draw your component. With a project merge, you can reuse it. If you need additional logic, then you can use the script, if not, then only the interface. You can copy as many of these items as you like.

What confuses you about this option? What is the main purpose of such components for you?

You can create all graphics from a script, i.e. you will have one JS file that you can update (modify) and a separate definition class (constructor) that will allow you to use this component in the right place.

This is impossible for the current architecture from the point of view of isolating such a component (if it is not written by us in native code) and it is basically impossible for C # in mobile applications (code must be compiled before execution).

Your task of reuse is completely solved by the JS script and the selection of a pop-up with elements in a separate project, which you can merge as needed.