http://docs.openhab.org/introduction.html
Eclipse Smarthome
This happens every couple of days, for history see:
https://hudson.eclipse.org/smarthome/job/SmartHomeDistribution-Stable/changes
http://docs.openhab.org/introduction.html
Eclipse Smarthome
This happens every couple of days, for history see:
https://hudson.eclipse.org/smarthome/job/SmartHomeDistribution-Stable/changes
Cool, thanks a lot. Kind of obvious but wasnât stil that clear to me Too many acronyms in ITâŚ
So again for my understanding: For the time being it is not possible to replace the jar until Kai has released a STABLE ESH version? In other words, before the STABLE release of 2.2 there is no chance to have a fixed astrobinding.jar?
Thanks again
If you want to stay on stable releases, you are right, you will have to wait for openHAB 2.2 stable.
You still can use snapshot bindings in openHAB2 (uninstall the binding via PaperUI, put the snapshot binding in your addons folder, restart openHAB).
I donât know if that is also possible with the astro binding, because it is part of ESH.
Thanks for clarification !
FTR: Major ESH upgrade in 2.2.0-SNAPSHOT
So in the latest 2.2.0-SNAPSHOT, the astro binding works smoothly!
I updated the astro binding. Letâs see
So when can we expect 2.2 stable then, please?
Is there someplace I can grab just the astro bindingâs JAR from SNAPSHOT and use that for now?
Iâm not brave enough to move to SNAPSHOT, but I am using astro and this bug is hitting me.
Iâm also not Java savvy, so building from source isnât an option for me.
Thanks for any help!
I havenât tried this, so use caution
Download zip from https://hudson.eclipse.org/smarthome/job/SmartHomeDistribution-Stable/
extract zip, find org.eclipse.smarthome.binding.astro_0.9.0.xyz.jar
install manually (donât forget to uninstall the existing astro binding first)
Maybe it wonât work since there are additional changes in the ESH distro in other jars also.
Moving to snapshot is really not something to worry about. It is as stable as the release build.
You can always revert back to 2.1 stable from snapshot if you donât like 2.2 snap
Okay, I uninstalled the astro binding, then dropped the jar into the addons folder, then restarted OpenHAB.
The astro binding started up with no errors, and rules are working, so weâll see what happens in a few days.
Thanks for your help!
Where did you download the JAR file, please? As I thought I had understood, Astro Binding is part of the core system and cannot be downloaded separately?
Happy to see that I might have been wrong
What Dim said worked for me, download the zip, and extract the jar from it manually.
I have not had any issues since I did this so it is a workaround.
Following @Dimâs suggestion to install the 0.9.0 astro binding seems to have resolved this issue for me as well.
I thought I would add a bit more detail here.
Trouble description:
After perhaps two weeks of normal operation, my astro-based rules stopped working. A reboot of the system would fix the problem, but the issue would re-appear after about two weeks.
Astro events stopped appearing in the event log, and the âQueue fullâ message appeared in the log file as noted by @spy0r, above.
System description:
I am running openHAB 2.1 on a raspberrypi using rasbpian jessie. I had installed the astro binding through the paperUI.
Resolution:
org.eclipse.smarthome.binding.astro_0.9.0.201708281632.jar
/usr/share/openhab2/addons
(note that this is for a Debian-like distribution)Once this is done, login to the Karaf console
ssh -p 8101 openhab@localhost
<- password is habopen
Issue the command
bundle:list |grep Astro
You should see a line indicating that the Astro binding is active.
N.B. The paperUI does NOT show that the binding is installed, but of course, it is.
For all who like to stay on the stable release:
After observing the logs within my graylog instance it seems that the faulty astro binding works for one week until âQueue fullâ strikes again.
Until 2.2 is stable I schedule an openHAB restart each sunday âŚ
Just want to put a +1 here. I did not observe the frequency but about two weeks seems correct.
i did check with the 0.9b but this does not help at all
openhab> bundle:list |grep Astro
181 | Active | 80 | 0.9.0.b5 | Astro Binding
017-09-03 00:00:00.028 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:moon:local
2017-09-03 00:00:00.063 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:sun:local
2017-09-03 00:00:00.071 [INFO ] [Manager$ExpressionThreadPoolExecutor] - Expression '0 0 0 3 9 ? 2017' has no future executions anymore
2017-09-03 00:00:00.076 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:moon:home
2017-09-03 00:00:00.075 [ERROR] [thome.binding.astro.internal.job.Job] - Queue full
java.lang.IllegalStateException: Queue full
at java.util.AbstractQueue.add(AbstractQueue.java:98)[:1.8.0_144]
at org.eclipse.smarthome.binding.astro.handler.AstroThingHandler.addJobToQueue(AstroThingHandler.java:314)[181:org.eclipse.smarthome.binding.astro:0.9.0.b5]
at org.eclipse.smarthome.binding.astro.internal.job.Job.schedule(Job.java:58)[181:org.eclipse.smarthome.binding.astro:0.9.0.b5]
at org.eclipse.smarthome.binding.astro.internal.job.Job.scheduleEvent(Job.java:94)[181:org.eclipse.smarthome.binding.astro:0.9.0.b5]
at org.eclipse.smarthome.binding.astro.internal.job.Job.scheduleRange(Job.java:115)[181:org.eclipse.smarthome.binding.astro:0.9.0.b5]
at org.eclipse.smarthome.binding.astro.internal.job.DailyJobSun.run(DailyJobSun.java:66)[181:org.eclipse.smarthome.binding.astro:0.9.0.b5]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_144]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_144]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_144]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_144]
at java.lang.Thread.run(Thread.java:748)[:1.8.0_144]
And from here it shuts down Openhab really complete - nothing works any moreâŚ
Is this still the solution if I am already running Astro Binding version 0.9.0.b5 ? I am running this on an openhab 2.1 and I am getting the queue error on a regular basis. Just wanted to make sure before I do all of this: deinstalling + reinstalling the binding from the current (openhab) snapshot fixes that?
Thanks!
Did you try it? I have the problem with âXXXXXX has no future executions anymoreâ. Also running on the release buildâŚ
Thank you in advance.
Edit: Not working for me - lots of errors with the Astro Binding â0.9.0.201712011551â
Same for me with org.eclipse.smarthome.binding.astro_0.9.0.201711242229.jar . More recent builds do not seem to work with 2.1 and older ones are not available any more on https://hudson.eclipse.org/smarthome/.
@bgilmer @kmeurer you happen to have your org.eclipse.smarthome.binding.astro_0.9.0.201708281632.jar (or the like) still somewhere lying around? Would appreciate a share, thanks a lot!
@GreenDaddy, I have that file. If you send me a PM, I will send you a share link.