Link:
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/268
Color is not in the Database for the above device, while alarm is.
I wasn’t sure which commands where available in the binding, still a novice.
Thanks for the info about “NOTIFICATION”=“ALARM” classes, Alarm is also available as a channel, I’ll just have to learn to use it, more completely.
I’ve approved it, but there is nothing new so the database hasn’t changed. If there’s something not working then it won’t be fixed with the update. If you uploaded an XML to update things like colour, then the database importer doesn’t add extra classes to avoid people uploading random files and screweing things up.
No probs - can you attach the XML for this and I’ll add the command class. It looks like it should work fine.
NOTIFICATION is ‘just’ an updated version of ALARM - it does support some new features and we might need to update some of the channels to make it work better, so if you have any issues, just yell…
I will add COLOR into the database for tonights version so let me know tomorrow if it’s ok (or not! 
).
node19.xml (10.2 KB)
Here’s the node.xml for the device. I shall check tomorrow’s release, thanks.
I need to do a little more research on ALARM/NOTIFICATION before I can say whether it works or not. LOL. 
So, If I need to have a command class added to an existing device, I should add it manually, as and .xml upload will not fix my issues. Is this a correct statement?
Thanks for the help!!!
Yep - sure is ;).
The fibaro wallplug still needs a db update to be able to use the reset command?
If so i can try and update it, if i have the correct access.
I can confirm that reset works on both the Fibaro WallPlug and the GreenWave PowerNode. It works in the latest OH2-Snapshot.
Had to clear the cache, temporary files and then remove the z-wave Thing and re-add it.
Regards, S
Great - thanks for the feedback 
I do get the following as a warning, don’t know if it should be suppressed?
2016-09-19 19:58:39.653 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No messages returned from converter
I have a color channel now, thanks!!!
Now to figure out how to use it as the color documentation so far is slim. I will change that once I figure everything out!!!
What documentation do you need? Just link it to a colour picker widget and it should allow you to select a colour… Simples ;).
Chris, haven’t dropped off the face of the earth, stupid things, like work and homecare have gotten in my way, will update you soon.
Sorry to bump this thread, but I can’t see a RESET channel for my FGWP101 wall plug. What do I need to do to have the reset function back? It worked in OH1.
I would suggest to update to a more recent version of the binding - what version are you using?
I’m using the latest nightly, updated a week ago.
Hmmm - ok, I thought there hadn’t been any updates for 2 or 3 weeks 
.
The other alternative is you have a different device than discussed here?
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/130
I’m running build 858.
This is the device xml
<node>
<deviceClass>
<basicDeviceClass>ROUTING_SLAVE</basicDeviceClass>
<genericDeviceClass>BINARY_SWITCH</genericDeviceClass>
<specificDeviceClass>NOT_USED</specificDeviceClass>
</deviceClass>
<homeId>0xcb5b3138</homeId>
<nodeId>7</nodeId>
<version>4</version>
<manufacturer>0x10f</manufacturer>
<deviceId>0x1000</deviceId>
<deviceType>0x600</deviceType>
<listening>true</listening>
<frequentlyListening>false</frequentlyListening>
<routing>true</routing>
<security>false</security>
<beaming>true</beaming>
<maxBaudRate>40000</maxBaudRate>
<nodeInformationFrame>
<commandClass>MANUFACTURER_SPECIFIC</commandClass>
<commandClass>VERSION</commandClass>
<commandClass>CONFIGURATION</commandClass>
<commandClass>ASSOCIATION</commandClass>
<commandClass>MULTI_INSTANCE_ASSOCIATION</commandClass>
<commandClass>SWITCH_BINARY</commandClass>
<commandClass>POWERLEVEL</commandClass>
<commandClass>METER</commandClass>
<commandClass>SENSOR_MULTILEVEL</commandClass>
<commandClass>FIRMWARE_UPDATE_MD</commandClass>
</nodeInformationFrame>
<supportedCommandClasses>
<entry>
<commandClass>MANUFACTURER_SPECIFIC</commandClass>
<manufacturerSpecificCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<initSerialNumber>false</initSerialNumber>
<deviceManufacturer>271</deviceManufacturer>
<deviceType>1536</deviceType>
<deviceId>4096</deviceId>
</manufacturerSpecificCommandClass>
</entry>
<entry>
<commandClass>ASSOCIATION</commandClass>
<associationCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<maxGroups>3</maxGroups>
</associationCommandClass>
</entry>
<entry>
<commandClass>CONFIGURATION</commandClass>
<configurationCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<configParameters>
<entry>
<int>1</int>
<configurationParameter>
<index>1</index>
<size>1</size>
<value>1</value>
<readOnly>false</readOnly>
<writeOnly>false</writeOnly>
</configurationParameter>
</entry>
</configParameters>
</configurationCommandClass>
</entry>
<entry>
<commandClass>MULTI_INSTANCE_ASSOCIATION</commandClass>
<multiAssociationCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<maxGroups>2</maxGroups>
</multiAssociationCommandClass>
</entry>
<entry>
<commandClass>BASIC</commandClass>
<basicCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</basicCommandClass>
</entry>
<entry>
<commandClass>POWERLEVEL</commandClass>
<powerLevelCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<powerLevel>0</powerLevel>
<powerTimeout>0</powerTimeout>
</powerLevelCommandClass>
</entry>
<entry>
<commandClass>VERSION</commandClass>
<versionCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<libraryType>LIB_SLAVE_ENHANCED</libraryType>
<protocolVersion>3.52</protocolVersion>
<applicationVersion>25.25</applicationVersion>
</versionCommandClass>
</entry>
<entry>
<commandClass>METER</commandClass>
<meterCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<meterType>ELECTRIC</meterType>
<meterScales>
<meterScale>E_W</meterScale>
<meterScale>E_KWh</meterScale>
</meterScales>
<canReset>true</canReset>
<isGetSupported>true</isGetSupported>
<isSupportRequestSupported>true</isSupportRequestSupported>
</meterCommandClass>
</entry>
<entry>
<commandClass>SWITCH_BINARY</commandClass>
<binarySwitchCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</binarySwitchCommandClass>
</entry>
<entry>
<commandClass>SENSOR_MULTILEVEL</commandClass>
<multiLevelSensorCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<sensors>
<entry>
<multilevelSensorType>POWER</multilevelSensorType>
<multilevelSensor>
<sensorType>POWER</sensorType>
<initialised>true</initialised>
</multilevelSensor>
</entry>
</sensors>
<isGetSupported>true</isGetSupported>
</multiLevelSensorCommandClass>
</entry>
<entry>
<commandClass>FIRMWARE_UPDATE_MD</commandClass>
<firmwareUpdateCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
</firmwareUpdateCommandClass>
</entry>
<entry>
<commandClass>NO_OPERATION</commandClass>
<noOperationCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
</noOperationCommandClass>
</entry>
</supportedCommandClasses>
<securedCommandClasses/>
<associationGroups>
<entry>
<int>1</int>
<associationGroup>
<index>1</index>
<associations>
<associationMember>
<node>1</node>
<endpoint>0</endpoint>
</associationMember>
</associations>
</associationGroup>
</entry>
<entry>
<int>2</int>
<associationGroup>
<index>2</index>
<associations/>
</associationGroup>
</entry>
<entry>
<int>3</int>
<associationGroup>
<index>3</index>
<associations/>
</associationGroup>
</entry>
</associationGroups>
<nodeNeighbors>
<int>1</int>
<int>8</int>
</nodeNeighbors>
<lastSent>2017-04-14 18:51:12.208 UTC</lastSent>
<lastReceived>2017-04-14 18:51:12.253 UTC</lastReceived>
</node>
Looks the same - the only other thing I can suggest then is you’ve not actually update the thing? Try deleting the thing and adding it back in again.
