Group Alarms Fibaro FGSD002

Hi,

I’m running two Fibaro FGSD002 Smoke Sensors. I receive all alarms. I can readout Battery Level and so on.
The only thing I can’t get working is, that I get “Group Alarms” working.
I tried to set the “associated groups” (2 and 4) “crossover” (Smokesensor 1 is in associated group of Smokesensor 2 and vice versa)
Unfourtnately I couldn’t get it work if Sensor 1 has an Smoke Alert that Sensor 2 is alarming. I also tried to set the controller in association group 2 and 4 without success.

Is it possible, that this doesn’t work, because the device is “sleeping”?
Do I need a separate siren for alarming?

Screenshots of both Smoke sensors (ZWave Nodes 11 and 12) with current configuration

image

image

Thanks a lot.

I doubt this is possible. These sensors are battery devices and not FLiRS (unless this has changed recently) so they are asleep most of the time and therefore you can’t send a message TO them.

Yes, this is probably the best option.

Hi, thanks for the info.
I ordered a Popp 4001 Smoke Detector with Siren. I do have a strange behaviour.
The Smoke Detector is joined into Z-Wave Network. I can recevice alarms, batterystatus and i also can switch on siren.
After (a few Minutes) the Smoke Sensors stopps communicating with Z-Wave Sensor. When I hit the test button, the sensor again works fine for a few minutes, afterwards -> same error…
The Smoke Sensor is marked like this:

Do you have any idea, whats going wrong?

Update: The Popp Support advised me to turn off polling. But I don’t find a switch for that.
I can only increase or decrease polling intervall…

Here’s the log, when i push the Z-Wave Button of the Device
017-10-27 16:17:51.048 [ItemStateChangedEvent ] - TaupunktAussen changed from 4.66 to 4.74
2017-10-27 16:18:33.993 [BindingEvent ] - org.openhab.binding.zwave.event.BindingEvent@af2807
2017-10-27 16:18:34.006 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from OFFLINE: Node not found in Z-Wave network to ONLINE: Node initialising: EMPTYNODE
2017-10-27 16:18:34.173 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from ONLINE: Node initialising: EMPTYNODE to ONLINE: Node initialising: PROTOINFO
2017-10-27 16:18:34.204 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from ONLINE: Node initialising: PROTOINFO to ONLINE: Node initialising: INIT_NEIGHBORS
2017-10-27 16:18:34.245 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from ONLINE: Node initialising: FAILED_CHECK to ONLINE: Node initialising: DISCOVERY_COMPLETE
2017-10-27 16:18:34.247 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from ONLINE: Node initialising: INIT_NEIGHBORS to ONLINE: Node initialising: FAILED_CHECK
2017-10-27 16:18:34.260 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from ONLINE: Node initialising: DISCOVERY_COMPLETE to ONLINE: Node initialising: PROTOINFO
2017-10-27 16:18:34.296 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from ONLINE: Node initialising: PROTOINFO to ONLINE: Node initialising: INIT_NEIGHBORS
2017-10-27 16:18:34.323 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from ONLINE: Node initialising: INIT_NEIGHBORS to ONLINE: Node initialising: FAILED_CHECK
2017-10-27 16:18:34.340 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from ONLINE: Node initialising: FAILED_CHECK to ONLINE: Node initialising: WAIT
2017-10-27 16:18:49.135 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from ONLINE: Node initialising: WAIT to ONLINE

If I want to turn on siren:
7-10-27 16:20:53.104 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller
2017-10-27 16:20:56.341 [ItemCommandEvent ] - Item ‘i_zwave_16_Sirene’ received command OFF
2017-10-27 16:20:56.350 [ItemStateChangedEvent ] - i_zwave_16_Sirene changed from ON to OFF

And than the device is offline again

Thanks a lot

Regards

Helmar

So I brought Device Online at

Last Time Online at 16:23:46.794:

2017-10-27 16:23:46.794 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE

After 30 Minutes (which is the standard polling interval) the device went offline again:

2017-10-27 16:52:14.364 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller

I think polling is the issue, how can I turn off polling for that device???
This are the options for the device:

Thanks a lot

Helmar

Reduced Polling interval to 10 minutes, the Device went offline after exactly 10 minutes:

2017-10-27 16:58:03.818 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE
2017-10-27 17:04:44.941 [ThingUpdatedEvent ] - Thing ‘zwave:device:020e4758:node16’ has been updated.
(Reduced Polling to 10 minutes)
2017-10-27 17:14:58.387 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller

The device is (I assume) a battery device, so I assume it is reporting as “listening = false” in HABmin? If so, it should not poll until the device wakes up.

Hi thanks a lot.
Yes is a battery device:
image

Maybe an error in the binding?
I reduced polling to 0, that was how the binding reacted:

That was the behaviour:
2017-10-27 17:21:59.174 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE
2017-10-27 17:22:17.149 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller

Changed Polling to 1 hour… waiting :wink:

I think this is not allowed. I think the value needs to be between 15 seconds and 2 days from memory.

Looking at the attributes, it shows it’s not a listening device, so it shouldn’t try and send to the device unless the device is awake. I would suggest to get a debug log to see what is happening.

OK, I’ll provide during the weekend.
… should I test excluding and including the device again?

What must I do to exclude? (I’ve never done that)
I know which button to press on the device, but I don’t know how to exclude from openhab…

Exactly after an hour it went offline again:

2017-10-27 17:23:40.862 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE
.
.
2017-10-27 18:23:32.086 [hingStatusInfoChangedEvent] - ‘zwave:device:020e4758:node16’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller

There’s no need to exclude the device.

I’d suggest to stop the binding, delete the XML for this node (in the {userdata}/zwave folder) and then restart the binding. Set polling to 30 seconds and let’s see what it shows.

Logfile has 7 MB how can i upload?
(is limited to 1MB)

File uploaded
https://www.file-upload.net/download-12784845/openhab.log.html

Unfortunately the file has no zwave debug logging in it (lots of other debug though which is why the file is so big). To enable debug logging, use the following command.

log:set debug org.openhab.binding.zwave

You might want to see if you can disable some of the other logging otherwise the file might get quite large.

For reference -:
http://docs.openhab.org/administration/logging.html

But the logging is than stored in /var/log/openhab2/openhab.log ?

Yes.

I’m wondering, as a switched log:set Debug…

Sorry - I don’t know what you mean?

I started karraf shell and switched to:
log:set Debug

I think, that should have turned on Debugging also for zwave…

If I turn on logging like that:
log:set debug org.openhab.binding.zwave

How do I switch back to warning?
Is it:
log:set warn org.openhab.binding.zwave