I think zwavejs just took all device configs from openzwave so support should be same. Maybe there is other issue? Maybe try remove and readd one of the devices or check the device list for zwavejs and verify support.
I reverted back to Zwave 1.4 via a previous backup and things are back to normal, with complete support for my devices.
I’ll wait awhile before attempting the migration again. Hopefully the integration will be more complete in the future and won’t break things, at least for my devices.
Did you checked entities disabled by default on devices in Zwave JS? I found that plenty of sensors I’ve been using were disabled, as apparently less frequently used… After turning some of them in configuration panel I did not missed any of these I used with old integration.
1 Like
Like others said, check disabled sensors. Also, a lot of sensors are now events. For example, my Schlage lock reports events when user codes are entered vs a sensor like it was in the old Z Wave. I think you may have given up too early.
This website gives a good idea of what devices are available in ZWaveJS and what is exposed.
https://devices.zwave-js.io/
I’d also recommend ZWaveJS2MQTT over just ZWaveJS since you get a nice GUI to troubleshoot and explore.
1 Like
Thanks for the feedback and suggestions.
You may be right about the sensor / event difference, but given that this wasn’t a drop-in replacement (functionally, at least), reverting back at least meant I didn’t have to re-think / re-write my automations.
The site you referenced is a little lean on information about something as complex as a lock, or at least my lock. The Yale lock can report a ton of information and the minimal doc on the Zwave-js site doesn’t reflect most of it.
Regarding ZWaveJS2MQTT - I was intrigued but couldn’t figure out how to install it, despite searching a lot of contradictory posts. Unless it’s in a HACs repo, it’s not appearing when I search either my integrations or Supervisor add-ons. And since everything I have is self-contained, I wasn’t really interested in spinning up a Docker container just for a nicer GUI.
Maybe I’m just lazy, but I have solved enough complex HA-related issues to go looking for more complexity when I have something that ‘just works’.
ZWaveJS2MQTT is under community addons. Dont install ZWaveJS if you install ZWaveJS2MQTT though. They do exactly the same thing, one just has the GUI. It is extremely helpful in some cases BTW.
You are right the config page is lacking in some areas. Some devices are very populated though. My Schlage lock doesn’t show much on there. But again, the GUI is nice because it shows you what sensors should be available and you can manually set lock codes and things like that a little easier if you aren’t using an automation package like Keymaster. Events you just need to set a listener and input some user codes to see what comes across. You can also contribute to the device page since it is an open source project.
Anyways, stick with the old Zwave if it works for you for now. Not sure what the developers plans are to phase it out eventually. If nothing else, take a snapshot, migrate over and mess around to see how your automations are affected. Then restore and repeat as necessary.
1 Like
This may or may not be on topic, does anybody have an automation trigger for specific user code entries for Z-Wave locks? Like User Code 1 Used was on Hubitat that I used in the past.
I see these in the automation UI:
If you have any examples I’d appreciate it.
Thanks.
Cant go too in depth at the moment, but under Developer Tools → Events, subscribe to these topics:
zwave_js_value_notification
zwave_js_notification
Then enter some codes and look at the output. You should be able to create an automation based on an event from that data.
1 Like
Thanks I was testing that as my wife arrived home and saw something like this:
I’ll play around a little more when I can push the buttons.
Trying to move away from geo presence.
My Schlage locks have a userid field that works well along with the event type to see if its unlock or lock. Hopefully that will show up when you try some user codes.
1 Like
I too am seeing a difference in the available sensors between ozw and the zwavejs for my door lock.
My Schlage BE468 automation in node-red used sensors access control (lock “event” i.e. pad entry, knob, or the Schlage button) and alarm level (index into the user code array). The BE468 has been working great since early 2018 with node-red and homeassistant versions 0.99 and earlier.
I have been trying to move to a new homeassitant environment (both hardware and software) since the first of November. Today I built an entirely new core-2021.12.10 environment using zwavejsmqtt 0.34.1 and a brand new Aeotec z-stick Gen5+. Try as I may for the past two months, the access control and alarm level sensors are not available for the BE468 using zwavejs-based integration.
So I am stuck. Like you, i don’t use geo location. The Schlage keypad is king for indicating occupant presence in the house. Not sure where to go from here.
I have successfully installed multiple iBlinds v3 with latest Home Assistant Zwave JS and they work great.
The controls work great using cover.open, close, and set position services.
However, I would prefer they use the cover.set_cover_tile_position, cover.open_cover_tilt, and cover.close_cover_tilt services, that more accurately reflect what the iblinds are controlling - rather than the position that they do not control at all.
Can anyone help with a way to configure this?
You’ll have to make template covers in order to handle this. Then you’d need to use the newly created template cover everywhere instead of the Zwave cover.
I migrated to zwave-js. I finally got BE489 lock to work user keypad notification based on this blog https://thissmart.house/2021/07/05/z-wave-js-locks-in-home-assistant-now-see-who-opened-the-door/ but I simplify it a little bit and come up with this automation
- id: 'xxx'
alias: Unlock By User Zwave JS
description: ''
trigger:
- platform: event
event_type: zwave_js_notification
condition:
- condition: template
value_template: '{{ trigger.event.data.device_id == ''[replace with your device_id]'' }}'
- condition: template
value_template: '{{ trigger.event.data.event == 6 }}'
action:
- data_template:
message: Front door unlocked by {{[ 'Unknown', 'User1', 'User2', 'User 3',
'user 4', 'user 5', 'user 6', 'User 7'][trigger.event.data.parameters.userId]}}
service: notify.phonexxx
I have a question. Did you have any problem adding the YRD-110 device. I have a newly installed Zooz_ZST10_700_Z-Wave controller that can't seem to find the YRD-110 lock. I have even done the factory reset on the lock and gone through the instructions to join the network, but can't get the two to talk to each other. Did you just follow the standard device installation?
I did a master reset on all my YRD-110 devices. Unfortunately, you need to ensure you have a strong zwave network surrounding these devices or they just won’t work due to weak antennas. You may also need to add them close to the zwave stick.
FYI: we moved to a new home which means new opportunities to do something different. Not using zwave at all in this new home and only Lutron, WiFi, Zigbee and August locks now.