BeNext door sensor not working

Bemie · Post by **Bemie** » Thursday 23 July 2015 16:44

(Just moved to this topic from Z-Wave discussion)

Hi,
I have bought http://www.planete-domotique.com/notice ... OORS_M.pdf, the BeNext door sensor.
They are somehow recognized as hardware and the procedure for inclusion worked smoothly (from the hardware tab I get this (as I bought two of them):),

016 (0x10) Unknown BeNext Door Sensor 2015-07-22 20:17:12 No [Heal node]
015 (0x0f) Unknown BeNext Door Sensor 2015-07-22 20:17:12 No [Heal node]

but they are not recognized by Domoticz. I tried learning Domoticz the sensor but without any succes. It simply does not see this wonderful sensor. Please help me out. Also in the logging I somtimes see the tamper switch come by). I am at my end of the rope here (an old guy learning domotica), what could I do? Any help is much appreaciated
Kind regards,
Bemie

heggink · Post by **heggink** » Wednesday 25 November 2015 9:44

Same issue here: I ordered 2 of these to replace KAKU sensors that send too many messages on trigger. I can include them but I get a timeout within a few minutes and they do not get recognised again even though the led on the device gives a blip. All subdevices (temp, alarm type and level and the switch) are recognised...
Rob: any thoughts?

heggink · Post by **heggink** » Wednesday 25 November 2015 23:26

Noticed that the devices timeout immediately after being added"

2015-11-25 23:16:08.013 OpenZWave: New Node added. HomeID: 3663738776, NodeID: 30 (0x1e)
2015-11-25 23:16:08.014 OpenZWave: Value_Added: Node: 30 (0x1e), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 0
2015-11-25 23:16:08.014 (AEOTEC) Lighting 2 (Unknown)
2015-11-25 23:16:08.019 OpenZWave: Value_Added: Node: 30 (0x1e), CommandClass: ALARM, Label: Alarm Type, Instance: 1
2015-11-25 23:16:08.019 (AEOTEC) Lighting 2 (Unknown)
2015-11-25 23:16:08.024 OpenZWave: Value_Added: Node: 30 (0x1e), CommandClass: ALARM, Label: Alarm Level, Instance: 1
2015-11-25 23:16:08.024 (AEOTEC) Lighting 2 (Unknown)
2015-11-25 23:16:08.028 OpenZWave: Value_Added: Node: 30 (0x1e), CommandClass: BATTERY, Label: Battery Level, Instance: 1
2015-11-25 23:16:08.550 (AEOTEC) Lighting 2 (Sensor)
2015-11-25 23:16:08.681 OpenZWave: Value_Added: Node: 30 (0x1e), CommandClass: SENSOR MULTILEVEL, Label: Temperature, Instance: 1
2015-11-25 23:16:08.681 (AEOTEC) Temp (Unknown)
2015-11-25 23:16:18.686 OpenZWave: Received timeout notification from HomeID: 3663738776, NodeID: 30 (0x1e)
2015-11-25 23:16:24.015 New sensors allowed for 5 minutes...
2015-11-25 23:16:24.017 OpenZWave: Node Include command initiated...
2015-11-25 23:16:27.519 Hardware Monitor: Fetching data (System sensors)
2015-11-25 23:16:32.743 OpenZWave: New Node added. HomeID: 3663738776, NodeID: 31 (0x1f)
2015-11-25 23:16:32.743 OpenZWave: Value_Added: Node: 31 (0x1f), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 0
2015-11-25 23:16:32.744 (AEOTEC) Lighting 2 (Unknown)
2015-11-25 23:16:32.749 OpenZWave: Value_Added: Node: 31 (0x1f), CommandClass: ALARM, Label: Alarm Type, Instance: 1
2015-11-25 23:16:32.749 (AEOTEC) Lighting 2 (Unknown)
2015-11-25 23:16:32.754 OpenZWave: Value_Added: Node: 31 (0x1f), CommandClass: ALARM, Label: Alarm Level, Instance: 1
2015-11-25 23:16:32.754 (AEOTEC) Lighting 2 (Unknown)
2015-11-25 23:16:32.759 OpenZWave: Value_Added: Node: 31 (0x1f), CommandClass: BATTERY, Label: Battery Level, Instance: 1
2015-11-25 23:16:33.251 (AEOTEC) Lighting 2 (Sensor)
2015-11-25 23:16:33.381 OpenZWave: Value_Added: Node: 31 (0x1f), CommandClass: SENSOR MULTILEVEL, Label: Temperature, Instance: 1
2015-11-25 23:16:33.382 (AEOTEC) Temp (Unknown)
2015-11-25 23:16:43.386 OpenZWave: Received timeout notification from HomeID: 3663738776, NodeID: 31 (0x1f)

That's not supposed to happen, right?

H

gizmocuz · Post by **gizmocuz** » Thursday 26 November 2015 9:24

Could you also post the log from openzwave?

You can enable 'debug' if you select the controller node, and from the settings enable it.
Do not forget to turn this off...!

in the 'Config' folder there should now be a log file called OZW_Log.txt

groetg · Post by **groetg** » Sunday 24 January 2016 10:46

same issue here, is there a solution??

heggink · Post by **heggink** » Sunday 24 January 2016 10:57

should have been fixed. check if it's included in the controller group.

groetg · Post by **groetg** » Sunday 24 January 2016 11:11

If the controler id (1) is in the groups of the doorsensor, you mean?

heggink · Post by **heggink** » Sunday 24 January 2016 21:58

I think so. When I installed them, they were not in group 1. adding them manually did the trick. There is a thread on this in the openzwave forum as well (https://groups.google.com/forum/#!searc ... cCPX2vBwAJ).

groetg · Post by **groetg** » Tuesday 26 January 2016 7:45

It worked, thanx!

heggink · Post by **heggink** » Tuesday 26 January 2016 8:17

great

.

Piet · Post by **Piet** » Saturday 13 February 2016 23:42

Using Raspberry Pi with Z-wave plus stick, 3 Fibaro door sensors and 3 Fibaro switches.
Door sensors did work fine for 2 months or more, 2 stopped sending a signal when the door opens
(2 weeks and 1 week ago)
the 1 left is still working ok. Added a Fibaro repeater but this did not help.
The sensors are visible in node maintenance and Group And network.
in wave control Panel the 2 sensors not sending a signal have the value Off, think the doors always appear to be closed
also when open. Feels as if it responds but does not send the open signal

What can I do to get this working again.

BeNext door sensor not working

BeNext door sensor not working

Re: BeNext door sensor not working

Re: BeNext door sensor not working

Re: BeNext door sensor not working

Re: BeNext door sensor not working

Re: BeNext door sensor not working

Re: BeNext door sensor not working

Re: BeNext door sensor not working

Re: BeNext door sensor not working

Re: BeNext door sensor not working

Fibaro door sensor not working

Who is online