I propose to vote for this codec, because this codec is necessary for the integration of some doorphone manufacturers (for example, bpt) into the management interface. If a sufficient number of integrators vote for it, then the priority of this task will increase and it will be resolved more quickly (the developers answer).
Having the client available for Linux would open the possibility to build more affordable wall panels and with more intelligence. It could run on oDroid boards, RaspberryPi, etc. which in their place support a wide variety of affordable touchscreens.
Windows and Android panels are hard to control remotely, not always stable and need extra attention for updates. Linux is much easier to keep up to date without user intervention and easy to control remotely (in a secure way).
I suggest to add a possibility to request the object status. Some equipment, for example Theben modules for controlling servo driver units, does not support regular sending of its status. In such cases it would be useful to send the "read" command in the KNX network, not the token request from the iRidium application, to avoid unsynchronization, for example at the relaunch of such equipment.
It wold help
greatly the ability to sort the feedbacks and channels on drivers both on panel project and server project. I have a KNX IP BAOS driver with more thana thousand commands and feedbacks.
I use iridium often in combination with LG Commercial displays, but they only support SNMP protocol over network. Now I have to use a global cache ethernet to rs232.
It would be great when I can control the display directly over ethernet.
Is this something to develop?
Paul van Boven
Customer support service by UserEcho