Chorus of “You are!”
Well, you can at least. Probable need advice about versioning though.
Chorus of “You are!”
Well, you can at least. Probable need advice about versioning though.
This is a community project, so, the community
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-database-guide
I’m not exactly sure what “this” is though - if there is a new firmware, and it changes the functionality, then it will require a new database entry. If the functionality is still the same (no new parameters or channels) then it doesn’t need a change.
Sadly folks, updating the database is quite far of my knowledge I’m afraid.
I’ve done the full communication with the Aeotec guys, the firmware is released, I did upgraded (hopefully with success), but the device is not recognized:
Window Covering Position/Endpoint Aware
Unknown: type=0003, id=008d (Node:2 Complete)
Hope to be able to access the button parameters soon with the db update, because my physical buttons are not working anymore…
That doesn’t sound like any of openHAB’s business?
Well, since the device is unknown and there is no parameter for the it, I cannot edit the parameters 85, 120, 121 for instance, to setup my buttons behavior.
It’s there:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/912
you need to upgrade to a recent 2.5 snapshot binding:
First update, then include the device, then post your xml file.
Edit: okay, you don’t need to post your xml, the parameters are already in the database, please just upgrade to a recent snapshot zwave binding:
Truth be told, I’m not using anymore OpenHab, neither Hass or any similar.
I’m using Node-Red for all my “scripting” and Zwave2Mqtt to setup my devices parameters only.
Zwave2Mqtt relies on Open-Zwave but the zw141.xml one have not been updated since June (https://github.com/OpenZWave/open-zwave/blob/master/config/aeotec/zw141.xml).
Would downloading the updated xml be enough in my case?
Then you need to be posting to a zwave2mqtt forum. How are we supposed to help you with software we have written and no one here uses?
At least, I’ve kept any people using —OpenHab— informed of the situation about the Nano Shutter on this topic over the months… I thought that was a “community” spirit… but I guess simply telling the truth of my real use case was a mistake (obviously by the “community” definition).
One could have said: “OpenHab is not relying on Open-Zwave, so that’s the reason blabla…” but sure, I’ve posted on Zwave2Mqtt discussions.
Thanks for the reminder.
I’ve just run OpenHab last snapshot, from scratch:
Z-Wave Node 002 (0371:0003:008D:3.0) Unknown Device
Voilà
No - it’s not… This is the wrong entry - there doesn’t seem to be an entry for this device in the database as far as I can see.
Aeon have changed manufacturer IDs…
These are the only info I can give you when I click “show properties” while editing the Thing:
zwave_beaming | true |
zwave_class_basic | BASIC_TYPE_ROUTING_SLAVE |
zwave_class_generic | GENERIC_TYPE_SWITCH_MULTILEVEL |
zwave_class_specific | SPECIFIC_TYPE_CLASS_C_MOTOR_CONTROL |
zwave_deviceid | 141 |
zwave_devicetype | 3 |
zwave_frequent | false |
zwave_listening | true |
zwave_manufacturer | 881 |
zwave_neighbours | |
zwave_nodeid | 2 |
zwave_plus_devicetype | NODE_TYPE_ZWAVEPLUS_NODE |
zwave_plus_roletype | ROLE_TYPE_SLAVE_ALWAYS_ON |
zwave_routing | true |
zwave_secure | false |
zwave_version | 3.0 |
Thanks. Do you have an XML file for this node - in the userdata/zwave folder? If so, we can generate a database record from this and then copy the configuration from the existing record.
Yes I do, should I copy it here?
Yes please. Just ensure you use code fences so that the formatting doesn’t get screwed (or paste it in, and use the </>
button to format the XML should also work).
<node>
<homeId>0xe1a23c91</homeId>
<nodeId>2</nodeId>
<version>4</version>
<manufacturer>0x371</manufacturer>
<deviceId>0x8d</deviceId>
<deviceType>0x3</deviceType>
<listening>true</listening>
<frequentlyListening>false</frequentlyListening>
<routing>true</routing>
<security>false</security>
<beaming>true</beaming>
<maxBaudRate>40000</maxBaudRate>
<sleepDelay>1000</sleepDelay>
<nodeInformationFrame>
<commandClass>COMMAND_CLASS_ZWAVEPLUS_INFO</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<commandClass>COMMAND_CLASS_ASSOCIATION_GRP_INFO</commandClass>
<commandClass>COMMAND_CLASS_TRANSPORT_SERVICE</commandClass>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<commandClass>COMMAND_CLASS_SCENE_ACTUATOR_CONF</commandClass>
<commandClass>COMMAND_CLASS_SCENE_ACTIVATION</commandClass>
<commandClass>COMMAND_CLASS_SWITCH_MULTILEVEL</commandClass>
<commandClass>COMMAND_CLASS_VERSION</commandClass>
<commandClass>COMMAND_CLASS_MANUFACTURER_SPECIFIC</commandClass>
<commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
<commandClass>COMMAND_CLASS_POWERLEVEL</commandClass>
<commandClass>COMMAND_CLASS_SECURITY</commandClass>
<commandClass>COMMAND_CLASS_SECURITY_2</commandClass>
<commandClass>COMMAND_CLASS_SUPERVISION</commandClass>
<commandClass>COMMAND_CLASS_FIRMWARE_UPDATE_MD</commandClass>
<commandClass>COMMAND_CLASS_CENTRAL_SCENE</commandClass>
</nodeInformationFrame>
<associationGroups class="concurrent-hash-map">
<entry>
<int>1</int>
<associationGroup>
<index>1</index>
<maxNodes>0</maxNodes>
<name>Lifeline</name>
<profile1>0x0</profile1>
<profile2>0x1</profile2>
<commands>
<commandClass>COMMAND_CLASS_BASIC</commandClass>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<commandClass>COMMAND_CLASS_CENTRAL_SCENE</commandClass>
<commandClass>COMMAND_CLASS_SWITCH_MULTILEVEL</commandClass>
<commandClass>COMMAND_CLASS_DEVICE_RESET_LOCALLY</commandClass>
</commands>
<associations>
<associationMember>
<node>1</node>
</associationMember>
</associations>
</associationGroup>
</entry>
<entry>
<int>2</int>
<associationGroup>
<index>2</index>
<maxNodes>0</maxNodes>
<name>Retransmit</name>
<profile1>0x0</profile1>
<profile2>0x0</profile2>
<commands>
<commandClass>COMMAND_CLASS_BASIC</commandClass>
<commandClass>COMMAND_CLASS_SWITCH_MULTILEVEL</commandClass>
<commandClass>COMMAND_CLASS_SCENE_ACTIVATION</commandClass>
</commands>
<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_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_VERSION</commandClass>
<COMMAND__CLASS__VERSION>
<version>2</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<libraryType>LIB_SLAVE_ENHANCED</libraryType>
<protocolVersion>6.4</protocolVersion>
<applicationVersion>3.0</applicationVersion>
<hardwareVersion>141</hardwareVersion>
</COMMAND__CLASS__VERSION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_FIRMWARE_UPDATE_MD</commandClass>
<COMMAND__CLASS__FIRMWARE__UPDATE__MD>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>4</versionSupported>
</COMMAND__CLASS__FIRMWARE__UPDATE__MD>
</entry>
<entry>
<commandClass>COMMAND_CLASS_SWITCH_MULTILEVEL</commandClass>
<multiLevelSwitchCommandClass>
<version>3</version>
<instances>1</instances>
<control>false</control>
<versionSupported>4</versionSupported>
<switchTypePrimary>OFF_ON</switchTypePrimary>
<switchTypeSecondary>UNDEFINED</switchTypeSecondary>
<isGetSupported>true</isGetSupported>
</multiLevelSwitchCommandClass>
</entry>
<entry>
<commandClass>COMMAND_CLASS_ASSOCIATION</commandClass>
<COMMAND__CLASS__ASSOCIATION>
<version>2</version>
<instances>1</instances>
<control>false</control>
<versionSupported>2</versionSupported>
<maxGroups>2</maxGroups>
</COMMAND__CLASS__ASSOCIATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_SECURITY</commandClass>
<COMMAND__CLASS__SECURITY>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
</COMMAND__CLASS__SECURITY>
</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>881</deviceManufacturer>
<deviceType>3</deviceType>
<deviceId>141</deviceId>
</COMMAND__CLASS__MANUFACTURER__SPECIFIC>
</entry>
<entry>
<commandClass>COMMAND_CLASS_SCENE_ACTIVATION</commandClass>
<COMMAND__CLASS__SCENE__ACTIVATION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
</COMMAND__CLASS__SCENE__ACTIVATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_SCENE_ACTUATOR_CONF</commandClass>
<COMMAND__CLASS__SCENE__ACTUATOR__CONF>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
</COMMAND__CLASS__SCENE__ACTUATOR__CONF>
</entry>
<entry>
<commandClass>COMMAND_CLASS_CONFIGURATION</commandClass>
<COMMAND__CLASS__CONFIGURATION>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<configParameters/>
</COMMAND__CLASS__CONFIGURATION>
</entry>
<entry>
<commandClass>COMMAND_CLASS_CENTRAL_SCENE</commandClass>
<COMMAND__CLASS__CENTRAL__SCENE>
<version>3</version>
<instances>1</instances>
<control>false</control>
<versionSupported>3</versionSupported>
<sceneCount>2</sceneCount>
</COMMAND__CLASS__CENTRAL__SCENE>
</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>1</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_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_ASSOCIATION_GRP_INFO</commandClass>
<COMMAND__CLASS__ASSOCIATION__GRP__INFO>
<version>1</version>
<instances>1</instances>
<control>false</control>
<versionSupported>1</versionSupported>
<autoSubscribeGroups>
<int>1</int>
<int>2</int>
</autoSubscribeGroups>
</COMMAND__CLASS__ASSOCIATION__GRP__INFO>
</entry>
<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_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>
</supportedCommandClasses>
</endPoint>
</entry>
</endpoints>
<nodeNeighbors/>
<lastReceived>2019-11-17 18:49:16.798 UTC</lastReceived>
</node>
Yes, now that he posted the manufacturer id for the first time I realized that, too.
@Tazintosh, thx for wasting my time
I’ve now added the new device -:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/database-history/devicesummary/1151
I’ll do a binding update shortly.
One of the reasons I moved here to OpenHAB was because of the pitiful device support in Home Assistant which also depends on Open-Zwave. I believe the also depend on volunteers for database updates but the one here appears much more complete.
It was proposed, a number of years ago, that we work together on databases but they refused the offer.