Open ebaauw opened 3 days ago
Hey @ebaauw, thanks for your pull request!
[!TIP] Modified bundles can be downloaded here.
fireangel/co_alarm.json
: Zigbee Radio Module (P-LINE) :heavy_check_mark:
fireangel/smoke_alarm.json
: Zigbee Radio Module (P-LINE) :heavy_check_mark:
fireangel/generic_alarm.json
: Zigbee Radio Module (P-LINE) :heavy_check_mark:
[!TIP] Everything is fine !
:clock3: Updated for commit f3e15a19ea3463bbc3c2351b3aa3ede74e2507d4
This PR does two things:
matchexpr
, cf. the work done in #7642 for OTA File Version;Ad 1) I changed the following:
RAttrZoneType
for/attr/zonetype
, based on 0x0500/0x0001;zcl_values
table in the database;RAttrZoneType
toDevice
;Device
RAttrZoneType
on device DDF initialisation;RAtttrZoneType
onlights
andsensors
API endpoints. Not sure if we want or need this. It was already included insensors
web socket notifications out of the box. Note that this attribute doesn't need to be defined on any of the subdevices for thematchexpr
to work, since the C++ code already added it to theDevice
.Note that I didn't add a hook to reload the DDF when 0x0500/0x0001 is read (and changes value), due to the recent issues with the API ignoring messages from devices after DDFs are re-initialised.
Ad 2) I added DDFs for:
matchexpr
for Zone Type having value Fire sensor;matchexpr
for Zone Type having value Carbon Monoxide (CO) sensor;matchexpr
for other Zone Type values.Note the Zigbee module can also be installed in heat alarms, but I don't know what Zone Type these use. Could very well be Fire sensor. On initial pairing, you should get a ZHAAlarm
sensors
resource; after reading IAS Zone and restarting deCONZ, this changes to a ZHAFire or ZHACarbonMonoxide.The only differences between the different devices are the
type
(ZHAAlarm, ZHAFire, ZHACarbonMonoxide) and thestate
attribute for an alarm (alarm
,fire
,carbonmonoxide
). I'm polling the alarm every 5 minutes for the Zone State, as the module doesn't support Supervision Reports nor attribute reporting for this attribute. This should keepstate/lastupdated
fairly current, but I need to assess the impact on battey usage.state/tampered
is set shortly after the smoke alarm is removed from it's base plate. It takes a couple of seconds before the Zone Status Change Notification is sent. [Note to self: check if CO alarm also supports this].state/test
briefly switches totrue
when pressing the device button, activating a self-test (cover your ears!). The Zigbee module only reports voltage if its (user replaceable) battery. This should be reported every 12 hours out of the box.config/battery
extrapolates the voltage linearly from documented range of 1.9V ... 3.0V to 0% ... 100%. Note that there's no indication for the internal, non-replaceable battery of the sensor.swversion
reports the firmware version of the Zigbee module, based on the File Version of the OTAU cluster.Additionally, there's a Warning Device
lights
resource.state/alert
can be used to activate the siren (cover your ears!). Note the module only supports Sqawk, so you only get a short alarm.