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.
deleting the thing and readding does also got give me Node41 XML…
but i reseted the device and added as new zwave device (NODE 43) then i got the XML for new node 43
https://we.tl/t-uerhCKvGHo
Your device is already in the database:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1127
<manufacturer>0x10f</manufacturer>
<deviceId>0x1000</deviceId>
<deviceType>0x902</deviceType>
It was added 10 days ago and merged into the binding 4 days ago, so you need to have a zwave binding snapshot version from after 21st of Oct:
https://openhab.jfrog.io/openhab/online-repo-snapshot/2.5/org/openhab/addons/bundles/org.openhab.binding.zwave/2.5.0-SNAPSHOT/
I have installed and am using (and verified) latest successfull zwave binding build from 2 days ago.
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.
Yeah will do 
When do the changes get picked up? Once a day, week?
Usually once a week at the weekends.
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.
BR,
Sebastian
Use tne manual install script to just install the snapshot zwave binding on 2.4.
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.
FYI
I’ve uploaded a XML file to the database from a device I’ve bought.
Any more information needed, just let me know.
Link to the device? Likely there are some manual steps needed.
Oh, actually I think it’s exactly this device :
Fibaro FGRGBW-442
I’ve updated to OpenHab 2.5 today and I still get this error. The thing with all its channels is present and I can add items, but they are all non-functional. The thing itself is stuck at:
Status: UNINITIALIZED - HANDLER_INITIALIZING_ERROR For input string: “1colorMode=DIFF_WHITE”
Please start a new thread. Although the symptoms may be similar, it gets too confusing trying to chase many problems in the same thread.
Thank you for your advice! I’ve created a new topic.
I’m having unknown device issue again. running 2.5 snapshot currently, but only switched to make sure stable wasn’t the issue. From Habmin it shows the following attributes:
Manufacturer: 010f"Fibargroup"
Type/ID: 0902:2000
Firmware: 5.0
and logs show
[WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 20: Device discovery could not resolve to a thingType! 010F:0902:2000::5.0
Sorry if this has been covered, but i’ve not come up with a solution. Thanks in advance
