I have been using a HomePro ZRP230 switch module for a couple of months now and suddenly it got broken for no special reason. I received a replacement module, which is working fine (I can switch it on/off with the button on the module itself). However, when trying to add this new module to my Z-Wave network, I see following debug log messages and the device is not added to my network:
2012-09-30 09:48:28,266 Z-Wave.ERROR Callback received, but no corresponding job in queue. Continue operations as if it is in queue.
2012-09-30 09:48:28,266 Z-Wave.DEBUG RECEIVED: ( 01 07 00 4A A0 06 00 00 14 )
2012-09-30 09:48:28,192 Z-Wave.DEBUG Removing job: Add/re-include node to network: Stop
2012-09-30 09:48:28,192 Z-Wave.DEBUG RECEIVED ACK
2012-09-30 09:48:28,108 Z-Wave.DEBUG SENDING (cb 0x00): ( 01 04 00 4A C5 74 )
2012-09-30 09:48:28,098 Z-Wave.DEBUG Removing job: Add/re-include node to network: Start
2012-09-30 09:48:28,098 Z-Wave.DEBUG Adding job: Add/re-include node to network: Stop
2012-09-30 09:48:28,097 Z-Wave.INFO Add/re-include node to network: Start: Failed
2012-09-30 09:48:28,097 Z-Wave.DEBUG RECEIVED: ( 01 07 00 4A A0 07 00 00 15 )
2012-09-30 09:48:27,307 Z-Wave.INFO Add/re-include node to network: Start: Node found: node 0
2012-09-30 09:48:27,307 Z-Wave.DEBUG RECEIVED: ( 01 07 00 4A A0 02 00 00 10 )
2012-09-30 09:48:25,530 Z-Wave.INFO Add/re-include node to network: Start: Ready to add - push button on the device to be added
2012-09-30 09:48:25,529 Z-Wave.DEBUG RECEIVED: ( 01 07 00 4A A0 01 00 00 13 )
2012-09-30 09:48:25,457 Z-Wave.DEBUG RECEIVED ACK
2012-09-30 09:48:25,405 Z-Wave.DEBUG SENDING (cb 0xa0): ( 01 05 00 4A C1 A0 D1 )
2012-09-30 09:48:25,400 Z-Wave.DEBUG Adding job: Add/re-include node to network: Start
I tried adding it several times, but no luck so far. I also removed the broken device from my network first. Any idea what's going wrong here?
Unable to include HomePro ZRP230 replacement switch module
-
- Posts: 10
- Joined: 03 May 2012 12:54
First of all try to exclude this module first
It's a common rule: when something can not be included, exclude it first. This might happen due to some inconsistent state in your new ZRP230.
-
- Posts: 10
- Joined: 03 May 2012 12:54
I tried this before, but still the same result
In fact I tried this before (just to be sure the inclusion would work) and just tried once again excluding it first and including it afterwards, but no result so far...
I checked the job queue while including the device and noticed that it said "Node found: node 0" and then "Failed" after pushing the inclusion button on the switch module. Is this normal?
I checked the job queue while including the device and noticed that it said "Node found: node 0" and then "Failed" after pushing the inclusion button on the switch module. Is this normal?
This happened with us too several times with ACT devices
as well as with some other extremely old Merten devices. This seems to be a problem in the stick SDK. What is the stick and it's version. There were versions of SDK having these problems.
-
- Posts: 10
- Joined: 03 May 2012 12:54
This is the version information of the stick
Hardware
Vendor: Z-Wave.Me
Vendors Product ID: 1 / 1
Z-Wave Chip: ZW0301
Firmware
Library Type: Static Controller
SDK Version: 5.03
Serial API Version: 03.55
Vendor: Z-Wave.Me
Vendors Product ID: 1 / 1
Z-Wave Chip: ZW0301
Firmware
Library Type: Static Controller
SDK Version: 5.03
Serial API Version: 03.55
hm.. with 5.03 it should work.
We have seen this with our 4.54 sticks.
Anyway, your controller should be SUS/SIS, so you might use any other controller (portable or static) to include your ACT device. First of all try with one of your portable controller (you certainly have some).
Anyway, your controller should be SUS/SIS, so you might use any other controller (portable or static) to include your ACT device. First of all try with one of your portable controller (you certainly have some).
-
- Posts: 10
- Joined: 03 May 2012 12:54
Unfortunately, I don't have
Unfortunately, I don't have any portable controller (only the Z-Wave.Me-stick attached to my OpenWRT-router)
I still don't understand why I could include this device a couple of months ago, while it fails now for the replacement module. Well, I guess I'll have to buy a portable controller to get it working...
I still don't understand why I could include this device a couple of months ago, while it fails now for the replacement module. Well, I guess I'll have to buy a portable controller to get it working...
It might happen due to different versions of ACT devices
This probelm is far bayond our and ACTs capabilities - it is inside Z-Wave protocol. Unfortunatelly we are not able to solve it.
I can only suggest you to try exclude the device using someone else's controller and try to include it again.
Also check the manual - may be a single click sends only a NIF packet (so, Z-Way will see it and will write "Node found: 0", but the fail). May be triple click should be the right combination to put it into LearnMode? Same with exclusion.
I can only suggest you to try exclude the device using someone else's controller and try to include it again.
Also check the manual - may be a single click sends only a NIF packet (so, Z-Way will see it and will write "Node found: 0", but the fail). May be triple click should be the right combination to put it into LearnMode? Same with exclusion.
-
- Posts: 10
- Joined: 03 May 2012 12:54
Thanks for the suggestions, I
Thanks for the suggestions, I have tried both single and triple-clicks which might explain the confusing error messages. According to the documentation (http://www.act-remote.com/HPW/Inst/ZRP230_instr.pdf), a single click should be enough for the inclusion/exclusion process. Anyway, I'll see if I can get another controller if I'm still unable to include the device...
-
- Posts: 10
- Joined: 03 May 2012 12:54
For the record, I bought the
For the record, I bought the Aeon Labs Minimote remote and was able to exclude the device with this remote. Afterwards, including the device in Z-Way was no problem at all!