My top is really light. The used memory and cpu is very low. So, I can say on openhabian mqtt binding don’t leak memory or cpu. Actually I never seen all that free memory with openhab. I use openhabian plus zigbee2mqtt on this raspy
Uninstalling and reinstalling the Sonos binding did fix my CPU usage problem.
Now all is well again…
1 Like
I seem to have generic problems with using group aggregation functions. In case of a groups of shutters, trying to get the floatValue() of the group results in AttributeError: 'org.eclipse.smarthome.core.types.UnDefType' object has no attribute 'floatValue'. Maybe this too has something to do with groups of lights not being visible in google assistant? Also, I get a new error 2019-11-19 07:40:39.199 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/event-stream, type=class org.glassfish.jersey.media.sse.OutboundEvent, genericType=class org.glassfish.jersey.media.sse.OutboundEvent. when trying to switch a light when a group of other lights reach a certain level.
Maybe there is a single underlying problem, I will try studying the logs a bit more.
OK, could resolve the first error with the floatValue() thing by giving a command to all shutters after the reboot. the AVG is undefined if at least one group member is undefined.
Resolved the 2nd issue by restarting openhab2 after some googling. So looks like everything is resolved now!
I had an interesting issue today. I am just starting to debug, but when I installed the 2.5m5 using apt looks like it broke my nginx.
I have not looked to see if the nginx package was updated in the process. I suspect this to be the case and the config file was overwritten. The issue is when I went to fix using openhabian the nginx config is broken. “Asking about this piece on git”
Thought I would post my findings for general knowledge. Working on fixing now.
The reverse proxy is fixed. I had to recreate the config file for nginx. I am uncertain why it was deleted. But reverse proxy works.
I updates using openhabian-config which basically uses apt. My nginx reverse proxy is still working fine on Debian.
Hue emulation is non functional for me on m5. There are issues posted on git already for hue emulation. But in my setup it will not function.
My config files that worked under 2.5m1 for the Dresden binding as well as the hue binding connecting to my emulated hub on Dresden don’t see the port correctly. I have my setup running on port 8090 and in my config files use 192.168.1.200:8090 but it still maps to port 80 and will not connect to my zigbee setup.
I will go and search git to see if this issue is sited. If not I will submit an issue.
Since I updated to 2.5 M5 I’m having stability issues with zwave:
2019-11-19 21:05:54.969 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Stopped ZWave serial handler
2019-11-19 21:05:55.165 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-binding-dominoswiss, openhab-binding-davis1'
2019-11-19 21:05:55.940 [INFO ] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null
2019-11-19 21:05:56.055 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/zwave'
2019-11-19 21:05:56.127 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
2019-11-19 21:05:56.159 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2019-11-19 21:05:56.160 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2019-11-19 21:06:54.949 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Stopped ZWave serial handler
2019-11-19 21:06:55.178 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-binding-dominoswiss, openhab-binding-davis1'
2019-11-19 21:06:55.870 [INFO ] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null
2019-11-19 21:06:55.998 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/zwave'
2019-11-19 21:06:56.092 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
2019-11-19 21:06:56.113 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2019-11-19 21:06:56.114 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
2019-11-19 21:09:54.721 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Stopped ZWave serial handler
2019-11-19 21:09:54.891 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-binding-dominoswiss, openhab-binding-davis1'
2019-11-19 21:09:55.536 [INFO ] [zwave.handler.ZWaveControllerHandler] - Attempting to add listener when controller is null
2019-11-19 21:09:55.649 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/zwave'
2019-11-19 21:09:55.676 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
2019-11-19 21:09:55.725 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2019-11-19 21:09:55.726 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
Every minute this error occures.
I’m using an Aeotec Zwave Gen5 USB Stick. It used to work with M4.
I tried to remove and reinstall the controller without success. Also an
openhab-cli clean-cache
did not help. Any further hint?
I would fix or remove the dominoswiss binding and the see if the zwave binding stabilizes. Zwave works fine for me.
Same here.
I’m missing many of my items after upgrading to 2.5M5 from 2.4. The items are there in the items file, but they are not seen in restdocs.
Sample error:
2019-11-19 21:21:45.456 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Rule 'Convert Temperature C to F': The name 'OUTDOOR_TEMPERATURE' cannot be resolved to an item or type; line 12, column 7, length 19
Yet my items file has:
Number OUTDOOR_TEMPERATURE "Outside in caps [%.1f °F]" <temperature>
I’ve stopped and restarted, cleaned the cache. What else can I try? Some of the items are there. So far I cannot spot any consistency between which items are there and which are not. There was no error in the log when the items file was loaded.
I removed the dominoswiss-Binding but am still getting the same zwave-error as above. After some hours of running, OH2 crashed with an Outofmemory Exeption:
2019-11-20 06:30:10.877 [ERROR] [pse.smarthome.model.script.Zwavedate] - Error reading json of zwave:device:58934352:node16 got Exception jva.lang.IllegalArgumentException: Invalid format: "
<meta http-equiv="..." 2019-11-20 06:30:15.897 [WARN ] [org.eclipse.jetty.server.HttpChannel] - /rest/things/zwave:device:58934352:node20 javax.servlet.ServletException: javax.servlet.ServletException: org.glassfish.jersey.server.ContainerException: java.lang.OutOfMemoryError: nable to create new native thread at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:88) ~[bundleFile:? at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.Server.handle(Server.java:494) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:374) [bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:268) [bundleFile:9.4.20.v20190813] at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) [bundleFile:9.4.20.v20190813] at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) [bundleFile:9.4.20.v20190813] at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) [bundleFile:9.4.20.v20190813] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) [bundleFile:9.4.20.v20190813] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) [bundleFile:9.4.20.v20190813] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) [bundleFile:9.4.20.v20190813] at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) [bundleFile:9.4.20.v20190813] at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:367) [bundleFile:9.4.20.v2019813] at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:782) [bundleFile:9.4.20.v20190813] at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:918) [bundleFile:9.4.20.v20190813] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131] Caused by: javax.servlet.ServletException: org.glassfish.jersey.server.ContainerException: java.lang.OutOfMemoryError: unable to create new ative thread at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:489) ~[?:?] at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) ~[?:?] at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388) ~[?:?] at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341) ~[?:?] at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228) ~[?:?] at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76) ~[?:?] at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:852) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:544) ~[bundleFile:9.4.20.v20190813] at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) ~[bundleFile:?] at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:536) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1581) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1307) ~[bundleFile:9.4.20.v20190813] at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:293) ~[bundleFile:?] at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:482) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1549) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1204) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) ~[bundleFile:9.4.20.v20190813] at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) ~[bundleFile:? ... 15 more Caused by: org.glassfish.jersey.server.ContainerException: java.lang.OutOfMemoryError: unable to create new native thread at org.glassfish.jersey.servlet.internal.ResponseWriter.rethrow(ResponseWriter.java:278) ~[?:?] at org.glassfish.jersey.servlet.internal.ResponseWriter.failure(ResponseWriter.java:260) ~[?:?] at org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:509) ~[?:?] at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:334) ~[?:?] at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) ~[?:?] at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) ~[?:?] at org.glassfish.jersey.internal.Errors.process(Errors.java:315) ~[?:?] at org.glassfish.jersey.internal.Errors.process(Errors.java:297) ~[?:?] at org.glassfish.jersey.internal.Errors.process(Errors.java:267) ~[?:?] at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) ~[?:?] at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305) ~[?:?] at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154) ~[?:?] at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473) ~[?:?] at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) ~[?:?] at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388) ~[?:?] at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341) ~[?:?] at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228) ~[?:?] at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76) ~[?:?] at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:852) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:544) ~[bundleFile:9.4.20.v20190813] at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) ~[bundleFile:?] at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:536) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1581) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1307) ~[bundleFile:9.4.20.v20190813] at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:293) ~[bundleFile:?] at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:482) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1549) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1204) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) ~[bundleFile:9.4.20.v20190813] at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) ~[bundleFile:? ... 15 more Caused by: java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) ~[?:1.8.0_131] at java.lang.Thread.start(Thread.java:717) ~[?:1.8.0_131] at org.eclipse.smarthome.io.rest.JSONResponse.createResponse(JSONResponse.java:181) ~[?:?] at org.eclipse.smarthome.io.rest.JSONResponse.createResponse(JSONResponse.java:88) ~[?:?] at org.eclipse.smarthome.io.rest.core.internal.thing.ThingResource.getThingResponse(ThingResource.java:656) ~[?:?] at org.eclipse.smarthome.io.rest.core.internal.thing.ThingResource.getByUID(ThingResource.java:270) ~[?:?] at sun.reflect.GeneratedMethodAccessor107.invoke(Unknown Source) ~[?:?] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_131] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_131] at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactoryjava:81) ~[?:?] at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:14) ~[?:?] at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:61) ~[?:?] at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDspatcherProvider.java:160) ~[?:?] at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.jav:99) ~[?:?] at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389) ~[?:?] at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347) ~[?:?] at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102) ~[?:?] at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326) ~[?:?] at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) ~[?:?] at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) ~[?:?] at org.glassfish.jersey.internal.Errors.process(Errors.java:315) ~[?:?] at org.glassfish.jersey.internal.Errors.process(Errors.java:297) ~[?:?] at org.glassfish.jersey.internal.Errors.process(Errors.java:267) ~[?:?] at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) ~[?:?] at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305) ~[?:?] at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154) ~[?:?] at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473) ~[?:?] at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) ~[?:?] at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388) ~[?:?] at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341) ~[?:?] at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228) ~[?:?] at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76) ~[?:?] at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:852) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:544) ~[bundleFile:9.4.20.v20190813] at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) ~[bundleFile:?] at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:536) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1581) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1307) ~[bundleFile:9.4.20.v20190813] at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:293) ~[bundleFile:?] at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:482) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1549) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1204) ~[bundleFile:9.4.20.v20190813] at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) ~[bundleFile:9.4.20.v20190813] at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) ~[bundleFile:? ... 15 more
Use code fences!!
What hardware are you using? You may have a memory issue or an SD card going bad.
I think I have found a bug which was introduced in M5. (or it is caused by Kodi 18.5, I can’t be sure because I just found out this now).
The Kodi binding show this error upon startup or on a bundle:refresh:
2019-11-20 16:32:15.390 [ERROR] [ome.core.thing.link.ThingLinkManager] - Exception occurred while informing handler: String index out of range: 10
java.lang.StringIndexOutOfBoundsException: String index out of range: 10
at java.lang.String.substring(String.java:1963) ~[?:1.8.0_222]
at org.eclipse.smarthome.core.library.types.DateTimeType.<init>(DateTimeType.java:121) ~[?:?]
at org.eclipse.smarthome.core.library.types.DecimalType.as(DecimalType.java:173) ~[?:?]
at org.eclipse.smarthome.core.internal.items.ItemStateConverterImpl.convertToAcceptedState(ItemStateConverterImpl.java:64) ~[?:?]
at org.eclipse.smarthome.core.thing.internal.profiles.ProfileCallbackImpl.sendUpdate(ProfileCallbackImpl.java:134) ~[?:?]
at org.eclipse.smarthome.core.thing.internal.profiles.SystemDefaultProfile.onStateUpdateFromHandler(SystemDefaultProfile.java:53) ~[?:?]
at org.eclipse.smarthome.core.thing.internal.CommunicationManager.lambda$9(CommunicationManager.java:467) ~[?:?]
at org.eclipse.smarthome.core.thing.internal.CommunicationManager.lambda$11(CommunicationManager.java:487) ~[?:?]
at java.lang.Iterable.forEach(Iterable.java:75) ~[?:1.8.0_222]
at org.eclipse.smarthome.core.thing.internal.CommunicationManager.handleCallFromHandler(CommunicationManager.java:483) ~[?:?]
at org.eclipse.smarthome.core.thing.internal.CommunicationManager.stateUpdated(CommunicationManager.java:465) ~[?:?]
at org.eclipse.smarthome.core.thing.internal.ThingManagerImpl$1.stateUpdated(ThingManagerImpl.java:168) ~[?:?]
at org.eclipse.smarthome.core.thing.binding.BaseThingHandler.updateState(BaseThingHandler.java:257) ~[?:?]
at org.eclipse.smarthome.core.thing.binding.BaseThingHandler.updateState(BaseThingHandler.java:276) ~[?:?]
at org.openhab.binding.kodi.internal.handler.KodiHandler.updateRating(KodiHandler.java:805) ~[?:?]
at org.openhab.binding.kodi.internal.protocol.KodiConnection.requestPlayerItemUpdate(KodiConnection.java:672) ~[?:?]
at org.openhab.binding.kodi.internal.protocol.KodiConnection.requestPlayerUpdate(KodiConnection.java:518) ~[?:?]
at org.openhab.binding.kodi.internal.protocol.KodiConnection.updatePlayerStatus(KodiConnection.java:509) ~[?:?]
at org.openhab.binding.kodi.internal.handler.KodiHandler.handleCommand(KodiHandler.java:306) ~[?:?]
at org.eclipse.smarthome.core.thing.binding.BaseThingHandler.channelLinked(BaseThingHandler.java:203) ~[?:?]
at org.eclipse.smarthome.core.thing.link.ThingLinkManager.lambda$0(ThingLinkManager.java:267) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_222]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_222]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_222]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_222]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_222]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_222]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_222]
Anyone has a clue why this happens? And some states are not updated (like current Time and total Time).
Anyone experienced the same? @cweitkamp Maybe can you help me?
I noticed the same in at least 2.5.0M4. Eventually the items came online.
1 Like
What I’ve noticed is that if I add a comment to an items file (no other changes) and then write out the file, then my items appear to come back. (Adding a comment may be irrelevant - it’s probably the write that helps.) Not sure why I need to do this.
I think the items have not yet been loaded when you see this error. By saving the file, the items are loaded immediately instead of where openHAB has put it in the queue.
Do you see this only at boot, or also after a few hours runtime? I only see it at boot.
Posting here to see if others are seeing this issue or not before I file the issue on github.
I have one instance of OH running in Docker which is exhibiting no problems what-so-ever.
However, I have another instance running on an RPi 3 that is losing it’s connection from the MQTT broker randomly. I’ve not yet been able to gather debug logs but will try to do so.
I have an event bus configured between the two OH instances and the remote instance is configured to publish a LWT message when the broker thinks it’s lost it’s connection.
-
On my Docker OH, it reports that the LWT message is sent and no more MQTT messages published by the RPi OH are received.
-
On the remote RPi:
- The broker thing shows as Online, I have no other MQTT things on this instance.
- Calls to publishMQTT generates a
WARNlogMQTT publish to <topic> failed!. - Restarting the Broker Thing bundle in the Karaf Console restores the connection and everything continues to work for a random number of hours.
Normally I’d assume that this is something I’ve messed up but I see that we’ve moved from Paho to HiveMQ for the client library so this might be a regression. But it’s odd that it works perfectly for my main OH.
One other thing that might be related is the remote RPi is truly remote (100 miles away) and it connects to my Mosquitto broker through an OpenVPN connection. So the network might not be completely solid between the two.
I’m running the latest Mosquitto on the same host as the Docker OH.
EDIT: I can confirm that the problem occurs when the network is interrupted between the broker and the remote client. I’m working to generate some logs and will file an issue.