I just upgraded my Level Bolt from HomeKit to Matter, which on the whole is better.
When I used my lock before Matter, I could detect if the bolt had only been half-engaged. This would come across as “Jammed” via HomeKit and Home Assistant. I had an automation that would re-lock the door if it wasn’t fully locked.
With Matter, the lock reports this state via the LockState attribute on the DoorLock cluster as NotFullyLocked, but this gets mapped to unlocked in Home Assistant.
I don’t quite think it makes sense to map this back to jammed as before, since there is another way the lock is meant to report this condition. Would it be reasonable to introduce a new lock state in HA to support NotFullyLocked?
What is your set up using the new matter bolt firmware?
I just updated mine and added a sky connect to be the Open thread border router.
Shared credentials to my phone (IPV6 enabled on the HA host VM)
But I’m not able to add it to HA.
I’m using a HomePod Mini as the thread border router. I found the SkyConnect + OTBR combo to be unreliable (it would lose connection after some amount of time). It’s probably something to do with IPv6 addresses and routes, since my network is a little bit tricky.
Thanks for the info - I’m also trying with the SMLIGHT SLZB-06 which is a PoE thread OTBR or zigbee coordinator.
Figured I could then run some cable to make it a little more central to the matter devices.
I’m definitely missing something as I can’t add the device to my home instance, but there are no logs anywhere for the failed join.
So far to recap:
SLZB-06 has the matter over thread firmware
IPV6 is enabled on the HA OS VM (set to automatic)
OTBR add-on and set the SLZB-06 as the preferred network.
Matter server add-on
I am using a iOS device (which I have ‘sent credentials to phone’ for thread) on