Unprocessed Event - when using Z-Wave JS

🛎️ Get Help Devices
1

@Hubitat_Staff

So I have more devices I am getting this on:

Unprocessed Event: NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 0, notificationType: 0, event: 0, sequence: false, eventParametersLength: 0, eventParameter: , sequenceNumber: 0)
parse:{"cc":113,"cmd":5,"ep":0,"values":[{"commandClass":113,"commandClassName":"Notification","endpoint":0,"newValue":0,"prevValue":0,"property":"alarmType","propertyName":"alarmType"},{"commandClass":113,"commandClassName":"Notification","endpoint":0,"newValue":0,"prevValue":0,"property":"alarmLevel","propertyName":"alarmLevel"}]}

Using this Driver: Generic Z-Wave Plus Smoke/CO Detector

For my First Alert Smoke/CO detectors (non Z-Wave Plus) ( I have 8 of them installed) This is ontop of the Utilitech Drvies that have the same issues: Water Leak, Glass Break, Alarm Siren

2

Here is a full log from a responce:

dev:15812025-08-19 10:51:23.370 AMdebugUnprocessed Event: NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 0, notificationType: 0, event: 0, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
dev:15812025-08-19 10:51:23.367 AMdebugparse:{"cc":113,"cmd":5,"ep":0,"values":[{"commandClass":113,"commandClassName":"Notification","endpoint":0,"newValue":0,"prevValue":0,"property":"alarmType","propertyName":"alarmType"},{"commandClass":113,"commandClassName":"Notification","endpoint":0,"newValue":0,"prevValue":0,"property":"alarmLevel","propertyName":"alarmLevel"}]}
dev:15812025-08-19 10:51:23.235 AMinfoLiving Room Smoke/CO carbon monoxide clear
dev:15812025-08-19 10:51:23.234 AMdebugparse:{"cc":113,"cmd":5,"ep":0,"values":[{"request":{"args":[{"alarmType":0,"notificationEvent":0,"notificationType":2}],"command":"endpoint.invoke_cc_api","commandClass":113,"endpoint":0,"messageId":"expected571","methodName":"get","nodeId":137},"response":{"alarmLevel":0,"notificationEvent":0,"notificationStatus":255}}]}
dev:15812025-08-19 10:51:23.232 AMdebugUnprocessed Event: NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 0, notificationType: 0, event: 0, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
dev:15812025-08-19 10:51:23.229 AMdebugparse:{"cc":113,"cmd":5,"ep":0,"values":[{"commandClass":113,"commandClassName":"Notification","endpoint":0,"newValue":0,"prevValue":0,"property":"alarmType","propertyName":"alarmType"},{"commandClass":113,"commandClassName":"Notification","endpoint":0,"newValue":0,"prevValue":0,"property":"alarmLevel","propertyName":"alarmLevel"}]}
dev:15812025-08-19 10:51:22.980 AMinfoLiving Room Smoke/CO battery is 100%
dev:15812025-08-19 10:51:22.978 AMdebugparse:{"cc":128,"cmd":3,"ep":0,"values":[{"commandClass":128,"commandClassName":"Battery","endpoint":0,"newValue":100,"prevValue":100,"property":"level","propertyName":"level"},{"commandClass":128,"commandClassName":"Battery","endpoint":0,"newValue":false,"prevValue":false,"property":"isLow","propertyName":"isLow"}]}
dev:15812025-08-19 10:51:22.855 AMinfoLiving Room Smoke/CO smoke clear
dev:15812025-08-19 10:51:22.853 AMdebugparse:{"cc":113,"cmd":5,"ep":0,"values":[{"request":{"args":[{"alarmType":0,"notificationEvent":0,"notificationType":1}],"command":"endpoint.invoke_cc_api","commandClass":113,"endpoint":0,"messageId":"expected570","methodName":"get","nodeId":137},"response":{"alarmLevel":0,"notificationEvent":0,"notificationStatus":255}}]}
dev:15812025-08-19 10:51:22.607 AMdebugUnprocessed Event: NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 0, notificationType: 0, event: 0, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
dev:15812025-08-19 10:51:22.605 AMdebugparse:{"cc":113,"cmd":5,"ep":0,"values":[{"commandClass":113,"commandClassName":"Notification","endpoint":0,"newValue":0,"prevValue":0,"property":"alarmType","propertyName":"alarmType"},{"commandClass":113,"commandClassName":"Notification","endpoint":0,"newValue":0,"prevValue":0,"property":"alarmLevel","propertyName":"alarmLevel"}]}
dev:15812025-08-19 10:51:22.544 AMinfoLiving Room Smoke/CO battery is 100%
dev:15812025-08-19 10:51:22.542 AMdebugparse:{"cc":128,"cmd":3,"ep":0,"values":[{"commandClass":128,"commandClassName":"Battery","endpoint":0,"newValue":100,"prevValue":100,"property":"level","propertyName":"level"},{"commandClass":128,"commandClassName":"Battery","endpoint":0,"newValue":false,"prevValue":false,"property":"isLow","propertyName":"isLow"}]}
dev:15812025-08-19 10:51:22.390 AMdebugLiving Room Smoke/CO Device wakeup notification
dev:15812025-08-19 10:51:22.388 AMdebugparse:{"cc":132,"cmd":7,"ep":0,"values":[]}
dev:15812025-08-19 10:51:22.116 AMdebugHeartbeat
dev:15812025-08-19 10:51:22.111 AMdebugparse:{"cmd":5,"cc":113,"ep":0,"values":[{"notificationEvent":{"event":5,"eventLabel":"Heartbeat","label":"System","type":9}}]}
3

@Hubitat_Staff Is this even being worked on? I really Need my smoke detectors to work in hubitat, they worked before, but now they throw this message. (All 11 of my smoke detectors are doing this):

[dev:1582](http://10.1.10.254/logs#)2025-08-28 11:50:14.354 AM

debug

Unprocessed Event: NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 0, notificationType: 0, event: 0, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)

[dev:1582](http://10.1.10.254/logs#)2025-08-28 11:50:14.352 AM

debug

parse:{"cc":113,"cmd":5,"ep":0,"values":[{"commandClass":113,"commandClassName":"Notification","endpoint":0,"newValue":0,"prevValue":0,"property":"alarmType","propertyName":"alarmType"},{"commandClass":113,"commandClassName":"Notification","endpoint":0,"newValue":0,"prevValue":0,"property":"alarmLevel","propertyName":"alarmLevel"}]}

I also have reported My Utillitech Glass Break sensors and Sirens. What do we need to do to get these working?

4

Switch Zwave back to legacy ZIP (via button on zwave details). The Zwave JS implementation has many lingering issues and they are being very slow to fix them unfortunately.

I have multiple pending issues I reported over in beta which are also not fixed yet AFAIK. One of which is the same issue you are seeing with the all 0 notifications.

Did they actually stop working? As far as I have seen this all 0 notification is just a bogus message and does not cause any issues other than being annoying.

1 Like
5

They work and respond locally, but they do not throw smoke or co2 when they are detected. THe smoke detected will alarm at the device, but no responce from hubitat, same with my other devices mentioned. THe only ones that do respond are the Zwave Plus versions, non plus ate the issue.

Seems odd they would release it for production and leave so many issues and then not respond to the reports. Very dissapointed is support lately from the hubitat team. Makes me worry they are going away. And there is no road map of the future of hubitat. Guess thats what I get for investing in the C8 Pro. C5,C7,C8 anow C8 Pro.

And now newer zwave will not work on the Legacy, WTF

6

I think that's a pretty big leap to make from all of this...

I fully agree that it's frustrating that JS remediation is moving slowly, but it is happening... Bryan recently posted that he is testing some new avenues (perhaps a newer SDK? :person_shrugging:), so it is all still in motion. I suspect the issues discovered with running JS on older hubs was a bigger surprise than anticipated, so staff is likely being cautious to ensure that the next attempt is tighter and doesn't suffer that same fate.

There never has been, and likely never will - they keep their cards close.

5 Likes
7

I mostly agree with you

The legacy ZIP supports all devices, so not sure what you are talking about here.

2 Likes
8

Sorry to hear that you're disappointed. I can understand your concerns. Effort has been put towards Z-Wave certification and I can assure you that our engineers are working closely with the Z-Wave Alliance to address issues with newest Z-Wave implementation. From a strictly support perspective, we've had more success stories post JS release than issues, but with every new implementation, there are a few issues that some users may be impacted more than others.

4 Likes
9

Ya i have made a few posts abiut the issues taging hubitat and no responce, i now have 4 types of devices that have the issue. JS is much quicker and better, but i need my devices to work on JS. Is there anything i can do to help get atleast my First Alert Smoke detectors and utilitech waterleak, and utillitech sirens working

10

The not working issue is probably not related to this notification message you get. As I was getting it on working devices as well as many others.

You could try a combination of waking the device and the manual re-interview.
http://YOUR.HUB.IP/hub/zwave2/reinterview?node=NODE_ID
NODE_ID = Decimal (not hex) node ID from zwave details

I would disable the device in the hub device list so the driver does not respond back and end the wake. Then wake it up and within 10-30 seconds run the interview.

This might get it working, the interview has to complete for events to be processed properly.

As a last resort some people have just excluded and re-paired battery devices that would not cooperate.

1 Like
11

So I tried and no luck. I have removed and re-paired, but moving back to legacy they work again, so its a JS issue with some of my devices.