Problem with module "Fire Protection"

[bjoern812]

Hi pz1,

maybe the problem is in the postfix.json under /opt/z-way-server/automation/modules/ZWave:

Code: Select all

        }, {
                "id": "40",
                "p_id": "340.4.2",
                "product": "Popp 10 year smoke detector ",
                "preInterview": [],
                "postInterview": [
                        "preventDeviceCreation(0,113, {});"
                ],
                "last_update": "0000-00-00 00:00:00"

Don't know if it fits to your smoke sensor. The needed creation of the alarm type 113 is prevented.

I'm very interested in this, because I am considering buying one for my utiliy room and can use the
siren for my alarm system, next to the smoke sensor.

Bjoern.

[pz1]

Helpful comment!
Below is what I think my device is.

I don't know the syntax of postfix, the "noVDev" puzzles me. So does the "preventDeviceCreation" in your device description.
Because ZWay does run on Popp controller as well, this time I naively expected that their Smoke sensors would work with the Fire protection app. (must admit the app still is marked as beta)

Code: Select all

{
			"id": "74",
			"p_id": "340.256.513",
			"product": "Popp Smoke Detector (Secudo)",
			"preInterview": [],
			"postInterview": [
				"noVDev,0-113",
				"rename,0-37,Siren",
				"rename,0-48-2,Smoke Alarm",
				"renameNode,Popp Smoke Detector/Siren"
			],
			"last_update": "2016-07-27 09:48:22"

UPDATE 15:40 Just noticed that my postfix.json has a different set of parameters than you presented. A.o. In your example it now also has noVdev instead preventDeviceCreation. May be because I am on release v2.2.4-rc9 at the moment.

[bjoern812]

HI pz1,

yes, the developer changed format of the postfix.json from 2.2.3 to 2.2.4

It seems that they prevent the creation of the alarm vDev, and I tink this is the problem, that
you cannot select your smoke sensor in the module, because the module accepts only alarm (113)
and alarmSensor (156).

You can try to delete the line

Code: Select all

"noVDev,0-113",

in the postfix.json, restart the server and look if a vDev with CC 113 is created and than try to
select it in the module.

Bjoern.

[pz1]

I did open new issue 378 on github, because I like to know why they decided to block the creation of a alarm vDev before doing further experimenting.

[ronie]

Hi,

yes we've changed a lot of things in our postfix logic in 2.2.4-rc*.
Knowingly we suppress the creation of all Alarm class vDev's for this device, because the smoke alarm is also triggered by a binary sensor.

Unfortunately this 'filter' was missing in the Fire Protection app. Please checkout v1.0.7 where it should work now.

fyi:
Postfix shall help us to fix knowing device bugs or to suppress unnecessary or wrong interpreted vDev's - hopefully at this way we can avoid a lot of irritations on user side. Also it should help us to enhance our support. At the moment it is still in process and some things are still under discussion.

[pz1]

Thanks for the explanantion. Seems a sensible approach to me. These are the hickups one can expect with rc's

I've updated the Fire Protection app in my system to 1.0.7, and can select all three Popp devices now.
Thanks