Hi Bruce,
Thanks you first of all for taking over this task!
I was willing to start on the weekend, XML and documentation were ready.
But it took till yesterday to get the permission to ad devices. During the week i have no time and then you already started to work in it.
Nevertheless i will follow your Implementation and will be ready when the next new device comes Up!
You are welcome. Help is always welcomed especially where devices have a large number of configuration parameters with options. It is a lot of extra work to try and make it as user-friendly as possible.
It gets complex when they confuse at a level smaller than a byte. I wanted to wait until I was fresh to tackle some of that.
I am definitely not the only one working on zwave. I think a separate topic for each one, tagged as z-wave would be best. Some devices may need binding changes. Due to the developer’s backlog of work that could take a while. An estimate for one long-awaited change was a month from now.
By the way, sihui assisted and completed & reviewed this device. The database is usually exported weekly to GitHub and then the snapshot build system builds a new binding. Usually I would then recommend updating your binding but Kay’s be cautious here. The latest snapshot bindings appear to have an error.
I tried latest zwave binding build (from Oct-23-2019) and got the Fibaro rgbw 2 Controller thing after including it. But there has to be a bug remaining, see below.
For that reason zwave thing get stuck at “get_configuration”. Setting the brightness is fine but choosing a color does not work. Tell me what is needed to debug and i will provide
2019-10-24 21:32:16.563 [ERROR] [alization.ZWaveNodeInitStageAdvancer] - NODE 41: Error in initialization thread
java.lang.NumberFormatException: For input string: “1colorMode=DIFF_WHITE”
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) ~[?:?]
at java.lang.Integer.parseInt(Integer.java:580) ~[?:?]
at java.lang.Integer.parseInt(Integer.java:615) ~[?:?]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialiseNode(ZWaveThingHandler.java:263) ~[192:org.openhab.binding.zwave:2.5.0.201910230344]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.ZWaveIncomingEvent(ZWaveThingHandler.java:1457) ~[192:org.openhab.binding.zwave:2.5.0.201910230344]
at org.openhab.binding.zwave.internal.protocol.ZWaveController.notifyEventListeners(ZWaveController.java:566) ~[192:org.openhab.binding.zwave:2.5.0.201910230344]
at org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer.setCurrentStage(ZWaveNodeInitStageAdvancer.java:1139) ~[192:org.openhab.binding.zwave:2.5.0.201910230344]
at org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer.access$5(ZWaveNodeInitStageAdvancer.java:1130) ~[192:org.openhab.binding.zwave:2.5.0.201910230344]
at org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer$1.run(ZWaveNodeInitStageAdvancer.java:207) [192:org.openhab.binding.zwave:2.5.0.201910230344]
Set the log level for the zwave binding to DEBUG. File can be downloaded here: https://we.tl/t-JSghHxBKKK
If you search for “color mode” i think you get to the right point. Node 41.
Unluckily there is no XML file for Node 41.
ll /var/lib/openhab2/zwave/ | grep 41 | wc -l -> 0
But i have one for Node 40 (which was the same device but i reseted the device and included again which is now 41) https://we.tl/t-EY4sDqSinR
That means the device has not been fully discovered and should not be expected to work properly.You can try deleting & re-adding the Thing to get it rediscovered, while keeping the dimmer awake.
Never seen that error, sorry.
For the older device we had to set a config option:
I did this for this device now, but I am not sure if this helps.
Please upgrade your binding once the changes got merged.
If it is still not working please provide a DEBUG log and ping Chris for assistance (please be patient as he is very busy at the moment)
Please also do the basic stuff before: clear the cache, delete the Thing and re-add it.
Hi there,
first of all thank you for your amazing work here. Did anyone a successful test with this device up to now? Tried to understand your implementation of this device for future experiments ;).
I tested yesterday the current snapshot of openhab to check if the device is working. I basically come as far as @spider1354.
But i am not sure if the latest version of the zwave binding with @sihui mods was included. Unfortunetly i switched back to stable version for productive operation already.
Hi all,
tried the latest current Binding from today 4.11:
openhab> bundle:list|grep -i zwave
193 │ Active │ 80 │ 2.5.0.201911040345 │ openHAB Add-ons :: Bundles :: ZWave Binding
But do get still errors when including the RGBW Controller 2:
2019-11-04 18:58:48.319 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method ‘ThingHandler.initialize()’ on ‘org.openhab.binding.zwave.handler.ZWaveThingHandler@186d7b’: For input string: “1colorMode=DIFF_WHITE”
java.lang.NumberFormatException: For input string: “1colorMode=DIFF_WHITE”
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) ~[?:?]
at java.lang.Integer.parseInt(Integer.java:580) ~[?:?]
at java.lang.Integer.parseInt(Integer.java:615) ~[?:?]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialiseNode(ZWaveThingHandler.java:263) ~[?:?]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.bridgeStatusChanged(ZWaveThingHandler.java:537) ~[?:?]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialize(ZWaveThingHandler.java:163) ~[?:?]
at sun.reflect.GeneratedMethodAccessor76.invoke(Unknown Source) ~[?:?]
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-11-04 18:58:48.344 [ERROR] [core.thing.internal.ThingManagerImpl] - Exception occurred while initializing handler of thing ‘zwave:device:22089965:node44’: For input string: “1colorMode=DIFF_WHITE”
java.lang.NumberFormatException: For input string: “1colorMode=DIFF_WHITE”
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) ~[?:?]
at java.lang.Integer.parseInt(Integer.java:580) ~[?:?]
at java.lang.Integer.parseInt(Integer.java:615) ~[?:?]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialiseNode(ZWaveThingHandler.java:263) ~[?:?]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.bridgeStatusChanged(ZWaveThingHandler.java:537) ~[?:?]
at org.openhab.binding.zwave.handler.ZWaveThingHandler.initialize(ZWaveThingHandler.java:163) ~[?:?]
at sun.reflect.GeneratedMethodAccessor76.invoke(Unknown Source) ~[?:?]
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) [?:?]
The binding was last updated 7 days ago.
The developer is on a much needed vacation so I would not expect an update for another 2 weeks or so. He does not currently have VPN access to update when away.