FGMS-001 ZWave plus

[Tamagnun]

Hi Tamagnun,
Any luck with trying with GEN5 controller? i.e. by only including the controller "only" to Group 2, do you see any Sensor value?

thanks.

Hi kman,

I've repeated the group association to group 1, 4 and 5 with the Gen5 controller, the behaviour is exactly the same tham using Gen3 controller.

I'm sorry but I haven't tested the motion reporting with group 2 only associated, I'll test it in the next days.

Regards

[kman]

Hi Tamagnun,
Any luck with trying with GEN5 controller? i.e. by only including the controller "only" to Group 2, do you see any Sensor value?

thanks.

Hi kman,

I've repeated the group association to group 1, 4 and 5 with the Gen5 controller, the behaviour is exactly the same tham using Gen3 controller.

I'm sorry but I haven't tested the motion reporting with group 2 only associated, I'll test it in the next days.

Regards

Super! thanks.

[kman]

In regards to this issue, jorgitold is right!; we may simply be unware of all the issues without domoticz being fully updated to support this new device.

Would be really good to get some pointers, on what all needs to be updated in Domoticz in order to support the FGMS-001 ZW5 EU v3.2.

Meanwhile, to address the 'no motion issue in group 2' - I have raised a github bug.

thanks.

[Gravityz]

not sure what your problems with this modules are.

i have the zw+ version with aotec gen5 stick
i only have the controller associated with group1(the rest is empty)
temp reading ok
lux reading ok

when motion de devices react as follows
00=no reaction, probably because no groups are associated
28=no raction,probably because no groups are associated
32=no reaction,probably because no groups are associated
33= no reaction,probably because no groups are associated
35= reaction, this is my pir sensor which i use to trigger events


when i put a light module in group 2 and trigger motion that light switches on(so association group 2 works

did you include the module right?
i mean, you are probalby using the correct config file but did you clean out the zwcfg_xxxx.xml file


stop zwave (goto setup-hardware, select zwave stick unselect enabled and press update)
make sure you got the right config file
make sure the id of the module 0x1001 0x801) is mapped to that config file
edit zwcfg_xxxx.xml and delete ONLY the node entry which belongs to the fgms module

start zwave (goto setup-hardware, select zwave stick select enabled and press update)

i attached my file

fgmszw5.xml

(16.29 KiB) Downloaded 108 times

[kman]

Hi Gravityz,
Thanks for responding.

Issues noticed are:
1.When I add the Controller to Only 'Group1'.
1.1 When motion is detected, there is no 'Sensor Value'(='00') being reported.
1.2 Instead you see 'Burglar'(='35') being reported, along with 'Alarm Value'(='32'), and 'Alarm Type'(='33') being reported every time a motion is detected. It looks something like this in the logs:

2017-01-06 23:21:55.124 (aeon-GEN5-USB) Lighting 2 (Alarm Type)
2017-01-06 23:21:55.129 OpenZWave: Alarm Level: Secure
2017-01-06 23:21:55.129 (aeon-GEN5-USB) Lighting 2 (Alarm Level)
2017-01-06 23:21:55.133 (aeon-GEN5-USB) Lighting 2 (Burglar)

¬¬¬¬
So, are you saying in your case when motion is detected - you don't see AL & AT, and instead you see only 'Burglar'? Please confirm.

If yes, can you please share the values that you have used to configure.

Also, I have tried a few configuration files(from within this forum and other similar issues reported on FGMS ZW5), the latest one which I am using is from ../open-zwave-master/config/fibaro. If you don't mind me asking, the fgmszw5.xml that you have shared, is this something which you created?


2. Now, when the controller is added to 'Group2' - you don't see any 'Sensor Value' being reported or any motion being reported for that matter, but in OZW_logs you can see it reporting motion i.e. 255 when motion, and 0 after motion stops - but this deoesn't get seen in Domoticz. Not entirely sure if Group2 is meant for only 'associated devices'. So, basically 'Sensor Value'(=00) doesn't get reported anywhere else other than Group4 which is meant for backward compatibility with zwave controllers. So, the question is what is the correct behaviour? Or as you are hinting, Group 2 is exclusively for associated devices (--controller shouldn't be included?), and hence the light module that you have included works fine. Meaning, 'burglar' that gets reported in Group1, is only motion value to be used for motion detection?

Cutting and pasting the text from the Manual(just for reference):
The Motion Sensor provides the association of four groups:
1st association group – “Lifeline” reports the device status and allows
for assigning single device only (main controller by default).
2nd association group – “Motion” is assigned to the motion sensor
- sends motion detection and alarm cancellation frames to the associated
devices.
3rd association group – “Tamper” is assigned to the tamper - sends
tamper alarm and alarm cancellation frames to the associated devices.
4th association group – “Motion BC” is assigned to the motion sensor
- sends motion detection and alarm cancellation frames to the
associated devices. Provides backward compatibility with controllers
not supporting Z-Wave+ protocol.
5th association group – “Tamper BC” is assigned to the tamper -
sends tamper alarm and alarm cancellation frames to the associated
devices. Provides backward

[kman]

@Gravityz - can you please confirm your version of domoticz and OZW.

thanks.

[Gravityz]

i have version 6332 and ozw v1.4.2347

ok i tested something
when i look at the log i indeed see this when motion is activated

Code: Select all

 2017-01-19 15:00:29.383 OpenZWave: Alarm Level: Secure
2017-01-19 15:00:29.384 (Aeonlabs Z-wave stick Gen5) Light/Switch (Alarm Type)
2017-01-19 15:00:29.387 (Aeonlabs Z-wave stick Gen5) Light/Switch (Alarm Level)
2017-01-19 15:00:29.390 (Aeonlabs Z-wave stick Gen5) Light/Switch (PIR sensor) 

i however looked into the devices and al those devices stay of, exept motion(35) which switches on so i can use this as a trigger.

where do you see them change value, in a script?

if i put a light(fgwpf plug) into groep 2 it switches on when there is motion
if i put a light(fgwpf plug) into group 5 Tamper BC the light does not switch on but the lights on the plug show the alarm blink)

i made my own zw5 version for the gms-001 because it was not available .
the one on github is fine to but contains a couple of flaws so you might want to try mine.

[kman]

Code: Select all

 2017-01-19 15:00:29.383 OpenZWave: Alarm Level: Secure
2017-01-19 15:00:29.384 (Aeonlabs Z-wave stick Gen5) Light/Switch (Alarm Type)
2017-01-19 15:00:29.387 (Aeonlabs Z-wave stick Gen5) Light/Switch (Alarm Level)
2017-01-19 15:00:29.390 (Aeonlabs Z-wave stick Gen5) Light/Switch (PIR sensor)

@Gravityz: Thanks - And I presume it appears as "PIR sensor" because you have named Burglar='35' as 'PIR sensor'?

1. So, why do you think AL, AT get triggered for every motion? (do you think it should be looked upon as 'as per design' or - is it an issue?)
2. On Group2: I suppose you have added a lighting device? if you add the controller, I suppose you don't detect any motion. This could be debatable, from the manual you get a sense it is for only associated devices. Would be nice if someone could confirm.

>> where do you see them change value, in a script?
In my case, I see it in the log itself as I have a HTTP_post for each of those devices. But I guess, otherwise, you would check against the device as you do!

Thanks, I will try with your fgmszw5.xml. In regards to the current xml from github, I am noticing that I am unable to change a few values -- ex: "2. Motion detection - blind time: 3", and many more ex:80(to 'led inactive'), 89(tamper led inactive) , not sure if there many more as I haven't tried all of them.

[Gravityz]

i think those work with my setup
i have put blind time at 15(which it was at the old non zwave+ version)
this gives you 15+1/2=8 seconds

3 will give you 2 seconds and will drain the battery.
just make sure everything in the new config is put in the zwcfg_xxxx file because the old non zwave5 file was wrong.

sometimes variables do not work because there is a fault in thre config file.
if you use my config file you are sure everything is ok(check the default variables because i changed some)

regarding the AT en AL triggered at once.

Fibaro is made for Fibaro so with a fibaro controller i believe they will work perfectly.
With domoticz not everything is working like it should
the seismic sensor for example is used for tamper(which works) but also as seismic notifier(which does not work in domoticz.

The same with the alarm secure. why is is sending out that message. probably because it pushes that message to every other zwave module which can act on it(door sensor perhaps)

[Tamagnun]

@kman: test results with Group 1 and Group 2 associated to the AeonLabs Gen5 controller:

temp reading ok
lux reading ok
00=no reaction in case of motion or tapemring detection
28=no reaction in case of motion or tampering detection
32=goes always OFF on tampering detection, never goes ON, not updated on motion
33=goes always OFF on tampering detection, never goes ON, not updated on motion
35=reacts to tampering (ON/OFF), not updated on motion

Anyway, because I control all the automated operation via LUA script and not with direct associations, I prefer to keep associated groups 1, 4 and 5, monitoring device 00 and 28.

Bye

[dutchdevil83]

i can confirm that since last update i also have issues with the motion sensor. Sensor and Burglar stays on and is not turning off. Seems like the changes in the zwave xml file is messing things up in domoticz. Using razberry z-wave controller. I have the same sensor working on the "old" zwave xml file and this one is working fine.

[DomoHouse]

I am also having similar issues with one of my three FGMS-001 ZW5 motion sensors. The one I bought in August 2016 does not work properly when using the fibaro/fgmszw5.xml configuration file. It continues reporting motion even when there is no motion detected. What's really weird (to me) is that the LED indicator on the sensor also indicates there's motion. The FGMS-001 ZW5 modules that I bought very recently are working fine with the fgmszw5.xml configuration file. According to the box in which my motion sensors were shipped, all three are version EU V3.2. I am starting to believe that there are differences though. I excluded the 'older' sensor and included it again using the fgms.xml file and now it is working fine.

I don't have a solution but I wanted to share my experience as it may be useful to you.

[dutchdevil83]

I am also having similar issues with one of my three FGMS-001 ZW5 motion sensors. The one I bought in August 2016 does not work properly when using the fibaro/fgmszw5.xml configuration file. It continues reporting motion even when there is no motion detected. What's really weird (to me) is that the LED indicator on the sensor also indicates there's motion. The FGMS-001 ZW5 modules that I bought very recently are working fine with the fgmszw5.xml configuration file. According to the box in which my motion sensors were shipped, all three are version EU V3.2. I am starting to believe that there are differences though. I excluded the 'older' sensor and included it again using the fgms.xml file and now it is working fine.

I don't have a solution but I wanted to share my experience as it may be useful to you.

Can you explain how I can reactivate the Old xml file that was working with my sensor? Or has anyone found a Solution to edit the new file so its working again?


Verzonden vanaf mijn iPhone met Tapatalk

[Gravityz]

this should not make a difference since you already included the device and new config files are only read agai when you exclude/include a device or remove it from the zwcfg_xxx.xml file

i have had similar experiece after upgrading with other devices(KwH meters not running anymore)

what might help is go to setup, select Zwave, click disable en then update
after that select zwave, select enable and click update again

you basically stop and start zwave again.
this helped me a lot with problems not solved even after a reboot.

[dutchdevil83]

thank you for your reply, i found this with google: https://community.home-assistant.io/t/h ... 01/3135/26

look for the reaction of "hdunst" i think the problem with the new config is that domoticz is look for the basic command for motion but that this has been changed to a binary report which domoticz doesn`t understand.

Probaly setting group associations 1,4 en 5 to the same assocation as the controller will fix things for now... Going to give this a try for now. Still hope that domoticz can support binary reports because this seems to be more secure

[Gravityz]

just tested with controller(1) added to group 1, 4 and 5

with motion
35 motion sensor goes on and off after a period
00 sensor goes on and off after a period

with tamper
28 general goes on and off after a period

32 alarm level does not react
33 alarm type does not react

for me everything works like it should temp, lux, motion, tamper.

so what should be working besides those devices

[dutchdevil83]

just tested with controller(1) added to group 1, 4 and 5

with motion
35 motion sensor goes on and off after a period
00 sensor goes on and off after a period

with tamper
28 general goes on and off after a period

32 alarm level does not react
33 alarm type does not react

for me everything works like it should temp, lux, motion, tamper.

so what should be working besides those devices

Group 1, 4 and 5 activated means that sensor is running in backward compabality mode normally it should be running with group 1,2 and 3 activated. Only it seems that Domoticz doesn't support binary sensor reports yet.

[Gravityz]

ok i understand.
do not know what ptoblem that causes.

other question

i see with other modules that sometimes commandclass 32 is mapped to commandclass 37

could we not do the same here and map commandclass 32 to 48 or other commandclass so commands are relayed
maybee this will solve the problem people are having.

update" tried mapping 48 but that made no difference but i believe this is the key to solving this"

Code: Select all

            <CommandClass id="48" name="COMMAND_CLASS_SENSOR_BINARY" version="1" request_flags="4" innif="true">
                <Instance index="1" />
                <Value type="bool" genre="user" instance="1" index="0" label="Sensor" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="False" />
                <SensorMap index="0" type="37" />
                <SensorMap index="0" type="45" />
                <SensorMap index="0" type="210" />
                <SensorMap index="0" type="218" />
            </CommandClass>
            <CommandClass id="49" name="COMMAND_CLASS_SENSOR_MULTILEVEL" version="8" innif="true">
                <Instance index="1" />
                <Value type="decimal" genre="user" instance="1" index="1" label="Temperature" units="C" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="22.9" />
                <Value type="decimal" genre="user" instance="1" index="3" label="Luminance" units="lux" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="6580" />
                <Value type="decimal" genre="user" instance="1" index="25" label="Seismic Intensity" units="mercalli" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="0.0" />
            </CommandClass>

i will do a second test with group 1,2,3 to see what happens in my situation

[Bikey]

ok i understand.
update" tried mapping 48 but that made no difference but i believe this is the key to solving this"
i will do a second test with group 1,2,3 to see what happens in my situation

Interesting! Where is this re-mapping done, is that in the OZW-part or in Domoticz?
Perhaps that could also be used to read the "binary report" as is used by the new sensors instead of the "Basic Command Class" as used by the old sensor.

Di you already do a test with group 1,2,3, and if things are working do you no longer have the "alarm level secure" messages in the log?

[dutchdevil83]

ok i understand.
update" tried mapping 48 but that made no difference but i believe this is the key to solving this"
i will do a second test with group 1,2,3 to see what happens in my situation

Interesting! Where is this re-mapping done, is that in the OZW-part or in Domoticz?
Perhaps that could also be used to read the "binary report" as is used by the new sensors instead of the "Basic Command Class" as used by the old sensor.

Di you already do a test with group 1,2,3, and if things are working do you no longer have the "alarm level secure" messages in the log?

I am running now with group 1,2 and 3 enabled and haven't found any problems since a week now. Dont know if anything changed in Domoticz since then but my sensors isn't staying on since then.

The "alarm level secure" is a sign that your Device is included as a secure Device with encryption enabled.