I'm in the UK and have recently started setting up my new Hubitat to replace my very frustrating VeraPlus.
I have a Remotec ZRC90EU which I have managed to connect using stephack`s device driver. It was a PITA to get paired but finally It is on the system and I have a couple of button controller events programmed. However, pressing the appropriate buttons gives 4 quick flashes of the blue LED, the programmed action doesn't occur and nothing appears in the device event log. Any ideas? I presumed the US version commands would be the same as the EU but I'm now wondering if that's not the case.
Yeah, mine took about 10 attempts and I had to hold the device right next to the hub to pair.
When it paired, did it initially set itself as a generic driver or did it automatically use my custom driver?
If it went to the generic first, did you hit save and then configure after selecting the custom driver?
That shouldn't be necessary. That is usually how 3rd party devices get added.
Open the device page and click the configure button and test the remote again. If that doesn't work..go to Setting-> Zwave Info and make sure the remote is listed as Alive. Also check for any strange looking or blank devices. I remember when trying to pair this controller I ended up with a bunch of ghost devices. I had to remove them all, including the one I felt was valid and re-pair it again.
I had a lot of difficulty pairing this bad boy initially, so my guess is that it did not complete the pairing process properly.
I will rely on the expertise of @mike.maxwell on this one.
In the meantime, try to remove the remote and pair again. Do this VERY close to the hub and leave it there for at least 2 full minutes. It can take a long time to complete the process. Make sure to delete any ghost devices in the zwave information page before attempting to pair again.
I've removed and re-paired it with the remote lying right on top of the Hubitat Zwave dongle (it was more like full on mating than remote pairing!) and left it for 10 mins. The blue light on the Remotec stopped flashing after a short while but I left it anyway. The Hubitat never did list the device in the normal way. But a device did appear in the Zwave list which I then allocated to the Remotec device driver and it seemed to understand. This is the same as happened before but there is now a slight improvement in that it shows as ACTIVE in the Zwave table. However, still nothing happens when I press the buttons, to either the allocated button commands or in the Device Event Log.
I appreciate all of your help stephack, but I think I will put the Hubitat in a drawer for a while and wait until it's a bit more developed.
I currently use 3 of these remotes for my Vera, and if it is going to be this much of a pain to set them up on Hubitat, I would be jumping out of the frying pan into the fire to switch my system over.
I wouldn't be so hasty. This is not a standard device and took a while before it was working with ST reliably as well. The button controller app that is built in to Hubitat is not built to utilize the double taps on this device as well.
Also, I never updated the logging code (original author devised a custom method for logging) in the driver I ported from Hubitat because the effort to reward ratio was too low for me. I may revisit it in the future but right now it does not log events in the logs. You should be able to see the button presses in the device event list though. If i registers there, the device has been successfully paired and setup in HE.
I think it simply isn't pairing properly. I get the quick flashing blue led for every button press (which on Vera at least means the command has not been accepted by the controller) and nothing appears in the devices event list. My device details don't have the data that yours does for doubleTapped, held & pushed. My only entries there are battery, checkInterval and numberOfButtons. I will try to re-pair it again later. I've just checked out your ABC app which is perfect!! If only I can get this thing paired properly I will definitely be using that. Seeing all the button press settings in one screen is ideal.
I get 2 quick flashes with every button press on mine. I believe this is the same way it worked on SmartThings.
If I press and hold, it waits until I release and then I get the 2 flashes, so it seems to indicate when the remote sends the update that the button has been handled in some way.
Did you hit the configure button after re-paring as well?
So I've tried re-pairing this again, having reset the ZRC90 to factory settings just in case. It goes through the same process as before, only appearing in the Zwave list with a Discover button available. Hitting that gives the Device as "Device" but I can then select the Custom Driver, give it a name, save and then configure. It then shows the Number of Buttons as 8 and the CheckInterval as 86700. Later on I hit a button and noticed that the Battery level then appeared on the Events list (see below)
2018-06-01 5:18:38.214 PM BST
2018-06-01 4:49:28.557 PM BST
2018-06-01 4:49:28.552 PM BST
So the device is definitely communicating with the Hubitat, but no button presses are recognised or acted on and they never appear in the Device Event list.
I have programmed buttons 1 &2 using the excellent ABC mapping app but nothing happens.
When I press any button I get about 5 or 6 rapid flashes of the blue LED. According to the ZRC90 manual this indicates that the command or operation is invalid. I presume this is based on feedback from the Primary Controller as I occasionally get the same with a ZRC90 connected to my Vera when the Vera is having a bad day and doesn't respond to the commands.
I'm really running out of ideas about this, and am now wondering if it's something to do with the fact that I am using the add on EU Zwave Dongle? I'd be really interested to hear if anyone has got a ZRC90 working on an EU version to rule that out.
ok, just finished the driver for this, so it will be in the next build.
There is a trick to pairing it, this is due to the fact that we treat secondary controllers differently than standard zwave devices.
If you follow these steps you shouldn't have any issue pairing it.
1- factory reset it, hold the R button until the led turns on then off, follow this with a triple click.
2- open a window with the zwave information page
3- open a separate window and start device discovery
4- click the L button on the controller
5- refresh the zwave information page until you see the device show up with the discover button in the right column
6- click the discover button, the device name should now read "Remotec ZRC-90"
7- Exit the device discovery page, and the device should be ready to use.
I reset and paired the device three times using this method with the controller about 6' from the hub, no issues.
Eureka!! I think the key to this is making sure you hit discover while the ZRC90 is still in Learn mode. I was waiting too long and by the time I went to the Zwave list to hit Discover the ZRC90 wasn't listening anymore. Mine still didn't come up with device name "Remotec ZRC-90" and I had to select the custom driver (I guess that will only happen with the next release?) but I now have working buttons
This is the EXACT problem I'm having, I tried following the steps above but can't find the "discover" button on either the add page or z wave page, only the discover devices button, but instructions lead me to believe that's a different button..
Mike, this process has presumably changed now that there isn't a discover button on the Zwave info page, so what is the procedure for installing one of these now?
I'm trying to re install one of these and getting nowhere.
I have removed it from HE and factory reset it, but when I hit L on it and put HE into discovery mode, nothing appears on either the device discovery page or the zwave page by the time the blue led stops flashing on the ZRC90.
Thanks! I couldn't figure out for the life of me from the included manual which button to push on the controller for the pairing. Your instructions on factory reset with the R button and pairing with the L button are exactly what I needed. Paired without any problem with the normal Hubitat add ZWave process and built in driver.