-
Notifications
You must be signed in to change notification settings - Fork 782
Astro binding - Channel 'astro:sun:local:set#event' does not trigger #4018
Comments
Have you tried deleting your caches and restarting openHAB?
Because in the newest snapshots the problem of non firing events in the Astro binding should have been fixed. |
Hi,
I waited for the next morning, expecting the following rule to be triggered: `rule "Zonsopgang - nachtverlichting uit" when However, the rule is still not triggered. I run OpenHAB 2.2 on my Synology via chroot. |
This has been going on since #850 I believe and was reported by a lot of folks.
|
Same here... after some time it stops working. |
@Baumi1245 Do you have any logs when it last worked and once it stopped? I am especially interested in the time when this happened: Also that you are saying that the ntp binding is reporting wrong times is interesting. Can you elaborate a bit on this please? In which sense is it wrong? What is the offset? |
Hi,
|
@DriesA Please have a look on whether the 30seconds hack fixes the issue for your and if not feel free to reopen this issue. Thanks. |
I will test! In which build can I expect the fix? The upcoming #1029? |
You mean the #1029 build of openHAB? No, it will not be included there. In openHAB it takes until we release a new ESH stable and then the next openHAB build will contain the fix. But meanwhile you can uninstall the Astro binding via paperui and download the attached zip file and extract the containing jar file into the |
@triller-telekom
Just searched for astro in the log... last crash was around 23:00(30.08.) - ntp stopped. Could it be, that the Astro-Binding can´t fire if the ntp-binding does not work? |
Here is my setup...
No - no wrong times... it stops!
Everytime the Astro didn´t trigger, the NTP-time has stopped working. |
@triller-telekom : I can confirm the Astro JAR file you provided works, thanks!! This is what I did:
|
NTP stopped working at 11:53
Astro triggert three times today - next trigger is in the evening. |
FTR, the latest openHAB distro 1030 includes @triller-telekom's fix. |
I installed 1030 and can confirm that the triggers work as designed (again). @triller-telekom : excellent job! |
@kaimahnke Could you provide me the necessary .items, .things and alike that I can use to reproduce the problem that some Astro linked jobs are executed ahead of their scheduled time? |
@kgoderis , as mentioned above, everything works fine since build 1030. But I can provide the item and ruel files if it would help you. |
Dear,
When I was on build #986 (OH 2.2). I freshly installed the Astro binding and made the required 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-08-10 00:00:00.371 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:moon:local 2017-08-10 00:00:00.876 [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. So the values of all Astro-items are calculated correctly.
My current build is #1003.
It seems I am not the only one with this issue. See this thread on the OpenHAB Community.
Thank you for looking in to this.
The text was updated successfully, but these errors were encountered: