theitprofessor Posted June 7, 2023 Posted June 7, 2023 I see some other folks experiencing door lock issues with ZMatter. So I bit the bullet and did a full move to Eisy and USB ZMatter with a PLM migration on top of it. Everything Insteon is perfect. ZMatter is another story. The issue, my Schlage door lock. Even though it is an S2 Lock it only works in one direction now, meaning I can execute anything from Eisy to the lock and it works fine, however anything that happens at the lock doesn't update on the the Eisy. I believe this has to do with ZMatter/S2 support itself and the reason I think this is everything worked just fine with ISY 300/500 and Polisy with Zooz 700. It stopped working in one direction when I moved to Eisy/Zmatter. Since the Polisy AC and the Eisy AC are basically the same the only thing that's different is ZMatter/S2 support which I did not have with the other three UD combination systems. I've done everything UD has asked me to do to resolve the issue and it just plain doesn't work. I have no idea if of when UD may choose to resolve this so I'm coming to grips that I may need to replace the lock now (ugh). I have 4 other Eisy upgrades/installations pending on hold because of the lock issue. What I looking for is anyone who has successfully moved their door lock to Eisy/ZMatter and has it working the way it should. If so, what make and model? Is this the time I ditch the ZWave door lock and move to a WiFi lock? That just opens up another can of worms and moves me away from a "universal system" that manages everything from one place!
tlightne Posted June 7, 2023 Posted June 7, 2023 I have three Kwikset 916 running Zwave connected to my Polisy and Zmatter board. They work with out issues. Polisy is 5.6.0.
gzahar Posted June 8, 2023 Posted June 8, 2023 On 6/6/2023 at 9:01 PM, theitprofessor said: I see some other folks experiencing door lock issues with ZMatter. So I bit the bullet and did a full move to Eisy and USB ZMatter with a PLM migration on top of it. Everything Insteon is perfect. ZMatter is another story. The issue, my Schlage door lock. Even though it is an S2 Lock it only works in one direction now, meaning I can execute anything from Eisy to the lock and it works fine, however anything that happens at the lock doesn't update on the the Eisy. I believe this has to do with ZMatter/S2 support itself and the reason I think this is everything worked just fine with ISY 300/500 and Polisy with Zooz 700. It stopped working in one direction when I moved to Eisy/Zmatter. Since the Polisy AC and the Eisy AC are basically the same the only thing that's different is ZMatter/S2 support which I did not have with the other three UD combination systems. I've done everything UD has asked me to do to resolve the issue and it just plain doesn't work. I have no idea if of when UD may choose to resolve this so I'm coming to grips that I may need to replace the lock now (ugh). I have 4 other Eisy upgrades/installations pending on hold because of the lock issue. What I looking for is anyone who has successfully moved their door lock to Eisy/ZMatter and has it working the way it should. If so, what make and model? Is this the time I ditch the ZWave door lock and move to a WiFi lock? That just opens up another can of worms and moves me away from a "universal system" that manages everything from one place! I am experiencing the same issue with one way operation (Schlage). I had 3 locks included with S0 from my ISY. After migrating to Polisy / Zmatter they still operated correctly. I tried to re-include several of them using S2 and that's when the reporting status issues started. If I recall, trying to go back and include on Zmatter with S0 caused no relevant nodes to be added (it's been a few updates ago, so may no longer be the case). As a work around for now, I query the lock(s) shortly after detecting the door being closed (using alarm system status). This keeps my lock status in sync over 95% of the time (obviously depends on your typical usage). 1
theitprofessor Posted June 12, 2023 Author Posted June 12, 2023 On 6/7/2023 at 9:47 PM, gzahar said: I am experiencing the same issue with one way operation (Schlage). I had 3 locks included with S0 from my ISY. After migrating to Polisy / Zmatter they still operated correctly. I tried to re-include several of them using S2 and that's when the reporting status issues started. If I recall, trying to go back and include on Zmatter with S0 caused no relevant nodes to be added (it's been a few updates ago, so may no longer be the case). As a work around for now, I query the lock(s) shortly after detecting the door being closed (using alarm system status). This keeps my lock status in sync over 95% of the time (obviously depends on your typical usage). Thanks gzahar, good to know it's not just me. I really believe there's some incompatibility issue between the S2 code with the new ZWave/ZMatter and the Schlage locks. When I was on Polisy with ZWave it worked fine and I had a 700 series (S2) ZWave controller in my Polisy but it was configured with S0 because UDI hadn't released the S2 code for the Polisy yet.
theitprofessor Posted June 12, 2023 Author Posted June 12, 2023 On 6/6/2023 at 7:40 PM, tlightne said: I have three Kwikset 916 running Zwave connected to my Polisy and Zmatter board. They work with out issues. Polisy is 5.6.0. A few questions please. 1. Did you do a software based ZWave migration to start using the ZMatter or did you rebuild your ZWave network from scratch? 2. Did you actually enable ZMatter? It's not enabled by default and when you enabled it you will need to rebuild the ZWave network. 3. Are you sure your locks are running at S2 and not S0. The issue we are seeing seems to be related to S2.
tlightne Posted June 12, 2023 Posted June 12, 2023 (edited) @theitprofessor I initially did the migration but one did not install all the nodes. I had to exclude it and include it with S2 before it would install all the nodes. Looking at them in AC they show S0 so I would say they are not using S2. Edited June 12, 2023 by tlightne
stevesreed Posted June 21, 2023 Posted June 21, 2023 On 6/7/2023 at 9:47 PM, gzahar said: As a work around for now, I query the lock(s) shortly after detecting the door being closed (using alarm system status). That is a great idea! Thanks. I have a notification when I leave the door unlocked for more than 5 minutes, and they are getting annoying. This should "fix" the issue for now.
Recommended Posts