When you currently import a large KNX Project file (> 100 devices) only the dropdown boxes are populated with all the available registers from the projectfile. You have to re-create all the Homey devices by hand by selecting 100+ drownboxes, sometimes 3 times per device. All the devices naming and group information is lost too. This re-creation process takes weeks of work for large project files.
In KNX projects the main source of truth is the KNX manager and updates the KNX project file. There is currently no way to keep the Homey KNX devices in sync with the projectfile which makes it unusable in time.
These two behaviours makes Homey unpractical for large KNX installations.
The usability for Homey in professional KNX installations would be greatly improved it it was possible to create a "master" KNX device from the KNX project file. The master KNX devices creates slave devices based on the contents of the project file, names the devices , group the devices and exactly configures each devices all based on the information in the KNX project file. When the KNX master is updated with a new projectfile all linked KNX slave devices are automatically updated. The source of truth is the KNX project file
ps I have a large KNX projectfile which can be used / examined which I can email on request.
When you currently import a large KNX Project file (> 100 devices) only the dropdown boxes are populated with all the available registers from the projectfile. You have to re-create all the Homey devices by hand by selecting 100+ drownboxes, sometimes 3 times per device. All the devices naming and group information is lost too. This re-creation process takes weeks of work for large project files.
In KNX projects the main source of truth is the KNX manager and updates the KNX project file. There is currently no way to keep the Homey KNX devices in sync with the projectfile which makes it unusable in time.
These two behaviours makes Homey unpractical for large KNX installations.
The usability for Homey in professional KNX installations would be greatly improved it it was possible to create a "master" KNX device from the KNX project file. The master KNX devices creates slave devices based on the contents of the project file, names the devices , group the devices and exactly configures each devices all based on the information in the KNX project file. When the KNX master is updated with a new projectfile all linked KNX slave devices are automatically updated. The source of truth is the KNX project file
ps I have a large KNX projectfile which can be used / examined which I can email on request.