GE/Jasco (37392/ZW5307) not recognized in ZWave-JS

As the title says, the device is NOT recognized at all. I have <unknown> for the Manufacturer and Model within the Integration panel. But the Device Database indicates the integration should see it: https://devices.zwave-js.io/ and https://github.com/zwave-js/node-zwave-js/blob/master/packages/config/config/devices/0x0063/37792_zw5307.json

Any idea how to troubleshoot this? Of course, the device does not work and never gets “ready”, even after waiting and after reboots.

Thanks!

BTW, I also had the exact same issue with Model 34184 / ZW530. I also tried secure and unsecure inclusion with the same results.

Only idea I have is that it looks like it was recently created? 7 days ago. If you’re running less than 6.6.1, then you may not yet have it.

As far as I know, I am running the latest updates of everything… Where can I see the version you are mentioning (6.6.1) ?

If you’re using Zwave JS Addon, you’re running 6.5.0. If you’re running zwavejs2mqtt, you’re running 6.6.1.

I am NOT using zwavejs2mqtt. The version of the “official” add-on is 0.1.10:

The version of the addon is 0.1.10. The addon provides the zwave-js driver library and the zwave-js server application. Those components have their own versioning. The 0.1.10 addon does not provide the latest zwave-js versions. You can see the zwave-js versions in use in the integration configuration page.

2 Likes

This is mine:

image

The device is removed, hence the reason why is shows all devices are ready…

That seems to be one minor version behind, I’m not sure why… I’m at the latest stable Core and Supervisor.

Addon 0.1.10 is pinned to those versions. A new version of the addon would need to be released to update the zwave-js versions.

1 Like

version 0.1.11 is out, I will try that and report back… Thanks!

Unfortunately, the update only increases the server version to 1.1.1. The driver version is still 6.5.0. If you want something that updates more frequently, try the zwavejs2mqtt community addon.

1 Like

I installed ZWaveJS2mqtt. It’s much better with lots of cool features. It took a while but it finally recognized all my devices. I will play with it some more…

Thanks for the suggestion.

ZWave-JS now can see the device. However, something isn’t right. It discovered two entities, but they are wrong:

image

They show a Battery Level and Battery Low binary sensor. When I click on one of the buttons, these values change randomly. They are clearly not showing battery levels. In the logs, I do get a Central Scene Notification, but no binary entities are created. I could see that the payload is different from pushing one of the buttons. Is there a way to use this to create a scene or activate a device?:

image

That’s how they work, you need to perform actions off the zwave_js_event.

I was able to configure ZWaveJS2MQTT to send events to the HA MQTT broker and from there, I set up a few automations. Seems to work fine now.

BTW, there is still something not right about the battery levels being reported by the integration, but I will ignore them.

Thanks!

You don’t need to use MQTT for this, although you can if you want. The aforementioned zwave_js_event is emitted for Central Scene notifications.

1 Like

Yes, that seems to work when I listen to zwave_js_event. I will try that as well, although I’m not that familiar with triggering automations based on events data.