Zwave / Java Exception / Fibaro Smoke Sensor V2

thats clear :slight_smile:

but is there a way to that I manually send a notfication of this kind? eg. a rule triggers this?

to achieve this:

I don’t know - not that I know of unless the manual says there is (I guess). At the moment the binding can’t send notifications - it’s on the list of things to do, but not near the top as there’s only one device that I currently know of that needs this (a doorbell I think). If you can find a way to do what you want - either something in the manual, or maybe someone on another forum has mentioned it, then I’m happy to help implement something…

is this added in the current build?

Add option to send notifications to a node (commit: 58ed7e07388654254e1999ee2b45debde689e744) (details)

Yes - I’ve implemented this tonight.

so how does it work?
add “notification_send” in the DB as a channel? which class?

thanks :smiley:

Yes…[quote=“shorty707, post:16, topic:14360”]
which class?

To the ALARM class.

You will need some config with that. What the converter does, is appends the value of the state to the work event, and then looks this up in the config setting. The state must currently be a number, so -:


will send NOTIFICATION type SMOKE, event 1 when the command value is 1. Multiple events can be separated by a comma.

Check here for the (untested!) siren command setting.

I need to work out how to best document this sort of thing - I hope to be able to automate some of this from the source at some stage, but that’s not quite there yet!

well most possible I did something wrong ;)) but this is what I did

  1. I added the send_notification for in the DB and updated the binding this morning

  2. I created a Number item for that channel

  3. I set the item to “1” and expected that the event Smoke is parsed

this happens really:

08:37:08.509 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'node11_IncomingNotification' received command 1
08:37:08.514 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: Command for unknown channel zwave:device:15348538564:node11:notification_send with DecimalType

sorry - I am pretty sure I messed something up :-/

Yep - it won’t have been me ;)…

Ok - so maybe not true. I found the database is exporting the incorrect type - I’ll update this morning.

However, I’m not convinced what you are trying to do will work, but I think we discussed that right? There’s no indication that the device will receive notifications… Still, worth trying as you never know, and I guess if it doesn’t work you will remove this channel right?

correct - I will try to process that incoming notfication like the device received an incoming notification in association group 4 which would trigger a smoke alarm

if this will not work out I will clean up the DB for sure.

But as I said earlier, the device doesn’t receive notifications in group 4 - association groups are for sending notifications. I just looked at the manual, and it also says this so I doubt it will work…

Actually, as this is a battery sensor, it can’t receive notifications in any case…

@shorty707 any luck with this?

I also see you added the same channel to the wall plug - if I understand the wall plug docs correctly, I’m not sure it supports the BURGLAR notification, or if it does, then it can’t differentiate this alarm at least -:

  1. Reaction to alarms.
    Define Z-Wave network alarms to which the Wall Plug will respond.
    Default setting: 63
    Available settings: 0 - 63.
    1 - general alarm,
    2 - smoke alarm,
    4 - CO alarm,
    8 - CO2 alarm,
    16 - high temperature alarm,
    32 - flood alarm,
    63 - device responds to all types of alarm frames

It seems best to align the channel with these options I guess so that the user can differentiate them in some way (although I think they all do the same thing with the LED, right?).

i will test for both devices tomorrow and give feedback and aswell correcting the db

so yes they all do the same… maybe some people want it only to be triggered for a specfiic type?

however before I update it to be 100% correct I would at least get it working with one first :slight_smile:

not sure why this is coming?

19:35:41.757 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: No messages returned from converter
19:35:41.760 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'node7_sendnoti' received command 1
19:35:41.786 [INFO ] [marthome.event.ItemStateChangedEvent] - node7_sendnoti changed from 2 to 1

@chris ping :slight_smile:

Some more information would be helpful ;).

Is there any other debug info logged? Is this for the smoke sensor, or the wallplug?

sorry :slight_smile:
I focus on the wallplug for the moment … there I think it should work … (smoke sensor is unlikeley as you said a battery device wont receive incoming notifications)

the debug shows not too much more

19:50:58.463 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Command received zwave:device:15348538564:node7:notification_send --> 1
19:50:58.464 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: No messages returned from converter
19:50:58.467 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'node7_sendnoti' received command 1

I set the the Item for the “send_notification” channel to 1 … which should be resolved to Smoke

parameter 63 of the plug is configured to let the LED flash when a incoming alarm is catched.

Ok, I suspect the wall plug has the same issue as the siren - it doesn’t claim to support notifications/alarms. So, we need to force this command class in the database by adding the ADD option. I’ve just added it here ( I’ll update the binding later tonight (after dinner :wink: ).

I’ve kicked off the build, so try an update in 30 minutes or so…

19 min minus 4 min = 15 min: fast dinner :grin:

build is done a while
however when I reinstall the binding it always installs a build from oct 9th…