Very nice 👍 When the implementation of more function like : scene, clima, rgbw/hcl light, hvac thermostat, locks, access control, sensors, doors, etc…. ? 🙏
@@michaelcritchf I would say that all the functions required by a KNX electrical system should be added. So all types of lighting management, then On/Off, dimmer, HCL, RGB, RGBW, HSV. All types of shading management, such as shutters, venetian blinds with slats, including limit switches and the state of movement. The weather stations, with all the sensors. The management of temperature, humidity CO2, VOC, lux, pressure, wind, proximity sensors, etc. Scenarios via central and 1 Byte commands. And much more. If the goal is really to create group addresses through functions, making the classic method we have used so far a method to be abandoned. Then you have to foresee all the possible functions that a KNX system may need, which are really many. If then the functions will be used for semantic export, to be used in IOT integrations and for the self-configuration of KNX supervisors, then all the more reason many more functions must be provided, compared to those proposed by ETS6 today. I congratulate you for the excellent work you have been doing for 34 years now. And I take this opportunity to ask you when you will make ETS6 a software with more accessible periodic pay-per-use cloud licenses, as streaming platforms already do (e.g. Netflix, Apple TV, etc..). If you could pay €10 per month to use a cloud license, you would drastically cut down the economic raving to use ETS, further encouraging new users to adopt the KNX standard. 🙏
The use of Building Functions adds an aggregation layer in the Building other than the Group Structure that would be relied on otherwise. An example for working with Functions: A Function "Ceiling Light" has a location "Office 2.251" on the "Second Floor". With that, the Groups included in that Function have short Descriptions such as "Switch On/Off". Doing the same without the use of Functions would require the ETS User to give more comprehensive Group Descriptions, such as "Main Building 2nd Floor Room 2.251 Ceiling Light Switch On/Off". When working with Functions, the additional context of Location and Function is displayed next to the Group Description on the Device Objects, in the Group Monitors and in Reports. Lastly, Visualizations can make use of this added context information from the ETS Project or Semantic Export and create Rooms and Functions based on this information. Hope this helps☺
Very nice 👍
When the implementation of more function like : scene, clima, rgbw/hcl light, hvac thermostat, locks, access control, sensors, doors, etc…. ? 🙏
Good suggestions! Any other recommendations, or suggested groups to be included in each?
@@michaelcritchf I would say that all the functions required by a KNX electrical system should be added.
So all types of lighting management, then On/Off, dimmer, HCL, RGB, RGBW, HSV.
All types of shading management, such as shutters, venetian blinds with slats, including limit switches and the state of movement.
The weather stations, with all the sensors.
The management of temperature, humidity CO2, VOC, lux, pressure, wind, proximity sensors, etc.
Scenarios via central and 1 Byte commands.
And much more.
If the goal is really to create group addresses through functions, making the classic method we have used so far a method to be abandoned. Then you have to foresee all the possible functions that a KNX system may need, which are really many.
If then the functions will be used for semantic export, to be used in IOT integrations and for the self-configuration of KNX supervisors, then all the more reason many more functions must be provided, compared to those proposed by ETS6 today.
I congratulate you for the excellent work you have been doing for 34 years now. And I take this opportunity to ask you when you will make ETS6 a software with more accessible periodic pay-per-use cloud licenses, as streaming platforms already do (e.g. Netflix, Apple TV, etc..). If you could pay €10 per month to use a cloud license, you would drastically cut down the economic raving to use ETS, further encouraging new users to adopt the KNX standard.
🙏
Oh very nice
Why do we use the building function?
What are the benefits of using the building function?
The use of Building Functions adds an aggregation layer in the Building other than the Group Structure that would be relied on otherwise. An example for working with Functions:
A Function "Ceiling Light" has a location "Office 2.251" on the "Second Floor".
With that, the Groups included in that Function have short Descriptions such as "Switch On/Off".
Doing the same without the use of Functions would require the ETS User to give more comprehensive Group Descriptions, such as "Main Building 2nd Floor Room 2.251 Ceiling Light Switch On/Off".
When working with Functions, the additional context of Location and Function is displayed next to the Group Description on the Device Objects, in the Group Monitors and in Reports.
Lastly, Visualizations can make use of this added context information from the ETS Project or Semantic Export and create Rooms and Functions based on this information.
Hope this helps☺
@@KNXAssociation thanks for your explain