I couldn’t find it either. 
Also can’t find the device.
I’m assuming you have a manual? That would be needed as well.
This is the device
The manual shows assembling and how to connect remote and emitter but nothing about z-wave.
Just ask Judy about the Z-Wave specifics of your device (association groups, configuration parameters, inclusion, …): Contact us
I have written the message and I am very curious what comes out of it
The xml might also provide clues as to the needed information
The xml file is this
<node>
<homeId>0xff727f7e</homeId>
<nodeId>114</nodeId>
<version>4</version>
<manufacturer>0x45a</manufacturer>
<deviceId>0x505</deviceId>
<deviceType>0x4</deviceType>
<listening>true</listening>
<frequentlyListening>false</frequentlyListening>
<routing>true</routing>
<security>false</security>
<beaming>true</beaming>
<maxBaudRate>40000</maxBaudRate>
<sleepDelay>500</sleepDelay>
<nodeInformationFrame>
<commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
<commandClass>COMMAND_CLASS_SWITCH_MULTILEVEL</commandClass>
<commandClass>COMMAND_CLASS_WINDOW_COVERING</commandClass>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<commandClass>COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
<commandClass>COMMAND_CLASS_TRANSPORT_SERVICE</commandClass>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
<commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
<commandClass>COMMAND_CLASS_INDICATOR</commandClass>
<commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
<commandClass>COMMAND_CLASS_SECURITY_2</commandClass>
<commandClass>COMMAND_CLASS_SUPERVISION</commandClass>
<commandClass>COMMAND_CLASS_FIRMWARE_UPDATE_MD</commandClass>
<commandClass>COMMAND_CLASS_APPLICATION_STATUS</commandClass>
</nodeInformationFrame>
<associationGroups class="concurrent-hash-map">
<entry>
<int>1</int>
<associationGroup>
<index>1</index>
<maxNodes>0</maxNodes>
<associations/>
</associationGroup>
</entry>
<entry>
<int>2</int>
<associationGroup>
<index>2</index>
<maxNodes>0</maxNodes>
<associations/>
</associationGroup>
</entry>
<entry>
<int>3</int>
<associationGroup>
<index>3</index>
<maxNodes>0</maxNodes>
<associations/>
</associationGroup>
</entry>
<entry>
<int>4</int>
<associationGroup>
<index>4</index>
<maxNodes>0</maxNodes>
<associations/>
</associationGroup>
</entry>
</associationGroups>
<endpoints class="concurrent-hash-map">
<entry>
<int>0</int>
<endPoint>
<deviceClass>
<basicDeviceClass>BASIC_TYPE_ROUTING_SLAVE</basicDeviceClass>
<genericDeviceClass>GENERIC_TYPE_SWITCH_MULTILEVEL</genericDeviceClass>
<specificDeviceClass>SPECIFIC_TYPE_CLASS_C_MOTOR_CONTROL</specificDeviceClass>
</deviceClass>
<endpointId>0</endpointId>
<secureCommandClasses/>
<supportedCommandClasses class="concurrent-hash-map">
<entry>
<commandClass>COMMAND_CLASS_NO_OPERATION</commandClass>
<COMMAND__CLASS__NO__OPERATION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
</COMMAND__CLASS__NO__OPERATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_BASIC</commandClass>
<COMMAND__CLASS__BASIC>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<isGetSupported>true</isGetSupported>
</COMMAND__CLASS__BASIC>
</entry>
<entry>
<commandClass>COMMAND_CLASS_APPLICATION_STATUS</commandClass>
<COMMAND__CLASS__APPLICATION__STATUS>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
</COMMAND__CLASS__APPLICATION__STATUS>
</entry>
<entry>
<commandClass>COMMAND_CLASS_SWITCH_MULTILEVEL</commandClass>
<multiLevelSwitchCommandClass>
<version>3</version>
<instances>1</instances>
<control>false</control>
<versionSupported>4</versionSupported>
<switchTypePrimary>DOWN_UP</switchTypePrimary>
<switchTypeSecondary>UNDEFINED</switchTypeSecondary>
<isGetSupported>true</isGetSupported>
</multiLevelSwitchCommandClass>
</entry>
<entry>
<commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
<COMMAND__CLASS__ASSOCIATION__GRP__INFO>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>3</versionSupported>
<autoSubscribeGroups/>
</COMMAND__CLASS__ASSOCIATION__GRP__INFO>
</entry>
<entry>
<commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
<COMMAND__CLASS__DEVICE__RESET__LOCALLY>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
</COMMAND__CLASS__DEVICE__RESET__LOCALLY>
</entry>
<entry>
<commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
<COMMAND__CLASS__ZWAVEPLUS__INFO>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<zwPlusVersion>2</zwPlusVersion>
<zwPlusRole>ROLE_TYPE_SLAVE_ALWAYS_ON</zwPlusRole>
<zwPlusNodeType>NODE_TYPE_ZWAVEPLUS_NODE</zwPlusNodeType>
<isGetSupported>true</isGetSupported>
</COMMAND__CLASS__ZWAVEPLUS__INFO>
</entry>
<entry>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<COMMAND__CLASS__CONFIGURATION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>4</versionSupported>
<configParameters/>
</COMMAND__CLASS__CONFIGURATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
<COMMAND__CLASS__MANUFACTURER__SPECIFIC>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<initSerialNumber>false</initSerialNumber>
<deviceManufacturer>1114</deviceManufacturer>
<deviceType>4</deviceType>
<deviceId>1285</deviceId>
</COMMAND__CLASS__MANUFACTURER__SPECIFIC>
</entry>
<entry>
<commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
<COMMAND__CLASS__POWERLEVEL>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<powerLevel>0</powerLevel>
<powerTimeout>0</powerTimeout>
</COMMAND__CLASS__POWERLEVEL>
</entry>
<entry>
<commandClass>COMMAND_CLASS_FIRMWARE_UPDATE_MD</commandClass>
<COMMAND__CLASS__FIRMWARE__UPDATE__MD>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>5</versionSupported>
</COMMAND__CLASS__FIRMWARE__UPDATE__MD>
</entry>
<entry>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<COMMAND__CLASS__ASSOCIATION>
<version>2</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<maxGroups>4</maxGroups>
</COMMAND__CLASS__ASSOCIATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<COMMAND__CLASS__VERSION>
<version>2</version>
<instances>1</instances>
<control>false</control>
<versionSupported>3</versionSupported>
<libraryType>LIB_SLAVE_ENHANCED</libraryType>
<protocolVersion>7.16</protocolVersion>
<applicationVersion>1.1</applicationVersion>
<hardwareVersion>1</hardwareVersion>
</COMMAND__CLASS__VERSION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_INDICATOR</commandClass>
<COMMAND__CLASS__INDICATOR>
<version>3</version>
<instances>1</instances>
<control>false</control>
<versionSupported>3</versionSupported>
<isGetSupported>true</isGetSupported>
<supportedIndicatorsInitialised>true</supportedIndicatorsInitialised>
<supportedIndicators>
<ZWaveIndicator>
<type>NODE_IDENTIFY</type>
</ZWaveIndicator>
</supportedIndicators>
</COMMAND__CLASS__INDICATOR>
</entry>
<entry>
<commandClass>COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION</commandClass>
<COMMAND__CLASS__MULTI__CHANNEL__ASSOCIATION>
<version>3</version>
<instances>1</instances>
<control>false</control>
<versionSupported>3</versionSupported>
<maxGroups>4</maxGroups>
</COMMAND__CLASS__MULTI__CHANNEL__ASSOCIATION>
</entry>
</supportedCommandClasses>
</endPoint>
</entry>
</endpoints>
<nodeNeighbors>
<int>1</int>
</nodeNeighbors>
<lastReceived>2023-05-01 09:15:33.802 UTC</lastReceived>
</node>
I’m not an expert at how this will end up when you load it, however, on a quick scan, there are 4 association groups and probably 3 channels (one up_Down for sure), but no parameters. It would be helpful (to filling out the DB) to ask Judy how many nodes can be in each association group, what the secondary Multiswitch channel does (Is it a percentage?) and what the indicator channel is supposed to do (are there lights on when the motor is moving?) Lastly if there are any parameters that govern operation (like no lights when running).
1 Like
I forwarded your message and also this thread to Judy. We’ll see what happens. 
I am in constant exchange with Zemismart support. They are really friendly and helpful (they also helped me with the remote control problem). They wrote me five days ago that they added the device to the database and asked if the channels would work for me now. According to them, the review process has been started. How long does it usually take for a device to be added to the DB?
Is there anything I can do to help with this?
The last database update was 5 or 6 days ago, but there are no devices waiting approval.
Please can you tell me what database entry this relates to.
The database entry should relate the xml file I posted in this thread.
Should I make an entry myself with this file or should I ask zemismart support to make a (new) entry?
What zemismart are probably talking about is the Zwave Alliance listing of zwave certified devices. When you first opened this issue I checked that listing and could not find either the manufacturer (0x045a) or the device 0004:0505:1.1. That is unusual and I’m guessing they are now applying for certification.
Separately (from the zwave Alliance DB) to get the device working in OH it will have to be added to the OH zwave db. As noted above you will need to load the xml to create a new device. However, first you will need to register and open a ticket for write access (explained in the Blog-link is in my first post of this thread) and also because this is a new mfg @chris will have to add (0x045a) before you will be able to create the device.
If I have understood this correctly, I can add the device to the db only after @chris added the manufacturer (0x045a) to the OH DB and he will do this only if they are listed in the zwave Alliance DB, right?
As long as Shenzhen ZVIDAR Technologies (0x45a) isn’t registered in the Z-Wave database, you cannot upload your XML file to the Z-Wave database.
The criteria for adding a new manufacturer to the Z-Wave database are up to @chris.
I figured zemismart may have been added as allowed to the OH zwave database over the past weekend, so I tried and added your XML to move this along.
OpenSmartHouse Z-Wave Device Database
I’ll leave it to you to add the missing information that you have been able to get from Judy. (such as any parameters, the association groups and manuals. After the errors are cleared mark “request review” on the first tab.
Thank you very much for that. Actually I didn’t get any information from Judy, I’m in touch with zemismart support over AliExpress. Hopefully they will deliver the necessary information.
Sorry, but obviously I didn’t understand what to do. I used “contact us” on the website and opened a ticket but that doesn’t seem to be the right way. Can anybody tell me what I should do?
Best regards
No idea
What I would do is fill in the zwave DB the best you can. (Scan manual that you have, etc.) to clear the errors and ask for review. It will then get included with at least the one channel that you can test and adjust if necessary.
Return it (lack of information and lack of support by the manufacturer).
1 Like
So @chris granted me write access, I updated the device and Chris approved it. Shouldn’t that be enough to find those channels while scanning? Or am I missing something?
Best regards