Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
New Z-Wave driver preview
Am I the only one trying to make the new ZWAVE driver work with a SmartThings hub as a primary controller? Wired devices work fine and show up properly, battery operated Yale locks works just fine. All other battery devices I have will not add into CQC. CQC knows that they are there but I cannot get them to talk properly.

I'm testing with a Linear WADWAZ-1. According to the device documentation I should simply have to open the case to wake it up, tried that. Also tried pulling the battery and re-inserting. Still won't get picked up. Tried forcing the configuration to the correct MFG, Unit type, no dice.

Why is it that the Yale locks will work, even though they are battery but other battery devices won't? That's a puzzler. The fact that they do work indicates that any battery device in theory should work. The only difference perhaps is that they are using the secured zwave protocol but why should that matter?
Locks are not really battery powered. They are 'frequent listeners' so they can be talked to at any time. Real battery powered units are a different deal.

What state are those units in? That will tell us more about what is going on.

If you swap the batteries and that doesn't work, that may mean that it's a not so helpful unit that doesn't send out a node information frame in that case. Though, you may also need to wait 30 seconds or so to make sure any capacitors bleed that might keep it alive for a short period of time.

If that doesn't work, then enable the trace (or flush it if currently on) and do the battery, then close the trace and post the file. If it's broadcasting the node info frame we should be able to see it.

As to setting it manually, what do you mean no dice? That should always work. When you do that, does it go to WaitApprove? If you then approve it, does it go to ready state?
Dean Roddey
Software Geek Extraordinaire
I mean that it goes to WaitApprove, goes online ready, and then nothing shows up in the data fields for the device, they remain ???
That's to be expected, at least for a period of time. We can't talk to them to get the value. They only send out a value when triggered. Or in some cases on a schedule. If you trigger the door on one of them, does the value show up?
Dean Roddey
Software Geek Extraordinaire
No the value does not show up, it never shows up. Master controller reflects the state change immediately.

On a different note, if I have any of the battery devices enabled (whether "configured" or not) then none of the wired devices respond properly.

Lastly, I have 1 wired device that is not responding either even though it was identified correctly and approved. It's the ACT LRM-AS, client side driver indicates that the device is "Ready". There is nothing in the ZWAVE trace file. CQC Log entry below when I try to write to toggle the light switch:

07/06 09:55:00-NCC1701-D, CQCServer, CQCDrv_zwaveThread23
CQCKit, CQCDriver_DriverBase.cpp.7204, Failed/Not Ready, Error: 2017/0/0
Field 'MBR_Foyer_Switch' is currently in error state
<CQCServer> CQCDriver_DriverBase.cpp - 8696
<CQCServer> CIDOrb_ThisFacility.cpp - 536
<CQCAdmin> CQCKit_CQCSrvAdminClientProxy.cpp - 1945
<CQCAdmin> CQCAdmin_DrvMonTab.cpp - 1325

There aren't any ACT units supported. So it must be a re-branded version of something else. What does it show up as in the client side interface when it gets id'd?
Dean Roddey
Software Geek Extraordinaire
ACT. I sent you the device file this morning, same info I provided you several months ago that allowed it to be recognized. Emailed a screen shot
OK, it's actually an Evolve LRM-AS, which I guess ACT rebrands? Not sure why I indicated ACT in the device info file. That guy doesn't support associations so it can't report its state. We don't poll anything, so it would be a write only unit. The driver should show Write access on for it.
Dean Roddey
Software Geek Extraordinaire
It does but it errors out if I try to write to it from the new driver, works just fine from the old driver, just now re-verified this.
Flush the CQC logs, and the driver trace, put the driver into verbose, do the field write, then go back to normal and send me both log outputs. Let's see what is going on.
Dean Roddey
Software Geek Extraordinaire

Possibly Related Threads...
Thread Author Replies Views Last Post
  Possible to copy all the name in a driver so can paste is elsewhere? ghurty 11 154 07-14-2018, 05:24 PM
Last Post: Dean Roddey
  RCS V2 Driver kblagron 2 133 06-10-2018, 04:35 PM
Last Post: Dean Roddey
  Sonos Driver with Sonos Connect Amp zra 5 334 05-05-2018, 09:43 AM
Last Post: Dean Roddey
  Radio RA driver issue dogman 7 461 04-22-2018, 08:33 AM
Last Post: Dean Roddey
  Preview of new Web based RIVA client Dean Roddey 464 75,168 04-07-2018, 12:13 PM
Last Post: Dean Roddey
  Elk Driver fails Ron Haley 11 775 03-08-2018, 07:28 PM
Last Post: Ron Haley
  Nest driver disconnecting and reconnecting dogman 59 6,009 03-08-2018, 05:23 PM
Last Post: dogman
  Aeotec USB stick, existing zWave (v3) driver? IVB 3 348 03-05-2018, 08:57 PM
Last Post: znelbok
  Problem with Jetstream Driver RichardU 16 1,189 02-27-2018, 03:05 PM
Last Post: batwater
  Problem with fooBarV2 driver pjgregory 2 406 02-21-2018, 01:01 PM
Last Post: Dean Roddey

Forum Jump:

Users browsing this thread: 1 Guest(s)