@tmrobert8 I upgraded to the latest Neeo firmware yesterday and saw some strange behaviour with controlling the lights I have linked through the transport.
Here is what I saw:
- switch a light on from the Neeo remote: immediately switched off again without user action
- switch the same light on from the Neeo app: stayed on
My next step was to install the latest binding and transport (I think I didn’t have the latest), to exclude that element. Now none of my lights can be switched from the Neeo side anymore. I do have one strange log entry for a virtual thing representing a scene with one switch item linked to it. I doubt that explains nothing working anymore though.
2018-05-03 11:56:43.362 [WARN ] [eclipse.jetty.servlet.ServletHandler] - /neeo/NEEO-d487672e%2Fdevice%2Fneeo_io%3Avirtual%3ADyZNtPvS%2FScene_TV%2Fnone%2F1%2Fswitch%2Fsensor/default
java.lang.NullPointerException: null
at org.openhab.io.neeo.internal.NeeoItemValueConverter.convert(NeeoItemValueConverter.java:158) [254:org.openhab.io.neeo:2.3.0.201804061952]
at org.openhab.io.neeo.internal.servletservices.NeeoBrainService.handleGetValue(NeeoBrainService.java:255) [254:org.openhab.io.neeo:2.3.0.201804061952]
at org.openhab.io.neeo.internal.servletservices.NeeoBrainService.handleGet(NeeoBrainService.java:160) [254:org.openhab.io.neeo:2.3.0.201804061952]
at org.openhab.io.neeo.AbstractServlet.doGet(AbstractServlet.java:120) [254:org.openhab.io.neeo:2.3.0.201804061952]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) [31:javax.servlet-api:3.1.0]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [31:javax.servlet-api:3.1.0]
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:848) [88:org.eclipse.jetty.servlet:9.3.22.v20171030]
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:584) [88:org.eclipse.jetty.servlet:9.3.22.v20171030]
at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:71) [191:org.ops4j.pax.web.pax-web-jetty:6.0.7]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) [87:org.eclipse.jetty.server:9.3.22.v20171030]
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) [85:org.eclipse.jetty.security:9.3.22.v20171030]
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) [87:org.eclipse.jetty.server:9.3.22.v20171030]
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180) [87:org.eclipse.jetty.server:9.3.22.v20171030]
at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:284) [191:org.ops4j.pax.web.pax-web-jetty:6.0.7]
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512) [88:org.eclipse.jetty.servlet:9.3.22.v20171030]
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) [87:org.eclipse.jetty.server:9.3.22.v20171030]
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112) [87:org.eclipse.jetty.server:9.3.22.v20171030]
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) [87:org.eclipse.jetty.server:9.3.22.v20171030]
at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:80) [191:org.ops4j.pax.web.pax-web-jetty:6.0.7]
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) [87:org.eclipse.jetty.server:9.3.22.v20171030]
at org.eclipse.jetty.server.Server.handle(Server.java:534) [87:org.eclipse.jetty.server:9.3.22.v20171030]
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:333) [87:org.eclipse.jetty.server:9.3.22.v20171030]
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) [87:org.eclipse.jetty.server:9.3.22.v20171030]
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:283) [79:org.eclipse.jetty.io:9.3.22.v20171030]
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108) [79:org.eclipse.jetty.io:9.3.22.v20171030]
at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) [79:org.eclipse.jetty.io:9.3.22.v20171030]
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303) [90:org.eclipse.jetty.util:9.3.22.v20171030]
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) [90:org.eclipse.jetty.util:9.3.22.v20171030]
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136) [90:org.eclipse.jetty.util:9.3.22.v20171030]
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) [90:org.eclipse.jetty.util:9.3.22.v20171030]
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) [90:org.eclipse.jetty.util:9.3.22.v20171030]
at java.lang.Thread.run(Thread.java:748) [?:?]
I switched on debug logging for the transport, but do not see anything obvious in there.
Here is a log when I try to switch on a light from the Neeo app:
2018-05-03 12:10:33.675 [DEBUG] [org.openhab.io.neeo.AbstractServlet ] - doGet: http://192.168.0.10:8080/neeo/NEEO-d487672e/device/nikohomecontrol:onOff:440e003a24e6:25/Licht_Zolder/1/switch/actor/default/true
2018-05-03 12:10:33.678 [DEBUG] [nal.servletservices.NeeoBrainService] - handleGetValue PathInfo [thingUid=nikohomecontrol:onOff:440e003a24e6:25, itemName=Licht_Zolder, subType=none, channelNbr=1, componentType=switch, componentSubType=actor, actionValue=null]: false
==> /var/log/openhab2/events.log <==
2018-05-03 12:10:33.684 [vent.ChannelTriggeredEvent] - neeo:brain:d487672e:forwardActions triggered {"action":"Licht_Zolder","device":"Zolder","room":"Boven","actionparameter":true}
==> /var/log/openhab2/openhab.log <==
2018-05-03 12:10:33.694 [INFO ] [.eclipse.smarthome.model.script.neeo] - action received: {"action":"Licht_Zolder","device":"Zolder","room":"Boven","actionparameter":true}
2018-05-03 12:10:35.519 [DEBUG] [org.openhab.io.neeo.AbstractServlet ] - doGet: http://192.168.0.10:8080/neeo/NEEO-d487672e/device/nikohomecontrol:onOff:440e003a24e6:25/Licht_Zolder/1/switch/actor/default/false
2018-05-03 12:10:35.522 [DEBUG] [nal.servletservices.NeeoBrainService] - handleGetValue PathInfo [thingUid=nikohomecontrol:onOff:440e003a24e6:25, itemName=Licht_Zolder, subType=none, channelNbr=1, componentType=switch, componentSubType=actor, actionValue=null]: false
It does look like Neeo is sending something as the binding picks it up (action trigger is logged in a rule), bu the transport does not act on it correctly.
I am still on openHAB 2.2.
Any ideas?
UPDATE:
I recreated a light and a dimmer. They now work from the Neeo app. So the issue of nothing working seems related to your change in format.
However, I now have the issue of lights immediately switching off again when I switch them on from the remote (not from the app). The issue only appears for a switch, not for a dimmer.
The null exception is also still there.