Zipato Multisiren Alarm Stopped working

Devices & Integrations
1

After the firmware update 000.018.00018 my Zipato Alarm has stopped working. To be more precise the Antitamper still sounds the alarm - when removing it from the wall.
The alarm appears to be ONLINE from the device menu on the portal.

However all attempt to sound the alarm or make a beep from the “Things Controller” or from code that had been working for months fails to work.

I even purchased a second alarm - it paired to the hub without problem but again it behaves identically to the first.
I have rebooted the hub several times.
I dont know it has anything to do with the firmware update but it seemed to stopped working at the same time.
I am using the Kevin LaFramboise 1.5.6 Driver

Any ideas?

2

That update has broken at least 3 of my handlers, but it’s not effecting all users.

I plan on looking into it tonight, but it would be helpful if you could post the live logging data.

3

Hi,
Happy to help out, But need some more guidance… to get the data
When I switch back to using their driver 1.5.6
I go to live logging on the smartthings web portal

When I use the tablet app on the siren thing - I press beep or siren.
It gives the usual message like playing sound 1 but nothing else.

What and how would you like me to collect additional log data…?

Cheers

Ben

4

Your device is the EU version, right?

  1. Switch it back to my device handler.
  2. Open Live logging from a web browser.
  3. Open the device from the Mobile App and go into the settings.
  4. Enable the “Enable debug logging” setting and tap Done.
  5. Tap the beep tile and wait 5-10 seconds to see if it makes noise
  6. Tap the siren tile and wait 5-10 seconds to see if it makes noise.
  7. On the live logging page, click your siren name so that only the log entries for that device are shown. (The device name should be listed above the log entries).
  8. Post the log entries by copying and pasting them.
5

Not sure If this helps but the siren still works properly if you use the basic aeon siren device handler but this only has basic alarm on / off capability. it has no beep command.

6

I just released a new version so let me know if that fixes the problem.

7

Kevin,

I have tested 1.5.7 from the Tile application and I confirm it seems to be fully working.
What changed with the firmware update if you dont mind sharing?

Here is the log details you asked for:
c40a3578-1e60-4596-9791-ffd02d0061a4 9:14:01 AM: debug Zipato Multisound Siren turned off
c40a3578-1e60-4596-9791-ffd02d0061a4 9:13:59 AM: debug Zipato Multisound Siren turned on
c40a3578-1e60-4596-9791-ffd02d0061a4 9:13:59 AM: info Playing Sound #1
c40a3578-1e60-4596-9791-ffd02d0061a4 9:13:57 AM: debug Zipato Multisound Siren turned off
c40a3578-1e60-4596-9791-ffd02d0061a4 9:13:51 AM: debug Device Checked In
c40a3578-1e60-4596-9791-ffd02d0061a4 9:13:51 AM: debug Zipato Multisound Siren turned on
c40a3578-1e60-4596-9791-ffd02d0061a4 9:13:50 AM: info Playing Sound #1
c40a3578-1e60-4596-9791-ffd02d0061a4 9:12:04 AM: debug Device Checked In
c40a3578-1e60-4596-9791-ffd02d0061a4 9:12:04 AM: debug Zipato Multisound Siren turned off
c40a3578-1e60-4596-9791-ffd02d0061a4 9:12:04 AM: debug Zipato Multisound Siren turned on
c40a3578-1e60-4596-9791-ffd02d0061a4 9:12:01 AM: info Playing sound #6 0 time(s)
c40a3578-1e60-4596-9791-ffd02d0061a4 9:12:01 AM: debug Zipato Multisound Siren turned off
c40a3578-1e60-4596-9791-ffd02d0061a4 9:11:59 AM: debug Notification Type: Notification Report
c40a3578-1e60-4596-9791-ffd02d0061a4 9:11:57 AM: debug Alarm State: enabled
c40a3578-1e60-4596-9791-ffd02d0061a4 9:11:54 AM: debug Alarm Duration: 180 Seconds
c40a3578-1e60-4596-9791-ffd02d0061a4 9:11:53 AM: debug
Strobe Sound: Emergency
Siren Sound: Emergency
Both Sound: Emergency
On Sound: Emergency
Beep Sound: Beep

8

Here are my Hub Version Details:
Home Hub

Firmware Version 000.018.00018
Hardware Version hub v2, UK customer

9

Done - Thanks so much. Just made a donation to your paypal page to encourage continued support

10

This is one of my older DTHs and when I wrote it I didn’t fully comprehend the Security Command Class so I implemented it in a weird way.

I’m not sure how a Hub Update could have caused it to break, but updating that part of the code appears to have fixed the problem.

Thank you for the donation, I really appreciate it.