Error loading rule list

They’re Items. It’s going to make your life simpler if you can see the difference between Items and Things
Items are openHABs internal models of simple “devices” - switch, number, string. Items are used in rules and UI
Things are descriptions of external devices or services.
channels link Items to Things.

ok I dont get it anymore, I had some sitemap.save copies of the main sitemap and when I deleted it it is all ok now but the rule is still not working.

2020-06-17 21:08:32.484 [ome.event.ItemCommandEvent] - Item 'FibaroDimmer1_DimmerSwitch1' received command 100

2020-06-17 21:08:32.569 [nt.ItemStatePredictedEvent] - FibaroDimmer1_DimmerSwitch1 predicted to become 100

2020-06-17 21:08:32.608 [vent.ItemStateChangedEvent] - FibaroDimmer1_DimmerSwitch1 changed from 0 to 100

2020-06-17 21:08:33.969 [ome.event.ItemCommandEvent] - Item 'FibaroDimmer1_DimmerSwitch1' received command 0

2020-06-17 21:08:34.014 [nt.ItemStatePredictedEvent] - FibaroDimmer1_DimmerSwitch1 predicted to become 0

2020-06-17 21:08:34.041 [vent.ItemStateChangedEvent] - FibaroDimmer1_DimmerSwitch1 changed from 100 to 0

2020-06-17 21:08:34.982 [ome.event.ItemCommandEvent] - Item 'Fibaro_Dimmer1' received command ON

2020-06-17 21:08:35.021 [nt.ItemStatePredictedEvent] - Fibaro_Dimmer1 predicted to become ON

2020-06-17 21:08:35.046 [vent.ItemStateChangedEvent] - Fibaro_Dimmer1 changed from OFF to ON

2020-06-17 21:08:35.934 [ome.event.ItemCommandEvent] - Item 'Fibaro_Dimmer1' received command OFF

2020-06-17 21:08:35.981 [nt.ItemStatePredictedEvent] - Fibaro_Dimmer1 predicted to become OFF

2020-06-17 21:08:35.993 [vent.ItemStateChangedEvent] - Fibaro_Dimmer1 changed from ON to OFF

2020-06-17 21:08:37.231 [ome.event.ItemCommandEvent] - Item 'zwave_device_3de88f51_node14_alarm_motion' received command OFF

2020-06-17 21:08:37.273 [nt.ItemStatePredictedEvent] - zwave_device_3de88f51_node14_alarm_motion predicted to become OFF

2020-06-17 21:08:37.299 [vent.ItemStateChangedEvent] - zwave_device_3de88f51_node14_alarm_motion changed from ON to OFF

2020-06-17 21:08:37.930 [ome.event.ItemCommandEvent] - Item 'zwave_device_3de88f51_node14_alarm_motion' received command ON

2020-06-17 21:08:37.970 [nt.ItemStatePredictedEvent] - zwave_device_3de88f51_node14_alarm_motion predicted to become ON

2020-06-17 21:08:37.997 [vent.ItemStateChangedEvent] - zwave_device_3de88f51_node14_alarm_motion changed from OFF to ON

2020-06-17 21:08:39.023 [ome.event.ItemCommandEvent] - Item 'demo_motion' received command ON

2020-06-17 21:08:39.068 [nt.ItemStatePredictedEvent] - demo_motion predicted to become ON

2020-06-17 21:08:39.099 [vent.ItemStateChangedEvent] - demo_motion changed from OFF to ON

2020-06-17 21:08:39.120 [ome.event.ItemCommandEvent] - Item 'FibaroDimmer1_DimmerSwitch1' received command ON

2020-06-17 21:08:39.143 [nt.ItemStatePredictedEvent] - FibaroDimmer1_DimmerSwitch1 predicted to become ON

2020-06-17 21:08:39.155 [vent.ItemStateChangedEvent] - FibaroDimmer1_DimmerSwitch1 changed from 0 to 100

2020-06-17 21:08:39.906 [ome.event.ItemCommandEvent] - Item 'demo_motion' received command OFF

2020-06-17 21:08:39.946 [nt.ItemStatePredictedEvent] - demo_motion predicted to become OFF

2020-06-17 21:08:39.965 [vent.ItemStateChangedEvent] - demo_motion changed from ON to OFF

2020-06-17 21:08:39.983 [ome.event.ItemCommandEvent] - Item 'FibaroDimmer1_DimmerSwitch1' received command OFF

2020-06-17 21:08:40.023 [nt.ItemStatePredictedEvent] - FibaroDimmer1_DimmerSwitch1 predicted to become OFF

2020-06-17 21:08:40.041 [vent.ItemStateChangedEvent] - FibaroDimmer1_DimmerSwitch1 changed from 100 to 0

2020-06-17 21:17:00.008 [vent.ChannelTriggeredEvent] - astro:sun:local:daylight#event triggered END

2020-06-17 21:17:00.013 [vent.ChannelTriggeredEvent] - astro:sun:local:set#event triggered START

2020-06-17 21:22:00.002 [vent.ChannelTriggeredEvent] - astro:sun:local:set#event triggered END

2020-06-17 21:22:00.005 [vent.ChannelTriggeredEvent] - astro:sun:local:civilDusk#event triggered START

==> /var/log/openhab2/openhab.log <==

2020-06-17 21:36:25.084 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model 'home.items' has errors, therefore ignoring it: [6,1]: missing EOF at 'witch'

==> /var/log/openhab2/events.log <==

2020-06-17 21:36:25.089 [temChannelLinkRemovedEvent] - Link 'zwave_device_3de88f51_node13_alarm_motion => zwave:device:3de88f51:node13:alarm_motion' has been removed.

2020-06-17 21:36:25.095 [temChannelLinkRemovedEvent] - Link 'zwave_device_3de88f51_node13_sensor_temperature => zwave:device:3de88f51:node13:sensor_temperature' has been removed.

2020-06-17 21:36:25.097 [temChannelLinkRemovedEvent] - Link 'zwave_device_3de88f51_node13_battery_level => zwave:device:3de88f51:node13:battery-level' has been removed.

2020-06-17 21:36:25.099 [temChannelLinkRemovedEvent] - Link 'FibaroDimmer1_DimmerSwitch1 => zwave:device:3de88f51:node11:switch_dimmer1' has been removed.

2020-06-17 21:36:25.103 [temChannelLinkRemovedEvent] - Link 'zwave_device_3de88f51_node14_alarm_motion => zwave:device:3de88f51:node14:alarm_motion' has been removed.

2020-06-17 21:36:25.108 [temChannelLinkRemovedEvent] - Link 'demo_motion => zwave:device:3de88f51:node14:alarm_motion' has been removed.

2020-06-17 21:36:25.115 [temChannelLinkRemovedEvent] - Link 'zwave_device_3de88f51_node14_battery_level => zwave:device:3de88f51:node14:battery-level' has been removed.

2020-06-17 21:36:25.118 [temChannelLinkRemovedEvent] - Link 'Fibaro_Dimmer1 => zwave:device:3de88f51:node11:switch_dimmer1' has been removed.

2020-06-17 21:36:25.147 [temChannelLinkRemovedEvent] - Link 'zwave_device_3de88f51_node14_sensor_temperature => zwave:device:3de88f51:node14:sensor_temperature' has been removed.

==> /var/log/openhab2/openhab.log <==

2020-06-17 21:36:36.295 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'home.items'

==> /var/log/openhab2/events.log <==

2020-06-17 21:36:36.366 [.ItemChannelLinkAddedEvent] - Link 'demo_motion-zwave:device:3de88f51:node14:alarm_motion' has been added.

2020-06-17 21:36:36.368 [.ItemChannelLinkAddedEvent] - Link 'Fibaro_Dimmer1-zwave:device:3de88f51:node11:switch_dimmer1' has been added.

2020-06-17 21:36:36.371 [.ItemChannelLinkAddedEvent] - Link 'FibaroDimmer1_DimmerSwitch1-zwave:device:3de88f51:node11:switch_dimmer1' has been added.

2020-06-17 21:36:36.375 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_3de88f51_node14_alarm_motion-zwave:device:3de88f51:node14:alarm_motion' has been added.

2020-06-17 21:36:36.379 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_3de88f51_node14_sensor_temperature-zwave:device:3de88f51:node14:sensor_temperature' has been added.

2020-06-17 21:36:36.382 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_3de88f51_node14_battery_level-zwave:device:3de88f51:node14:battery-level' has been added.

2020-06-17 21:36:36.387 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_3de88f51_node13_alarm_motion-zwave:device:3de88f51:node13:alarm_motion' has been added.

2020-06-17 21:36:36.391 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_3de88f51_node13_sensor_temperature-zwave:device:3de88f51:node13:sensor_temperature' has been added.

2020-06-17 21:36:36.396 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_3de88f51_node13_battery_level-zwave:device:3de88f51:node13:battery-level' has been added.

==> /var/log/openhab2/openhab.log <==

2020-06-17 21:37:58.376 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model 'iPhone.sitemap' has errors, therefore ignoring it: [1,1]: missing 'sitemap' at 'ssitemap'

[1,10]: mismatched input 'iPhone' expecting '{'

2020-06-17 21:38:06.561 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'iPhone.sitemap'

Can we see the rule, since you last edited it? Have you checked your openhab.log to see if the rules file refreshed okay after editing?

This is the rule.

//motion sensor rules

rule "light on test"
when
    Item demo_motion changed
then
        if (newState == ON) {
                 FibaroDimmer1_DimmerSwitch1.sendCommand(ON)
        } else {
                 FibaroDimmer1_DimmerSwitch1.sendCommand(OFF)
        }
end

and thats what appeadred in logs before about the rule

2020-06-17 21:43:34.246 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'home.rules'

however when I closed the SSH this appeared in the logs

2020-06-17 22:17:06.464 [ERROR] [ersey.server.ServerRuntime$Responder] - An I/O error has occurred while writing a response message entity to the container output stream.

org.glassfish.jersey.server.internal.process.MappableException: org.eclipse.jetty.io.EofException

	at org.glassfish.jersey.server.internal.MappableExceptionWrapperInterceptor.aroundWriteTo(MappableExceptionWrapperInterceptor.java:92) ~[?:?]

	at org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:162) ~[bundleFile:?]

	at org.glassfish.jersey.message.internal.MessageBodyFactory.writeTo(MessageBodyFactory.java:1130) ~[bundleFile:?]

	at org.glassfish.jersey.server.ServerRuntime$Responder.writeResponse(ServerRuntime.java:711) [bundleFile:?]

	at org.glassfish.jersey.server.ServerRuntime$Responder.processResponse(ServerRuntime.java:444) [bundleFile:?]

	at org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:434) [bundleFile:?]

	at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:329) [bundleFile:?]

	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) [bundleFile:?]

	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) [bundleFile:?]

	at org.glassfish.jersey.internal.Errors.process(Errors.java:315) [bundleFile:?]

	at org.glassfish.jersey.internal.Errors.process(Errors.java:297) [bundleFile:?]

	at org.glassfish.jersey.internal.Errors.process(Errors.java:267) [bundleFile:?]

	at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) [bundleFile:?]

	at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305) [bundleFile:?]

	at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154) [bundleFile:?]

	at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473) [bundleFile:?]

	at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) [bundleFile:?]

	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388) [bundleFile:?]

	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341) [bundleFile:?]

	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228) [bundleFile:?]

	at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76) [bundleFile:?]

	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:?]

	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.v20190813]

	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_252]

Caused by: org.eclipse.jetty.io.EofException

	at org.eclipse.jetty.io.ChannelEndPoint.flush(ChannelEndPoint.java:283) ~[bundleFile:9.4.20.v20190813]

	at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:422) ~[bundleFile:9.4.20.v20190813]

	at org.eclipse.jetty.io.WriteFlusher.completeWrite(WriteFlusher.java:378) ~[bundleFile:9.4.20.v20190813]

	at org.eclipse.jetty.io.ChannelEndPoint$3.run(ChannelEndPoint.java:132) ~[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:298) ~[bundleFile:9.4.20.v20190813]

	... 6 more

Caused by: java.io.IOException: Broken pipe

	at sun.nio.ch.FileDispatcherImpl.write0(Native Method) ~[?:1.8.0_252]

	at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47) ~[?:1.8.0_252]

	at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93) ~[?:1.8.0_252]

	at sun.nio.ch.IOUtil.write(IOUtil.java:65) ~[?:1.8.0_252]

	at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:468) ~[?:1.8.0_252]

	at org.eclipse.jetty.io.ChannelEndPoint.flush(ChannelEndPoint.java:261) ~[bundleFile:9.4.20.v20190813]

	at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:422) ~[bundleFile:9.4.20.v20190813]

	at org.eclipse.jetty.io.WriteFlusher.completeWrite(WriteFlusher.java:378) ~[bundleFile:9.4.20.v20190813]

	at org.eclipse.jetty.io.ChannelEndPoint$3.run(ChannelEndPoint.java:132) ~[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:298) ~[bundleFile:9.4.20.v20190813]

	... 6 more

2020-06-17 22:17:13.062 [ERROR] [ersey.server.ServerRuntime$Responder] - An I/O error has occurred while writing a response message entity to the container output stream.

org.glassfish.jersey.server.internal.process.MappableException: org.eclipse.jetty.io.EofException

	at org.glassfish.jersey.server.internal.MappableExceptionWrapperInterceptor.aroundWriteTo(MappableExceptionWrapperInterceptor.java:92) ~[?:?]

	at org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:162) ~[bundleFile:?]

	at org.glassfish.jersey.message.internal.MessageBodyFactory.writeTo(MessageBodyFactory.java:1130) ~[bundleFile:?]

	at org.glassfish.jersey.server.ServerRuntime$Responder.writeResponse(ServerRuntime.java:711) [bundleFile:?]

	at org.glassfish.jersey.server.ServerRuntime$Responder.processResponse(ServerRuntime.java:444) [bundleFile:?]

	at org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:434) [bundleFile:?]

	at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:329) [bundleFile:?]

	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) [bundleFile:?]

	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) [bundleFile:?]

	at org.glassfish.jersey.internal.Errors.process(Errors.java:315) [bundleFile:?]

	at org.glassfish.jersey.internal.Errors.process(Errors.java:297) [bundleFile:?]

	at org.glassfish.jersey.internal.Errors.process(Errors.java:267) [bundleFile:?]

	at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317) [bundleFile:?]

	at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305) [bundleFile:?]

	at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154) [bundleFile:?]

	at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473) [bundleFile:?]

	at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427) [bundleFile:?]

	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388) [bundleFile:?]

	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341) [bundleFile:?]

	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228) [bundleFile:?]

	at com.eclipsesource.jaxrs.publisher.internal.ServletContainerBridge.service(ServletContainerBridge.java:76) [bundleFile:?]

	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:?]

	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.v20190813]

	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_252]

Caused by: org.eclipse.jetty.io.EofException

	at org.eclipse.jetty.io.ChannelEndPoint.flush(ChannelEndPoint.java:283) ~[bundleFile:9.4.20.v20190813]

	at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:422) ~[bundleFile:9.4.20.v20190813]

	at org.eclipse.jetty.io.WriteFlusher.completeWrite(WriteFlusher.java:378) ~[bundleFile:9.4.20.v20190813]

	at org.eclipse.jetty.io.ChannelEndPoint$3.run(ChannelEndPoint.java:132) ~[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:298) ~[bundleFile:9.4.20.v20190813]

	... 6 more

Caused by: java.io.IOException: Broken pipe

	at sun.nio.ch.FileDispatcherImpl.write0(Native Method) ~[?:1.8.0_252]

	at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47) ~[?:1.8.0_252]

	at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93) ~[?:1.8.0_252]

	at sun.nio.ch.IOUtil.write(IOUtil.java:65) ~[?:1.8.0_252]

	at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:468) ~[?:1.8.0_252]

	at org.eclipse.jetty.io.ChannelEndPoint.flush(ChannelEndPoint.java:261) ~[bundleFile:9.4.20.v20190813]

	at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:422) ~[bundleFile:9.4.20.v20190813]

	at org.eclipse.jetty.io.WriteFlusher.completeWrite(WriteFlusher.java:378) ~[bundleFile:9.4.20.v20190813]

	at org.eclipse.jetty.io.ChannelEndPoint$3.run(ChannelEndPoint.java:132) ~[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:298) ~[bundleFile:9.4.20.v20190813]

	... 6 more

==> /var/log/openhab2/events.log <==

2020-06-17 22:17:18.367 [ome.event.ItemCommandEvent] - Item 'FibaroDimmer1_DimmerSwitch1' received command 100

2020-06-17 22:17:18.424 [nt.ItemStatePredictedEvent] - FibaroDimmer1_DimmerSwitch1 predicted to become 100

2020-06-17 22:17:18.445 [vent.ItemStateChangedEvent] - FibaroDimmer1_DimmerSwitch1 changed from 0 to 100

2020-06-17 22:17:20.048 [ome.event.ItemCommandEvent] - Item 'FibaroDimmer1_DimmerSwitch1' received command 0

2020-06-17 22:17:20.100 [nt.ItemStatePredictedEvent] - FibaroDimmer1_DimmerSwitch1 predicted to become 0

2020-06-17 22:17:20.149 [vent.ItemStateChangedEvent] - FibaroDimmer1_DimmerSwitch1 changed from 100 to 0

2020-06-17 22:17:20.159 [vent.ItemStateChangedEvent] - Fibaro_Dimmer1 changed from OFF to ON

2020-06-17 22:17:20.164 [vent.ItemStateChangedEvent] - FibaroDimmer1_DimmerSwitch1 changed from 0 to 100

2020-06-17 22:17:21.747 [vent.ItemStateChangedEvent] - Fibaro_Dimmer1 changed from ON to OFF

2020-06-17 22:17:21.751 [vent.ItemStateChangedEvent] - FibaroDimmer1_DimmerSwitch1 changed from 100 to 0

==> /var/log/openhab2/openhab.log <==

2020-06-17 22:18:41.619 [INFO ] [panel.internal.HABPanelDashboardTile] - Stopped HABPanel

2020-06-17 22:18:42.252 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel

==> /var/log/openhab2/events.log <==

2020-06-17 23:24:00.004 [vent.ChannelTriggeredEvent] - astro:sun:local:nauticDusk#event triggered END

Okay, from your events.log earlier, here is rule in action.

First your demo_motion Item has a state change, exactly what is needed to trigger your rule.

A few milliseconds later, your Item FibaroDimmer1_DimmerSwitch1 receives a command ON, which is exactly what we’d expect the rule to issue.

The rule is running, and does everything you asked of it.

If the result of sending a command to FibaroDimmer1_DimmerSwitch1 is not what you expected, then you need to look at any channel and Thing that you linked to that Item.

That can happen with unexpected UI closures, I wouldn’t worry about it. Nothing to do with your rule or Item.

So I checked again all the items and rules and made sure they all have the same name like you suggested but they all do same with channels. Do you know anythings else that might be wrong with it, maybe I have not installed something, maybe I need to write some scrypt or add some variables or something or maybe a binding is missing?

However if not then my only idea is to format it and start from the beginning and maybe it might work but I really appriciate your time and help nonetheless, if you think you have any last ideas then please tell me.

Well, what is the problem exactly? I’ll guess that you expected this Item FibaroDimmer1_DimmerSwitch1 to actually control a light or something?
It probably is something small that is wrong, but if we can’t see it then we cannot tell you what.

Can we see your Item definition? Can we see the channel and Thing that you think it is linked to? PaperUI screenshots?

FibaroDimmer1_DimmerSwitch1 is a dimmer that you put inside your light switch and it allows you to controll the light from your phone and that works I can control it. However I tried to make a rule that using demo_motion which is a motion senso that is a zwave device, would turn the lights on when you walk into a room and whenever I move my hand in front of the demo_motion then the device indicates that it detected motion with a red LED blinking once but the rule does not turn the FibaroDimmer1_DimmerSwitch1 dimmer on even that the rule like you said is working.

These are the two Things I am trying to connect Fibaro Dimmer1 and NEO Coolcam

This is the item from the Fibaro Dimmer1 with the items linked that I created in SSH

This is the item from the NEO Coolcam with the items linked that I created in SSH

Is that what you are asking for?

That’s brilliant, yes.

If we look at the channel for your Dimmer, it shows two Items linked to it.
It should be fine to link a channel to multiple Items, but I think I’ve seen that mess people about before. Maybe it depends on the binding.
In any case, you don’t need two Items linked to the same channel.

I would remove the link to Item Fibaro_Dimmer1, and then remove the Item.
If you created and linked that Item in an xxx.items file, that is where you have to remove them, too.

That should leave you one link to Item FibaroDimmer!_DimmerSwitch1, which is the one your test rule is commanding. so that should work.

Because you’ve been making lots of changes, and some stuff is not so good at making changes in-flight, it would be smart to reboot openHAB after you have made changes, and then see if the rule works.

When you’ve got your light turning on and off, then we’ll worry at the motion sensor.

I mean the light is working perfectly fine I can dim it and switch it on and off using HABpanel as well as BasicUI and the physical light bulb does turns on and off when I change it there.

The one above is the dimmer and one below is the switch from the linked items because in the BasicUI I wanted to be able to switch and dim the same item.
7

The logs from the light dimming and switching

2020-06-18 19:05:04.744 [ome.event.ItemCommandEvent] - Item 'FibaroDimmer1_DimmerSwitch1' received command 0

2020-06-18 19:05:04.867 [nt.ItemStatePredictedEvent] - FibaroDimmer1_DimmerSwitch1 predicted to become 0

2020-06-18 19:05:06.104 [ome.event.ItemCommandEvent] - Item 'FibaroDimmer1_DimmerSwitch1' received command 100

2020-06-18 19:05:06.168 [nt.ItemStatePredictedEvent] - FibaroDimmer1_DimmerSwitch1 predicted to become 100

2020-06-18 19:05:06.212 [vent.ItemStateChangedEvent] - FibaroDimmer1_DimmerSwitch1 changed from 0 to 100

2020-06-18 19:05:07.825 [vent.ItemStateChangedEvent] - Fibaro_Dimmer1 changed from OFF to ON

2020-06-18 19:05:07.882 [vent.ItemStateChangedEvent] - zwave_device_3de88f51_node11_config_decimal_param19 changed from NULL to 0

2020-06-18 19:05:07.898 [ome.event.ItemCommandEvent] - Item 'Fibaro_Dimmer1' received command OFF

2020-06-18 19:05:07.937 [nt.ItemStatePredictedEvent] - Fibaro_Dimmer1 predicted to become OFF

2020-06-18 19:05:07.971 [vent.ItemStateChangedEvent] - Fibaro_Dimmer1 changed from ON to OFF

2020-06-18 19:05:09.610 [vent.ItemStateChangedEvent] - FibaroDimmer1_DimmerSwitch1 changed from 100 to 0

2020-06-18 19:05:10.298 [ome.event.ItemCommandEvent] - Item 'Fibaro_Dimmer1' received command ON

2020-06-18 19:05:10.346 [nt.ItemStatePredictedEvent] - Fibaro_Dimmer1 predicted to become ON

2020-06-18 19:05:10.378 [vent.ItemStateChangedEvent] - Fibaro_Dimmer1 changed from OFF to ON

2020-06-18 19:05:11.987 [vent.ItemStateChangedEvent] - FibaroDimmer1_DimmerSwitch1 changed from 0 to 100

2020-06-18 19:05:13.080 [ome.event.ItemCommandEvent] - Item 'Fibaro_Dimmer1' received command OFF

2020-06-18 19:05:13.122 [nt.ItemStatePredictedEvent] - Fibaro_Dimmer1 predicted to become OFF

2020-06-18 19:05:13.149 [vent.ItemStateChangedEvent] - Fibaro_Dimmer1 changed from ON to OFF

2020-06-18 19:05:14.771 [vent.ItemStateChangedEvent] - FibaroDimmer1_DimmerSwitch1 changed from 100 to 0

2020-06-18 19:05:15.947 [ome.event.ItemCommandEvent] - Item 'FibaroDimmer1_DimmerSwitch1' received command 100

2020-06-18 19:05:15.996 [nt.ItemStatePredictedEvent] - FibaroDimmer1_DimmerSwitch1 predicted to become 100

2020-06-18 19:05:16.031 [vent.ItemStateChangedEvent] - FibaroDimmer1_DimmerSwitch1 changed from 0 to 100

2020-06-18 19:05:17.656 [vent.ItemStateChangedEvent] - Fibaro_Dimmer1 changed from OFF to ON

However if you still want me to try removing the switch item Fibaro_Dimmer1 then I surely can.

Why would you want to keep two Items linked to the same channel? What could it do for you, but add confusion?

You don’t do that with multiple Items.
An openHAB Dimmer type Item accepts both ON/OFF commands and numeric % commands.
So the same Item can be used in both Switch widgets and Slider widgets.

sitemap

Slider item=FibaroDimmer1_DimmerSwitch1
Switch item=FibaroDimmer1_DimmerSwitch1

That is assuming FibaroDimmer1_DimmerSwitch1 is a Dimmer type Item?

Ok that does makes sense I didnt not think about doing it this way, so I did remove it and I have FibaroDimmer1_DimmerSwitch1 in the test rule and I also reastarted the RPI and the lights are working perfectly. What should I do next, should I do the same with the motion sensor, remove demo_motion and just keep the original Motion Alarm?

Have a look in your events.log, see which motion Item is already working, if any.
Use the working one, discard duplicates.

So when I move my hand in front of the motion sensor nothing appears on the log as if it is not working but the red LED in it tells me it detected motion. However since I created a switch item in the sitemaps then I tried turning it on with the switch and this apprears in the logs

Thats the switch

This is the part of the sitemap in the picture

sitemap iPhone label="Home"
{
        Frame label="Home"
        {
                Slider item=FibaroDimmer1_DimmerSwitch1
                Switch item=zwave_device_3de88f51_node14_alarm_motion
                Switch item=FibaroDimmer1_DimmerSwitch1
                Text item=zwave_device_3de88f51_node14_sensor_temperature
        }

These are the logs that appear when I turn it ON and OFF

2020-06-19 14:58:29.127 [ome.event.ItemCommandEvent] - Item 'zwave_device_3de88f51_node14_alarm_motion' received command ON

2020-06-19 14:58:29.187 [nt.ItemStatePredictedEvent] - zwave_device_3de88f51_node14_alarm_motion predicted to become ON

2020-06-19 14:58:29.226 [vent.ItemStateChangedEvent] - zwave_device_3de88f51_node14_alarm_motion changed from OFF to ON

2020-06-19 14:58:29.252 [ome.event.ItemCommandEvent] - Item 'FibaroDimmer1_DimmerSwitch1' received command ON

2020-06-19 14:58:29.321 [nt.ItemStatePredictedEvent] - FibaroDimmer1_DimmerSwitch1 predicted to become ON

2020-06-19 14:58:29.357 [vent.ItemStateChangedEvent] - FibaroDimmer1_DimmerSwitch1 changed from 0 to 100

2020-06-19 14:58:58.527 [ome.event.ItemCommandEvent] - Item 'zwave_device_3de88f51_node14_alarm_motion' received command OFF

2020-06-19 14:58:58.571 [nt.ItemStatePredictedEvent] - zwave_device_3de88f51_node14_alarm_motion predicted to become OFF

2020-06-19 14:58:58.596 [vent.ItemStateChangedEvent] - zwave_device_3de88f51_node14_alarm_motion changed from ON to OFF

2020-06-19 14:58:58.602 [ome.event.ItemCommandEvent] - Item 'FibaroDimmer1_DimmerSwitch1' received command OFF

2020-06-19 14:58:58.639 [nt.ItemStatePredictedEvent] - FibaroDimmer1_DimmerSwitch1 predicted to become OFF

2020-06-19 14:58:58.651 [vent.ItemStateChangedEvent] - FibaroDimmer1_DimmerSwitch1 changed from 100 to 0

Okay, not a lot of help, we know you can command Items from the sitemap, but you want one that responds to your sensor.

Let’s work on that.

Earlier you showed us NEO Coolcam Thing zwave:device:3de88f51:node14
You still have that, it still shows online in PaperUI?

That had an alarm_motion switch type channel.
You had it linked to two Items then.
Are we down to one Item now, and it is a Switch type to match the channel?

But no sign of that in the logs?
You’ll have to investigate zwave device settings, like here

Yes the NEO Coolcam Thing zwave:device:3de88f51:node14 still shows up online in PaperUI and I am down to one Item now witch is a Switch type channel

//motion detector
Switch zwave_device_3de88f51_node14_alarm_motion "Motion Alarm" <motion> (zwave) {channel="zwave:device:3de88f51:node14:alarm_motion"}


but like you said it does not appear in the logs.

I also had a look at that post you sent and I checked the zwave NEO Coolcam settings but after trying stuff out like in Association Groups changing 1:Life line to Controller and 2:Group 2 to Controller I cant seem to be able to unchange it, it is stuck on that option just like all the other options in there.


I also tryed changing stuff like 6. Re-trigger Interval to 1 accept of default 8 and 8.Lux Level Function Enable from Dissable to Enable as well as 2. ON/OFF Duration Setting from 30 to 35 and non of thoes options saved even that it allowed me to change the name of the Thing.

Some logs appeared but I dont think they give much info

2020-06-19 17:41:44.862 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=wakeup_node, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=wakeup_interval, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]

2020-06-19 17:42:28.846 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:3de88f51:node14' has been updated.

2020-06-19 17:42:28.855 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]

2020-06-19 17:42:28.959 [hingStatusInfoChangedEvent] - 'zwave:device:3de88f51:node14' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline

2020-06-19 17:42:28.977 [hingStatusInfoChangedEvent] - 'zwave:device:3de88f51:node14' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE

2020-06-19 17:42:28.989 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:3de88f51:node14' has been updated.

2020-06-19 17:42:42.482 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:3de88f51:node14' has been updated.

2020-06-19 17:42:42.509 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:3de88f51:node14' has been updated.

2020-06-19 17:42:42.511 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]

2020-06-19 17:42:54.684 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:3de88f51:node14' has been updated.

2020-06-19 17:42:54.687 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]

2020-06-19 17:43:15.435 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:3de88f51:node14' has been updated.

2020-06-19 17:43:15.438 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]

2020-06-19 17:49:30.376 [vent.ItemStateChangedEvent] - zwave_device_3de88f51_node14_sensor_temperature changed from NULL to 20.4

2020-06-19 17:59:40.705 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:3de88f51:node14' has been updated.

2020-06-19 17:59:40.707 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]

Do you think it is worth asking the person that made that post you sent for his configuration on his NEO Coolcam if he can and if he has done anything different from me?

What you need is help getting your device talking to openHAB, it doesn’t matter who from (it won’t be me, I don’t know zwave)

These things usually begin by finding out if your device has completed initialization and you have woken it up a few times.
Changes you make in PaperUI won’t get uploaded until it is intialized, I think. Making random changes doesn’t sound wise.

1 Like

Well thats ok thank you so much for all the time and help you gave me. I will try out some stuff, dig some more online and if that doesnt help I will probably try redoing everything from scratch on a new RPI or I will try getting some new motion sensors.

Your motion sensor is battery powered, so you will either need to wait for it to wake up several times or manually wake it up for these changes to be picked up by the device.

When making these changes, ALWAYS (until OH 3.0) use Hamin rather than Paper UI, since the latter will send ALL parameters, take a very long time, and can possibly screw things up.

Another thing is that this device has had changes in the device database, so you will need to delete the Thing and rediscover it to pull in the new Thing definitions. If you don’t, strange things may happen. If this is a fresh installation of OH 2.5.5, then this will not be a factor.

1 Like

So you are right I finnaly got them to work and what I had to do it manually wake it up by clicking a button at the back of it a lot of times and it is working perfectly now. Turns out that NEO products are just weird and they dont fully wake up. Thank you again Scott and rossko57 for help.

2 Likes