Hi there,
I’m trying to add my MCOHOME PM2.5 air quality monitor (Z-Wave) to OpenHAB. It’s not in the database.
network_d0294c80__node_26.xml (8.2 KB)
I found this thread, saw the database links above, created an account and opened a ticket on cd-jackson.com, now just waiting for @chris to let me in, please. 
I’ve updated your access. The ticket you opened this morning somehow seems broken, but you should be good to go
Thanks, Chris!
Working on it. Not easy (it’s my first time) but doing my best.
I’m afraid I’ve made a bit of a mess of things, though.
I mistakenly modified the channel list on device #115. Please disregard this edit.
I also mistakenly added a new device #1055 when in fact device #244 already existed with different IDs. I don’t know how I didn’t find it the first time, because I did search… I thought I did, anyway. Please delete device #1055. Sorry for the mess, I’ll get the hang of this eventually.
No worries Leif, we’ll make it thru yes!!
Okay, having a few problems.
Every. Single. Page. is labeled simply “Device List”. That doesn’t help.
Anyway. I can’t seem to delete things when I’ve added something by mistake, nor can I seem to cancel a request. Might be a privilege issue.
I’m seeing a red exclamation point on parameter 255 (which I added), with no explanation or tooltip or other error message. 255 is correct – it’s listed as FF in the manual, I tried making it FF in the device list but it came out as 0, so I the field must be decimal, not hexadecimal.
Anyway… phew. I’ve made my submission now, device #244.
Please delete device #1055, I did not mean to add it.
Please also disregard the change to #115.
Will now try to add the updated device into openhab manually, hopefully that is a thing.
Looks like that’s NOT a thing – I found the following thread:
https://community.openhab.org/t/z-wave-device-template-adding-new-device/36074
Alright, I will wait patiently for an update, and add my device back to Fibaro HC2 in the mean time, since I really need the ventilation system automation to work. 
Here we go, that wasn’t so bad.
Fibaro HC2 LUA scene (script) to feed a parameter from a Z-Wave device (in this case id 301) directly to OpenHAB through the REST API.
--[[
%% properties
310 value
%% events
%% globals
--]]
payload = fibaro:getValue(310, 'value');
-- fibaro:debug('value ' .. payload)
local http = net.HTTPClient()
http:request('http://172.22.22.100:8080/rest/items/AirQualitySensor_PM25', {
options = {
method = 'POST',
headers = {},
data = payload,
timeout = 5000
}
})
This will hold me over until openHAB supports my device.
Done.
I think your initial thought (adding a new device) was the right one: the existing database entry
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/244
is a non plus device without the configuration command class.
Your device is a zwave plus device and has the configuration command class.
@chris could you take a quick look, please?
Existing database entry is a non plus zwave device, @leif 's device is a zwave plus device (firmware version 2.3), should we separate the two devices in the database (I have some spare time today to do that).
Correct, database users with normal access rights can only add and edit entries, not delete them.
It’s hard to tell how best to handle this. There are two options -:
I found a newer manual which still doesn’t mention the configuration command class, but does list config parameters.
I also tried to find this device in the zwave alliance database, but couldn’t.
Given that the new manual specifically mentions ZWave Plus Technology, where the old one only says ZWave Technology, they are probably different, and probably it’s therefore best to split them.
Thanks @sihui
This just means that this is marked as a critical parameter so in the UI there should be an “Are you sure” question raised.
Ah wow! Nice attention to detail there @sihui, I didn’t think to compare the manuals, especially since the devices are identical externally. I saw that the command class was missing, but I actually assumed that the original poster had been lazy and deleted the command class (to get rid of the database warning that there’s a command class but no defined commands) rather than fill out the commands! My bad.
So, it looks like I added a whole bunch of information to 244 which really only applies to #1055 then.
Do you need me to do anything else or will you take it from here?
@chris, I checked the manual you linked to and found the following on page 5:
Isn’t that it?
My version of the manual (the one I uploaded) has it too.
I will create separate database entries and revert the changes to #244. Give me a minute or two 
Well - this is the list of command classes, but as I said, it doesn’t list the configuration command class.
It’s in his xml file so I guess separating the devices is a good idea:
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<COMMAND__CLASS__CONFIGURATION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<configParameters/>
</COMMAND__CLASS__CONFIGURATION>
But what does this mean?
#### Device definition contains errors
* Channel in endpoint 0 uses an unsupported channel (particulate_matter)!
Error in the xml or do you need to add this command class to the database?
I seem to have caused confusion - sorry. I didn’t mean to infer that it was not supported. Clearly the device supports the configuration command class as the manual lists the configuration parameters.
My point was simply that the configuration command class is not listed in EITHER manual. However, in the newer manual the config parameters ARE listed. Clearly this means that the newer device supports configuration command class, but it still doesn’t prove that the older device didn’t support the parameters. It’s not uncommon for Chinese manufacturers to have really crappy manuals that don’t list configuration parameters. It’s just not possible to say from the information we have.
It means the database error checker doesn’t know about this channel. It probably means that the importer created the channel incorrectly.
It would pay to use what the old device used (sensor_particulate).
Okay, all done:
non plus device:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/244
plus device:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1056
Interestingly, there is another device with the same issue… Myself and @TimScottz8 have been discussing off list the MCO MH8-FC. This seems to have done the same thing - ie there is a newer version that is ZWave Plus, and contains similar parameters to the PM2.5 we were discussing earlier.
Currently Tim has updated the old database entry, but I think we probably should take the same approach as we did above with the PM2.5 as the version Tim has is the Plus version -:
http://manuals-backend.z-wave.info/make.php?lang=en&sku=MCOEMH8-FC&cert=
I wanted to move this discussion onto the forum so there’s a record of what/why we’ve done this
@sihui how did you differentiate the devices earlier - was it just with the firmware versions? I think we should do the same here…
Yes, looks like exact the same issue.
Yes.
Would be great to have the xml as a starting poiint 
If it is not available I could add them manually … tomorrow
Arghhhh, did it again: unfortunately I hit the “Export” button, sorry …
Done:
non plus device:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/336
plus device:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1057
Added a comment to this post as reference, omitted the “Export” this time
As I don’t know the device type and id you were talking about I added them all, please remove if necessary.