Hello
I do see that we have a Device 018.000 Scene Control to activate and learn KNX scenes
I was woundering what the best pratice would be for import this Group addresses and setup a template to call and learn them from the Interface
Thanks for the help in advance
Helo Ricardo
Thanks for your great explanaion
I took KNX scene aproach as they relay in KNX equipments and so keep decentralized funcionality ,
Fully agree comfortclick way more flexible
Bellow the aproach I took each Room as it own Group address
Perfect! If it works for you, the learn and run function are actually the ones you should really need in your case.
I understand the decentralized functionality requirement, but they are scenes, so I don't mind having those centralized functions.
Inevitably most of us end up centralizing several logic functions, tasks, etc, me included, because on bOS we can have some more powerful tools, that we won't find on any standalone KNX. When you find a product that's stable, and you can rely on the support, that gives you more confidence to work with.
If you use a KNX logic module for example, then you're also "centralizing". So...
So all my installations (and most of us here) are kind of hybrid. The main part is on the KNX devices, another big part is on the "brain" (bOS).
The fully decentralized installations, made sense several years ago, where we didn't have any "powerful and stable" servers we could rely to develop extra stable logics. Some of them were even running on Windows XP Home Edition (LOOOOL). We have stable Linux, and stable Windows IoT / Enterprise LTSB etc... and they are tough enough to handle with this logics now.
I can surely say now (this is not a commercial by any means) that I have several dozens of installations running with bOS and all of them are stable (needless to say that I monitor all of those installations, and the costumers can call me anytime to fix any issue). Smart homes and buildings / industry are actually a long term relationship between me and my costumers.
Best regards
Hello,
After I've started to work with ComfortClick, I confess that I've never used KNX scenes anymore, as the scenes on ComfortClick are easier for the costumer and more flexible for the installer, who can add / remove controls to the scenes remotely without using ETS. After all, they can also be triggered by KNX buttons, so for me they are a better way to use scenes.
But, if you need to use your own KNX scene addresses, my advise would be probably import the group address, and create your own template.
When you place the object on the visualization, you get several different options for control / status:
Scene number status;
Learn status;
Read value from address;
Write value from status address;
Write current value;
Activate scene;
Learn scene;
If was using scene control and learn functions, I would probably only use Scene Control, Learn Scene, Learn Status and Activate Scene.
Then you can adapt our visualization to be a little bit more pretty than my example below (it's just a very quick example without testing). There's almost endless ways you can design your own control.
Scene control button to choose the scene you want to learn;
Learn button to start learning and status to show if it's learning or if it's stopped;
And eventually an activate scene button;
But that's up to you. As I've said, as soon as I've started using the bOS Scenes, I never went back to the internal KNX scenes...
Give a chance to the bOS scenes, try them out, and you'll see that they are way more powerful and flexible for the costumer to change them.
These are all bOS scenes, available to be changed at any time (short press executes with a confirmation dialog, and long press opens up the scene devices to configure):
Best regards