[SOLVED] Popp Mold detector not really included

Add-ons Bindings
,
1

Hi together,
I’m trying to included a Popp Mold detector (https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/990) and it looks like it’s working, but the XML file (var/lib/openhab2/zwave) is not being generated, and I’m not receiving any sensor data. I tried it over 10 times. What could be the issue? To my understanding this means, that the inclusion process is not complete, but I tried it many times and work up the device multiple times. I don’t know what else I can do.

  • OH 2.5.1, trying to include within Habmin. Device is <1m away.

Inclusing Logs (node32): https://1drv.ms/u/s!Ai6iyljBVlg0hjc5XM76lXq08lBG?e=9B0Ikv

2

No, it means the OpenHAB discovery process is not complete. You can delete and re-discover the Thing. It must be kept awake long enough to get fully discovered. You do NOT need to exclude and re-include into the Z-Wave network.

3

Thanks for the information. I deleted and rediscovered the thing now 3 times. Still, there is no XML file and therefore I don’t get a sensor data.

2020-02-13 16:34:44.228 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 32: Device discovered

2020-02-13 16:34:46.172 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 32: Device discovery completed

2020-02-13 16:34:46.178 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 32: Device discovery resolved to thingType zwave:popp_pope701202_00_000

2020-02-13 16:35:41.499 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Controller status changed to ONLINE.

2020-02-13 16:35:41.500 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Controller is ONLINE. Starting device initialisation.

2020-02-13 16:35:41.502 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Channel zwave:device:aeotec:node32:battery-level linked - polling started.

2020-02-13 16:35:41.503 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Updating node properties.

2020-02-13 16:35:41.506 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Updating node properties. MAN=340

2020-02-13 16:35:41.507 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Updating node properties. MAN=340. SET. Was 340

2020-02-13 16:35:41.507 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Properties synchronised

2020-02-13 16:35:41.509 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Configuration synchronised

2020-02-13 16:35:41.519 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Initialising Thing Node...

2020-02-13 16:35:41.520 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Initialising cmd channel zwave:device:aeotec:node32:sensor_binary for OnOffType

2020-02-13 16:35:41.520 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Initialising state channel zwave:device:aeotec:node32:sensor_binary for OnOffType

2020-02-13 16:35:41.521 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Initialising cmd channel zwave:device:aeotec:node32:sensor_dewpoint for DecimalType

2020-02-13 16:35:41.522 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Initialising state channel zwave:device:aeotec:node32:sensor_dewpoint for DecimalType

2020-02-13 16:35:41.522 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Initialising cmd channel zwave:device:aeotec:node32:sensor_temperature for QuantityType

2020-02-13 16:35:41.523 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Initialising state channel zwave:device:aeotec:node32:sensor_temperature for QuantityType

2020-02-13 16:35:41.523 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Initialising cmd channel zwave:device:aeotec:node32:sensor_relhumidity for DecimalType

2020-02-13 16:35:41.524 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Initialising state channel zwave:device:aeotec:node32:sensor_relhumidity for DecimalType

2020-02-13 16:35:41.524 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Initialising cmd channel zwave:device:aeotec:node32:alarm_general for OnOffType

2020-02-13 16:35:41.525 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Initialising state channel zwave:device:aeotec:node32:alarm_general for OnOffType

2020-02-13 16:35:41.525 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Initialising cmd channel zwave:device:aeotec:node32:battery-level for PercentType

2020-02-13 16:35:41.526 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Initialising state channel zwave:device:aeotec:node32:battery-level for PercentType

2020-02-13 16:35:41.526 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Polling initialised at 1800 seconds - start in 1611000 milliseconds.

2020-02-13 16:35:41.526 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 32: Device initialisation complete.
4

I cannot look right now but the zwave log viewer may help.

https://www.cd-jackson.com/index.php/openhab/zwave-log-viewer

5

You get no XML because the device is not working. You CAN get sensor data without the XML, but not if the device is not communicating.

From the log you provided here, there is no information at all - ie no communication with the device. Maybe it needs to be woken up?

1 Like
6

The logs are in the first post.

grafik
grafik1164×854 171 KB

7

Ok, I looked at the latest post logs :wink:

Please can you provide a new log - the first one does not look correct since there appears to be stuff missing.

Also, as per my previous question - have you woken the device up? I don’t see this in the log.

8

I excluded and included it again to provide a new log (node 33).
https://1drv.ms/u/s!Ai6iyljBVlg0hji6cFXMGmdcpbgR?e=ruD9UP

And yes, I have woken it up more than 10 times. Thank you.

9

I have had to do 20 or more for some devices :frowning:

10

Thanks. You were right. I took more than 20 times and the description of the device was wrong.
I had to triple click to the tamper button to wakeup the device (description says single click) and that almost 20 times. After that it’s fully included :slight_smile:

11

I had to do that with a different item. I did tell support their manual was incorrect.

EDIT: I corrected the instructions in our database linked in your first post.

1 Like
12

Just some info for someone struggling with this device.

I also bought it and had the same problems. Looks like you have to press the tamper button 3 times within 1,5 seconds really often!

this is my log to give you an indication (i almost continuesly pressed the tamper button 3 times, waited for the leds to go off and pressed it again.):

2020-09-05 11:26:58.750 [hingStatusInfoChangedEvent] - ‘zwave:device:a50060f6:node12’ changed from ONLINE to ONLINE: Node initialising: ASSOCIATIONS

2020-09-05 11:28:21.818 [hingStatusInfoChangedEvent] - ‘zwave:device:a50060f6:node12’ changed from ONLINE: Node initialising: ASSOCIATIONS to ONLINE: Node initialising: SET_WAKEUP

2020-09-05 11:28:49.891 [hingStatusInfoChangedEvent] - ‘zwave:device:a50060f6:node12’ changed from ONLINE: Node initialising: SET_WAKEUP to ONLINE: Node initialising: SET_ASSOCIATION

2020-09-05 11:29:40.268 [vent.ItemStateChangedEvent] - Hal_allowed changed from OFF to ON

2020-09-05 11:31:31.519 [hingStatusInfoChangedEvent] - ‘zwave:device:a50060f6:node12’ changed from ONLINE: Node initialising: SET_ASSOCIATION to ONLINE: Node initialising: SET_LIFELINE

2020-09-05 11:32:13.417 [hingStatusInfoChangedEvent] - ‘zwave:device:a50060f6:node12’ changed from ONLINE: Node initialising: SET_LIFELINE to ONLINE: Node initialising: GET_CONFIGURATION

2020-09-05 11:33:08.890 [vent.ItemStateChangedEvent] - Slaapkamer_vocht changed from NULL to 41

2020-09-05 11:33:08.942 [vent.ItemStateChangedEvent] - ZWaveNode012POPE701202PoppMoldDetector_SensorTemperature changed from NULL to 28.6 °C

2020-09-05 11:33:09.084 [hingStatusInfoChangedEvent] - ‘zwave:device:a50060f6:node12’ changed from ONLINE: Node initialising: GET_CONFIGURATION to ONLINE