PAT02-B not recognized

[yhd (yahoodee)]

Hi there,

my OH skills are just basic, so I hope I understood everything right.

I’m on OH 2 since 2 months via openhabian (so on stable branch as I think). I ran a tool- and system-update via openhabian-config yesterday.
I bought a Philio PAT02-B and one PAT02-A. The A is working properly, but the B is just listed as a unknown device.

I found this one in the DB. When I look at the timestamps, it seems to be just recently added to the db.

Am I right, that the db is compiled into the z-wave binding and a device lookup in my oh-installation is just read from this “offline”-db? Am I right, that the newly added device will be delivered with a new compiled unstable-branch-release and not the stable-one which I am using?

Is there any way to get this device working in my setup?

For the case I understood some basics wrong, here is my node.xml

<?xml version="1.0"?>

-<node>


-<deviceClass>

<basicDeviceClass>ROUTING_SLAVE</basicDeviceClass>

<genericDeviceClass>MULTILEVEL_SENSOR</genericDeviceClass>

<specificDeviceClass>ROUTING_SENSOR_MULTILEVEL</specificDeviceClass>

</deviceClass>

<homeId>0xccd333b0</homeId>

<nodeId>4</nodeId>

<version>4</version>

<manufacturer>0x13c</manufacturer>

<deviceId>0x20</deviceId>

<deviceType>0x2</deviceType>

<listening>false</listening>

<frequentlyListening>false</frequentlyListening>

<routing>true</routing>

<security>false</security>

<beaming>true</beaming>

<maxBaudRate>40000</maxBaudRate>


+<nodeInformationFrame>


-<supportedCommandClasses>


-<entry>

<commandClass>ASSOCIATION</commandClass>


-<associationCommandClass>

<version>2</version>

<instances>1</instances>

<versionSupported>2</versionSupported>

<maxGroups>1</maxGroups>

</associationCommandClass>

</entry>


-<entry>

<commandClass>NO_OPERATION</commandClass>


-<noOperationCommandClass>

<version>1</version>

<instances>1</instances>

<versionSupported>1</versionSupported>

</noOperationCommandClass>

</entry>


-<entry>

<commandClass>ZWAVE_PLUS_INFO</commandClass>


-<zwavePlusCommandClass>

<version>1</version>

<instances>1</instances>

<versionSupported>2</versionSupported>

<zwPlusVersion>1</zwPlusVersion>

<zwPlusRole>6</zwPlusRole>

<zwPlusNodeType>0</zwPlusNodeType>

<zwPlusDeviceType>0xd01</zwPlusDeviceType>

<zwPlusInstallerIcon>0xd01</zwPlusInstallerIcon>

<isGetSupported>true</isGetSupported>

</zwavePlusCommandClass>

</entry>


-<entry>

<commandClass>ALARM</commandClass>


-<alarmCommandClass>

<version>4</version>

<instances>1</instances>

<versionSupported>4</versionSupported>


-<alarms>


-<entry>

<alarmType>BURGLAR</alarmType>


-<alarmState>

<alarmType>BURGLAR</alarmType>


-<reportedEvents>

<int>3</int>

</reportedEvents>

<outer-class reference="../../../.."/>

</alarmState>

</entry>

</alarms>

<v1Supported>true</v1Supported>

<isGetSupported>true</isGetSupported>

</alarmCommandClass>

</entry>


-<entry>

<commandClass>BATTERY</commandClass>


-<batteryCommandClass>

<version>1</version>

<instances>1</instances>

<versionSupported>1</versionSupported>

<batteryLevel>100</batteryLevel>

<batteryLow>false</batteryLow>

<isGetSupported>true</isGetSupported>

</batteryCommandClass>

</entry>


-<entry>

<commandClass>SENSOR_BINARY</commandClass>


-<binarySensorCommandClass>

<version>2</version>

<instances>1</instances>

<versionSupported>2</versionSupported>

<isGetSupported>true</isGetSupported>


-<types>

<binarySensorType>TAMPER</binarySensorType>

</types>

</binarySensorCommandClass>

</entry>


-<entry>

<commandClass>VERSION</commandClass>


-<versionCommandClass>

<version>2</version>

<instances>1</instances>

<versionSupported>2</versionSupported>

<libraryType>LIB_SLAVE_ENHANCED</libraryType>

<protocolVersion>4.5</protocolVersion>

<applicationVersion>1.14</applicationVersion>

<hardwareVersion>1</hardwareVersion>

</versionCommandClass>

</entry>


-<entry>

<commandClass>MULTI_CMD</commandClass>


-<multiCommandCommandClass>

<version>1</version>

<instances>1</instances>

<versionSupported>1</versionSupported>

</multiCommandCommandClass>

</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>SENSOR_MULTILEVEL</commandClass>


-<multiLevelSensorCommandClass>

<version>5</version>

<instances>1</instances>

<versionSupported>5</versionSupported>


-<sensors>


-<entry>

<multilevelSensorType>RELATIVE_HUMIDITY</multilevelSensorType>


-<multilevelSensor>

<sensorType>RELATIVE_HUMIDITY</sensorType>

<initialised>true</initialised>

</multilevelSensor>

</entry>


-<entry>

<multilevelSensorType>TEMPERATURE</multilevelSensorType>


-<multilevelSensor>

<sensorType>TEMPERATURE</sensorType>

<initialised>true</initialised>

</multilevelSensor>

</entry>

</sensors>

<isGetSupported>true</isGetSupported>

</multiLevelSensorCommandClass>

</entry>


-<entry>

<commandClass>CONFIGURATION</commandClass>


-<configurationCommandClass>

<version>1</version>

<instances>1</instances>

<versionSupported>1</versionSupported>

<configParameters/>

</configurationCommandClass>

</entry>


-<entry>

<commandClass>WAKE_UP</commandClass>


-<WakeUpCommandClass>

<version>2</version>

<instances>1</instances>

<versionSupported>2</versionSupported>

<targetNodeId>1</targetNodeId>

<interval>86400</interval>

<minInterval>1800</minInterval>

<maxInterval>432000</maxInterval>

<defaultInterval>86400</defaultInterval>

<intervalStep>1800</intervalStep>

<lastWakeup>2017-03-26 12:55:21.202 UTC</lastWakeup>

<isGetSupported>true</isGetSupported>

</WakeUpCommandClass>

</entry>


-<entry>

<commandClass>MANUFACTURER_SPECIFIC</commandClass>


-<manufacturerSpecificCommandClass>

<version>1</version>

<instances>1</instances>

<versionSupported>2</versionSupported>

<initSerialNumber>false</initSerialNumber>

<deviceManufacturer>316</deviceManufacturer>

<deviceType>2</deviceType>

<deviceId>32</deviceId>

</manufacturerSpecificCommandClass>

</entry>


-<entry>

<commandClass>BASIC</commandClass>


-<basicCommandClass>

<version>1</version>

<instances>1</instances>

<versionSupported>1</versionSupported>

<isGetSupported>true</isGetSupported>

</basicCommandClass>

</entry>


-<entry>

<commandClass>FIRMWARE_UPDATE_MD</commandClass>


-<firmwareUpdateCommandClass>

<version>1</version>

<instances>1</instances>

<versionSupported>2</versionSupported>

</firmwareUpdateCommandClass>

</entry>


-<entry>

<commandClass>DEVICE_RESET_LOCALLY</commandClass>


-<deviceResetLocallyCommandClass>

<version>1</version>

<instances>1</instances>

<versionSupported>1</versionSupported>

</deviceResetLocallyCommandClass>

</entry>


-<entry>

<commandClass>ASSOCIATION_GROUP_INFO</commandClass>


-<associationGroupInfoCommandClass>

<version>1</version>

<instances>1</instances>

<versionSupported>1</versionSupported>


-<autoSubscribeGroups>

<int>1</int>

</autoSubscribeGroups>

</associationGroupInfoCommandClass>

</entry>

</supportedCommandClasses>

<securedCommandClasses/>


-<associationGroups>


-<entry>

<int>1</int>


-<associationGroup>

<index>1</index>

<name>LifeLine</name>

<profile1>0x0</profile1>

<profile2>0x1</profile2>


-<commands>

<commandClass>ALARM</commandClass>

<commandClass>BATTERY</commandClass>

<commandClass>SENSOR_BINARY</commandClass>

<commandClass>DEVICE_RESET_LOCALLY</commandClass>

<commandClass>MULTI_CMD</commandClass>

<commandClass>SENSOR_MULTILEVEL</commandClass>

</commands>

<associations/>

</associationGroup>

</entry>

</associationGroups>


-<nodeNeighbors>

<int>1</int>

<int>3</int>

</nodeNeighbors>

<lastSent>2017-03-26 12:55:22.700 UTC</lastSent>

<lastReceived>2017-03-26 12:55:22.743 UTC</lastReceived>

</node>

Thank in advance

[sihui]

@yhd

Is there any way to get this device working in my setup?

Either switch to unstable (recommended) or try this tricky thing:

Trouble with Fibaro metered smart plug

Yes, but it is a bit tricky: uninstall the zwave binding, download the snapshot, put it in your addons folder, start the binding through karaf. If you get an error a dependency package is missing, install it (in this case, sometimes the serial transport is missing):

[Tomibeck]

Hey,

i had the same issue updated to the latest unstable and voila device is recognised. However i still have some trouble as it only sends one value forever. But this is likely a configuration issue with the Device itself

Thomas