Hi,
is it only the overhead of opening a session what concerns you, @David_Graeff?
If so, I think the overhead of trying to keep it alive will typically be higher. Or did I get something wrong here?
Anyway, if the v6 bridge would work, many people would be happy.
Yes exactly. The limitlessled website is not existing anymore though and there is no official information. You can find those pieces on different web-pages but none has archived yet to keep a session alive for longer. They are all establishing a new session for each command as far as I have seen.
Do I get you right, that the session handling is the only issue with your current version of the bindung? Whatâs the benefit about trying to keep the session alive?
Opening the session for every command sounds acceptable as typically therw wonât be that much commands per given timeframe.
Is there anything I can help with?
Simon
Yup, if you can do a bit of Java programming, you could try that scenario out. Establish a new session for each command and see if that is more reliable.
The session is used to determine if the bridge is still online. We can of course also just poll via the discover package (most solutions out there do it like this).
New here and to Opensource projects after recently retiring. So please guidance as needed if I am out of bounds. My ultimate goal is to build a binding for Pioneer SC-LX501. Planned steps on the way were to get a few things setup and then move on to determining how the bindings are built. My immediate next step is to install eclipse and find the documentation on building bindings. I am also expecting an ESP8266 and assorted goodies in the mail tomorrow to play with SimonFlei binding as well. However, if it helps - I am getting this in the logs
==> /var/log/openhab2/openhab.log <==
2019-02-22 15:38:38.323 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method âThingHandler.handleCommand()â on âorg.openhab.binding.milight.internal.handler.MilightV6RGBCWWWHandler@13fe0d13â: null
java.lang.NullPointerException: null
at org.openhab.binding.milight.internal.handler.AbstractLedV6Handler.sendRepeatableCat(AbstractLedV6Handler.java:212) ~[?:?]
at org.openhab.binding.milight.internal.handler.AbstractLedV6Handler.setBrightness(AbstractLedV6Handler.java:96) ~[?:?]
at org.openhab.binding.milight.internal.handler.AbstractLedHandler.handleCommand(AbstractLedHandler.java:139) ~[?:?]
at org.openhab.binding.milight.internal.handler.AbstractLedV6Handler.handleCommand(AbstractLedV6Handler.java:202) ~[?:?]
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.$Proxy125.handleCommand(Unknown Source) [208:org.openhab.binding.milight:2.4.0]
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) [?:?]
Looks like a serious bug. Unfortunately I do not have time to fix that in the very near future, as Iâm busy with another openHab part. Because you are a new user, I cannot expect you to fill a bug report, can I?
David -
Those Java error were due to be adding the bulb thing without marking the bridge. My mistake. If there is not one already - I can capture the logs and versions of everything a create a pull request for the binding and apparently v1.0.08 of the bridge not successfully marrying the globes. Offer woould include testing as well.
Apologies for the mistake
I stumbled across this and thought it may be useful, it is a JAR file with instructions on how to use it for sniffing the traffic between a ibox1/2 and the milight app. It will display the keep alive packets Milight uses and more. See post number 6âŠ
Hi @David_Graeff,
could you maybe give me some hints where to start and what to change?
I found the classes MilightV6SessionManager and BridgeV6Handler, but canât where the changes should be made.
Iâm new to openhab and bindings development, so please forgive my stupid questions.
Simon
Most people are using the EspMilightHub which works great. You have posted in multiple threads so I know you have seen it, you just need to read, learn and use it.
Stuck at the very beginning:
Ihave the ibox2 with 2 rgb led stripes. I can add the box correctly but i dont see any channels i could use nor can i add new thingsâŠ