Hi Stefan,
sorry it took me some time to get back to it. So here’s what I did today.
I removed the old nanoleaf thing. Then I noticed there were still some items left. I couldn’t remove them from paper UI. So I tried from habmin:
2019-12-03 21:53:23.795 [INFO ] [rest.core.internal.item.ItemResource] - Received HTTP DELETE request at 'items/AuroraWohnzimmer_Brightness' for the unknown item 'AuroraWohnzimmer_Brightness'.
Weird … but I’d guess it’s not a problem. So I restarted the openhab service to get a clean start. The apprently “unknown item” was still present after the restart.
So here the log after the restart and accepting the Nanoleaf Controller from the Inbox with the default name.
2019-12-03 21:58:01.206 [DEBUG] [ery.NanoleafMDNSDiscoveryParticipant] - Nanoleaf found: 192.168.0.40 16021
2019-12-03 21:58:01.209 [DEBUG] [ery.NanoleafMDNSDiscoveryParticipant] - Adding Nanoleaf light panels to inbox: 62D0E39E8239 at 192.168.0.40
2019-12-03 21:58:01.211 [DEBUG] [ery.NanoleafMDNSDiscoveryParticipant] - Nanoleaf Type: NL22
2019-12-03 21:58:02.694 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2019-12-03 21:58:03.898 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'nanoleaf:lightpanels:62D0E39E8239' to inbox.
2019-12-03 21:58:04.773 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at http://192.168.0.199:8080
2019-12-03 21:58:04.777 [INFO ] [.dashboard.internal.DashboardService] - Started Dashboard at https://192.168.0.199:8443
2019-12-03 21:58:05.241 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
2019-12-03 21:58:06.503 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
2019-12-03 21:58:06.733 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to 'localhost' with clientid paho4519767739041426 and file store '/var/lib/openhab2/mqtt/localhost'
2019-12-03 22:00:17.816 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler NanoleafHandler tried updating the thing status although the handler was already disposed.
2019-12-03 22:00:17.821 [DEBUG] [eaf.internal.handler.NanoleafHandler] - Start pairing job, interval=25 sec
2019-12-03 22:00:17.902 [WARN ] [e.jetty.util.thread.QueuedThreadPool] - QueuedThreadPool[ESH-httpClient-common]@fbab2{STOPPING,10<=10<=40,i=0,q=3}[org.eclipse.jetty.util.thread.TryExecutor$$Lambda$116/8106205@15ee4a5] Couldn't stop Thread[ESH-httpClient-common-92,5,main]
2019-12-03 22:00:17.906 [WARN ] [e.jetty.util.thread.QueuedThreadPool] - QueuedThreadPool[ESH-httpClient-common]@fbab2{STOPPING,10<=10<=40,i=0,q=3}[org.eclipse.jetty.util.thread.TryExecutor$$Lambda$116/8106205@15ee4a5] Couldn't stop Thread[ESH-httpClient-common-93,5,main]
2019-12-03 22:00:18.315 [DEBUG] [eaf.internal.handler.NanoleafHandler] - Auth token response code: 403
This went on for some time, as I got distracted. Then I pressed the power button to allow pairing:
2019-12-03 22:06:59.292 [WARN ] [e.jetty.util.thread.QueuedThreadPool] - QueuedThreadPool[ESH-httpClient-common]@fbab2{STOPPING,10<=20<=40,i=0,q=15}[org.eclipse.jetty.util.thread.TryExecutor$$Lambda$116/8106205@15ee4a5] Couldn't stop Thread[ESH-httpClient-common-93,5,main]
2019-12-03 22:06:59.330 [DEBUG] [eaf.internal.handler.NanoleafHandler] - Auth token response code: 403
2019-12-03 22:06:59.671 [DEBUG] [eaf.internal.handler.NanoleafHandler] - Nanoleaf 62D0E39E8239 updated
2019-12-03 22:06:59.675 [DEBUG] [eaf.internal.handler.NanoleafHandler] - Stop pairing job
2019-12-03 22:06:59.678 [DEBUG] [eaf.internal.handler.NanoleafHandler] - Start initializing light panels
2019-12-03 22:06:59.698 [DEBUG] [eaf.internal.handler.NanoleafHandler] - Start pairing job, interval=25 sec
2019-12-03 22:06:59.731 [WARN ] [e.jetty.util.thread.QueuedThreadPool] - QueuedThreadPool[ESH-httpClient-common]@fbab2{STOPPING,10<=20<=40,i=0,q=7}[org.eclipse.jetty.util.thread.TryExecutor$$Lambda$116/8106205@15ee4a5] Couldn't stop Thread[ESH-httpClient-common-92,5,main]
2019-12-03 22:06:59.735 [WARN ] [e.jetty.util.thread.QueuedThreadPool] - QueuedThreadPool[ESH-httpClient-common]@fbab2{STOPPING,10<=20<=40,i=0,q=7}[org.eclipse.jetty.util.thread.TryExecutor$$Lambda$116/8106205@15ee4a5] Couldn't stop Thread[ESH-httpClient-common-93,5,main]
2019-12-03 22:06:59.913 [DEBUG] [eaf.internal.handler.NanoleafHandler] - Auth token response code: 403
2019-12-03 22:07:24.926 [WARN ] [e.jetty.util.thread.QueuedThreadPool] - QueuedThreadPool[ESH-httpClient-common]@fbab2{STOPPING,10<=17<=40,i=16,q=14}[org.eclipse.jetty.util.thread.TryExecutor$$Lambda$116/8106205@15ee4a5] Couldn't stop Thread[ESH-httpClient-common-92,5,main]
2019-12-03 22:07:24.930 [WARN ] [e.jetty.util.thread.QueuedThreadPool] - QueuedThreadPool[ESH-httpClient-common]@fbab2{STOPPING,10<=17<=40,i=16,q=14}[org.eclipse.jetty.util.thread.TryExecutor$$Lambda$116/8106205@15ee4a5] Couldn't stop Thread[ESH-httpClient-common-526,5,main]
2019-12-03 22:07:24.934 [WARN ] [e.jetty.util.thread.QueuedThreadPool] - QueuedThreadPool[ESH-httpClient-common]@fbab2{STOPPING,10<=17<=40,i=0,q=12}[org.eclipse.jetty.util.thread.TryExecutor$$Lambda$116/8106205@15ee4a5] Couldn't stop Thread[ESH-httpClient-common-525,5,]
2019-12-03 22:07:24.938 [WARN ] [e.jetty.util.thread.QueuedThreadPool] - QueuedThreadPool[ESH-httpClient-common]@fbab2{STOPPING,10<=17<=40,i=0,q=12}[org.eclipse.jetty.util.thread.TryExecutor$$Lambda$116/8106205@15ee4a5] Couldn't stop Thread[ESH-httpClient-common-529,5,]
2019-12-03 22:07:24.941 [WARN ] [e.jetty.util.thread.QueuedThreadPool] - QueuedThreadPool[ESH-httpClient-common]@fbab2{STOPPING,10<=17<=40,i=0,q=12}[org.eclipse.jetty.util.thread.TryExecutor$$Lambda$116/8106205@15ee4a5] Couldn't stop Thread[ESH-httpClient-common-93,5,main]
2019-12-03 22:07:25.005 [DEBUG] [eaf.internal.handler.NanoleafHandler] - Auth token response code: 200
2019-12-03 22:07:25.018 [DEBUG] [eaf.internal.handler.NanoleafHandler] - Pairing succeeded.
After that the controller is shown as “online”. The things are created and the channels linked.
I can switch the panels on and off. I cannot change effects (nothing to choose). I can change the overall brightness/color for all panels at once. I can change the audio source for the rhythm (probably … not tested if it has an effect).
At some point while playing with the controls, I got this exception (not sure when exactly it happened though)
2019-12-03 22:11:16.903 [DEBUG] [eaf.internal.handler.NanoleafHandler] - Received channel: nanoleaf:lightpanels:62D0E39E8239:color, command: 70
2019-12-03 22:11:16.906 [ERROR] [eaf.internal.handler.NanoleafHandler] - Unhandled command type: org.eclipse.smarthome.core.library.types.PercentType
2019-12-03 22:11:16.909 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method 'ThingHandler.handleCommand()' on 'org.openhab.binding.nanoleaf.internal.handler.NanoleafHandler@8be0d1': Unhandled command type
org.openhab.binding.nanoleaf.internal.NanoleafException: Unhandled command type
at org.openhab.binding.nanoleaf.internal.handler.NanoleafHandler.sendEffectCommand(NanoleafHandler.java:148) ~[?:?]
at org.openhab.binding.nanoleaf.internal.handler.NanoleafHandler.handleCommand(NanoleafHandler.java:189) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [102:org.eclipse.smarthome.core:0.10.0.oh240]
at org.eclipse.smarthome.core.internal.common.InvocationHandlerSync.invoke(InvocationHandlerSync.java:59) [102:org.eclipse.smarthome.core:0.10.0.oh240]
at com.sun.proxy.$Proxy138.handleCommand(Unknown Source) [212:org.openhab.binding.nanoleaf:2.5.0.201901190212]
at org.eclipse.smarthome.core.thing.internal.profiles.ProfileCallbackImpl.handleCommand(ProfileCallbackImpl.java:75) [109:org.eclipse.smarthome.core.thing:0.10.0.oh240]
at org.eclipse.smarthome.core.thing.internal.profiles.SystemDefaultProfile.onCommandFromItem(SystemDefaultProfile.java:49) [109:org.eclipse.smarthome.core.thing:0.10.0.oh240]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHandler.java:153) [102:org.eclipse.smarthome.core:0.10.0.oh240]
at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [102:org.eclipse.smarthome.core:0.10.0.oh240]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]
2019-12-03 22:11:19.683 [DEBUG] [eaf.internal.handler.NanoleafHandler] - Received channel: nanoleaf:lightpanels:62D0E39E8239:color, command: 177,100,70
2019-12-03 22:11:19.989 [DEBUG] [eaf.internal.handler.NanoleafHandler] - API response code: 204
When I look at configuration -> things, I only have the one nanoleaf thing
Light Panels 52:44:31
Nanoleaf Light Panels
nanoleaf:lightpanels:62D0E39E8239
So I go to the Inbox - and it’s empty
I click the scan button on the top right corner and choose the nanoleaf binding … nothing happens. Nothing in the log.
I press the “search for things” button at the bottom of the inbox and choose nanoleaf again.
Now this is in the log:
2019-12-03 22:17:50.067 [DEBUG] [ery.NanoleafMDNSDiscoveryParticipant] - Nanoleaf Type: NL22
2019-12-03 22:17:50.070 [DEBUG] [ery.NanoleafMDNSDiscoveryParticipant] - Nanoleaf found: 192.168.0.40 16021
2019-12-03 22:17:50.072 [DEBUG] [ery.NanoleafMDNSDiscoveryParticipant] - Adding Nanoleaf light panels to inbox: 62D0E39E8239 at 192.168.0.40
2019-12-03 22:17:50.075 [DEBUG] [ery.NanoleafMDNSDiscoveryParticipant] - Nanoleaf Type: NL22
2019-12-03 22:18:03.128 [DEBUG] [ery.NanoleafMDNSDiscoveryParticipant] - Nanoleaf Type: NL22
2019-12-03 22:18:03.131 [DEBUG] [ery.NanoleafMDNSDiscoveryParticipant] - Nanoleaf found: 192.168.0.40 16021
2019-12-03 22:18:03.133 [DEBUG] [ery.NanoleafMDNSDiscoveryParticipant] - Adding Nanoleaf light panels to inbox: 62D0E39E8239 at 192.168.0.40
2019-12-03 22:18:03.136 [DEBUG] [ery.NanoleafMDNSDiscoveryParticipant] - Nanoleaf Type: NL22
But when I go to the inbox, it’s still empty.
When I go to things … it’s still only the controller.
Not sure what I’m doing wrong … hope the logs help!
[edit]
tried a few more things
- removed thing, restart service. add thing again from inbox, don’t play with it, so I didn’t get an exception. try scanning … same as above
- removed thing, restarted service and brought nanoleaf into pairing mode. thing shows up in inbox, I press the ok button and it’s paired (as the log indicates, while adding it, the auth token box was still empty). sadly no changes
- after the thing was authenticated, i brought the nanoleaf into pairing mode again before starting the second scan from the inbox. no change either.