No, for non-technical people rules are going to be the hardest part. We have done a lot to make rules easier and are doing more all the time, but it’s going to be programming no matter what and programming is hard.
Assuming that 00:00-00:01 is a time that means the rule will only be allowed to run between midnight and one minute after midnight. I’m pretty sure that’s not what you want.
As James points out, that only controls the execution of the rule. It doesn’t do anything about the Items. You can update or command the Item at any time in a variety of ways such as from the sitemap.
The But only if… only prevents the things defined in the “Then” section of the rule from executing unless the conditions are met. That’s all.
With the one exception being that you can enable/disable/call another rule as an action in a rule.
Learning openHAB and rules coding in openHAB is just as big of a learning job, if not bigger.
Any home automation system is going to require you to learn you some programming. There is no way around that. Some relatively simple stuff can be done but as soon as you have anything more complicated than “when x happens flip the y relay” is going to require some programming.
Well, if you have a But only if… of between midnight and one minute after midnight that means that rule will only run when valve0 receives the command
open sometime between 00:00 and 00:01. The rule won’t run if valve0 happens to already be open before 00:00. The rule won’t run if you send the command
open to valve0 at any other time of day.
Also, the rule you posted doesn’t do anything like that. As written when valve0 receives the command
open it sends the command
open to valve0 (but valve0 already received an
open command an now we enter an infinite loop) and it sends the command
I assume these are all String Items? Usually it’s best to use the openHAB Item that is the most near to what’s going on. So for a relay or a valve which can only be open or closed, a Switch Item would make the most sense to use in openHAB. If you used a Switch Item, you’d be using ON and OFF as the commands and what you’d look for as the State and use a transformation to convert ON to “open” and OFF to “closed” in the Thing’s Channel config.
Anyway, it would help to show us your attempt at creating the rule that didn’t work. It might also help to see your Items and Thing configs. All of this stuff works together. When something goes wrong you need to get a full picture of the config.
One last little bit, even if you don’t really know programming real well it can still be useful to see some logging in a rule. You can most easily do that in a “codeless” rule like this by adding a Script Action, choosing Blockly and then add a log block to log out the states of relevant Items and such.
If all you need is to see if the rule is running, you can bring up the developer sidebar (alt-shift-d or from the Developer Tools page) and start the event stream. That will show your Items updating, receiving command, changes, and it will show when your rules run.