Thank you Rich for your answer.
Aiiieeee, I admit that I am quite disappointed by the “poor” functionalities offered to user by openHAB, compared to the complexity of the “gas plant” which is the software.
Just doing a dummy thermostat user interface seems to be too much complicated for having confidence to go forward with this software.
I just give a look of what I did :
Here, the panel dedicated to a thermostat. This is OK for me, friendly, simply configurable by sitemap.
The functionality is :
In “AUTOMATIC” mode, my system transmits set-points to the thermostat on the basis of the configuration of a “day/night” periods (configurable in “Reglages/Horaires”) and a “day/night” temperatures (configurable in “Reglages/Temperatures”).
How configuration it works :
enter in Reglages/Horaires
enter “beginning of the day period”
as soon I modify a Setpoint, OK/CANCEL appears
when happy or not, I push OK or CANCEL
This action updates (or not) the variable storing the actual valid time
But from here, things go wrong!
Below are the misc. config elements used,
just to handle one parameter !
of just one dummy thermometer !
Perhaps I missed something basic !?
I cannot conceive another way than “OK/CANCEL” to handle safely user parameters and parameters consistency, mostly regarding the poor UI components available.
My master keywords are Modularity, Genericity, Coherency, and simplicity (if possible).
I let you imagine my problem when I have to dispatch configuration elements across 5 different files, configure thousands of rules / triggers without having the slightest notion of ARRAY and OBJECT,…
That being said :
In few time, I discovered z-wave, raspberry, z-wave thermostat and relay, and I agree that in very very few time, I had my devices binded and running with openHAB.
In very few time I had a simple interface (with android app) with which I communicated with my thermostat.
That is very efficient and simple.
What is the best solution to keep only the basis of the system, the bindings and the related “drivers”,
and to do all the automation aspects and visual aspects with … netbeans, by example, or an equivalent of .NET / ASP.NET, or C/C++ in multi-threading environment (for automation) ?
Make sense !?
Excuse me if I was a little “critic”, I don’t master very well English (at least in diplomatic aspect)
But respect !!! for a so huge system.
Text label="Horaires" icon="time"
Text item=Indoor_Time_Jour_str icon="sun"
Setpoint item=Indoor_Time_Jour_HR_nb minValue=0 maxValue=23 step=1
Setpoint item=Indoor_Time_Jour_MN_nb minValue=0 maxValue=55 step=5
Switch item=Indoor_Time_Jour_SetOK mappings=[2="OK", 3="CANCEL"] visibility=[Indoor_Time_Jour_SetOK!=0]
Number Indoor_Temp_Jour "Temp. Jour [%.1f °C]" <temperature_hot>
String Indoor_Time_Jour_str "Début Horaire Jour [%s]" <time>
Number Indoor_Time_Jour_HR_nb "Heure [%02d]" <clock>
Number Indoor_Time_Jour_MN_nb "Minute [%02d]" <clock>
Number Indoor_Time_Jour_SetOK ""
rule "Thermo Indoor Handle Indoor_Time_Jour modification"
when Item Indoor_Time_Jour_HR_nb changed
or Item Indoor_Time_Jour_MN_nb changed
rule "Thermo Indoor Handle Indoor_Time_Jour OK/CANCEL"
Item Indoor_Time_Jour_SetOK received update
if(Indoor_Time_Jour_SetOK.state == 2)
val String tmp = Indoor_Time_Jour_HR_nb.state.format("%02d") + ":" + Indoor_Time_Jour_MN_nb.state.format("%02d")
if(Indoor_Time_Jour_SetOK.state == 3)