Here you can find the updated file with correct size parameters.
got it working now for 9hours and no problems
Config file for Fibaro FGMS001 zwave+ version
Moderator: leecollings
-
- Posts: 483
- Joined: Tuesday 12 August 2014 5:37
- Target OS: Raspberry Pi / ODroid
- Domoticz version: V3_8394
- Location: Rumbeke,Belgium
- Contact:
Re: Config file for Fibaro FGMS001 zwave+ version
- Attachments
-
- fgms001zw5.xml
- (17.28 KiB) Downloaded 143 times
-
- Posts: 331
- Joined: Sunday 22 February 2015 12:19
- Target OS: Linux
- Domoticz version: 2020.x
- Location: Netherlands
- Contact:
Re: Config file for Fibaro FGMS001 zwave+ version
Hi Ropske, thanks very much!
I'm now having both sensor and tamper alarm working, without Alarm Level: Secure messages in the log.
For this I had to assign the controller (1) to groups 4 (Motion Backward Compatible) and group 5 (Tamper backwards compatible), although I have a Gen 5 OpenZwave USB controller (on an RPI2).
Only 2 devices are now active: xx00 the PIR Sensor, and xx28 "General" which reacts on movement (i.e. tamper).
Further observations:
**EDIT2** Unfortunately this also introduced the simultaneous triggering of the alarm level/typ and burglar switches together with the IR-sensor, so also introducing the messages in the log again.. Not good yet...
***EDIT3** Also noticed this error during startup: "OpenZWave: Value_Added: Unhandled Label: Seismic Intensity, Unit"
I'm now having both sensor and tamper alarm working, without Alarm Level: Secure messages in the log.
For this I had to assign the controller (1) to groups 4 (Motion Backward Compatible) and group 5 (Tamper backwards compatible), although I have a Gen 5 OpenZwave USB controller (on an RPI2).
Only 2 devices are now active: xx00 the PIR Sensor, and xx28 "General" which reacts on movement (i.e. tamper).
Further observations:
- If I assign the controller to group 2 (Motion) no motion is detected.
- I assign Group 4 to the controller devices xx32 (Alarm Level) xx33 (Alarm Type) and xx35 (Burglar) become also active when movement/tamper is detected. However that also introduces the "Alarm Level" Secure" messages again.
- I have seem to have lost the Lux and Temp devices
**EDIT2** Unfortunately this also introduced the simultaneous triggering of the alarm level/typ and burglar switches together with the IR-sensor, so also introducing the messages in the log again.. Not good yet...
***EDIT3** Also noticed this error during startup: "OpenZWave: Value_Added: Unhandled Label: Seismic Intensity, Unit"
-
- Posts: 1
- Joined: Saturday 21 January 2017 13:15
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Config file for Fibaro FGMS001 zwave+ version
I'm having similar issues.
Alarm level, Alarm typ and Burglar switches are triggered simultaneous, where Alarm level and Alarm typ stay Off, while Burglar turns On and 30 seconds later Off, triggering Alarm level and Alarm typ again.
Changing "22. Tamper alarm cancellation delay" to 10 seconds brings no change, it keeps turning Off after 30 seconds. Even changing "20. Tamper sensitivity" to 0 (inactive) does not change the behavior.
Alarm level, Alarm typ and Burglar switches are triggered simultaneous, where Alarm level and Alarm typ stay Off, while Burglar turns On and 30 seconds later Off, triggering Alarm level and Alarm typ again.
Changing "22. Tamper alarm cancellation delay" to 10 seconds brings no change, it keeps turning Off after 30 seconds. Even changing "20. Tamper sensitivity" to 0 (inactive) does not change the behavior.
Who is online
Users browsing this forum: Google [Bot] and 0 guests