gregkinney Posted December 8, 2020 Posted December 8, 2020 I have an Aeotec Siren 6. I'm trying to turn the tamper alarm off. I've tried to change the parameters but I can't find any parameter setting for mute, or off. The best I have done is gotten the alarm to turn off after 1 second, which is just long enough to make me jump up every time I bump the desk it's sitting on. Does anyone have experience with this?
Screw Loose Dan Posted December 9, 2020 Posted December 9, 2020 I believe I was able to change the volume of the tamper alarm, including muting it. Your post prompted me to look into and try to figure it out as it's annoyed me on occasion. My initial testing shows that I was able to mute it. When I add it to ISY, I get a bunch of different devices listed. From what I could tell in this document, the tampering alarm is end point #2. So, I muted the volume on the 2nd device and it appears to mute the tampering alarm. See the attachment for what mine looks like (I'm on 5.3.0 firmware), but it I believe the the device you want to change the volume on will be like "ZWXXX_002_1". See if that works.
gregkinney Posted December 9, 2020 Author Posted December 9, 2020 (edited) Thanks so much for the reply. It appears that it's not adding correctly to the ISY because I don't have the above options. Your screenshot shows Siren.2, and I should have Siren.1 thru Siren.8 but I don't. Currently working with UD on a support ticket. Thanks for confirming this! It's a big help. Edited December 9, 2020 by gregkinney 1
lilyoyo1 Posted December 9, 2020 Posted December 9, 2020 6 minutes ago, gregkinney said: Thanks so much for the reply. It appears that it's not adding correctly to the ISY because I don't have the above options. Your screenshot shows Siren.2, and I should have Siren.1 thru Siren.8 but I don't. Currently working with ISY on a support ticket. Thanks for confirming this though! It's a big help. What's your firmware and UI
Screw Loose Dan Posted December 9, 2020 Posted December 9, 2020 25 minutes ago, gregkinney said: Thanks so much for the reply. It appears that it's not adding correctly to the ISY because I don't have the above options. Your screenshot shows Siren.2, and I should have Siren.1 thru Siren.8 but I don't. Currently working with UD on a support ticket. Thanks for confirming this! It's a big help. I probably need to open a ticket as well with them regarding the siren. It all works, but regardless what I do it's constantly says it's writing to the device. It's the only device I have with this behavior, so I'm not sure if it's the device or something with the ISY.
larryllix Posted December 9, 2020 Posted December 9, 2020 (edited) ISY has developed a problem writing to battery devices and some Insteon plug-in devices over the last year or so. I have no Zwave but many of my Insteon devices have had to be put into linking mode and manually updated. This is not just battery devices anymore but AC powered devices also. The battery write option can be disabled but each time ISY gets rebooted the option turns itself back on and ISY grinds to a halt with massive caching of writing to so many devices. I have attempted to bring this to UDI's attention but has been ignored many times over the last two years in the latest releases. A "run at startup" program to disable the battery write option, can help but is a poor workaround, as the a cache is already full of update instruction by the time the program runs. The updating of Insteon Scenes needs to go back to the way it was previously, and stop attempting to write to battery devices completely. The "Battery Write" option needs to remember where it was last set. as a minimum. I had to put each battery device and about 8 plug-in devices into linking mode and select update to get my ISY back to functioning again. Now every so often I find ISY's cache full of owing writes again, and crippled for HA speed, again. I have also experienced several "ALL-ON" events now, that ISY has become so famous for. Edited December 9, 2020 by larryllix 1
Screw Loose Dan Posted December 9, 2020 Posted December 9, 2020 18 minutes ago, larryllix said: ISY has developed a problem writing to battery devices and some Insteon plug-in devices over the last year or so. I have no Zwave but many of my Insteon devices have had to be put into linking mode and manually updated. This is not just battery devices anymore but AC powered devices also. The battery write option can be disabled but each time ISY gets rebooted the option turns itself back on and ISY grinds to a halt with massive caching of writing to so many devices. I have attempted to bring this to UDI's attention but has been ignored many times over the last two years in the latest releases. A "run at startup" program to disable the battery write option, can help but is a poor workaround, as the a cache is already full of update instruction by the time the program runs. The updating of Insteon Scenes needs to go back to the way it was previously, and stop attempting to write to battery devices completely. The "Battery Write" option needs to remember where it was last set. as a minimum. I had to put each battery device and about 8 plug-in devices into linking mode and select update to get my ISY back to functioning again. Now every so often I find ISY's cache full of owing writes again, and crippled for HA speed, again. I have also experienced several "ALL-ON" events now, that ISY has become so famous for. Well, I'm not sure this counts as a battery device. A hybrid, I suppose. It does have a battery, but it's plugged in 99% of the time. The battery in this device is intended only as a backup (it only lasts ~4 hours). And, I have no issues making changes to the device, it writes my updates immediately. It just shows in the UI that's it's still "WRITING". Also, I'm not overly familiar with ZWave but I don't know of any way to put this device (or the other ZWave devices I have) into the equivalent of linking mode. I have excluded the device (that seems like the only way this device will go into a linking state?), reset the device, and then re-added the device. I also tried synchronizing the ZWave device. But, as I said, everything appears to work. Here's me updating the volume on endpoint #2 and doing a query 14 seconds later. Wed 12/09/2020 10:38:10 AM : [ZWAVE-TE ] [79/05] CC=0x79 cmd=0x05 [0000] ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:10 AM : [ZWAVE-TX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:10 AM : [ZWAVE-RX ZW014_1] [98/80] Security Nonce Report - nonce=[3B825B0E1909A301] ACK,AUTO,EXPLORE From=0x0E Wed 12/09/2020 10:38:24 AM : [ZWAVE-WAKEUP 14.002] Query device ZW014_002_1 Wed 12/09/2020 10:38:24 AM : [ZWAVE-TE ] [79/01] CC=0x79 cmd=0x01 [] ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:24 AM : [ZWAVE-TX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:24 AM : [ZWAVE-RX ZW014_1] [98/80] Security Nonce Report - nonce=[69E1398235CA2B98] ACK,AUTO,EXPLORE From=0x0E Wed 12/09/2020 10:38:24 AM : [ZWAVE-RX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x0E Wed 12/09/2020 10:38:24 AM : [ZWAVE-TX ] ... Wed 12/09/2020 10:38:25 AM : [ZWAVE-RD ] [010E00130E07600D020079021E25003D] REQ ZW_SEND_DATA Wed 12/09/2020 10:38:25 AM : [ZWAVE-TE ] [79/09] CC=0x79 cmd=0x09 [] ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:25 AM : [ZWAVE-TX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:25 AM : [ZWAVE-RX ZW014_1] [98/80] Security Nonce Report - nonce=[22B5218F19FA27A7] ACK,AUTO,EXPLORE From=0x0E Wed 12/09/2020 10:38:25 AM : [ZWAVE-RX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x0E Wed 12/09/2020 10:38:25 AM : [ZWAVE-TX ] ... Wed 12/09/2020 10:38:25 AM : [ZWAVE-RD ] [010E00130E07600D0200790A0025002F] REQ ZW_SEND_DATA Wed 12/09/2020 10:38:25 AM : [ZWAVE-TE ] [79/06] CC=0x79 cmd=0x06 [] ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:25 AM : [ZWAVE-TX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x0E Wed 12/09/2020 10:38:26 AM : [ZWAVE-RX ZW014_1] [98/80] Security Nonce Report - nonce=[FBAEBF3A8F2A6797] ACK,AUTO,EXPLORE From=0x0E Wed 12/09/2020 10:38:26 AM : [ZWAVE-RX ZW014_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x0E Wed 12/09/2020 10:38:26 AM : [ZWAVE-TX ] ... Wed 12/09/2020 10:38:26 AM : [ZWAVE-RD ] [010F00130E08600D02007907001125002C] REQ ZW_SEND_DATA Wed 12/09/2020 10:38:26 AM : [D2D EVENT ] Event [ZW014_002_1] [SVOL] [0] uom=51 prec=0 Wed 12/09/2020 10:38:26 AM : [ ZW014_002_1] SVOL 0 (uom=51 prec=0)
Recommended Posts