forum

Hello,

I have 3 smoke sensors included in my network, 2x Fibaro FGSS-001 and 1x Fibaro FGSD-002. I've changed the
/opt/z-way-server/automation/modules/ZWave/postfix.json viewtopic.php?f=3422&t=22509&p=61064&hi ... sor#p61064 (thanks to @AlphaX2!), so that the Fibaro FGSD-002 shows all the alarm classes (113) on UI.
Now I want to use the module "Fire Protection".I can select the older FGSS-001 without problems, but I cannot
select the Fibaro FGSD-002 device. The FGSD-002 creates, amongst other, zway vDevs with 113-1-2 and 113-1-3.
So looking at the modules.json from module "Fire Protection":

"field": "enum",
"datasource": "namespaces",
"enum": "namespaces:devices_sensorBinary:alarm:smoke:deviceId,namespaces:devices_sensorBinary:alarmSensor:smoke:deviceId",
"required": true

the namespace "devices_sensorBinary:alarm:smoke" must match my vDev Fibaro FGSD-002 113-1 !?

I have no idea, why the FGSD-002 is not listet.

Anyone an idea?

Thanks
Bjoern.

Hello,

i found out that changing following lines in modules.json from: to does the trick to select the Fibaro FGSD-002 smoke sensor.

So looking into the automation/modules/ZWave/index.js I found other lines (2288...): Changing this to: works also.

Is this a bug in ZWave/index.js?

BTW, there are other lines in Zwave/index.js (for co and flood) that looks same as for smoke alarm.

Maybe, a developer can have a look at it.

Thanks
Bjoern

Since I believe this is one of Maros's modules, he'll be happy to address the issue. He's fairly regular on here so give him a few days....

Hi Mike,

no, this module isn't from Maros. It is a module from Zwave.me (in beta status).
But, I think the module is correct and the problem seems in "automation/modules/ZWave/index.js",
where the definition of the probeTypes is.

From developer.z-wave.me at help site:

The datasource is either “namespaces” for devices or “locations” for rooms. The “enum” receives the array. In this case it would consist of the device IDs of all binary and multilevel sensors. Namespace masks are always in the following scheme:
deviceType : CommandClass : subCommandClass : id OR name

and the scheme in the modules.json is:

"namespaces:devices_sensorBinary:alarm:smoke:deviceId,namespaces:devices_sensorBinary:alarmSensor:smoke:deviceId"

Therefore, I think the problem isn't in the module.

Bjoern

Hello,

after installing v2.2.3 the module works as expected, because the developer have changed
the code in "automation/modules/ZWave/index.js".

Thanks.
Bjoern.

Thanks for reporting back to the forum!

bjoern812 wrote:Hello,

after installing v2.2.3 the module works as expected, because the developer have changed
the code in "automation/modules/ZWave/index.js".

Thanks.
Bjoern.

Unfortunately the App does not recognise my three POPP 004001 Smoke detectors
Strangely the type info says unknown device type, but in EUI under /Control/Sensors the type is Smoke

This is the virtualDevice sensor created from on of the Popp 004001 smoke sensor that is failing to show up.

Hi pz1,

the problem is that your smoke sensors reports alarm on the command class 48 (sensorBinary),
but the module only supports command class 113 and 156.

The manual of your smoke sensor, if a have googled the correct one, says it supports also
command class "alarm" (113 or 156 - don't know).
May be you can change the command class that reports smoke thru a configuration option?

Greetings
Bjoern.

Good morning bjoern812,

Thanks for diving into this. Unfortunately no parameter for that as far as I can see (Pepper1 database #725).
Apparantly ZWay does not recognise the alarm in this device. It only creates this binarySensor and a switch to activate the alarm.
Hope someone from zwave.me can shed some light on this.