Aeotec Siren 6 only obeys commands if debug logging is enabled

🧰 Built-In Apps and Drivers Built-in Drivers
1

Took me a while to figure this one out... hopefully it helps someone else out there.

For the longest time now, my Aeotec Siren 6 was not obeying volume based commands. It was still playing sounds, but stuck at 100% volume. Changing the volume via Rule or manually in the device page yielded the following similar errors in the log:
java.lang.NumberFormatException: null on line 181 (method volumeDown)
java.lang.NumberFormatException: null on line 181 (method setVolume)

So I enabled debug logging on the device page and lo and behold the commands work now. I turned off debug logging to make sure I wasn't crazy and again I get the Java errors. So I guess the only way for the device to function correctly is to leave debug logging enabled for whatever reason.

2

Something is wrong with your Siren 6 or its pairing. Or perhaps the driver being used.

I don't have debug logging on, and my Siren obeys all the commands on the device page. The driver being used on my system is "Aeotec Siren 6 new".

1 Like
3

Debug logging shouldn't be required, but putting that aside, doesn't debug logging automatically turn off after 30 minutes. At least it does on my hub and I haven't found a way to stop that.

4

It's all up to how the developer coded the driver; and what options they provided for debugging.

3 Likes
5

Thanks for the info. I had thought that the 30 minutes timeout was built into the Hubitat to prevent unnecessary excess load.

I am glad that it exists in all the devices I have used it on, because I usually forget I had enabled it.

1 Like
6

Lol.. yeah, it's certainly a neat option.
Some developers give a multiple selection (30 mins, 60 mins, 24 hours, etc.)... followed by an auto-off. Others just have a simple on/off.

7

I'm not seeing any reason debug logging should matter for this (there never should be, but typos can introduce weird bugs...). However, if you have it enabled, you should be able to show some logging for successful commands. If you try the same ones unsuccessfully, what is the log output for both?

The value of your "Chime Tone" setting might play into this, however. What is that set to? Does it affect anything if you change it?

Additionally, what hub platform version are you running (Settings > Hub Details) and have you ever used a beta version?