@rlkoshak Thanks! I don’t know why I did not see that. I changed local to home, hopefully that was the error.
I am actually using openhab 2.1.0, my bad, but 4.0.8 is what typing in ‘version’ returns in the openhab console… strange.
The duration is mainly a concern for when people want to have a switch that remains ON for the full sunset time so they can check the sunset state and do something different in other rules.
The time of day design pattern shoes how to use the events, DateTimes, and how to keep track of the time of day without letting your rules with duplicated if(now.isAfter(sunrise) && now.isBefore(noon)) statements.
hm, i tried now to set an event via channel astro:sun:local:set#start. As to me it looked the most promising to what i want to reach…a trigger when sunset starts. Did not trigger. So I had a second look and saw that in the docs its stated to use the following channel: astro:sun:home:rise#event
Will do the same analog for set event. but my question is - in order to use events I have to use this “range event” channel. It does not work to simply make use of another channel like the one for set_start (?)
rule "Zonsopgang - nachtverlichting uit"
Channel 'astro:sun:local:rise#event' triggered START
logInfo("Astro","De zon komt op. Goedemorgen.")
So I guess I got the naming correct, but it still doesn’t work. Any idea?
No, it’s not.
You have two or even more bindings started, but not one of them is active.
You screwed up your setup!
Delete any astro bindings you may have in your addons folder, then install the astro binding through PaperUI and make sure it is “active”, not started.
Also make sure you don’t have any bindings loaded in your addons.cfg.
Edit: okay, did not see the last couple of lines (too much beer this evening ).
If only ONE binding is active it should be fine. But why do you have so many astro bindings installed?
Clean up your installation, then it should work …
START LEVEL 100 , List Threshold: 50
ID | State | Lvl | Version | Name
202 | Active | 80 | 0.9.0.201706170545 | Astro Binding
openhab> feature:list|grep -i astro
esh-binding-astro | 0.9.0.SNAPSHOT | | Started | addons-2.2.0-SNAPSHOT |
openhab-binding-astro | 2.2.0.SNAPSHOT | x | Started | addons-2.2.0-SNAPSHOT | Astro Binding
So the duplicate entries have been removed.
So now I’ll have to wait untill the sun sets before I can check if the trigger is now triggered correctly (the values in items were already populated correctly before).