[SOLVED] Astro binding problem - events do not trigger (multiple triggers solved)

Hi, I am using openhab 2.1-SNAPSHOT with the astro binding.

I have configured this thing for my rollershutters:

astro:sun:rolladen  [ geolocation="xx.xxxxx, yy.yyyyy", interval=60 ] {
    Channels:
        Type rangeEvent : rise#event [
            offset=-10,
	    earliest="08:00",
            latest="08:00"
        ]
	Type rangeEvent : set#event [
	    offset=30
	]
	Type start : rise#start [
            offset=-10,
	    earliest="08:00",
	    latest="08:00"
        ]
        Type end : set#start [
            offset=30
        ]
}

My rules for the rollershutters are the following:

rule "DOWN" 
when
	Channel	'astro:sun:rolladen:set#event' triggered START
then
	logInfo("Rolladen CTRL", "SET RULE TRIGGERED")
        ...
end

rule "Rolladen UP CTRL"
when
	Channel 'astro:sun:rolladen:rise#event' triggered START
then
        logInfo("Rolladen CTRL", "RISE RULE TRIGGERED")
        ...
end

Yesterday the rollershutters closed, but did not open this morning. As I looked into the events.log I saw no event fired for “rise#event”. As I then looked at the fired events for “set#event” I saw >4000 fired events! There were also thousands of events considering the moon thing.

Here is an excerpt of the events.log

...   
2017-06-20 23:49:05.050 [ChannelTriggeredEvent     ] - astro:sun:rolladen:set#event triggered START
2017-06-20 23:49:05.055 [ChannelTriggeredEvent     ] - astro:moon:home:set#event triggered END
2017-06-20 23:49:05.258 [ItemCommandEvent          ] - Item 'XYZ' received command DOWN
2017-06-20 23:49:06.053 [ChannelTriggeredEvent     ] - astro:sun:rolladen:set#event triggered START
2017-06-20 23:49:06.058 [ChannelTriggeredEvent     ] - astro:moon:home:set#event triggered END
2017-06-20 23:49:06.274 [ItemCommandEvent          ] - Item 'XYZ' received command DOWN
2017-06-20 23:49:07.034 [ChannelTriggeredEvent     ] - astro:sun:rolladen:set#event triggered START
2017-06-20 23:49:07.039 [ChannelTriggeredEvent     ] - astro:moon:home:set#event triggered END
2017-06-20 23:49:07.242 [ItemCommandEvent          ] - Item 'XYZ' received command DOWN
2017-06-20 23:49:08.049 [ChannelTriggeredEvent     ] - astro:sun:rolladen:set#event triggered START
2017-06-20 23:49:08.054 [ChannelTriggeredEvent     ] - astro:moon:home:set#event triggered END
2017-06-20 23:49:08.281 [ItemCommandEvent          ] - Item 'XYZ' received command DOWN
2017-06-20 23:49:09.048 [ChannelTriggeredEvent     ] - astro:sun:rolladen:set#event triggered START
2017-06-20 23:49:09.052 [ChannelTriggeredEvent     ] - astro:moon:home:set#event triggered END
...

Item XYZ is my rollershutter for testing. The event began to fire around 22:20 and still fired over one hour later.

Am I missing anything or is this a known bug in the SNAPSHOT?

Additional info from karaf:

openhab> feature:list | grep -i astro
openhab-binding-astro1                      | 1.10.0.SNAPSHOT  |          | Uninstalled | openhab-addons-legacy-2.1.0-SNAPSHOT | Astro Binding (1.x)
esh-binding-astro                           | 0.9.0.SNAPSHOT   |          | Started     | addons-2.1.0-SNAPSHOT                |
openhab-binding-astro                       | 2.1.0.SNAPSHOT   | x        | Started     | addons-2.1.0-SNAPSHOT                | Astro Binding


openhab> bundle:list -s | grep -i astro
177 | Active   |  80 | 0.9.0.201706191632     | Astro Binding                                          | org.eclipse.smarthome.binding.astro

Maybe you can give me a hint what I am doing wrong @gerrieg?
Thanks in advance!

Hi,
i got yesterday evening the same Problem.

I use lastet Snapshot 2.1.0~20170620042803-1

2017-06-20 21:37:15.026 [ItemCommandEvent          ] - Item 'Rollo_EG_Flur' received command 100
2017-06-20 21:37:16.015 [ItemCommandEvent          ] - Item 'Rollo_EG_Flur' received command 100
2017-06-20 21:37:17.020 [ItemCommandEvent          ] - Item 'Rollo_EG_Flur' received command 100
2017-06-20 21:37:18.014 [ItemCommandEvent          ] - Item 'Rollo_EG_Flur' received command 100
2017-06-20 21:37:19.021 [ItemCommandEvent          ] - Item 'Rollo_EG_Flur' received command 100
2017-06-20 21:37:20.028 [ItemCommandEvent          ] - Item 'Rollo_EG_Flur' received command 100
2017-06-20 21:37:21.013 [ItemCommandEvent          ] - Item 'Rollo_EG_Flur' received command 100
2017-06-20 21:37:22.023 [ItemCommandEvent          ] - Item 'Rollo_EG_Flur' received command 100
2017-06-20 21:37:23.018 [ItemCommandEvent          ] - Item 'Rollo_EG_Flur' received command 100

This where the first time where this happen. I hope it was the last time :wink:

See existing thread

@rossko57: Thanks, didn’t see this one, sorry!

The thousands of triggered events are solved for me with latest SNAPSHOT from 21.06. but I still have the problem, that some events are NOT fired.

See events.log

2017-06-21 16:17:56.626 [hingStatusInfoChangedEvent] - 'astro:sun:rolladen' changed from INITIALIZING to ONLINE
2017-06-21 22:21:00.036 [ChannelTriggeredEvent     ] - astro:sun:rolladen:set#event triggered START
2017-06-21 22:25:00.023 [ChannelTriggeredEvent     ] - astro:sun:rolladen:set#event triggered END
2017-06-21 22:44:00.042 [ChannelTriggeredEvent     ] - astro:sun:rolladen:civilDusk#event triggered END
2017-06-22 08:00:00.047 [ChannelTriggeredEvent     ] - astro:sun:rolladen:rise#event triggered END

These are ALL events that I can find in my events.log. I am e.g. missing

rise#event START
civilDusk#event START

My openhab.log says the following

2017-06-21 16:17:56.499 [DEBUG] [ding.astro.handler.AstroThingHandler] - Thing astro:sun:rolladen initialized ONLINE
2017-06-21 16:17:56.996 [DEBUG] [ding.astro.handler.AstroThingHandler] - Publishing planet Sun for thing astro:sun:rolladen
2017-06-21 16:17:57.106 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:sun:rolladen
2017-06-21 16:17:57.113 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-21T22:21:00
2017-06-21 16:17:57.140 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-21T22:25:00
2017-06-21 16:17:57.147 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-21T22:44:00
2017-06-21 16:17:57.151 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-21T21:55:00
2017-06-21 16:17:57.156 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-21T22:44:00
2017-06-21 16:17:57.169 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-21T21:51:00
2017-06-21 16:17:57.174 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-21T21:51:00
2017-06-21 16:17:57.200 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-21T22:44:00
2017-06-21 16:17:57.205 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-21T21:55:00
2017-06-22 00:00:00.342 [DEBUG] [ding.astro.handler.AstroThingHandler] - Publishing planet Sun for thing astro:sun:rolladen
2017-06-22 00:00:00.386 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:sun:rolladen
2017-06-22 00:00:00.403 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T08:00:00
2017-06-22 00:00:00.408 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T08:00:00
2017-06-22 00:00:00.425 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T22:21:00
2017-06-22 00:00:00.432 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T22:26:00
2017-06-22 00:00:00.449 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T13:34:00
2017-06-22 00:00:00.464 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T13:35:00
2017-06-22 00:00:00.477 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T00:00:00
2017-06-22 00:00:00.482 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T03:04:00
2017-06-22 00:00:00.503 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T03:04:00
2017-06-22 00:00:00.522 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T04:23:00
2017-06-22 00:00:00.527 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T04:23:00
2017-06-22 00:00:00.536 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T05:12:00
2017-06-22 00:00:00.551 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T22:44:00
2017-06-22 00:00:00.562 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T21:56:00
2017-06-22 00:00:00.572 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T22:44:00
2017-06-22 00:00:00.576 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T05:16:00
2017-06-22 00:00:00.581 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T21:51:00
2017-06-22 00:00:00.586 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T05:12:00
2017-06-22 00:00:00.591 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T21:51:00
2017-06-22 00:00:00.595 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T13:34:00
2017-06-22 00:00:00.600 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T05:16:00
2017-06-22 00:00:00.604 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T03:04:00
2017-06-22 00:00:00.609 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T04:23:00
2017-06-22 00:00:00.613 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T22:44:00
2017-06-22 00:00:00.617 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T21:56:00

Can anyone give me a hint what may be wrong?
Thanks in advance!

The scheduler in the astro binding has been replaced with this PR
I do not know the changes, you have to contact amitjoy

Hi @gerrieg, thanks for that!

This morning the START event of rise#event triggered, but no END event. Seems to be a little random what events are fired and what events are lost…

@gerrieg I hope that you are still helping to support that binding - note that amitjoy only tried to do the refactoring from Quartz to the ESH scheduler (as you mentioned that you were lacking the time for that change), which should (in theory) not have had any functional impact on the binding. Please also help reviewing such PRs as you are the best person to judge whether it is done correctly and what was the reason for some of the design decisions.

1 Like

Same here,
since the scheduler changed, the astro events ar mostly not triggered any more.

First it will be helpfull to see in the debug-log, for what event the scheduler is created:

2017-06-22 00:00:00.464 [DEBUG] [thome.binding.astro.internal.job.Job] - Scheduled astro job for thing astro:sun:rolladen at 2017-06-22T13:35:00

in the old versions you see the event for wich the scheduler was created:

2017-06-23 10:35:39.405 [DEBUG] [.astro.internal.job.AbstractDailyJob] - Scheduled astro job-event-start-set#event for thing astro:sun:home at 2017-06-23T21:21:00
2017-06-23 10:35:39.406 [DEBUG] [.astro.internal.job.AbstractDailyJob] - Scheduled astro job-event-end-set#event for thing astro:sun:home at 2017-06-23T21:26:00
2017-06-23 10:35:39.408 [DEBUG] [.astro.internal.job.AbstractDailyJob] - Scheduled astro job-event-start-noon#event for thing astro:sun:home at 2017-06-23T13:24:00
2017-06-23 10:35:39.409 [DEBUG] [.astro.internal.job.AbstractDailyJob] - Scheduled astro job-event-end-noon#event for thing astro:sun:home at 2017-06-23T13:25:00
2017-06-23 10:35:39.411 [DEBUG] [.astro.internal.job.AbstractDailyJob] - Scheduled astro job-event-start-nauticDusk#event for thing astro:sun:home at 2017-06-23T22:20:00
2017-06-23 10:35:39.413 [DEBUG] [.astro.internal.job.AbstractDailyJob] - Scheduled astro job-event-start-civilDusk#event for thing astro:sun:home at 2017-06-23T21:46:00
2017-06-23 10:35:39.414 [DEBUG] [.astro.internal.job.AbstractDailyJob] - Scheduled astro job-event-end-civilDusk#event for thing astro:sun:home at 2017-06-23T22:40:00
2017-06-23 10:35:39.415 [DEBUG] [.astro.internal.job.AbstractDailyJob] - Scheduled astro job-event-end-daylight#event for thing astro:sun:home at 2017-06-23T21:21:00
2017-06-23 10:35:39.417 [DEBUG] [.astro.internal.job.AbstractDailyJob] - Scheduled astro job-sunPhase-sun_set for thing astro:sun:home at 2017-06-23T21:51:00
2017-06-23 10:35:39.418 [DEBUG] [.astro.internal.job.AbstractDailyJob] - Scheduled astro job-sunPhase-noon for thing astro:sun:home at 2017-06-23T13:24:00
2017-06-23 10:35:39.420 [DEBUG] [.astro.internal.job.AbstractDailyJob] - Scheduled astro job-sunPhase-nautic_dusk for thing astro:sun:home at 2017-06-23T22:50:00
2017-06-23 10:35:39.421 [DEBUG] [.astro.internal.job.AbstractDailyJob] - Scheduled astro job-sunPhase-civil_dusk for thing astro:sun:home at 2017-06-23T21:56:00
2017-06-23 10:35:39.422 [INFO ] [.astro.internal.job.AbstractDailyJob] - Scheduled astro event-jobs for thing astro:sun:home

@Kai

I hope that you are still helping to support that binding

Sure, at the moment i am quite busy and i am going to leave soon, so in the next few weeks i will not have time…

Ok, perfect - enjoy your well-deserved holidays :sunglasses:

I had posted my issues with the Astro binding scheduler here . In the meantime I cleaned up all links from old configs as suggested, created a new channel, items and rules.
The result is that now:

  • the channels only fire on the day I started OH2, but nothing after midnight (e. g. nautic dawn, civil dawn), although event jobs get scheduled
(23:59:58.512 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:sun:home)
  • nothing fires at all after one day has elapsed with the system running.

I started OH2 in debug mode and also specifically log the binding:

log4j.logger.org.openhab.binding.astro = DEBUG, astro

As everything was working for months up until I switched to build 983 from 885 I assume the changed made to the scheduler broke the binding. Is there a way to get the last working version of the binding back?

I think I have the same problem.

I’m current on OH 2.2, build #988. I freshly installed the Astro binding when I was on build #986 (so with the new ESH version). And made all the settings.

I have the following rule:


rule "Zonsondergang - nachtverlichting aan"

when
    Channel 'astro:sun:local:set#event' triggered START 
then
	logInfo("Astro","De zon gaat onder. Slaapwel.")
        sendCommand(KNX_GV_Nachtverlichting_4_2_0, ON)
end

It does not get triggered.

At midnight I do see this:

2017-07-21 00:00:00.050 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:moon:local
2017-07-21 00:00:00.282 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:sun:local

If I check out the value of my Astro-items, the sun should have risen on 05:50 and will set at 21h37.

DateTime Astro_Sunrise_Starttime		"Zonsopgang [%1$tH:%1$tM]"  									<sunrise>			(gAstro)		{ channel="astro:sun:local:rise#start" }
DateTime Astro_Sunset_Starttime			"Zonsondergang [%1$tH:%1$tM]"  									<sunset>			(gAstro)		{ channel="astro:sun:local:set#start" }

I checked outside, the sun has actually risen. So I think the bug is in OpenHAB and not in the coding of the sun. :wink:

Sounds familiar. Did a fresh install of the system, build #988 yesterday as well (including moving all the zwave stuff :frowning: )
Started the system and all astro item initialized correctly.

16:12:04.507 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:sun:home
16:12:04.514 [INFO ] [marthome.event.ItemStateChangedEvent] - Sunrise_Time changed from NULL to 2017-07-20T06:04:00.000-0500
16:12:04.517 [INFO ] [marthome.event.ItemStateChangedEvent] - Sunset_Time changed from NULL to 2017-07-20T19:53:00.000-0500
16:12:04.521 [INFO ] [marthome.event.ItemStateChangedEvent] - NauticDawn_Time changed from NULL to 2017-07-20T05:05:00.000-0500
16:12:04.524 [INFO ] [marthome.event.ItemStateChangedEvent] - CivilDawn_Time changed from NULL to 2017-07-20T05:38:00.000-0500
16:12:04.527 [INFO ] [marthome.event.ItemStateChangedEvent] - NauticDusk_Time changed from NULL to 2017-07-20T20:23:00.000-0500
16:12:04.529 [INFO ] [marthome.event.ItemStateChangedEvent] - CivilDusk_Time changed from NULL to 2017-07-20T19:56:00.000-0500

Then the channels fired yesterday evening as expected, i. e. civil dusk, nautical dusk:

19:55:59.613 [INFO ] [marthome.event.ChannelTriggeredEvent] - astro:sun:home:civilDusk#event triggered START
19:55:59.613 [INFO ] [marthome.event.ChannelTriggeredEvent] - astro:sun:home:set#event triggered END
20:22:59.568 [INFO ] [marthome.event.ChannelTriggeredEvent] - astro:sun:home:civilDusk#event triggered END
20:22:59.569 [INFO ] [marthome.event.ChannelTriggeredEvent] - astro:sun:home:nauticDusk#event triggered START

At midnight got the same scheduling message :

23:59:59.197 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:sun:home

Update: I tested the values of select items today (2017-07-21, 11:45), and here’s the result:

11:46:00.102 [INFO ] [eclipse.smarthome.model.script.event] - Civil dawn: CivilDawn_Time (Type=DateTimeItem, State=**2017-07-20**T05:38:00.000-0500, Label=Civil Dawn, Category=null)
11:46:00.103 [INFO ] [eclipse.smarthome.model.script.event] - Nautic dawn: NauticDawn_Time (Type=DateTimeItem, State=**2017-07-20**T05:05:00.000-0500, Label=Nautic Dawn, Category=null)

No wonder nothing happens after midnight.
So I guess once we have a change of date the scheduler doesn’t work correctly any more, which renders the binding useless for the time being.

Here the same problem.
Version 2.2.0-SNAPSHOT Build #988.

At midnight this message:

2017-07-21 23:59:59.982 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:sun:22f155ed

At startup this message:

2017-07-22 09:00:43.800 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:sun:22f155ed

After the job scheduling at 1 second before midnight on 2017-07-21:

23:59:59.652 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:sun:home

here’s the output of a rule scheduled for 1 minute after midnight:

00:01:00.009 [INFO ] [eclipse.smarthome.model.script.event] - Civil dawn: CivilDawn_Time (Type=DateTimeItem, State=2017-07-21T05:38:00.000-0500, Label=Civil Dawn, Category=null, Groups=[Astro])
00:01:00.010 [INFO ] [eclipse.smarthome.model.script.event] - Nautic dawn: NauticDawn_Time (Type=DateTimeItem, State=2017-07-21T05:06:00.000-0500, Label=Nautic Dawn, Category=null, Groups=[Astro])

So it seems that the scheduler indeed uses the current day (the one before midnight at the time of scheduling), and not the next day (2017-07-22).
That would at least explain why the dawn events do not fire at all.

This evening at 19:55 Civil Dawn should have fired and turned on the lights, as expected nothing happened.

Another update:

For one day the scheduler on midnight generated thiese messages:

23:59:57.426 [INFO ] [marthome.event.ItemStateChangedEvent] - NauticDusk_Time changed from 2017-07-21T20:22:00.000-0500 to 2017-07-22T20:22:00.000-0500
23:59:57.427 [INFO ] [marthome.event.ItemStateChangedEvent] - CivilDusk_Time changed from 2017-07-21T19:55:00.000-0500 to 2017-07-22T19:55:00.000-0500
00:00:00.015 [INFO ] [marthome.event.ItemStateChangedEvent] - Sunrise_Time changed from 2017-07-22T06:06:00.000-0500 to 2017-07-23T06:06:00.000-0500
00:00:00.016 [INFO ] [marthome.event.ItemStateChangedEvent] - Sunset_Time changed from 2017-07-22T19:52:00.000-0500 to 2017-07-23T19:52:00.000-0500
00:00:00.016 [INFO ] [marthome.event.ItemStateChangedEvent] - NauticDawn_Time changed from 2017-07-22T05:07:00.000-0500 to 2017-07-23T05:07:00.000-0500
00:00:00.017 [INFO ] [marthome.event.ItemStateChangedEvent] - CivilDawn_Time changed from 2017-07-22T05:39:00.000-0500 to 2017-07-23T05:39:00.000-0500
00:00:00.017 [INFO ] [marthome.event.ItemStateChangedEvent] - NauticDusk_Time changed from 2017-07-22T20:22:00.000-0500 to 2017-07-23T20:21:00.000-0500
00:00:00.017 [INFO ] [marthome.event.ItemStateChangedEvent] - CivilDusk_Time changed from 2017-07-22T19:55:00.000-0500 to 2017-07-23T19:54:00.000-0500

Note that the times for the new day are correct.
This led me to believe that there respective rules would finally be triggered - unfortunately, nothing happened again.
The following day midnight the job only logged the usual

23:59:57.421 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:sun:home

On my side it seems that the trigger is working for exactly 7 Days after that, the binding stop triggering. I install a new system on 04.07. first time it stops on 11.07.

I restart the system on 20.07. without any changes. and the trigger was working again to yesterday, it stops again. Today I restart again and will see if the trigger is working tomorrow…

Is there any solution? With this status the astro binding is useless!

My configuration and schedule you find here: Astro Binding: Event triggered Start bt no light switch on

Same for me.
It is stopping after some days. After restarting OH (2.1) it is fine for some days and is stopping to trigger the events again.
I do use mainly triggers with offsets to the normal sunset (-60 Min & +20 Min).

You are not alone:

so I guess it is time to create an issue from any of you in: