This week I bought a new and not yet intigrated zwave item: The Fireangel ZW-Module. The Smoke Detectors are well tested ones and they’ve been working several years with a proprietary radio module. Now they offer a new zwave module also. There are smoke-, heat- and co²-detectors and they could all be combinied with the same zwave module.
The inclusion was not the challenge and its possible to get the battery. Now I’m struggling with the else configuration parameters. First there should be a assoziation group, but habmin don’t show it.
Looks like there are no config parameters and there’s just the lifeline group, so I think it’s ok. I’ll take a look over this later and will probably do a binding update with the database changes tonight.
As discussed on email, I would assume that these are reported through the multilevel sensor command class, and the fact that they are not there probably means that the device does not report them in the NIF (which is how the device tells users what commands it supports). If the device doesn’t notify us, then we don’t know what it does, and it won’t be supported.
It is possible to work around device bugs by configuring the database, but incorrectly doing this can cause even more problems.
I can take a look at a debug log to see what the initialisation looks like - ie to double check what the device is reporting. This will at least confirm that the database is consistent with what the device reports.
I could potentially purchase one to play with, but at the moment I can’t find it on the net anyway…
Please excuse me. I wouldn’t poll the email discussion here. It was just to make the points accessible for the community.
Thanks to your offer to investigate in this way.
The device is offerd by some more or less smaler internet shops for fire detection or home automation hardware. So when its ok I will buy a one and will sent it to you. Perhaps someone will help us in doing this - I will ask on Monday by telephone.
Sorry - I’ve done the export, but something has changed somewhere in the build system (in ESH/OH I think) and I’m trying to work out why. Once I’ve resolved this I’ll kick off build - it doesn’t necessarily have to wait until tomorrow if I solve it today).
I think you should be able to install the latest ZWave binding from this though by uninstalling it in PaperUI and then installing it again (I’m not 100% sure though and maybe if you’re using some other package installer, this might not work).
Cloudbees wasn’t updated last night - packages still from friday night.
