Charmed Quark Systems, Ltd. - Support Forums and Community
zWave, how I hate thee. need to redo network - Printable Version

+- Charmed Quark Systems, Ltd. - Support Forums and Community (https://www.charmedquark.com/vb_forum)
+-- Forum: General Discussion (https://www.charmedquark.com/vb_forum/forumdisplay.php?fid=3)
+--- Forum: Installation/Configuration (https://www.charmedquark.com/vb_forum/forumdisplay.php?fid=10)
+--- Thread: zWave, how I hate thee. need to redo network (/showthread.php?tid=10697)

Pages: 1 2


zWave, how I hate thee. need to redo network - IVB - 10-18-2018

To my utmost dismay my mf'ing ISY has stopped handshaking with 95% of my devices. Dunno if it's the ISY beta, don't care, UDI is painfully slow in making updates so I don't see the point.

I moved away from using CQC and the Aeostick as it only recognized 50% of my devices.  As of this moment i'm considering using CQC for the devices it recognizes, and blowing away/resetting the ISY for the devices it recognizes.  Assuming a blowaway / restart gets the ISY working again, otherwise i'm just boned.

Any opinion on using the CQC Beta zWave vs the G/A one?


RE: zWave, how I hate thee. need to redo network - Dean Roddey - 10-18-2018

The new driver is designed to make it fairly straightforward for us to add support for devices. I'm happy to work with you to get yours added. And there are generic handlers for common stuff that can be used as well in the meantime. You can always redo the ISY for the short term while we work on adding support for your stuff, then you can switch over.


RE: zWave, how I hate thee. need to redo network - IVB - 10-18-2018

We tried but I think I have some strange ones.

OK I'll try the beta and only put unrecognized ones into the ISY


RE: zWave, how I hate thee. need to redo network - Dean Roddey - 10-19-2018

The new driver should be able to handle just about anything, though it may require specific code to do so.


RE: zWave, how I hate thee. need to redo network - IVB - 10-22-2018

ISY got even worse, just ditched all but 3 devices tonight and moved into CQC/VRUSB/Aeotec tonight. Last 3 are in difficult-to-access locations (which is why I wanted them automated), will move those into CQC tomorrow.

In ISY defense 2 (out of 25) devices are >5 years old, might even be 10. Getting "unknown" in RFIT for mfr type, I have one extra new zWave switch, will switch one out tomorrow. The other will be a dumb switch until I have the time to swap it out, at which point i'll buy one.

CQC picked up the model #s on ~60% OOB. I had to manually set the unit type for 40%. I think it's working fine, will know as time progresses.

The other wildcard is that this is on a $180 "minix" mini-pc, 4GB/32GB embedded Win10 Home. It's a little hokey on various things, a little petrified that it won't be stable as a CQC server. My MS is a VM machine, can't plug the Aeotec into the host and pass through, so will suck up and buy a beefier machine as a 2ndary server only if absolutely required.


RE: zWave, how I hate thee. need to redo network - IVB - 10-30-2018

Woke up this morning, Aeotec was offline (red). Rebooted mini-pc, now it's online but no lighting fields. I flushed the logs, put driver into verbose, below is the only thing I see.

I also started getting the "The client side driver directory could not be cleaned out" again, so I wonder if this is a Windows/networking issue. I wasn't getting that, just came up again.



Quote:10/30 08:42:10-MINI-PC, CQCAdmin, MainThread
{
CQCKit, CQCAdmin_ThisFacility.cpp.368, Status/App Status
Exiting normally
}
10/30 08:42:12-MINI-PC, CQCAdmin, MainThread
{
CIDOrb, CIDOrb_ThisFacility.cpp.1243, Status/App Status
CIDOrb termination started
}
10/30 08:42:14-MINI-PC, CQCAdmin, MainThread
{
CQCKit, CQCAdmin_ThisFacility.cpp.154, Status/App Status
CQCAdmin is starting up. Version=5.3.909
}
10/30 08:42:17-MINI-PC, CQCAdmin, MainThread
{
CQCIGKit, CQCIGKit_ThisFacility.cpp.236, Failed/Not Found, Error: 932/0/0
Loading a client driver in test mode, but no resource dir found in environment
<CQCAdmin> CQCIGKit_ThisFacility.cpp - 250

}
10/30 08:53:00-HA-VM, CQCEventSrv, CQCEventWorkerThread3
{
CQCEventSrv, CQCEventSrv_ThisFacility.cpp.2165, Info/App Status
Started processing scheduled event 'CreateTempAllCSV'
}
10/30 08:53:01-HA-VM, CQCEventSrv, CQCEventWorkerThread3
{
CQCEventSrv, CQCEventSrv_ThisFacility.cpp.2208, Info/App Status
Scheduled event 'CreateTempAllCSV' completed successfully
}



RE: zWave, how I hate thee. need to redo network - Dean Roddey - 10-30-2018

That means that the CQC Client Server either has been stopped, isn't in auto mode, or is being blocked by something so that the Admin Interface can't talk to it. Running CQCNetTest can provide more information.


RE: zWave, how I hate thee. need to redo network - IVB - 10-30-2018

et voila. Something hinky is going on. Man I hate M$...

Code:
CQC Network Info Test
Copyright (c) Charmed Quark Systems


System Information
--------------------------------
      OS Version: 6.2.0, Build: 9200
         IP Name: MINI-PC
       Host Name: MINI-PC
Local Date/Time: 7:27:11 2018 -0700
     TCP Version: 2.2


Network Adaptor Information
--------------------------------
  {52E76AFA-B293-4CC7-A4B8-64CDC948153D}
  Broadcom 802.11ac WDI SDIO Adapter
           Ready: False
    DHCP Enabled: True
    IPV4 Enabled: True
    IPV6 Enabled: True
     Is Loopback: False
       Is Tunnel: False
       Dedicated: True
   Hardware Addr: AC 83 F3 8C 21 99
    Address #0: fe80::7ca3:907e:a115:507f%7
    Address #1: 169.254.80.127

  {D3987A32-EE87-4AC3-8863-32516756B5B1}
  Microsoft Wi-Fi Direct Virtual Adapter #4
           Ready: False
    DHCP Enabled: True
    IPV4 Enabled: True
    IPV6 Enabled: True
     Is Loopback: False
       Is Tunnel: False
       Dedicated: True
   Hardware Addr: AE 83 F3 8C 21 99
    Address #0: fe80::55a4:9f6a:155f:b420%13
    Address #1: 169.254.180.32

  {2B3B7834-709E-4523-9081-13C3AA2AE8A6}
  Microsoft Wi-Fi Direct Virtual Adapter #5
           Ready: False
    DHCP Enabled: True
    IPV4 Enabled: True
    IPV6 Enabled: True
     Is Loopback: False
       Is Tunnel: False
       Dedicated: True
   Hardware Addr: AE 83 F3 8C 29 99
    Address #0: fe80::14d0:d1db:7eb7:84c6%5
    Address #1: 169.254.132.198

  {9BE0F559-C411-441A-A178-CC09AB32A52A}
  Realtek PCIe GBE Family Controller
           Ready: True
    DHCP Enabled: True
    IPV4 Enabled: True
    IPV6 Enabled: True
     Is Loopback: False
       Is Tunnel: False
       Dedicated: True
   Hardware Addr: A0 1E 0B 08 88 C5
    Address #0: fe80::a85a:71d3:ba43:fca5%12
    Address #1: 192.168.3.54

  {53375597-C7A4-480B-98C1-41A859875D01}
  Bluetooth Device (Personal Area Network)
           Ready: False
    DHCP Enabled: True
    IPV4 Enabled: True
    IPV6 Enabled: True
     Is Loopback: False
       Is Tunnel: False
       Dedicated: True
   Hardware Addr: AC 83 F3 8C 21 9A
    Address #0: fe80::14c6:9c08:a378:6143%8
    Address #1: 169.254.97.67

  {AEC22B24-50D5-11E8-957D-806E6F6E6963}
  Software Loopback Interface 1
           Ready: True
    DHCP Enabled: False
    IPV4 Enabled: True
    IPV6 Enabled: True
     Is Loopback: True
       Is Tunnel: False
       Dedicated: True
   Hardware Addr:
    Address #0: ::1
    Address #1: 127.0.0.1


Environment Information
--------------------------------
      CID_NSADDR: ha-vm
DATADIR (client): C:\ProgramData\CQCData\A042B2F41B22D606-3EF63F660CBC6F6C
DATADIR (server): C:\Program Files (x86)\CQC\CQCData


Name Resolution
--------------------------------
    Reported Addr Families: IPV4 & IPV6

    Looking up host name (default address family): MINI-PC ...
    Resolved to: fe80::a85a:71d3:ba43:fca5%12
        Reverse: MINI-PC

   IPV4 Lookup: 192.168.3.54
   IPV6 Lookup: fe80::a85a:71d3:ba43:fca5%12

    Trying to resolve name server host [ha-vm.13502]
    Resolved to: 192.168.3.70:13502



CQC Connection Tests
--------------------------------
    Trying to connect to CQC name server
    Connected to name server successfully at: ha-vm.13502
       [192.168.3.70:13502]

    Testing Log Server...
        Server is registered at HA-VM.13503
        Log Server tests completed successfully.

    Testing MS Cfg Server...
        Server is registered at HA-VM.13504
        MS Cfg Server tests completed successfully.

    Testing Client Service...
        Server is registered at MINI-PC.13520
Test failed! Error=
01/01 00:00:00-MINI-PC, CQCNetTest, CQCNetTest
{
    CIDOrb, CIDOrb_ClientBase.cpp.456, Failed/Not Found, Error: 1006/0/0
    The server at fe80::a85a:71d3:ba43:fca5%12:13520 was not available
}



RE: zWave, how I hate thee. need to redo network - Dean Roddey - 10-30-2018

Is the CQC Client Service running on that machine? Check the services list and you should see at least it and usually it and the app shell service. The client service should always be running on all CQC enabled machines. If it's not marked auto-start, then it may have been changed at some point, so mark it thusly and start it.

If it's running, then something is blocking it on that machine. It has the right address and port it's trying to talk to, so one of these scenarios would have to sort of be the culprit.


RE: zWave, how I hate thee. need to redo network - IVB - 10-31-2018

Both services are running (App & Client). I wonder if it's a malwarebytes thing. Are there a certain set of ports I should exclude? I know I changed the actual #s, is it the 13520 one?