I need someone that’s completely migrated to the new mobile app to see if they’re still able to play sounds by # using the “Custom Message” option in SHM and/or Speaker Companion.
I just received a complaint about that not working with one of my other chime DTHs and based on their logs it looks like the new app is passing a GUID to the DTH instead of the entered message. If something was changed and it also applies to numbers that are entered as the custom message then that feature most likely won’t work with this DTH either…
Hey Kevin. So I tried this, and your back-up is definitely firing, but it’s also not working.
The annoying thing is, I can’t really test it, because anything I manually trigger always works fine. The cases where it’s failed, is where I’ve not had anything use the Siren in 24 hours and the first thing it does registers as valid command (ie. I don’t see any errors), it just doesn’t actually do anything, even though it thinks it should be.
When the SmartApp is triggered it executes a command on the DTH and the DTH generates the z-wave commands hands them off to ST so if the problem occurs in the DTH or SmartApp you’d see an error in the logs, but that would only happen if one of those had a bug and that bug would be affecting all users.
ST takes those z-wave commands and passes them to the hub which then sends them to either the device (or repeater which then sends them to the device), and then the device performs the action, but if those parts fail you won’t see anything in the logs.
In order to turn on the strobe it has to send 3 messages to the device so I suspect that the commands aren’t making it to the siren for some reason, but moving the device closer to the hub or performing a z-wave repair if you don’t done one in a while might fix it.
Another potential solution is to change 200 to 500 in the “getSirenStrobeCmds” method which is probably about 10-20 lines below the strobe method you already edited. Unfortunately this change will delay the siren turning on by about 1 1/2 seconds…
If those changes don’t solve the problem then I should be able to make that backup method work.
I’m not positive that the backup function is passing the commands to ST the correct way which would cause it to fail without an error, but you can easily test that without waiting 24 hours by putting // in front of the “return getSiren…” line and see if the strobe still turns on 2 seconds after you tap the strobe button.
If the backup code is turning the strobe on then there are some other tweaks that might solve the problem.
Much appreciated for your time & effort in resolving this.
Didn’t know about the Z-wave Repair, so I’ve just completed that.
I have a SmartThings button directly calling strobe on the Siren, and it’s working at the moment. I will try it when I get home from work tomorrow to see if it does it first time.
Thanks again!
Note: The Siren is 2m from the Hub (ethernet & WiFi), and I have many other devices much further away without problems.
It’s most likely a defective device, but it’s possible something changed in the latest firmware that breaks my DTH.
To rule that out, remove the device, remove my DTH, factory reset the device, and see if it works with the default handler it gets assigned when you join it.
There’s been an usually high number of people reporting that the device joins and is functional, but doesn’t make sound so I was starting to think they made a breaking change in 1.5.
On the plus side, I’m pretty sure all the bad devices that have been reported either arrived like that or died after a couple of weeks so if you don’t run into any issues within the first couple of months then you most likely won’t run into any in the future.
Siren and Chime work with firmware 1.5, however I have noticed when playing a chime or alarm ST sometimes gets stuck saying it is still playing the Chime or Alarm even though it has completed. It won’t play the Chime again until I hit refresh in ST to get it go back to off status. I’ve had it a day and had to hit the refresh three or four times to get it unstuck. I have it set so that when the switch is turned on it plays the chime, tone 15 for 1 second. I have a webcore piston that says when any of the doors change state to open then it turns on the Aeotec Siren 6.
Post some live logging results, but leave enough time between the tests so I can easily see when they start and stop. Also make sure you filter the results so that only the siren’s are showing before posting them.
I opened the back door and it chimed, Walked to the garage door and it chimed, then went to the front door and it didn’t chime, then when back to the back door and it didn’t chime.
In webcore and in ST live long I see “Skipped execution of physical command [Aeotec Siren 6].on() because it would make no change to the device.”
I need the live logging results, which is what you posted the first time, but filter the logging results before posting it by clicking that device.
Live logging needs to be opened before you start testing and I also need you to remove the comment from that log.trace line and publish the code before testing which will show additional logging data which will give me a better idea of what’s going on behind the scenes…
I guess I don’t know how to see the Live logging for a device… In the IDE under live logging it doesn’t split it out by device, only integrations, like pistons, alexa, action tiles, and Smart home monitor. Here is a screenshot of the state it get stuck in. If I hit the refresh button it will change to off.
If you uncomment that line in the code, open live logging, and do something with the siren, then the name of your siren will be in the same area as pistons, alexa, etc.
If you’re using the new mobile app then you should also check the settings to make sure that the debug logging setting didn’t get disabled.
If you clear live logging before you start it will be easier to find the device.
There’s only one live logging and it displays all app and device log entries so if you’re still not seeing the device’s log entries and you’ve done everything I mentioned above then post a screenshot of live logging.
Hi,
Firstly can I repeat what others have said and thank you for helping out so many people! I’m new to this scene but I would have thought it’s Aeotec’s job to iron out any issues.
Please could you tell me what I’ve done wrong here, or what I can do to get proper functionality?
I’ve replied to this post, as I have not used the Classic app previously, only the new one.
Yesterday I received my new Aeotec Siren 6 (ver ZW164-C). I installed your device handler before adding it to my hub. Then it was found quickly and auto-added into the new app. When I selected it, I had a few options - Alarm (off or Siren/strobe) and sounds 2-8. See screenshot. The “alarm” just sounds a doorbell chime & strobe. Sounds 2-8 just give a spinning loading wheel, then “a network or server error occurred”, then kick me out of the app back to phone home screen. The siren/strobe does sound when I knock the siren presumably from a vibration sensor.
Of course I then downloaded and installed the classic app as I gather that is the only one that configures all options. No options appear here though except I can rename it, replace it or remove it.
I did also try speaker companion on both apps too but neither detect a speaker option.
I do have more screenshots, but as a new user I can only post 1.