I have published a test version of ID Lock Next a new community app for ID Lock smart locks on Homey Pro.
Install test version:
ID Lock Next is a ground-up, independent app for ID Lock smart door locks. It supports both Z-Wave and Zigbee through the same app, so the same settings, flows and user management should work no matter which module your lock uses.
Supported locks
ID Lock 101 - Z-Wave
ID Lock 150 - Z-Wave or Zigbee
ID Lock 202 - Z-Wave or Zigbee, using the same module/driver approach as ID Lock 150
Main features
Lock and unlock from Homey
Door open/closed, battery, tamper and heat alarm status
See who unlocked the door and how, for example PIN, RFID, manual, app or auto
User and PIN management from the app settings
Add, change and clear PIN codes
Master PIN support for Z-Wave
Import/export user list
Queue-based PIN synchronization with synced, pending and failed status per user
Notifications for lock events
Activity/audit log
Diagnostics page with health overview and downloadable report
Flow triggers for locked, unlocked and jammed events
Flow actions and conditions for away mode, auto-lock, service PIN, refresh and last user checks
Away mode support, including keypad sync using code + *
Advanced lock settings such as auto-lock, relock, sound volume and hinge direction
Z-Wave firmware update support through Homey
English, Norwegian and Swedish translations
Test status
This is currently a TEST release.
The main feature set is implemented. The ID Lock 150 Z-Wave and Zigbee modules have been developed against real hardware. ID Lock 101 and ID Lock 202 use the same command classes/module behavior, but I would especially appreciate feedback from users with those models.
Important note about Z-Wave firmware updates:
The app includes embedded official ID Lock Z-Wave firmware files for different lock models, but the OTA update feature has not yet been tested or verified by me. Using this feature is NOT ADVISED at this stage.
If you choose to try it anyway, you do so entirely at your own risk and responsibility. I take no responsibility whatsoever for failed updates, broken firmware, lock malfunction, loss of functionality, re-pairing issues, or any other problems caused by using the Z-Wave OTA firmware update feature.
Please report:
Pairing issues
Missing or wrong lock status
PIN/user sync problems
Flow cards that do not behave as expected
Translation mistakes
Anything else that looks unstable or unclear
Known roadmap item:
Codes added directly on the lock keypad are not yet fully reconciled back into the user list.
This is an independent community project. It is not affiliated with, endorsed by, or supported by ID Lock AS. Since this controls a door lock, please test carefully and use at your own risk.
Good catch — the changelog wording oversold this. The Away history is recorded, but Homey only shows yes/no insights in the mobile app: open the lock device and tap the Away tile to see the on/off history (Homey keeps the last ~50 events). They never appear in my.homey.app’s Insights — the web app only charts numeric logs, so even the built-in “Locked” log isn’t shown there. That’s platform behavior, not something the app controls.
And as you noted, the “Away mode is on” condition card is the intended way to use it in Flows — boolean tags don’t show in text/number Logic fields either. I’ll phrase future changelogs as “history in the mobile app” to avoid the confusion.
Im just wondering… If you have the door settings in app level settings and not in the device settings, how can you manage if the app have more than one lock?
How does the settings work in my house, garage and cabin?
This is mockdata, so would be nice if someone could verify that it works correctly
There are more specific lock settings in Advanced Settings in the device itself that are not available in the Settings pages.
But codes and tags need to be defined in the Settings pages or by flows that allow it with service codes.
Bare ett tips du kan bruke i dine flowkort condition er å bruke inverter så slipper du så mange like kort. Du finner det sdk3 dok Flow | Homey Apps SDK
When a PIN code can’t be synced to the lock, the app now notifies you and names the user — a new toggle on the Notifications screen, on by default. Plus fixes: the “PIN code failed to sync” Flow card no longer shows a raw [[user]] placeholder, and the new app icon now sits centered. Existing locks pick it up automatically — no re-pairing needed.
2.0.0
A fresh look for ID Lock Next. A redesigned app icon and a new brand colour, plus distinct icons for the Away mode toggle and the Last unlock method and Last unlock user sensor tiles — these previously all reused the generic app icon. The device icons have been refreshed too. This is a visual update; the app’s functionality is unchanged from 1.9.0.
Reliability & new automations. A lock now shows as Unavailable when it stops responding, and a tile warning flags any PIN code that failed to sync. New Flow cards: “a PIN code failed to sync”, “the door has been left open” (with a configurable alert time in the device’s advanced settings), “battery is below …%”, and a Z-Wave “too many wrong codes” security trigger. New “Clear sync queue” maintenance action, and the settings app now updates live. Existing locks pick everything up automatically — no re-pairing needed.
Simpler Flow cards: the separate locked/unlocked, per-user lock/unlock, and away-mode on/off cards are now single cards with a dropdown, so there’s less to scroll through. Please rebuild any Flow that used the old “door was locked/unlocked”, “a specific user locked/unlocked”, “was the last to lock/unlock”, or “away mode activated/deactivated” cards.
Hi Kenneth — thanks for flagging this, and sorry it’s being stubborn. There are two things going on:
Why the device history shows only “Ulåst/Låst”: that built-in timeline only logs the lock’s state, and Homey always credits the change to the app itself (“ID Lock Next”) — an app can’t put a person in that particular list. The “who” is meant to show up in three other places instead:
On the lock, the Last unlock user and Last unlock method tiles.
The Who tag from the “The door was locked or unlocked” Flow trigger — drop it into a notification action.
A timeline notification, if you enable “Unlocked by PIN code” in the app’s Notifications settings.
But — if none of those are showing the user either, then your lock may not be handing the app the user/PIN on unlock, and until now the app wasn’t logging what the lock actually sends, so I couldn’t tell which it was. That’s the key thing I’ve changed.
In the next update (2.1.0, releasing shortly):
The app now logs exactly what the lock transmits on each lock/unlock, so a diagnostics report will reveal whether your lock is sending the user ID at all.
It’s more robust at reporting the method (PIN/RFID) and firing your Flow even when the lock leaves the user out.
“Unlocked by PIN/RFID” notifications are on by default.
To help me pin it down: once you’re on 2.1.0, unlock the door with a PIN a couple of times, then create a diagnostic report for ID Lock Next from the app, with a short note like “unlocked with PIN around HH:MM.” That’ll tell me whether to fix the decoding or whether it’s a lock-side setting — and I’ll get you sorted from there.
One quick check in the meantime: make sure each PIN is added under Users in the app — that’s what maps a code to a name (otherwise it shows “Unknown (code N)” instead of the person).
Hi Kenneth — quick update. Your diagnostics actually confirmed the app side is working: when the lock sends the keypad-unlock event, it now correctly reads it as “Unlocked by Kenneth (PIN)” and fires the notification. The snag is your lock only sent that event once across your ~5 PIN unlocks — so what’s missing is the lock not reporting every unlock over Z-Wave, not the app misreading it.
The latest update turns the “who unlocked” notification on by default and adds a Verbose logging toggle on the lock’s Diagnostics page for future troubleshooting. If it stays flaky, it’s worth strengthening the Z-Wave link to the lock (your log showed Homey struggles to reach it) — a mains-powered Z-Wave device nearby as a repeater, plus a network heal, usually does it.
Activate this before testing, and if you need to provide a debug log in the future:
Just swapped to this app from the old. Teamly easy to pair the locks. One of my locks my 101 has 1.0 firmware. And the app says its up to date when i try to update it. Any idea or should i put the zwave module in my 150 lock and try to update it since that can update with idlock app. ???
im gonna test it an reply
