Thanks for your answers!
I’ve been playing with OH3 for a couple of weeks, and had to restart from scratch a few times to make a robust structure, especially to have a good naming convention (as uid can’t be changed after creation, unless modifying the .json files, which I also did), in order to be able to easily use them in scripts.
About Location → Equipment → Point, this can’t always be used, at least with a KNX setup. For example, some lights of a room may not all be on the same physical relay (as the setup evolved with the years, I added/removed things; KNX is really nice for that). On the other end, I have some smart buttons with embedded temperature sensor, which are also able to handle the room heating. These are equipments.
So, here is what I finally did:
for lights, I created a generic global ‘KNX Lights’ device, and added all channels matching my lights GAD. Some of these GAD are not even linked to a specific light, but rather handle all lights of the house, or the ground floor, or the first floor, and so on.
for temperatures, as they match an equipment, I created a KNX Device for each KNX button. As said, some of these buttons also handle heating, so I added a heat control switch. I also created an HeliosVent Device, using the Modbus/Tcp gateway.
I’m still refining my naming convention, as I just found last night specific use case which breaks the one I chose. So, this week-end, I will have to play with rpl on json files to change that ;o)
There are a lot of things to understand in OH, some are well documented, some not (well, there is documentation for everything, but not always enough to understand how to correctly use them in a OH setup). Also, OH has a lot of features from previous versions which are no longer recommended. It can be confusing for beginners.
More generally, I found that all these powerful smart home softwares are more developers-oriented rather than users. That’s why I made my own web interface to control my KNX installation, a few years ago¹, but now, I would like something that other people in my house can manage (getting old, you realise you are not eternal). So, I’m trying to make things easy to understand, without fancy stuffs. For example, even if I’m a Python developer and love this language, I will only use Blocky for OH3 scripts.
For now, I think I have enough understanding to make a basic setup, but I will probably need some help for custom widgets, in the future.
Again, thank you for your help!
¹ Fred / pKNyXui · GitLab using Fred / pKNyX · GitLab (sorry, links on the mains web sites and documentation are down, as we migrated our server a few months ago, and didn’t take time to restart Trac).