Charmed Quark Systems, Ltd. - Support Forums and Community

Full Version: Official 5.3 Beta Discussion Thread
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hey, download 5.2.904 again. I didn't bother changing the version for this little fix. That's getting to be too much overhead to do a new version and new build every time. The installer comments will tell you if you are installing the B version of 904. This one should fix the naming issue.

So, if you bring this up and go to the client page, and just watch it. You should see everything not battery powered make it up to WaitDevInfo within a fairly short period of time. If that happens, then we are good. That means that it's done all it can do until it's told what the units are.

Once you get me the device info dumps above, you can try to manually set some to generic handlers if you want. But get the device info dumps first, so that we are seeing what was gotten, not what you set.
Will do. I have traced down models for device dumps for 5 different devices, I think I have 3 other types to go. Do you want me to wait on the dumps until I do .904b?

The other half is due home soon so I may not get to the b version until tomorrow.
Go ahead and wait on the dumps since you'll need 904B to get the rest of them past waiting for the name. They have to get up to WaitDevInfo, and the B version should get them all there now.

BTW, I should have said before that approve new units is greyed out because that's to approve units that we auto-id. We aren't auto-id'ing any of these since we don't know about them yet. So there won't be any to approve until I get the device info and can see about setting up device info files for them.
Oh, and you may need to manually set up the associations on some of them, so that we can see what they send when their state changes. That may not be documented, so we may have to figure it out ourselves. If we can at least find the appropriate association group (usually it's 1 but not always), and just add the driver to it, even if the driver doesn't understand them yet, we'll see the incoming async msgs and that will tell me what command class I need to use to handle those.

But first we just get the info dumps and then we can start working through them.
On .904b

About half of the devices were still showing GetName. A re-include to replicate did not seem to help. I completely removed the driver, removed the folder, restarted all CQC services, and started again from square1. Excluded and joined the zwave network, and the whole enchilada. Still same result, about half are now in WaitDevInfo and the other half are get name or something similar.

Dumps are attached. I included a txt with the unit, state, and the model for the patter of what is doing what. It looks like anything that was ZWave Plus made it to WaitDevInfo, and anything older was stuck at GetName. I am not sure why one of the newer zwave+ dimmers got stuck at GetManSpec.
(03-31-2018, 04:12 PM)Dean Roddey Wrote: [ -> ]Is the HC2 a master controller?

Yes, it’s a stand-alone automation hub / gateway. 

https://www.fibaro.com/en/products/home-center-2/
Here's my trace file.  i get an exception at the end.

I've updated to 904B:

 - excluded the Aeotec USB stick from HC2
 - removed the ZWave driver
 - deleted zwave .cfg file and both driver files
 - updated to 904B

I then added all back, and this was the result. I get a report that replication failed.  The USB stick did successfully include on the HC2.
For HC2, it never sent the security scheme inherit message which is necessary to complete the inclusion. Maybe it sent it considerably later or something, but that wouldn't do the driver any good. Everything was good up until then. Try it again and let it run a minute or so, so we can see if it ultimately ever sent the message or not.
(03-31-2018, 09:25 PM)bobskie708 Wrote: [ -> ]On .904b

About half of the devices were still showing GetName. A re-include to replicate did not seem to help. I completely removed the driver, removed the folder, restarted all CQC services, and started again from square1. Excluded and joined the zwave network, and the whole enchilada. Still same result, about half are now in WaitDevInfo and the other half are get name or something similar.


Can you get me another trace of the startup process?
It looks like all of the device info dumps you sent me were for ones not in WaitDevInfo state, since none of them have manufacturer ids in them. The only ones that are useful are ones that are in WaitDevInfo, since that's the point at which it has gathered all of the data it can.

Oh, one of them was, the DZ155 is one that has the required info.