[SOLVED] Neo Coolcam Motion Sensor with temperature sensor

Hardware Home Automation
1

Hi all,

Openhab Version
Version: 2.5.0 (Build)
Zwave binding version: 2.5.0

Problem

I’m having issue with the Neo Coolcam Motion detector.
The discovery is succesful. However, I don’t get any motion alarms at all.
I only see the temperature being reported in the logs:

2019-12-30 16:52:23.248 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@7f528085.
2019-12-30 16:53:33.041 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:VERSION)
2019-12-30 16:53:33.041 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 24: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0
2019-12-30 16:53:33.041 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
2019-12-30 16:53:33.041 [DEBUG] [e.internal.protocol.commandclass.ZWaveCommandClass] - NODE 24: Received COMMAND_CLASS_SENSOR_MULTILEVEL V0 SENSOR_MULTILEVEL_REPORT
2019-12-30 16:53:33.042 [DEBUG] [col.commandclass.ZWaveMultiLevelSensorCommandClass] - NODE 24: Sensor Type = Temperature(1), Scale = 0
2019-12-30 16:53:33.042 [DEBUG] [col.commandclass.ZWaveMultiLevelSensorCommandClass] - NODE 24: Sensor Value = 24.9
2019-12-30 16:53:33.042 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2019-12-30 16:53:33.042 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_MULTILEVEL, value=24.9
2019-12-30 16:53:33.042 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Updating channel state zwave:device:3d4427ff:node24:sensor_temperature to 24.9 °C [QuantityType]
2019-12-30 16:53:33.043 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
2019-12-30 16:53:33.043 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@29a5df56.
2019-12-30 16:54:40.800 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update received
2019-12-30 16:54:40.802 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update set binding_cmdrepollperiod to 1500 (BigDecimal)
2019-12-30 16:54:40.803 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update ignored config_11_1 to 1 (BigDecimal)
2019-12-30 16:54:40.803 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update ignored config_10_1 to 5 (BigDecimal)
2019-12-30 16:54:40.803 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update ignored group_4 to null (null)
2019-12-30 16:54:40.803 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update set group_1 to controller (String)
2019-12-30 16:54:40.803 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Association 1 consolidated to [controller]
2019-12-30 16:54:40.803 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Unknown association group 1
2019-12-30 16:54:40.804 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update ignored group_3 to null (null)
2019-12-30 16:54:40.804 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update ignored group_2 to null (null)
2019-12-30 16:54:40.804 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update set wakeup_node to null (null)
2019-12-30 16:54:40.804 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Error converting wakeup value null
2019-12-30 16:54:40.804 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update ignored config_12_1 to 1 (BigDecimal)
2019-12-30 16:54:40.804 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update ignored config_99_2 to 1000 (BigDecimal)
2019-12-30 16:54:40.805 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update set action_failed to false (Boolean)
2019-12-30 16:54:40.805 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update ignored wakeup_interval to 0 (BigDecimal)
2019-12-30 16:54:40.805 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update set action_remove to false (Boolean)
2019-12-30 16:54:40.805 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update set binding_pollperiod to 86400 (BigDecimal)
2019-12-30 16:54:40.805 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Polling initialised at 86400 seconds - start in 76118400 milliseconds.
2019-12-30 16:54:40.805 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update set action_heal to false (Boolean)
2019-12-30 16:54:40.806 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update ignored config_1_1 to 12 (BigDecimal)
2019-12-30 16:54:40.806 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update ignored config_7_2 to 180 (BigDecimal)
2019-12-30 16:54:40.806 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update ignored config_8_1 to 0 (BigDecimal)
2019-12-30 16:54:40.806 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update ignored config_9_2 to 100 (BigDecimal)
2019-12-30 16:54:40.806 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update ignored config_2_2 to 30 (BigDecimal)
2019-12-30 16:54:40.806 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update ignored config_3_1 to 255 (BigDecimal)
2019-12-30 16:54:40.807 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Configuration update ignored config_4_1 to 255 (BigDecimal)

Also, when I want to set association group 1 to controller, it’s not accepted…also in the logs above.

The “thing” looks as follow in habmin:
image

bit stuck here now…
@chris Maybe I’m doing something wrong?

/Jasper

2

That is not needed. The binding automatically figures that out and that group is already set as Lifeline in the binding database.

I have found on some of those sensors that to get them functioning properly you need to Exclude, Factory Reset, and then Include them.

I have 3 of those sensors. 1 with Temperature and 2 without.

3

Hi @Bruce_Osborne,

Ok, thanks for the clarification on the group part.

I already did factory rest, exclude / include etc. But I’ll do it once more in the order you suggest.

/Jasper

4

OK, I like using HABmin to let me know the device has been fully discovered and not stuck in REQUEST_NIF for instance. You need to wake up that device many, many times to get it completely discovered.

5

Wake up -> that’s by pressing the button during discovery right?

6

Yup. I think sometimes pressing 3 times helps.

7

Hi @Bruce_Osborne,

Good news! The device is working now. I get motion detection messages in the logs and Am able to use the alarm channel with the connected switch item! so…this part is working.
The only problem is the battery percentage…I don’t see any value on that yet (value reported is null).

I had to remove the node from the controller via my laptop with the zensys tool, cause the exclusion via paperui did not work. After that I removed the thing manually. Stopped openhab, clean-cache, restarted and did a fresh inclusion…and you were correct, had to use the wake-up couple of times before full reporting…

8

What I need to do sometimes is power the sensor off. I usually depress the button for a for seconds. I then power on and wake up a couple of times. The battery then usually shows.

9

Again…it works now…just like you said. Power off, drain remaining current…power on, wake up (2x) and battery is showing!

Thanks for the support @Bruce_Osborne!

1 Like
10

hi @Bruce_Osborne,

Just a follow up question. I see the sensor is not always waking up as expected. I was using the luminantion level to determine if I need to switch on the light when movement is detected. However, this becomes buggy since I don’t get accurate lumination levels from the sensor…do you experience the same?

thanks!

11

I do not use the lumination levels. I use the astro binding to determine dawn & dusk, etc.

1 Like
12

yes, was thinking the same…I’ll dive into that

Thanks again @Bruce_Osborne

13

I’ve created a helper switch, which toggles now on sun rise and sun set…then a rule when sensor is triggered and the helper switch has state “on” the lights will go on…

Have to see how it goes during the darker days…but it’s a start!

1 Like
14

I do something similar with an added motion sensor for my dogs when they go outside after dark. During the day the light stays off in spite of any motion.

15

Super…it’s a good period for testing if it’s ok for the house…since it’s dark days anyway…but I guess it’s fine for now…