Charmed Quark Systems, Ltd. - Support Forums and Community

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82

Dean,
To facilitate adding new z-wave models can you make an "important" or sticky post with the instructions?. The more people that help fill in the missing models the better.
What thread do you want people to post log file to? (do you want to make a thread for just this?)
Thanks┬á
Kevin

Please add Zwave support for a Schlage BE469 Front door┬álock.(battery power)
(Save on Unit Information didn't save a text file. just popped up a save dialog) Here is a copy and paste of Unit Info┬áand a trace.
thanks
Kevin

┬á ┬á ┬á ┬á Name: Unit_1E
┬á ┬á ┬á ┬á ┬á Id: 1E
┬á ┬á ┬áDevType: Routing Slave
┬á ┬á ┬áGenType: EntryCtrl
┬á ┬á SpecType: 3
┬á ┬á ┬á ┬á Make:┬á
┬á ┬á ┬á ┬áModel:┬á
┬á ┬á ┬á ┬áFlags: Beaming FreqListen┬á
┬á ┬á ┬á ManIds: 0 0 0
┬á ┬á Classes:┬á
┬á ┬á ┬á ┬á ┬á ┬á ┬á ManSpec (1)
┬á ┬á ┬á ┬á ┬á ┬á ┬á Security (1)
┬á ┬á ┬á ┬á ┬á ┬á ┬á Version (1)

Extra Info:

Dean,
Was trying to set the few Canned light┬ápatterns with the new┬áFibaro RGBW zwave driver.
The ones that I tested under the┬áold z-wave driver:
┬á ┬á┬áFire Place paramNumber:72, value:6, ┬ásize:1
┬á ┬á Storm paramNumber:72, value:7, ┬ásize:1
┬á ┬á Deep Fade paramNumber:72, value:8, ┬ásize:1
┬á ┬á Lite Fade ┬á paramNumber:72, value:9, ┬ásize:1
┬á ┬á Police paramNumber:72, value:10, size:1

When I try to use the InvokeCmd
SetCfgParam Fibaro_RGBW 72 6 1

I get this error in the log.┬á

04/17 11:36:38-CQC-PC, CQCServer, CQCDrv_Z-StickThread25
{
┬á ┬á CQCKit, CQCDriver_DriverBase.cpp.6980, Failed/Not Found, Error: 2016/0/0
┬á ┬á The value written to field Z-Stick.InvokeCmd was rejected by the driver. Reason=BadValue
┬á ┬á Bad Value
┬á ┬á ┬á <CQCServer> CQCDriver_DriverBase.cpp - 8511
┬á ┬á ┬á <CQCServer> CIDOrb_ThisFacility.cpp - 536
┬á ┬á ┬á <CQCAdmin> CQCKit_CQCSrvAdminClientProxy.cpp - 1945
┬á ┬á ┬á <CQCAdmin> CQCAdmin_DrvMonTab.cpp - 1321

}

Thanks again!!
Kevin

(04-17-2018, 06:10 AM)kfly Wrote: [ -> ]Please add Zwave support for a Schlage BE469 Front door┬álock.(battery power) (Save on Unit Information didn't save a text file. just popped up a save dialog) Here is a copy and paste of Unit Info┬áand a trace.
thanks
Kevin

┬á ┬á ┬á ┬á Name: Unit_1E
┬á ┬á ┬á ┬á ┬á Id: 1E
┬á ┬á ┬áDevType: Routing Slave
┬á ┬á ┬áGenType: EntryCtrl
┬á ┬á SpecType: 3
┬á ┬á ┬á ┬á Make:┬á
┬á ┬á ┬á ┬áModel:┬á
┬á ┬á ┬á ┬áFlags: Beaming FreqListen┬á
┬á ┬á ┬á ManIds: 0 0 0
┬á ┬á Classes:┬á
┬á ┬á ┬á ┬á ┬á ┬á ┬á ManSpec (1)
┬á ┬á ┬á ┬á ┬á ┬á ┬á Security (1)
┬á ┬á ┬á ┬á ┬á ┬á ┬á Version (1)

Extra Info:

It gives you a save dialog so that you can name it. Otherwise it's very difficult for me to keep up with what's what. So give it a name like:

Bubba_Make_Model_Id.Txt

and then save it, where bubba is you. That way can know who it's front, what the make/model of the device it's supposed to represent is, and what id it is if I have have to look through any traces.

That one hasn't gotten far enough through the process yet to have gotten any useful info. So something isn't happy with it. If it doesn't have the ManIds values filled in, then it hasn't gotten the required info yet. It got the basic info but hasn't gotten further than that. Probably the state is still on something like "GetSecClasses" I'm guessing?

I'll look at the trace.

You may not have flushed the trace file, since it sorts of ends abruptly. Or it may be that it the lock wasn't responding. The driver would have tried again in 30 seconds or so. But it looks like the lock isn't responding to secure messages. Try it again and let it run for about a minute, so we can see if its timing out. We can see a couple attempts by the driver that way.

(04-17-2018, 08:52 AM)Dean┬áRoddey Wrote: [ -> ]You may not have flushed the trace file, since it sorts of ends abruptly. Or it may be that it the lock wasn't responding. The driver would have tried again in 30 seconds or so. But it looks like the lock isn't responding to secure messages. Try it again and let it run for about a minute, so we can see if its timing out. We can see a couple attempts by the driver that way.

OK let the trace file run longer:

Looks like lock is stopped at GetSecureCls
https://imgur.com/VYDPNSP

It isn't responding to a request for its secure classes. It responds to a request for a security nonce, but doesn't respond to the supported secure classes query. Given that it's just a failure to respond there's not much for me to go by. Is that your own secure module? It would be useful to know if any secure msgs are working.

Node 0x17 also isn't responding. What is that guy?

Just as a sanity check, since a lot has changed in these early drops, can you do this:

1. Exclude the driver from the network
2. Delete the driver's configuration file
3. Maybe look at positioning the Z-Stick such that it has better line of sight outwards from wherever it is, so up above computers and other big metal bits.
4. Add the driver back

Let's give it a chance to do the whole process from the start, to insure it has a good security key and all that. See if it gets the lock up to WaitDevInfo this time. That's where it should get to if it is not auto-id'd but it gets all of the info we require.

(04-17-2018, 09:41 AM)Dean┬áRoddey Wrote: [ -> ]It isn't responding to a request for its secure classes. ┬áIt responds to a request for a security nonce, but doesn't respond to the supported secure classes query. Given that it's just a failure to respond there's not much for me to go by. Is that your own secure module? It would be useful to know if any secure msgs are working.

Node 0x17 also isn't responding. What is that guy?

Just as a sanity check, since a lot has changed in these early drops, can you do this:

1. Exclude the driver from the network
2. Delete the driver's configuration file
3. Maybe look at positioning the Z-Stick such that it has better line of sight outwards from wherever it is, so up above computers and other big metal bits.
4. Add the driver back

Let's give it a chance to do the whole process from the start, to insure it has a good security key and all that. See if it gets the lock up to WaitDevInfo this time. That's where it should get to if it is not auto-id'd but it gets all of the info we require.

Dean,
0x17 I think is a garage light switch.. very far away so not supprised.
The lock and my server room(Z-Stick) are only 20 feet apart so should be good signal stregnth wise.

I just updated to the new CQC version today from a version that didn't have the z-wave stuff. do you still want me to do the above 1-4 steps?

You might consider putting a repeater in. I am using┬áAeon Labs DSD37 Range Extenders┬áwith great result.┬á I have 3 fence gates that have zwave switches on them, the repeaters allow the signal from the gate switches┬áto reach the SmartThings hub reliably.

Charmed Quark Systems, Ltd. - Support Forums and Community

kfly

kfly

kfly

Dean Roddey

Dean Roddey

kfly

kfly

Dean Roddey

kfly

batwater