With the latest snapshot from this morning #961 the astro binding does not trigger events anmyore:
openhab.log (one example from many):
2017-06-22 21:57:00.393 [INFO ] [Manager$ExpressionThreadPoolExecutor] - Expression '0 57 21 22 6 ? 2017' has no future executions anymore
During startup I’m seeing (restart does not solve the problem):
2017-06-22 15:03:10.439 [WARN ] [ig.xml.osgi.XmlDocumentBundleTracker] - The XML document '/ESH-INF/config/config.xml' in module 'org.eclipse.smarthome.binding.astro' could not be parsed: lat : lat
---- Debugging information ----
message : lat
cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException
cause-message : lat
class : java.util.ArrayList
required-type : java.util.ArrayList
converter-type : com.thoughtworks.xstream.converters.collections.CollectionConverter
path : /config-descriptions/config-description/parameter/description/lat
line number : 11
class[1] : org.eclipse.smarthome.config.core.ConfigDescriptionParameter
converter-type[1] : org.eclipse.smarthome.config.xml.ConfigDescriptionParameterConverter
class[2] : org.eclipse.smarthome.config.core.ConfigDescription
converter-type[2] : org.eclipse.smarthome.config.xml.ConfigDescriptionConverter
version : 1.4.7
-------------------------------
com.thoughtworks.xstream.converters.ConversionException: lat : lat
---- Debugging information ----
message : lat
cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException
cause-message : lat
class : java.util.ArrayList
required-type : java.util.ArrayList
converter-type : com.thoughtworks.xstream.converters.collections.CollectionConverter
path : /config-descriptions/config-description/parameter/description/lat
line number : 11
class[1] : org.eclipse.smarthome.config.core.ConfigDescriptionParameter
converter-type[1] : org.eclipse.smarthome.config.xml.ConfigDescriptionParameterConverter
class[2] : org.eclipse.smarthome.config.core.ConfigDescription
converter-type[2] : org.eclipse.smarthome.config.xml.ConfigDescriptionConverter
version : 1.4.7
-------------------------------
at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79)[98:org.eclipse.smarthome.config.xml:0.9.0.201706211154]
at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)[98:org.eclipse.smarthome.config.xml:0.9.0.201706211154] ...
Astro things and channels are GUI configured.
Edit: did the syntax for lat/lon change? Adding a new thing shows:
2017-06-22 23:04:58.149 [ERROR] [ding.astro.handler.AstroThingHandler] - Astro parameter geolocation is mandatory and must be configured, disabling thing 'astro:sun:d8d1e9c3'
2017-06-22 23:04:58.151 [ERROR] [ding.astro.handler.AstroThingHandler] - Astro parameters geolocation could not be split into latitude and longitude, disabling thing 'astro:sun:d8d1e9c3'
2017-06-22 23:04:58.153 [ERROR] [ding.astro.handler.AstroThingHandler] - Astro parameter interval must be in the range of 1-86400, disabling thing 'astro:sun:d8d1e9c3'
regardless if I use a comma between lat/lon or a colon …
Actually a better idea is to open an issue so those astro messages go into debug level log instead of info level log.
If you would raise your message log to WARN or even higher you may miss some needed messages …
Almost: because the astro binding is part of Eclipse it should have gone to:
But I’m sure you will get a message if it needs to be moved, so don’t worry.
And: it is always a good idea to link to a forum thread (like this one) to have a a reference and additional information for the maintainers.
I think that the INFO log entry is originating from org.eclipse.smarthome.core.scheduler (where Christoph applied the fix also)
try to lower the log level for that