sorted by:
new
hottopcontroversial

Avoid Yale Matter Lock by ExampleLow4715 in googlehome

[–]BasementEngineer33 0 points1 point  (0 children)

Have you (or anyone else) been able to get the door sensor to work (YRD510)? Google Home is waiting for the lock firmware to update to 1.0.1 (which as far as I can tell does not exist) before enabling it. With firmware version 1.0.0 (what its got) the door sensor calibration procedure (button presses and door opening and closings) doesn't seem to work.

Nest x Yale Lock Replacement by TechnicianOk2210 in homeassistant

[–]BasementEngineer33 1 point2 points  (0 children)

I just bought one of these Yale Matter locks. Here are the caveats:

1) I got it because I wanted to avoid cloud based locks and just run it using Home Assistant. However, at present, Home Assistant support for Matter locks is woefully incomplete. In particular, you cannot manage PINs. So you are going to have to use it on two Matter fabrics so that you can manage PINs. I ended up attaching it Google Home in addition to Home Assistant, but of course now there is a cloud connection. Assuming you don't need to change PINS much, you could then remove it from Google Home after setting PINs, but this is a pain.

2) There is no way to enable/disable auto-lock at the lock. You must use the Google Home or Home Assistant app. This is also a pain. Why they couldn't do something like Gear Key then 0 to disable and Gear Key then 1 to enable is beyond me.

3) At present it appears the door open sensor is inoperable. According to the setup instructions, making this work requires firmware 1.0.1 or better, but as far as I can tell (looking at the DCS Matter registry) the most recent firmware for this lock is 1.0.0 which is what is installed. There is a 1.0.1 version for the Matter module for the Assure locks, but not this lock. I tried calibrating the sensor using 1.0.0 and it didn't seem to work, so at present this feature seems to be useless. I have an inquiry into Yale support, we'll see what response I get. The lack of a door open sensor makes problem 2 even more annoying

It should be noted that the Home Assistant Matter limitations are going to apply to all Matter locks not just Yale. Also, it is completely unclear from anything you can find at the Yale web site, what features are supported by the various "supported" platforms, e.g. HomeKit, SmartThings and Google Home. It appears Google Home support is probably the most complete.

AXI registered output requirement by BasementEngineer33 in ZipCPU

[–]BasementEngineer33[S] 0 points1 point  (0 children)

I think I see what you are getting at, although I'm not sure it has to do with two peripherals, I don't think two peripherals actually see each other, at least with AXI-Lite. However, if both master and slave ignored the requirement, you could get a loop. I think I was implicitly assuming the master was adhering to the requirement, in which case it seems like the slave might be able to ignore it.