Zwave device type UNKNOWN

For Z-Wave related questions in Domoticz

Moderator: leecollings

Post Reply
xavierlp
Posts: 70
Joined: Tuesday 01 November 2016 16:22
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Location: France
Contact:

Zwave device type UNKNOWN

Post by xavierlp »

Hello I bought 4 Access Control Sensor EVERSPRING Z-Wave+ SM810
http://www.everspring.com/portfolio-ite ... ct-sensor/

It's work very weel but in domoticz / setup / hardware / setup they are unknow.

I could understand that we can update an xml file to add information.

May be one of you use SM810 without issues and can help me.

Thanks a lot

The message in the line is : Unknown: id=0060 Unknown: type=0002, id=0003+
Sans titre.png
Sans titre.png (10.32 KiB) Viewed 1952 times
Snowtiger
Posts: 120
Joined: Tuesday 18 October 2016 13:15
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.10915
Contact:

Re: Zwave device type UNKNOWN

Post by Snowtiger »

Did you try to do a Node Heal in the Zwave devices listing (under Zwave controller device, press settings) - after the Heal command you have to wake up your Device (if I am correct and it is Battery-powered)
xavierlp
Posts: 70
Joined: Tuesday 01 November 2016 16:22
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Location: France
Contact:

Re: Zwave device type UNKNOWN

Post by xavierlp »

Hello @snowtiger

I did it but same behaviour.

Do you know where is the xml file with all zwave devices ?

thanks
User avatar
LouiS22
Posts: 433
Joined: Friday 27 February 2015 13:21
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Budapest, Hungary
Contact:

Re: Zwave device type UNKNOWN

Post by LouiS22 »

Snowtiger wrote: Sunday 12 July 2020 16:10 Did you try to do a Node Heal in the Zwave devices listing (under Zwave controller device, press settings) - after the Heal command you have to wake up your Device (if I am correct and it is Battery-powered)
This has nothing to do with healing, the required .xml file is not present hence OZW cannot handle it. You need to create the .xml, also update the manufacturer_specific.xml or simply wait til the device gets supported.

@xavierlp: you need to follow the manual provided @ openzwave's github, it's quite simple to understand.
xavierlp
Posts: 70
Joined: Tuesday 01 November 2016 16:22
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Location: France
Contact:

Re: Zwave device type UNKNOWN

Post by xavierlp »

@LouiS22 thanks for the tip

So I updated the file manufacturer_specific.xml to add this line

Code: Select all

<Product config="everspring/sm810.xml" id="0003" name="SM810 Door/Window Sensor" type="0002"/>
under

Code: Select all

<Manufacturer id="0060" name="Everspring">
then add a file sm810.xml in the dir /home/pi/domoticz/Config/everspring
like this

Code: Select all

<Product Revision="5" xmlns="https://github.com/OpenZWave/open-zwave">
  <MetaData>
    <MetaDataItem name="OzwInfoPage">http://www.openzwave.com/device-database/0060:0003:0002</MetaDataItem>
    <MetaDataItem name="ProductPic">images/everspring/sm810.png</MetaDataItem>
    <MetaDataItem id="0003" name="ZWProductPage" type="0002">https://products.z-wavealliance.org/products/2985/</MetaDataItem>
    <MetaDataItem id="0003" name="Identifier" type="0002">SM810</MetaDataItem>
    <MetaDataItem name="Name">Door/Window Sensor</MetaDataItem>
    <MetaDataItem name="ProductPage">http://www.everspring.com/SM810.aspx</MetaDataItem>
    <MetaDataItem id="0003" name="FrequencyName" type="0002">CEPT (Europe) / Russia / CEPT (Europe)</MetaDataItem>
    <MetaDataItem name="Description">The Mini Door/Window contact detector consists of two parts; a Detector and a Magnet.  They are designed to be fitted to doors or windows with the Magnet mounted on the opening part and the Detector mounted on the fixed frame. Opening the protected door/window will remove the magnetic field, trigger the Detector and generate an alarm condition, (if the system is armed).
The Door/Window Detector is a Z-Wave enabled device and is fully compatible with any Z-Wave enabled network.
If several windows need to be protected, adopt the wire according to the placement as mentioned below. This should be wired to the terminal block provided in the battery compartment in series connection. 
</MetaDataItem>
    <ChangeLog>
      <Entry author="Justin Hammond - [email protected]" date="03 May 2019" revision="3">Initial Metadata Import from Z-Wave Alliance Database - https://products.z-wavealliance.org/products/394/xml</Entry>
      <Entry author="Justin Hammond - [email protected]" date="03 May 2019" revision="4">Updated Metadata Import from Z-Wave Alliance Database - https://products.z-wavealliance.org/products/921/xml</Entry>
      <Entry author="Justin Hammond - [email protected]" date="03 May 2019" revision="5">Updated Metadata Import from Z-Wave Alliance Database - https://products.z-wavealliance.org/products/924/xml</Entry>
    </ChangeLog>
  </MetaData>
  <!-- Configuration Parameters -->
  <CommandClass id="112">
    <Value genre="config" index="1" label="On Level" max="127" min="0" type="byte" units="" value="99">
      <Help>
				Defines the level in the event sent when the sensor is triggered.  Default is 99 (full brightness for a Z-Wave dimmer). 100-127 will set device on to the last value it was when turned off.
			</Help>
    </Value>
    <Value genre="config" index="2" label="Off Time" max="127" min="0" type="byte" units="seconds" value="1">
      <Help>
				On Time sets the number of seconds the sensor stays alerted before the off event is sent.
			</Help>
    </Value>
    <Value genre="config" index="3" label="Power Saving" max="127" min="0" type="byte" units="" value="0">
      <Help>
			  	Enable/Disable power saving mode. 0 enables.
			</Help>
    </Value>
  </CommandClass>
  <!-- Basic set as report -->
  <CommandClass id="32">
    <Compatibility>
      <SetAsReport>true</SetAsReport>
    </Compatibility>
  </CommandClass>
  <!-- COMMAND_CLASS_ALARM.  This class is supported but is missing from the list reported by the SM103 -->
  <CommandClass action="add" id="113">
    <Compatibility>
      <GetSupported>false</GetSupported>
    </Compatibility>
  </CommandClass>
  <!-- COMMAND_CLASS_ASSOCIATION. Groups -->
  <CommandClass id="133">
    <Associations num_groups="1">
      <Group index="1" label="Reports" max_associations="5"/>
    </Associations>
  </CommandClass>
</Product>
To keep ID = 3 and type = 2

I used the sm103.xml file to have a model.

But it still the same ....


Anything that I missed ?
User avatar
LouiS22
Posts: 433
Joined: Friday 27 February 2015 13:21
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Budapest, Hungary
Contact:

Re: Zwave device type UNKNOWN

Post by LouiS22 »

xavierlp wrote: Monday 13 July 2020 11:02 @LouiS22 thanks for the tip

So I updated the file manufacturer_specific.xml to add this line

Code: Select all

<Product config="everspring/sm810.xml" id="0003" name="SM810 Door/Window Sensor" type="0002"/>
under

Code: Select all

<Manufacturer id="0060" name="Everspring">
then add a file sm810.xml in the dir /home/pi/domoticz/Config/everspring
like this

Code: Select all

<Product Revision="5" xmlns="https://github.com/OpenZWave/open-zwave">
  <MetaData>
    <MetaDataItem name="OzwInfoPage">http://www.openzwave.com/device-database/0060:0003:0002</MetaDataItem>
    <MetaDataItem name="ProductPic">images/everspring/sm810.png</MetaDataItem>
    <MetaDataItem id="0003" name="ZWProductPage" type="0002">https://products.z-wavealliance.org/products/2985/</MetaDataItem>
    <MetaDataItem id="0003" name="Identifier" type="0002">SM810</MetaDataItem>
    <MetaDataItem name="Name">Door/Window Sensor</MetaDataItem>
    <MetaDataItem name="ProductPage">http://www.everspring.com/SM810.aspx</MetaDataItem>
    <MetaDataItem id="0003" name="FrequencyName" type="0002">CEPT (Europe) / Russia / CEPT (Europe)</MetaDataItem>
    <MetaDataItem name="Description">The Mini Door/Window contact detector consists of two parts; a Detector and a Magnet.  They are designed to be fitted to doors or windows with the Magnet mounted on the opening part and the Detector mounted on the fixed frame. Opening the protected door/window will remove the magnetic field, trigger the Detector and generate an alarm condition, (if the system is armed).
The Door/Window Detector is a Z-Wave enabled device and is fully compatible with any Z-Wave enabled network.
If several windows need to be protected, adopt the wire according to the placement as mentioned below. This should be wired to the terminal block provided in the battery compartment in series connection. 
</MetaDataItem>
    <ChangeLog>
      <Entry author="Justin Hammond - [email protected]" date="03 May 2019" revision="3">Initial Metadata Import from Z-Wave Alliance Database - https://products.z-wavealliance.org/products/394/xml</Entry>
      <Entry author="Justin Hammond - [email protected]" date="03 May 2019" revision="4">Updated Metadata Import from Z-Wave Alliance Database - https://products.z-wavealliance.org/products/921/xml</Entry>
      <Entry author="Justin Hammond - [email protected]" date="03 May 2019" revision="5">Updated Metadata Import from Z-Wave Alliance Database - https://products.z-wavealliance.org/products/924/xml</Entry>
    </ChangeLog>
  </MetaData>
  <!-- Configuration Parameters -->
  <CommandClass id="112">
    <Value genre="config" index="1" label="On Level" max="127" min="0" type="byte" units="" value="99">
      <Help>
				Defines the level in the event sent when the sensor is triggered.  Default is 99 (full brightness for a Z-Wave dimmer). 100-127 will set device on to the last value it was when turned off.
			</Help>
    </Value>
    <Value genre="config" index="2" label="Off Time" max="127" min="0" type="byte" units="seconds" value="1">
      <Help>
				On Time sets the number of seconds the sensor stays alerted before the off event is sent.
			</Help>
    </Value>
    <Value genre="config" index="3" label="Power Saving" max="127" min="0" type="byte" units="" value="0">
      <Help>
			  	Enable/Disable power saving mode. 0 enables.
			</Help>
    </Value>
  </CommandClass>
  <!-- Basic set as report -->
  <CommandClass id="32">
    <Compatibility>
      <SetAsReport>true</SetAsReport>
    </Compatibility>
  </CommandClass>
  <!-- COMMAND_CLASS_ALARM.  This class is supported but is missing from the list reported by the SM103 -->
  <CommandClass action="add" id="113">
    <Compatibility>
      <GetSupported>false</GetSupported>
    </Compatibility>
  </CommandClass>
  <!-- COMMAND_CLASS_ASSOCIATION. Groups -->
  <CommandClass id="133">
    <Associations num_groups="1">
      <Group index="1" label="Reports" max_associations="5"/>
    </Associations>
  </CommandClass>
</Product>
To keep ID = 3 and type = 2

I used the sm103.xml file to have a model.

But it still the same ....


Anything that I missed ?
You need to remove the node, then readd.

Also, don't forget that once you update your domoticz, your contribution to the manufacturer_specific will be lost.
xavierlp
Posts: 70
Joined: Tuesday 01 November 2016 16:22
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Location: France
Contact:

Re: Zwave device type UNKNOWN

Post by xavierlp »

Perfect it's works :)

Thanks a lot
User avatar
LouiS22
Posts: 433
Joined: Friday 27 February 2015 13:21
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Budapest, Hungary
Contact:

Re: Zwave device type UNKNOWN

Post by LouiS22 »

xavierlp wrote: Monday 13 July 2020 13:34 Perfect it's works :)

Thanks a lot
Glad you solved it :)
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest