I am setting up the semantic model and cannot find the proper way to define a “multi-command/multi-state” switch.
In sitemaps, this was achieved by Selection or mapping. What is the equivalent for semantic model points?
Why are points (and items…) so much specialized? Why don’t we just define one type of point * called genericpoint with the following characteristics:
- type of command it can receive (text or number or combination of both, with limits for numbers and list of valid text commands)
- type of state it can be set to (text or number)
- if it is able to process a command (yes for wall switches, light…, no for sensors)
- a switch is a genericpoint that only can receive ON and OFF and can be set to ON and OFF
- a dimmer is a genericpoint that can receive ON, OFF, DIM, BRIGHT or any number between 0 and 100 and can be set to any number between 0 and 100
- a rollershutter is a genericpoint that can receive UP, DOWN, STOP or any number between 0 and 100 and can be set to any number between 0 and 100
- a TV channel controller is a genericpoint that can receive any text corresponding to the list of channel and be set to any value of the corresponding list
- the audio setup of my AV system is a genericpoint that can be set to “stereo front”, “multichannel 7.1” or “stereo back”
- a light scene in a room is a genericpoint that can receive same commands as a dimmer + custom commands such a “NIGHT”, “MAX”, “WARM”, “READER”
I think you see the idea: reducing the number of types for points and making them much more versatile to use