First of all: I’m not a programmer, but I will try to give the way I look at it, a way that might be wrong off course.
Blinking is a standard scene in digitalSTROM.
http://developer.digitalstrom.org/Architecture/dss-json.pdf >> page 71
Having it available in openHAB will reduce UI development time in openHAB a lot, and will keep the openHAB configuration much more transparant in relation to the digitalSTROM configuration ( they will be “the same”). In my opinion this is in line with the openHAB2 design philosophy to make openHAB “as standard as possible” to end-users.
User Defined States
UDS’s are standard functionality of digitalSTROM as from firmware version dSS V1.13.0 release notes.
User Defined States (UDS’s) are a kind of digitalSTROM environment variables/settings that can be created and set by the digitalSTROM user/configurator (dss-app in the configurator). The state of a created UDS can be set by rules in DigitalSTROM and/or by the user in de digitalSTROM UI (smartphone app) , e.g. an UDS with the name
Holiday and the states
ON HOLIDAY and/or
WORKING-MY-ASS-OFF. In a way they are similar to UDA’s but instead of triggering a range of actions, they set a state, which can be used in other rules and scripts on the dSS/dSS-apps, and hopefully in openHAB.
Again, this can be done in openHAB as well, but for the above mentioned reason it will be very nice to have it integrated in the digitalSTROM binding.
Availability of sessiontoken
If the development of the digitalSTROM-binding keeps in pace with the functionality of the digitalSTROM system, there’s no need at all for having the sessiontoken available in the binding.
But if not, when you want to make use of new digitalSTROM functionality that is not not (yet) available in the binding, you will need to code around it in openHAB using the digitalSTROM JSON “api”. To do that you have to get a sessiontoken (60secs valid) everytime. Since (I guess) it is already available in the binding, it can be used in openHAB and reduce coding. In effect: if UDA’s and UDS’s will not be available, I will try to get them through digitalSTROM JSON requests. dSS JSON architecture
I guess all of my feature requests relate to a redundancy discussion: redundant in the binding or redundant code in all of the scripts of openHAB users. Equivalances of UDA’s can be coded in openHAB as well, but a nice interface for this is all ready available on the dSS.