How to make automation to turn off a switch at xx:xx ?

[fableman]

How to I turn off a switch at 23:59 ?

I now use module: Logical rule
Boolean operator: or
Item: Time
>= 23:59

Action:
Item: Switch
OFF


But it dose not work at all!!

[n0ahg]

A logical rule simply checks a set of states i.e. time >= 23:59 AND motion sensor triggered

It does not schedule an action, you should use the ScheduledScene module if you want to set a scene at a specified time.

[fableman]

thanks for explaining this but...

I got strange GUI problems...

When I make a light scene and rename it to something nice.

Then I create a ScheduledScene and try to find the lightscene I just created , it's not there!!
But I do see alot other stuff thats not even scenes!!! (alarm triggers and , smoke detektors, I never created them, auto made i guess?!?!) and the 3rd try I did this then I see something called lightscene19.

Is this common GUI problems with Razberry software?

[n0ahg]

I'm also seeing names not being saved correctly or used in the expected places. You can use Preferences -> Widgets for now to check you have the correct scene.

BTW, I'm using Chrome on Windows 8.1 to access the automation interface running v2.0.1-rc18

[fableman]

Thanks for the tip with Widgets.

I use chrome aswell, but I belive this is a coding problem then browser problems.

I use RC18 aswell

[pz1]

thanks for explaining this but...

I got strange GUI problems...

When I make a light scene and rename it to something nice.

Then I create a ScheduledScene and try to find the lightscene I just created , it's not there!!
But I do see alot other stuff thats not even scenes!!! (alarm triggers and , smoke detektors, I never created them, auto made i guess?!?!) and the 3rd try I did this then I see something called lightscene19.

Is this common GUI problems with Razberry software?

This is not a GUI problem, but inherent to the HA engine. Actually it is no problem at all, but I admit it can be confusing and overwhelming.
These smoke detectors etc are virtual devices created by the system on the basis of your physical Z-Wave devices. So your Zwave multisensor is split into multiple normalised virtual devices like battery, humidity, luminescense, temperature etc. For the automation engine this means that it can deal with simple building blocks (lego like) to choose from. It allows for mixing of Zwave devices and others to configure functions with easy pick lists. Other technologies like EnOcean can now more easily be integrated.
It is a bit rough still, specifically for new users.
If you don't like the standard user interfaces, you could choose for other integration platforms like Domoticz etc., and as I did with OpenRemote

[n0ahg]

Since the new expert ui gives you the option of changing a devices name it should at least persist the name and make it available to the ha engine.

[pz1]

Since the new expert ui gives you the option of changing a devices name it should at least persist the name and make it available to the ha engine.

I fully agree, and similarly if you instanciate a new scene in HA, the name given to that scene should be given to the underlying widget at the same time