I have a Aeotec Doorbell 6 and 2 Siren 6 - all are using the Aeotec Siren 6 New driver. The Doorbell works as expected - tell it to play a certain tone, and it does. The Sirens, however, do not work that way - tell then to play a certain tone (Events show correct tone), but what is played is the "default" siren tone.
I notice the State Variables are radically different between the Doorbell and the siren:
The firmware reported on the Doorbell is 1.5, but on the Siren is 1.05 - Aeotec support page does not list any available firmware updates, so I don't know if I have "old" Sirens, or if the firmware reporting is wrong.
New to all of this (hey there!), so there may be some "trick" I am unaware of. Any insights appreciated. Amazed at the quality of information and community on this forum, BTW.
Well, had a nice email exchange with Aeotec, and they confirmed that the firmware IS the same. Seems the issue is with the Aeotec Siren 6 New driver - no Component Chime is created with this driver, either.
Here is what Aeotec said about the firmware:
V1.5 and V1.05 are the same, its just listed differently.
V1.5 (or V1.05) with the decimal point is stating:
Version 1
Subversion 5 / 05 (while it isn't 50, if it was 50, then it would state V1.50 instead)
V1.5 is not the same as V1.50, but it is equal to V1.05. (its just that the value 0 in front is dropped).
Mashed that Configure button I don’t know how many times. Totally unsatisfactory user experience when you do that - it just sits there, looking gray, taunting you with its ineffectiveness.
Configure worked when I switched drivers on my doorbell, too - but no joy on the Siren.
I ended up sending back my sirens and ordering 2 more doorbells. That way I now have 2 backup doorbell buttons for my front gate - at a lower cost than buying a replacement button. One of the sirens failed, as well - just a low hiss, and no sounds at all. Been happy with the doorbells, but I was not happy with the sirens. All are now working as expected.
