Fibaro FGFS-101

[hjvdijk]

Hi,

I purchased a Fibaro FGFS-101 flood sensor for my aquarium. The inclusion seems to be going sort of ok. The device is seen as an unnamed ZDDX-452-010f-0b00-1001-03-03-34-17-17.xml Sensor is showing up in het sensor section. Strange thing is that the event is triggering one of the door sensors in the network. I spent a lot of time on this...removing and adding the involved senors one by one but the issue does not seem to go away.

Is there a way to investigate this ande come to the source of the issue? At the moment this is a very expensive stand alone flood sensor.

Regards,

Hendrik-Jan

[PoltoS]

Can you explain your problem better? Preferable with logs and screenshots

[hjvdijk]

Can you tell me where I can find the logs in zwave.me?

Yes I am a noob but this app is hard to get into.

[pz1]

/var/log look for z-way

[hjvdijk]

I included the device and it was assigned `device 18´. I triggered it and got the following in the log )device did not change state in zwave.me btw'

[2014-03-30 18:14:51.955] SENT ACK
[2014-03-30 18:14:51.956] SETDATA devices.18.data.lastReceived = 0 (0x00000000)
[2014-03-30 18:14:51.956] SETDATA devices.1.instances.1.commandClasses.32.data.srcNodeId = 18 (0x00000012)
[2014-03-30 18:14:51.956] SETDATA devices.1.instances.1.commandClasses.32.data.srcInstanceId = 1 (0x00000001)
[2014-03-30 18:14:51.956] SETDATA devices.1.instances.1.commandClasses.32.data.level = 255 (0x000000ff)
[2014-03-30 18:15:01.625] RECEIVED: ( 01 0D 00 04 00 12 07 9C 02 12 05 00 00 00 6A )
[2014-03-30 18:15:01.626] SENT ACK
[2014-03-30 18:15:01.626] SETDATA devices.18.data.lastReceived = 0 (0x00000000)
[2014-03-30 18:15:01.626] SETDATA devices.18.instances.0.commandClasses.156.data.5.srcId = 18 (0x00000012)
[2014-03-30 18:15:01.627] SETDATA devices.18.instances.0.commandClasses.156.data.5.sensorState = 0 (0x00000000)
[2014-03-30 18:15:01.627] SETDATA devices.18.instances.0.commandClasses.156.data.5.sensorTime = 0 (0x00000000)
[2014-03-30 18:15:01.649] RECEIVED: ( 01 09 00 04 00 12 03 20 01 00 C2 )
[2014-03-30 18:15:01.649] SENT ACK
[2014-03-30 18:15:01.649] SETDATA devices.18.data.lastReceived = 0 (0x00000000)
[2014-03-30 18:15:01.650] SETDATA devices.1.instances.0.commandClasses.32.data.srcNodeId = 18 (0x00000012)
[2014-03-30 18:15:01.650] SETDATA devices.1.instances.0.commandClasses.32.data.srcInstanceId = 0 (0x00000000)
[2014-03-30 18:15:01.650] SETDATA devices.1.instances.0.commandClasses.32.data.level = 0 (0x00000000)
[2014-03-30 18:15:01.661] RECEIVED: ( 01 0D 00 04 00 12 07 60 0D 01 01 20 01 00 AF )
[2014-03-30 18:15:01.661] SENT ACK
[2014-03-30 18:15:01.661] SETDATA devices.18.data.lastReceived = 0 (0x00000000)
[2014-03-30 18:15:01.662] SETDATA devices.1.instances.1.commandClasses.32.data.srcNodeId = 18 (0x00000012)
[2014-03-30 18:15:01.662] SETDATA devices.1.instances.1.commandClasses.32.data.srcInstanceId = 1 (0x00000001)
[2014-03-30 18:15:01.662] SETDATA devices.1.instances.1.commandClasses.32.data.level = 0 (0x00000000)

[hjvdijk]

Also strange... the status in the application is not changed. It should say 18.15

Capture.JPG (20.72 KiB) Viewed 12214 times

In Domoticz the front door sensor is tripped but not in zwave.me

[pofs]

Your device is sending Basic and AlarmSensor reports when you trigger an event.
But interface looks like it is showing SensorBinary and SensorMultilevel values for channels. They're not changed (no report from device), so interface is not actually updated.

For SensorBinary v1 there's a hack that alters its value on Basic report, but your SensorBinary on channel #1 probably is v2, so the hack doesn't work. This will be fixed in the next release (1.7.0-rc2).

Triggering other sensor is something to do with association groups, I believe. There are 3 association groups for this device type.
First one is for devices to get Basic Set and Alarm reports, and seems your RaZberry is in it.
Third one is for controller to receive device status updates. Try to include RaZberry into it, probably it would be updated then.