Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First Alert ZCOMBO v1 alarm notifications are unsupported #1546

Closed
2 of 10 tasks
kpine opened this issue Feb 1, 2021 · 0 comments · Fixed by #1562
Closed
2 of 10 tasks

First Alert ZCOMBO v1 alarm notifications are unsupported #1546

kpine opened this issue Feb 1, 2021 · 0 comments · Fixed by #1562
Labels
bug Something isn't working

Comments

@kpine
Copy link
Contributor

kpine commented Feb 1, 2021

Describe the bug

Alarm notifications from a First Alert ZCOMBO are unsupported.

17:16:12.130 SERIAL « 0x010d00a800010a0471050c0000cbe6                                    (15 bytes)
17:16:12.132 SERIAL » [ACK]                                                                   (0x06)
17:16:12.133 DRIVER « [Node 010] [REQ] [BridgeApplicationCommand]
                      └─[NotificationCCReport]
                          V1 alarm type:  12
                          V1 alarm level: 0
17:16:12.137 CNTRLR « [Node 010] received unsupported notification {
                          "nodeId": 10,
                          "ccId": "Notification",
                          "ccCommand": "0x05",
                          "alarmType": 12,
                          "alarmLevel": 0
                      }

Device information

Which device(s) is/are affected (make/model)? First Alert ZCOMBO
What are the node IDs? 10

Last Known Working Configuration

  • New device

  • Previously working device (node-zwave-js)

    • Which library version/docker image/adapter version?
    • Have you made any recent configuration changes to the device? Describe.
  • Previously working device (other platform)

    • Which platform? OZW
    • Have you made any recent configuration changes to the device? Describe. No.

Installation information
How did you install node-zwave-js?

  • zwavejs2mqtt (latest) docker image
  • zwavejs2mqtt (dev) docker image
  • ioBroker.zwave2 adapter
  • Pkg
  • Manual Docker build
    • node-zwave-js branch: b1b4f74
    • zwavejs2mqtt branch: v1.0.1
  • Manually built (as described in the docs)
  • Other:

To Reproduce
Steps to reproduce the behavior:

  1. Hold down the test button on the alarm
  2. Watch in the node-zwave-js logs that the alarm is unsupported
  3. Notice that zwavejs2mqtt shows no events or value updates in the debug trace except for battery

Additional context
As in this comment, the only values I see are for battery levels. I see "unsupported notification" error in the logs.

Logfile: zwavejs_1.log
Cache files: cache.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant