Yale Z-Wave Module 2 and USB Z Wave stick?

Hardware
244

Thank you for the advice I have tried that and also removing the batteries for 10 mins

It happened a few weeks ago, the next day I rang yale And while on the phone it started working again.

The person I spoke with hadn’t heard of the issue before and asked me video if it happens again, I’ve now done that but with it being the Easter break they are closed until Tuesday (I’m in the UK).

I think it’s caput… :tired_face:

245

Is it more or less than 2 years? The warranty is 2 years, not 1:
https://help.yale.co.uk/for-what-period-of-time-is-the-yale-alarm-warranty-valid-for/

1 Like
246

2yrs last Oct :neutral_face:
Now there is one thing it first happened when I switched over to zwave js and used HA to unlock the door. Knowing I couldn’t ring yale until the morning I switched back to the old zwave in HA (as mentioned it was still doing it, until the moment I got in contact with yale :face_with_symbols_over_mouth:) .

That said, I moved the entire system to a new rpi and SSD and this time installed Zwave JS straight away, that was 1 week ago. This morning I hit the unlock button in HA (which I’ve done numerous times this week) and it started happening again.

Now I’m pretty sure is a coincidence… Right?!

247

lol I love coincidences.
I’m with ZwaveJS at the mo. Not tried to go back, because I only have this lock on it.
I know the battery level doesn’t report on time, and for now the alarmtype doesn’t report at all, but It’s not mission critical so I can live with it until it gets fixed (though I really should see if this has been reported and report it myself if not)…

EDIT: our AlarmType issue may be related to the fact that RElease 3.0.0 (zwavejs V7) is incompatible with HA versions before 2021.4.x:


https://zwave-js.github.io/node-zwave-js/#/getting-started/migrating-to-v7

1 Like
248

Really! Me not so much right now :neutral_face: lol
I always work on a process of a limitation, and thats the one thing that connects to the two events.

Again I can’t see how it could be, but the back of my head says… But could it.

This yale lock is my only z wave device too.

Currently I’ve accepted the facts: it’s broken and I’m out of warrently and I’ve been unlucky to have a fault no one else on the entire Internet has reported/mentioned (until now)

so I’ve ordered a new one :grimacing:

2 Likes
249

Slightly off HA topic, but has anyone managed to get 3rd party RFID tags to work directly with the lock?

I have a RFID tag on the outside wall next to the door that is linked to an iOS shortcut that when I tap my iPhone it uses HA to open the door, but It would be great to be able to pair a 3rd party fob to the door.

250

I’ve tried quite a few different ones but can’t get any to pair. I’ve just slipped the Yale sticker in between my phone and case.

1 Like
251

Interesting video here where someone tried to clone the cards/tags

He doesn’t say anything about putting it on a mobile device, only how he was able to clone the card, which then stops the true card from working.

1 Like
252

This hasn’t been reported to my knowledge if it needs the alarm type/value mapping. It’s an easy add if it needs it but no one has asked for it to be mapped. I believe they rescinded that incompatibility note after the email went out though I could be wrong.

253

I was hoping that 2021.4 would resolve the issue, since there was a breaking change annonced on ZW-JS
Just created an issue: https://github.com/zwave-js/zwavejs2mqtt/issues/1028…

254

Wait, if it used to work then this isn’t this issue I’m referring to. You’re going to need to post logs in the issue.

255

This has started with mine too, no updates on them but everything else works.
Did you try and exclude and re-include the lock ? Don’t know if its worth trying that

256

Hi guys,
I’ve noticed the the new z wave integration only updates the alarm level when it detects a different key.

This is a real pain as I have an automation that turns my alarm off if it detects one of our keys, so I only use one key the automation doesn’t trigger.

257

Hi,

Same here with my Yale Conexis L1 lock - stuck on ‘alarmType 144’.
Very annoying, it was good to know when the lock gets jammed by someone not lifting handle properly.

I have tried downgrading to Core-2021.3.4 and still no joy.
I actually downgraded because of the sluggish UI while trying to amend Automations in version 2021.4…onwards, not usable with large automations on the RPI4.

Hope there is a fix on the Zwave-js server soon!

258

I had to switch back to the old zwave, not being able to run my automation that are based on certain keys is no good to me.

Fingers crossed they work on it,

259

Thanks Phairplay.

What Zwave version have you gone back to, an older zwave-js server or an integration?

alarmType did work well a while ago, with all the upgrades its confusing to remember at what stage it broke. :slight_smile:

260

I’ve moved back to the Z-Wave (deprecated) integration until a possible fix is in place.

261

On the Ultion I believe that is a Danalock 3 so if you can integrate Danlock 3 it should work. I believe others have it working with Conbee II stick.

262

Hi all,
I noticed the z-wave JS has been updated and has an update to this lock and its mapping.

The issue I saw that made me drop back to the old zwave config was it didn’t capture who unlocked the door on every occasion (based on the fob). It would only update when a different fob was used.

Can someone on the js z wave confirm if this is still the case.

:grinning:

263

I can’t really see any improvements to be honest.
Not sure what I’m looking for here though, but the AlarmType and AlarmLevel entitites aren’t giving me the info I’m after.
At the moment I’m getting by with a template sensor that is a combination of the lock status and the AlarmType and AlarmLevel entitites :
I have 1 sensor that extracts information from the AlarmType and AlarmLevel entitites:

- platform: template
  sensors:
    yale_alarmtype_status:
      value_template: >
        {% if states("sensor.yale_conexis_l1_alarmtype") == "144" and states("sensor.yale_conexis_l1_alarmlevel") == "2" %}Unlocked by RFID tag (Div)
        {% elif states("sensor.yale_conexis_l1_alarmtype") == "144" and states("sensor.yale_conexis_l1_alarmlevel") == "3" %}Unlocked by RFID tag (Lolo)
        {% elif states("sensor.yale_conexis_l1_alarmtype") == "16"  %}Unlocked by Yale App
        {% endif %}

then I have a temnplate trigger sensor to combine all sensors into a single one:

template:
  - trigger:
      - platform: event
        event_type: zwave_js_notification
    sensor:
      - name: "Yale Notification Status"
        state: "{{ trigger.event.data.event_label }}"
  - trigger:
    - platform: state
      entity_id:
      - sensor.yale_notification_status
      - sensor.yale_alarmtype_status
      - lock.yale_conexis_l1_lock
    sensor:
      - name: "Porch Door Lock Status"
        state: "{{ trigger.to_state.state | title}}"

The above is a trigger template sensor, so it takes the state from the sensor that changed last.
It kinda works for me for now, though it’s a bit scrappy.
I’m also having to use automations to force pull sensor data like the battery else it does not update automatically.
I can’t be *rsed to go back so I’ve done this for now.

1 Like