Major issues with Fibaro Motion Sensor

For Z-Wave related questions in Domoticz

Moderator: leecollings

dhanjel
Posts: 102
Joined: Tuesday 05 August 2014 22:16
Target OS: Linux
Domoticz version: 3.5146
Location: Sweden
Contact:

Re: Major issues with Fibaro Motion Sensor

Post by dhanjel »

Might be, but I don't manage to update the firmware on that stupid stick :)

Sent from my Nexus 6P using Tapatalk
kman
Posts: 78
Joined: Wednesday 30 September 2015 19:33
Target OS: Linux
Domoticz version:
Contact:

Re: Major issues with Fibaro Motion Sensor

Post by kman »

(OK - at least it is reassuring that someone is also talking of this issue - lot more here viewtopic.php?f=6&t=12159)

So, I think it is consistent then irrespective of the domoticz and OZW version you are on - you/we are seeing issues with Fibaro Motion & Door version 3.2 with Aeon ZSTICK GEN5. [I have had no issues with previous version of Fibaro Motion(v2.7) & Door(v2.5) ]

Has anyone raised this issue with OpenZwave folks?

---cutting paste some of my questions & comments from the above post-----
Honestly hope someone takes a note and responds! I can now quite consistently prove that we do indeed have a Domoticz & OpenZwave show-stopper, with the below combination.

Set-up Details:
¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬
+ You need to use (1) AEON-ZSTICK-GEN5 and (2) latest version of Fibaro Zwave Plus sensors, specifically the Motion & Door, which are version 3.2. (3) Create a network using the TKB-TZ88e
+ Please note, earlier version of Fibaro Motion & Door which are 2.x are Zwave-Only and they work perfectly fine - with the exact same setup.
+ Few more of the setup details:-
* domoticz v3.8483
* OZW v1.4.1
* 2 - TKB TZ88e (zwave-Only)
* AEON-ZSTICK-GEN5 (zwave-Plus)
* 3 - Fibaro Motion v3.2 (zwave-plus sensors)
* 3 - Fibaro Door/Window v3.2 (zwave-plus sensors)
+ Please note: Fibaro Motion v3.2, and Fibaro Door/Window v3.2 - Are ZwavePlus Sensors.
+ Also, please note, I have create multiple set-ups with huge number of Fibaro motion and door with the earlier version, with exactly same above setup except with the earlier version of OZW 1.3492. But moved to 1.4.1 as it seemed that for Fibaro Motion & Door v3.2 required some additional parameters - such as Alarm Level, Alarm Type, Burglar.
¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬

Problems seen:
---------------------
(even if you choose to ignore the functionality issues 1 to 4 as merely consistency issues as the back-ward compatibility(group4) works; issue 5 really a show-stopper)
1. with v3.2 of Fibaro Motion - with controller added to Group-1 - you don't receive "Sensor" value when motion is detected. You see 'Burglar'. Which is inconsistent.
2. Now, you add the controller to Group 4 of Motion sensor, which is supposed to function in Back-ward compatibility mode. You see the Motion detected appearing as "Sensor" value.
3. Similar observations with Fibaro Door/Window v3.2 - when the controller is added to Group-1 you don't receive "Sensor" value when magnet is moved in open/close positions.
4. Add the controller to Group 4 of Fibaro Door/Window v3.2 and you see "Sensor" value appearing during open/close.
5. Leave the network running over-night(approx 16 hours) with TKB TZ-88e. You will find TKB's drop out - but also all along the fibaro motion and door don't find route via the TKB's. Not sure if this a problem because of the TKB's being Zwave-Only?

¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬
Questions:
1. Has anyone else used AEON-ZSTICK-GEN5 with Fibaro Motion v3.2 and Door/Window v3.2? If yes, what is the version of OZW required?
2. Should I use a different version of TKB as I am using zwave-plus sensors in the network? (TKB TZ88e with my other zwave-only sensors, including fibaro motion & door v2.x)
DanM
Posts: 79
Joined: Thursday 23 October 2014 22:41
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Major issues with Fibaro Motion Sensor

Post by DanM »

I have a very smilar setup to yourself. I even have the 3.2 door sensor (although still in its box so I was unaware of the problems). I do however have 3 of the GEN5 TKBs and none of the older ones and I still see the problems.

Could you clarify what you mean by adding to different groups? For the most part I have ignored groups in Z-Wave and wasnt aware that adding to different groups might exhibit different behaviour?
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest