[APP][Pro] ID Lock Next

[Tore_Th]

Sure, where do I update Test?

I can confirm that it is NOT a problem between module/lock, as I just tried putting “8888” on spot 8 and similar on 9 - neither the indexes nor the codes have ever been used. Still, the log is “New user code not added due to duplicate code”

Current status/versions:

[c0d3x]

Test channel: ID Lock Next | Homey — though your screenshot shows you’re already on it (v2.6.0).

Your screenshot actually pinpoints the problem: “Låsens fastvare 0.0.0”. That field is the lock panel’s own firmware as reported through the Z-Wave module — zeros mean the module can’t communicate with the lock itself. In that state the module accepts codes into its own memory (and rejects “duplicates” against old leftovers in that memory — which is why even a brand-new code on a brand-new slot fails), but nothing is ever handed to the actual lock. So both of us were half right: it’s not the radio link to Homey, it’s the connection between the plug-in module and the lock.

The fix: take the batteries out, pull the Z-Wave module out of its slot, seat it back in firmly, and reinsert the batteries — the lock should announce the module. Don’t use the keypad menu’s module reset — that can unpair the lock from Homey. Afterwards, press “Refresh from lock” in the app and check the Update page: “Låsens fastvare” should now show a real version like 1.5.x. If it does, add a test code — and if it shows something below 1.4.9, your lock panel’s firmware is too old for module 1.6 and needs ID Lock’s own updater. The next app update (2.6.1) will detect this 0.0.0 state and warn about it directly on that page.

Code sync works fine on my lock since my lock firmware is detected correctly.

[Tore_Th]

Thanks for troubleshooting! After removing/reinstalling and refreshing, it’s still v0:

Idlock updater app shows no updates, and I know I updated within last 6 months.

Edit: hold on, the updater found an update now after the reset. Let’s see if it helps

[c0d3x]

Thanks for trying that. Since re-seating didn’t change it, I need three data points to pin this down:

1. Which lock is it physically — ID Lock 150 or 202 Multi? (It matters: the app label says 150/202, but the two panels behave differently, and everything we know about firmware versions comes from the 150.)
2. On the Users page, tap “Sjekk koder på låsen” and tell me what it says — how many codes it finds, or the error if it fails. This reads the code slots directly through the module, so it tells us whether the module↔lock connection works for codes at all (independent of the version display).
3. Program a brand-new code at the keypad, confirm it opens the door, then run the scan again — does the app now see that slot as occupied? If yes, the link is alive and 0.0.0 is a version-reporting quirk; if the scan can’t see it, the module really is cut off from the code registry.

Then go to Diagnostics, enable verbose logging, press “Oppdater fra låsen” once, and send me a new diagnostic report — it captures the lock’s raw version answer, so I can see whether it truly reports zeros or my parsing misreads your model’s reply.

---

First update to v2.6.2 before you try this.

[Tore_Th]

It’s a 150, and we’re in business now after fw-update! “Sjekk koder” however doesn’t seem to so anything, but I could just add what I knew was slot 1, and delete it again.

I can confirm now both deleting and adding codes work edit seems more quirky, and pulling the codes, but that’s not critical function.

[c0d3x]

Good to hear!

• The check codes feature takes about 60 seconds to check all the 25 slots. So just be a bit patient, dont do any updates while doing this check.
• Edit code should work, what is the quirk?

I might disable the functionality while the “Check codes” is running so it dont create issues.

[c0d3x]

Ok, I have disabled interactions while doing the code checking, so should be less quirks!

[Tore_Th]

OK thanks,

I will investigate a bit more..! A tip: it does not seem “door was unlocked” is triggered by manual/button unlock from inside, unless it is also activated for timeline logging.

I have this flow, and it did not trigger until I asked the app to include button-unlocks in the timeline logging:

[Goran_Wiberg]

Hi there,

First of all, thanks for a fantastic app—I love it.

I have a question—perhaps I’ve misunderstood something—but the app says the lock’s firmware is 1.0.1, whereas the ID Lock Updater says I have version 1.5.9?

I’ve run the Updater a few times, but that hasn’t helped; I’ve also tried removing the batteries and the Z-Wave module, then putting them back in, but that didn’t work either, still version 1.0.1.

Am I misunderstanding something, or is something wrong?

[c0d3x]

Hi Goran — thanks, glad you like it! Nothing’s wrong, you’re just looking at
two different chips:

• The ID Lock Updater shows your LOCK’s own firmware (keypad/motor), updated
  over Bluetooth. 1.5.9 is the latest — you’re fully up to date there.
• The app’s “Z-Wave firmware 1.5” is the separate Z-Wave MODULE that plugs
  into the lock. It has its own version numbering that happens to also start
  with 1.5 — unrelated to the 1.5.9 above.
• The app’s “Lock firmware 1.0.1” is the app trying to read the lock’s own
  firmware through the Z-Wave module. That reading is only accurate once the
  Z-Wave module is on version 1.6 — on the older 1.5 module it shows a
  placeholder, not your real 1.5.9. Safe to ignore it.

Short version: your lock firmware really is 1.5.9 and it’s the newest. Removing
batteries/module won’t change the 1.0.1 line — only a Z-Wave module on 1.6 makes
the app report the real number.

[Goran_Wiberg]

Okay, I get the picture now.
Thanks for the clarification.

Then I’m just waiting for someone to try upgrading via your app