HC3 Z-Wave Engine 3 migration issue with ID Lock 150

[Jonas bergkvist 2]

Environment

• Home Center 3
• Firmware: 5.210.12
• Previously running Z-Wave Engine 2
• Migrated to Z-Wave Engine 3
• Approximately 40 Z-Wave devices in the network
• All other Z-Wave devices continue to work normally after migration

Problem

An ID Lock 150 that was previously fully functional stopped working immediately after the migration from Z-Wave Engine 2 to Z-Wave Engine 3.

The lock can no longer be controlled from HC3 and HC3 is unable to properly identify the device.

Current behavior

After inclusion, HC3 creates the lock device, but:

• Lock / Unlock commands do not work
• Device shows:
  • Z-Wave SDK version: 0.0
  • Version: 0.0
  • Security level: None
  • Parameters template: No
• Advanced / Parameters page generates API errors
• HC3 Diagnostics reports:
  • "No template"
• Browser console shows:
  • GET /api/zwave/hc/configuration/ returns HTTP 404

Example:

GET /api/zwave/hc/configuration/70 -> 404

Troubleshooting already performed

• Excluded lock from HC3
• Factory reset of ID Lock 150
• Factory reset of Z-Wave module
• Re-included multiple times
• Reconfigure device
• Read configuration
• Included using S2
• Included using S0
• Included without security
• Included using Network Wide Inclusion
• Included without Network Wide Inclusion
• Firmware updated on ID Lock 150

None of the above changes the behavior.

Important observation

The issue appeared immediately after migration from Z-Wave Engine 2 to Z-Wave Engine 3.

The lock worked correctly before the migration.

All other Z-Wave devices in the network continue to operate normally, including secure devices.

Because the lock shows SDK version 0.0, Version 0.0, Security None and No Template regardless of inclusion method, it appears HC3 is unable to fully interview or identify the device after the Engine 3 migration.

Could you please verify whether there are any known compatibility issues between HC3 Z-Wave Engine 3 and ID Lock 150, or if additional diagnostics can be collected to determine why the device interview fails?

[Support FIBARO 11]

Further discussion of the issue has been moved to a private channel.
After identifying the cause or resolving the issue, the appropriate information will be published. 

[Brors94 115]

8 hours ago, Jonas bergkvist said:

Environment

• Home Center 3
• Firmware: 5.210.12
• Previously running Z-Wave Engine 2
• Migrated to Z-Wave Engine 3
• Approximately 40 Z-Wave devices in the network
• All other Z-Wave devices continue to work normally after migration

Problem

An ID Lock 150 that was previously fully functional stopped working immediately after the migration from Z-Wave Engine 2 to Z-Wave Engine 3.

The lock can no longer be controlled from HC3 and HC3 is unable to properly identify the device.

Current behavior

After inclusion, HC3 creates the lock device, but:

• Lock / Unlock commands do not work
• Device shows:
  • Z-Wave SDK version: 0.0
  • Version: 0.0
  • Security level: None
  • Parameters template: No
• Advanced / Parameters page generates API errors
• HC3 Diagnostics reports:
  • "No template"
• Browser console shows:
  • GET /api/zwave/hc/configuration/ returns HTTP 404

Example:

GET /api/zwave/hc/configuration/70 -> 404

Troubleshooting already performed

• Excluded lock from HC3
• Factory reset of ID Lock 150
• Factory reset of Z-Wave module
• Re-included multiple times
• Reconfigure device
• Read configuration
• Included using S2
• Included using S0
• Included without security
• Included using Network Wide Inclusion
• Included without Network Wide Inclusion
• Firmware updated on ID Lock 150

None of the above changes the behavior.

Important observation

The issue appeared immediately after migration from Z-Wave Engine 2 to Z-Wave Engine 3.

The lock worked correctly before the migration.

All other Z-Wave devices in the network continue to operate normally, including secure devices.

Because the lock shows SDK version 0.0, Version 0.0, Security None and No Template regardless of inclusion method, it appears HC3 is unable to fully interview or identify the device after the Engine 3 migration.

Could you please verify whether there are any known compatibility issues between HC3 Z-Wave Engine 3 and ID Lock 150, or if additional diagnostics can be collected to determine why the device interview fails?

After My migration from eng2 to eng 3 I actually got more functionality on my id lock 150.
couldnt set code before, but now the code works from the web ui. 
Havent made a quickapp to make a new code just yet 😅
If I remember correct i reconfigured the device and did wake it up with enteringthe master code 🤔

Please login or register to see this image.

/monthly_2026_06/image.png.7e8f722665dd2bac3cdc8ed4eeac2e56.png" />

Please login or register to see this attachment.

[Jonas bergkvist 2]

28 minutes ago, Brors94 said:

After My migration from eng2 to eng 3 I actually got more functionality on my id lock 150.
couldnt set code before, but now the code works from the web ui. 
Havent made a quickapp to make a new code just yet 😅
If I remember correct i reconfigured the device and did wake it up with enteringthe master code 🤔

Please login or register to see this link.

Please login or register to see this attachment.

Yeah, it worked perfectly for me on Z-Wave Engine 2. After the migration to Engine 3 it stopped working completely, which is really strange.
 

I also upgraded the ID Lock 150 to the latest firmware using the official mobile app, but unfortunately that didn't resolve the issue either.
 

To be honest, when it was working, it was absolutely amazing. The lock was very stable and reliable, and I was extremely happy with how well it integrated with Fibaro HC3. That's why I'm putting quite a bit of effort into troubleshooting this issue and trying to get it working again.

Hopefully we can find the root cause, not only for my setup but also so other users don't run into the same issue in the future. If we manage to identify the problem and solution

[Brors94 115]

6 minutes ago, Jonas bergkvist said:

Yeah, it worked perfectly for me on Z-Wave Engine 2. After the migration to Engine 3 it stopped working completely, which is really strange.
 

I also upgraded the ID Lock 150 to the latest firmware using the official mobile app, but unfortunately that didn't resolve the issue either.
 

To be honest, when it was working, it was absolutely amazing. The lock was very stable and reliable, and I was extremely happy with how well it integrated with Fibaro HC3. That's why I'm putting quite a bit of effort into troubleshooting this issue and trying to get it working again.

Hopefully we can find the root cause, not only for my setup but also so other users don't run into the same issue in the future. If we manage to identify the problem and solution

Yea, hope they find the cause
I am considering the IDlock 202, that uses the same z-wave module for another door in my home  

If the support need a idlock 150 that works on eng3 to see the diffrence they could check out mine if they want to.  

Btw as you see in my pictures it is included with s0 security. 
And when I first included it the HC3 had to be on the side of the lock (move the hc3 to the door and try to include it with s0 security) 
 

Edited 7 hours ago by Brors94

[Jonas bergkvist 2]

20 minutes ago, Brors94 said:

Yea, hope they find the cause
I am considering the IDlock 202, that uses the same z-wave module for another door in my home  

If the support need a idlock 150 that works on eng3 to see the diffrence they could check out mine if they want to.  

Btw as you see in my pictures it is included with s0 security. 
And when I first included it the HC3 had to be on the side of the lock (move the hc3 to the door and try to include it with s0 security) 
 

My guess is that the ID Lock 202 would behave exactly the same way, since it uses the same Z-Wave module. Of course, I could be wrong, but that would be my expectation.
 

One thing worth noting is that running the lock with S0 security means you're missing one of the coolest features. With S2 security, HC3 receives information about which user/PIN code unlocked the door.
That makes it possible to create automations based on who actually entered the house, which is incredibly useful and fun.

[Brors94 115]

3 minutes ago, Jonas bergkvist said:

My guess is that the ID Lock 202 would behave exactly the same way, since it uses the same Z-Wave module. Of course, I could be wrong, but that would be my expectation.
 

One thing worth noting is that running the lock with S0 security means you're missing one of the coolest features. With S2 security, HC3 receives information about which user/PIN code unlocked the door.
That makes it possible to create automations based on who actually entered the house, which is incredibly useful and fun.

Hmm this is a good point!

I will wait to here from you first before removing it and adding it with s2 😅

So please come and post if you find a solution