Z-WAVE POPE700168 POPP Rain-Sensor - unknown device

Add-ons Bindings
1

I’ve installed battery Z-WAVE POPE700168 POPP Rain-Sensor.
Unfortunately device is not recogonized. I have information:" Z-Wave Node 013 Unknown Device"
I have Openhab 2.5.0 but z-wave bindings 2.5.1 .

I don’t know how to properly initialize this thing. It is my first battery z-wave unit. Maybe I need to do some additional activities to have this thing properly recognized. Could you help me?
Below you have some informations from the logs:

2020-07-08 07:41:21.985 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model ‘network_96de1d4f_node_13.things’ is either empty or cannot be parsed correctly!
2020-07-08 07:41:21.997 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model ‘network_96de1d4f__node_13.things’ is either empty or cannot be parsed correctly!
2020-07-08 07:47:09.587 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model ‘network_96de1d4f_node_13.things’
2020-07-08 07:47:09.614 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model ‘network_96de1d4f__node_13.things’
2020-07-08 07:47:16.176 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model ‘network_96de1d4f_node_13.things’ is either empty or cannot be parsed correctly!
2020-07-08 07:47:16.178 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model ‘network_96de1d4f__node_13.things’ is either empty or cannot be parsed correctly!
2020-07-08 12:07:52.461 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:96de1d4f:node11’ to inbox.
2020-07-08 12:07:52.465 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:96de1d4f:node12’ to inbox.
2020-07-08 12:07:52.470 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:96de1d4f:node13’ to inbox.
2020-07-08 12:27:58.951 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:96de1d4f:node13’ to inbox.
2020-07-08 12:07:52.469 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-07-08 12:27:58.949 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 13: Device discovery could not resolve to a thingType! Manufacturer data not known.
2020-07-08 12:15:08.884 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node13’ changed from UNINITIALIZED to INITIALIZING
2020-07-08 12:15:08.910 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node13’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2020-07-08 12:15:08.925 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node13’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2020-07-08 12:15:08.932 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:96de1d4f:node13’ has been updated.
2020-07-08 12:15:08.936 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:96de1d4f:node13’ has been updated.
2020-07-08 12:15:08.984 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:96de1d4f:node13’ has been updated.
2020-07-08 12:27:31.100 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node13’ changed from ONLINE to UNINITIALIZED
2020-07-08 12:27:31.140 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node13’ changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2020-07-08 12:27:58.951 [home.event.InboxAddedEvent] - Discovery Result with UID ‘zwave:device:96de1d4f:node13’ has been added.
2020-07-08 07:47:33.837 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node10’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2020-07-08 07:47:33.841 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node8’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2020-07-08 07:47:40.642 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node5’ changed from ONLINE to ONLINE: Node initialising: PING
2020-07-08 07:47:40.650 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node6’ changed from ONLINE to ONLINE: Node initialising: PING
2020-07-08 07:47:40.652 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node8’ changed from ONLINE to ONLINE: Node initialising: PING
2020-07-08 07:47:40.654 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node7’ changed from ONLINE to ONLINE: Node initialising: PING
2020-07-08 07:47:40.661 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node10’ changed from ONLINE to ONLINE: Node initialising: PING
2020-07-08 07:47:40.674 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node4’ changed from ONLINE to ONLINE: Node initialising: PING
2020-07-08 07:47:40.684 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node9’ changed from ONLINE to ONLINE: Node initialising: PING
2020-07-08 07:51:59.664 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node5’ changed from ONLINE: Node initialising: PING to ONLINE: Node initialising: REQUEST_NIF
2020-07-08 07:52:41.247 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node5’ changed from ONLINE: Node initialising: REQUEST_NIF to ONLINE
2020-07-08 07:52:48.094 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node6’ changed from ONLINE: Node initialising: PING to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
2020-07-08 07:52:48.095 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node6’ changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE: Node initialising: REQUEST_NIF
2020-07-08 07:53:36.173 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node8’ changed from ONLINE: Node initialising: PING to ONLINE: Node initialising: REQUEST_NIF
2020-07-08 07:53:50.174 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node7’ changed from ONLINE: Node initialising: PING to ONLINE: Node initialising: REQUEST_NIF
2020-07-08 07:54:49.173 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node10’ changed from ONLINE: Node initialising: PING to ONLINE: Node initialising: REQUEST_NIF
2020-07-08 07:55:36.592 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node7’ changed from ONLINE: Node initialising: REQUEST_NIF to ONLINE
2020-07-08 07:56:09.263 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node4’ changed from ONLINE: Node initialising: PING to ONLINE: Node initialising: REQUEST_NIF
2020-07-08 07:56:10.473 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node10’ changed from ONLINE: Node initialising: REQUEST_NIF to ONLINE
2020-07-08 07:56:10.573 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node4’ changed from ONLINE: Node initialising: REQUEST_NIF to ONLINE
2020-07-08 07:56:10.593 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node9’ changed from ONLINE: Node initialising: PING to ONLINE: Node initialising: REQUEST_NIF
2020-07-08 07:59:14.706 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node9’ changed from ONLINE: Node initialising: REQUEST_NIF to ONLINE
2020-07-08 08:23:01.459 [hingStatusInfoChangedEvent] - ‘zwave:device:96de1d4f:node6’ changed from ONLINE: Node initialising: REQUEST_NIF to ONLINE

2

First thing would be to check the ZWAVE device database
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devices

The log says “manufacturer data not known”

However, I checked and its in there so that’s as far as my knowledge goes :0)

Then it looks like the controller goes offline and finally it says your device is not communicating with the controller all strange. I’ve always found with battery devices keeping them awake is a challenge, usually if they have a tamper switch having this in tamper keeps the device awake.

Hopefully Chris will have a chance to look.

3

Your device is in the database:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/588

You need to wake ist up a couple of times (see your device manual)

From the filename naming this is usually an xml file in your userdata/zwave folder. For what reason did you create a things file? Use the autodiscovery feature of openHAB2.

1 Like
4

I checked it before purchasing of the Popp Rain Sensor to have no problems with including :slight_smile:
According to the manual, I push button once to wake up unit. Without any success.
Below you have informations from manual regarding waking up:

Communication to a Sleeping device (Wakeup)
This device is battery operated and turned into deep sleep state most of the time to save battery life time. Communication with the device is limited. In order
to communicate with the device, a static controller C is needed in the network. This controller will maintain a mailbox for the battery operated devices and
store commands that can not be received during deep sleep state. Without such a controller, communication may become impossible and/or the battery life
time is significantly decreased.
This device will wakeup regularly and announce the wakeup state by sending out a so called Wakeup Notification. The controller can then empty the
mailbox. Therefore, the device needs to be configured with the desired wakeup interval and the node ID of the controller. If the device was included by a
static controller this controller will usually perform all necessary configurations. The wakeup interval is a tradeoff between maximal battery life time and the
desired responses of the device. To wakeup the device please perform the following action: Push the Z-Wave button once

Device was not properly discovered, so I was trying to do it through the things file. This file is already deleted but information was written in the logs.

Do you think that problem is only with waking up device in the right time during autodiscovery or can be in the other place? I can spend more time on discovery and waking up device but is there any chance for a success?
I have OpenHab working in container on QNAP but I don’t think that there is a problem. Rain Sensor is my first battery device, maybe there is different procedure for this kind of devices.

5

Without debug logs from the device as explained in the binding documentation we cannot know. Only your system knows what is happening.

6

I will turn on debug logs and I will send some more informations but because of short holidays I will do it after 1 week.

7

Hi! I just included my old POPP Z-Rain in openHAB 2.5.7 with zwave binding 2.5.7, but the device just shows up as “Z-Wave Node 155 - Unknown device”. I’ve woken it up around 20 times and it does indeed send rain info but is still unknown. The device ID and manufacturer ID is missing. Any help would be appreciated :slight_smile:

Log is attached.

Thanks,
Andreas
node155.txt (301.5 KB)

8

Please post your xml. Your device looks fine in the database:

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/588#

9

Now attached. Thanks for having a look :slight_smile:

network_efa242ea__node_155.xml (10.1 KB)

10

Here is your problem:

<manufacturer>0x7fffffff</manufacturer>
  <deviceId>0x7fffffff</deviceId>

The device did not report its properties yet.
You need to wake it up more often :slight_smile:
If that does not work exclude, reset the device, include it again. Make sure it has good batteries.

1 Like
11

Success! I excluded, reset and included again and this time it worked after only 3-4 wake-ups. The only thing I did different from last time is that I stayed within decimeters from the controller while waking it up, compared to previously a few meters away. Don’t know if that can make a difference though.

Thanks @sihui

1 Like
12

Now moved to -:

:slight_smile:

1 Like
13

Did I miss an anouncement?

14

Possibly - I thought you were also on the private chat we had on the database, but also this -:

15

Are we exporting from the new one yet though?

16

Okay, but I can’t find a “migration completed” post so I thought transit is still going on …

1 Like
17

Sorry - my bad. I’ll add a post to the above.

1 Like
18

Finally I started again to discover this unit with waking up device. After many tries, finally unit was properly discovered and I can use it.
It is not comfortable to add this kind of devices but possible.