I got the doorbell 6 on Wednesday and I have not been able to configure it through HA. I contacted Aeotec who also said that it can’t be done in HA until OZW 1.6 is available. There is some Windows software that they suggested I use but I run HA on a Raspberry Pi 4 so I currently have no way of configuring the doorbell.
It is sat in the box not being used as the default volume is enough to cause a local earthquake! Not great from Aeotec in my opinion - why make a consumer product that the consumer cannot easily configure?!
Not really Aeotecs fault really. The new zwave integration (with ozw 1.6) is in development and since one of the devs have a doorbell I expect it to be testable pretty soon.
That’s good news. My frustration is not with the status of ozw 1.6, more with Aeotec for releasing a product to the consumer with no easy way to configure the settings.
Well, that does entirely depend on your zwave hub of course. I’ve read it works fine with other hubs, it’s just a matter of Home Assistant not supporting it. If you mean that you should be able to configure it on the device it self somehow, that would be against it’s purpose as a siren.
It’s a doorbell. It’s sold as a doorbell, it’s purpose is a doorbell, not a siren. It should behave like a doorbell. If they have packaged up a siren as a doorbell with no consideration to the differences then again they are at fault, in my opinion.
Your frustration should be focused on a combination of OpenZWave, HA, and yourself. Aeotec released a product that implements and properly uses the ZWave control and command standard protocol for its device class, including but not limited to Central Scene, ZWave+, Secure node, and direct communication commands. Their devices work with current ZWave ecosystem products that are commercially available. HA and OpenZWave are opensource/community sourced that you have to do some configuring to put together and effectively simulate your own commercially available ecosystem. The developers of these two programs don’t get paid like the developers of the other ecosystems, if at all. So with a little patience, troubleshooting, and testing your doorbell will work with your homebrew setup. If you can’t be patient, go buy an all-in-one ecosystem where you’ll find your doorbell works just fine. Aeotec will not be blamed here because their product does work, you’re just using it in a non-standard and potentially unsupported ecosystem.
Hi All!
I am using the new beta version of the future z-wave integration:
the Open Z-Wave Daemon
Which uses the new ozw 1.6
I am still expecting it to be able to “sound the alarm” from within HA - at some point in the future - but right now it shows the different sensors only.
Until HA implements support for sirens, you should be able to use MQTT commands directly to turn on the siren. I don’t know the exact syntax, but I think it’s the setValue command.
@loluk44 hi, did you have to define the rfxtrx device to recognise a specific activity. Mine is currently defined to enable transmission of lightwave, visonic and RFY signals using the RFXtrx433E device, or am i barking up the wrong tree (I thought this was a one way transmit device only).
Yes you need to make sure the correct protocols area enabled and also make sure you don’t have 2 protocols enabled that would create interferences with one another
@lolouk44 I’d already checked the doc you point to, but couldn’t see anything obvious relating to the protocol appropriate to the Aeotec doorbell, hence the reason why i asked the question, do i need to bust the thing apart to find the chipset? or is this a case of having to try each and every protocol?
