@Ioana I am bumping this back up
I also want to buy this doorbell. It is the only zwave doorbell that works on other platforms, only still not on Vera.
@sorin @melih please give more priority to get all the popular zwave devices that came on the market past two years working on Vera. This one is only one example of many.
And also improve further on the shortcomings in the current hardware and software (I refer to all the research, analysis, improvements and recommendations made by @Rafale77.
In stead of developing all kinds of apps and features that are nice for some people but not basic requirements for a domotica controller.
And introducing several new ezlo controllers that at this moment are just useless toys for the majority of the domotica crowd (even for beginners). Sorry for sounding so negative but I think majority of current Vera userbase agrees with me.
To clarify my goal: I am not asking Staff to fix this today. Simply asking for Staff to open back up the “Integration Request” thread, because right now people are saying this is a priority, but there is not a systematic method for us to show you that (as the thread has been closed).
Trying to get some info on this guys, and keep you posted.
Actually we are asking that this is something that needs to be fixed today!
The thread that you mention is locked because it was already accepted to be implemented as it had most votes, but even though it should be implemented it still isn’t.
There no reason to vote, we already did that and were promised this would be added. So add it now, we don’t need another vote!
See Edwards post that it was supposedly added to 7.30 here:
Unfortunately it never was…
Thanks for looking into it, @Sorin!
My first thought upon reading this was, “Why doesn’t ezlo just partner with the Apilio team, whose sole purpose is integrating home automation API’s into a single endpoint?”
(i.e. instead of rolling your own…)
I’ve talked with edward and the reasoning behind closing that topic. Prior to 7.30 the pairing with this doorbell was not possible and this has been fixed in 7.30. A full device integration is a total different story and that’s not available for this device and Vera.
Aeotec Doorbell 6 is already on our integration road map but most probably it will be available on the Ezlo Hardware.
Thanks for getting back to us.
That thread is about a full integration of the doorbell, not just pairing. Obviously you understand that pairing is useless if you can’t use the device, why pair something that doesn’t work? People voted for that and it actually was the highest on the list if I remember correctly. So I have no clue why Edward would interpret that in a different way that obviously isn’t the case in that thread, let alone think this helped us in any way at all.
Also I bought a VeraPlus, all those other people asking for this integration are running a Vera of some kind and I have yet to see a single one interested in the Ezlo hardware. We want integration on the Vera product and we’ve been more than patient, I really don’t care about Ezlo (sorry) and it has nothing to do with the Vera’s. We bought hardware that was supposed to support everything, that means continuous development to support new devices and that really just stopped completely and is not OK!
My ears hurt and I’m sick of it not working. I can’t even configure how loud this thing is (100+ dB!!!) and can’t turn off alarms or change the chime.
I don’t really care how it gets fixed, at least make it possible to configure this thing.
I contacted Aeotec about this, and Chris Cheng is always insanely helpful. Here is a short-term workaround, that I’ll use until Vera supports full integration.
MY PLAN based on Chris’s advice:
- Use Zensys to configure device using my Aeotec Z-Stick (easy way to adjust settings)
- Connect to Domoticz for full integration using my Aeotec Z-Stick (need to do Zensys first, as Domoticz can’t change all the paramters concerning tones, volume)
- Use Domoticz to notify Vera when doorbell goes off
Chris’s instructions on using Zensys to configure parameters:
Zensys Tools is more or less used as a debug tool, but allows you to directly send packets related to their command classes (you won’t be able to setup automation here).
- Download Zensys Tools here:https://aeotec.freshdesk.com/helpdesk/attachments/6091420613
- Close Software that is linked to Z-Stick Gen5
- Unzip Zensys Tools file, and open the .exe file.
- Click and highlight your Doorbell 6 (in our image, it is Node #3)
- Select “Node Info” button (4th button on the left)
- Now open up “Command Class” tab on the right side of the software
Command Classes: “COMMAND_CLASS_MULTI_CHANNEL_V2”
Command Name: “MULTI_CHANNEL_CMD_ENCAP”
- Input these Values:
Source End Point: 00 // leave as default
Res: 00 //Don’t touch this, this does nothing.
Destination Endpoint: 02 // Tamper Switch endpoint of Siren or Doorbell 6, you can use this to control sound of your button or other alarm options
- Endpoint 01 - Play sound
- Endpoint 02 - Tamper Switch
- Endpoint 03 - Button #1
- Endpoint 04 - Button #2
- Endpoint 05 - Button #3
- Endpoint 06 to 08 - Various alarm usecases.
Bit address: 00
Command Class: 79 //Sound Switch Command Class
Command: 05 //Sound Switch Configuration Set Command
Parameter: 05 01 //Volume #5 (as 05) Sounds #01 (as 01)
- Volume is a range between 00 - 65 (in hex which is 0 - 100 in decimal or easily seen as 0 - 100%)
- Sound can be a range between 00 - 1E (or decimal value of 1 - 30 or sound #1 - 30).
- Example, Sound = 05, Volume = 0A (10%)
- Parameter: 0A 05
This worked perfectly…I was able to turn down the volume (especially for the “tamper” alarm which was so jarring). And then integrate into Domoticz as a means to then notify Vera (via an HTTP request).
I know this is not ideal, and quite an intensive workaround. I’m looking forward to the day (2022? ) where this is fully integrated by Vera.
Wow you are a trouper for being willing to go through all this song and dance to get it to work.
FYI, Zensys was the developper of Z-wave, a danish company which then sold it to Sigma Design who in turn sold it to Silicon Labs. So this tool is an original. Silicon Labs provides an updated version of this tool, the PC controller v.5.39 which comes in very handy.
You can easily run the exact same configuration with z-way…
I am finding hilarious that you have to install another controller (domoticz) as a relay to the vera… I would migrate to that other controller altogether then. Why bother? Oh wait… I did.
Do you need to sign up with SiLabs to get access to that tool? I’m not seeing it on their Z-Wave dowload page https://www.silabs.com/products/development-tools/software/z-wave
Rene, the link Aeotec sent me was a direct download link
Yes you need to sign up for an account with them. (It’s free) That’s how I also got access to their firmware and I have tinkered with various newer versions of zwave sdk.
This just reminded me… @LibraSun, The vera plus you got from me probably has a newer zwave firmware than the standard veras… offer. I think it is running 6.81.06 and therefore showing an API version of 6.7. The vera runs 6.81.00/6.1 from what I recall.
@jrweiland, That’s an ancient version which works fine with the aeotec gen5 stick running an an their obsolete sdk and firmware but for other zwave sticks, the newer version from silabs is better. The GUI has also been refreshed making it much more intuitive. I even ran a zwave 700 series stick on it.
Although I admire your workarounds and the work you put in, not everyone can do this.
I am running a containerized Home Assistant set-up and my only physical device is the VeraPlus which is being used as the z-wave gateway. I do not have Domoticz or some z-wave dongle to create workarounds like above.
I do not have an option to plug in physical hardware to my Home Assistant and work from there.
Like most people I guess, this just needs to be fixed the right way.
And if all Vera will stop being used/supported/developed I’d like my 180$ back and I’ll buy a new solution that does work, I’ll send back the VeraPlus or just throw it in the dumpster…
I also would like to see some development effort in making Vera Plus stable, implementing @rafale77 suggestions in another thread, while also adding improved device support for GE/Jasko and Aeotec devices. These two companies produce quite a few devices. If you have decent developers, it wouldn’t be difficult to port between Ezlo and Vera Plus. Like others here, I don’t care about the newer product Ezlo as I had recently purchased a Vera Plus and would expect support on this product. If you need to update the Vera Plus code base, so that it’s easier to backport and maintain device integrations for both platforms then do so… and use this effort to make the product more stable with the recommendations you constantly keep ignoring from the active developers on this forum.
They really should contract out developers like @rafale77 and others to fix their product. I do t have a sense their current programmers are any good.
Sorry Sorin, would you please take a few minutes and clarify your statement please.
What exactly do you mean by it will be “available on Ezlo Hardware”. Is the Vera platform End Of Life? Is their a timeline when the Vera Hardware will be EOL? Why do you continue selling Vera units?
It sure reads like the writing is on the wall.
Been feeling that way here for about a year or more. Sad.