Your comments
As I said, unfortunately, Iridium works only with a fixed port and it does not can work with dynamic ports.
Hello!
To switch between projects, you can use the IR.DesignSwitch method. But at the moment this method normally works only for projects downloaded through the Transfer. Because projects downloaded through the cloud do not have a permanent name. But we will try to fix it in future versions.
Здравствуйте!
Переключение с помощью горячих клавиш было внесено в бета версию 1.1.8
Переключаться между элементами можно в рабочей области установив курсор над элементами и зажав левую кнопку мыши нажимать на Alt. Будет происходить поочередное переключение между элементамми находящимися под курсором. К сожалению, переключать таким образом элементы в окне Projects Overview нельзя.
К сожалению, повторить не удалось. Все таки пришлите ваш проект, на котором это наблюдается и опишите все ваши действия.
Could you describe exactly how you updated the password in the project and what were your next steps?
Hello!
Unfortunately, this functionality is not implemented on the cloud yet. But you can set passwords for the project in the editor. To do this, you need to go to the project settings.
So...Why now I can't use an different sender port to communicate with iRidium Driver?
This is due to the fact that Iridium only works with fixed ports. In order for Iridium to receive a response from your program, you must constantly change the port in its settings. This can be done using the SetParameters method.
But for this you need to transfer the new port to Iridium.
Have you tried to connect your program to Hercules?
I think that Hercules will not be able to receive an answer from your program either,
because it will also need a fixed port, which it will listen to.
Sorry, but I do not quite understand your first question. Could you describe the problem in more detail.
Hello!
No, the "Waiting" state is not exactly what you need. Your task can be solved, for example, using scripts.
Customer support service by UserEcho
The server sends a command to the IP router, and then the IP router sends this command to the KNX bus. Most likely your KNX IP routers on the network have addresses 15.15.250.
That is, Iridium does not have its own Group address in KNX bus.