Posts: 33
Threads: 8
Joined: Mar 2008
Sorry, I didn't mean to imply the software was hacky.
I also didn't mean that the fields should show up on the client interface screen. I was suggesting that it would be nice to see the field values on the driver screen in real time as they change. I.E. if I turned a switch on, that field (on the driver page) would change without having to refresh everything.
Unless I'm doing something wrong, the only way I see to get the fields to update is to left click on the server label, hit "refresh", and wait several seconds.
Posts: 40,483
Threads: 491
Joined: Aug 2002
11-27-2016, 06:48 PM
(This post was last modified: 11-27-2016, 06:51 PM by Dean Roddey.)
They should be updating. That's what all of the auto-config is for, to get them to send their changes to the VRC0P and hence to CQC. Are you sure you have the right unit marked as the VRC0P in CQC's Z-Wave configuration? That's what controls how the associations are set up when you do the auto-config thing. If you mark the wrong one, maybe the USB stick, then CQC is never going to see any change because the units will be sending those status changes reports to the wrong place.
If you think you got the wrong one, and you change it, you'll have to do the auto-config on them all again, because they will have all gotten pointed at the wrong controller and will have to be updated to point to the right one. Do one and get it working, before you commit to all of the work. If you can't get one working, you won't get any of them working.
Dean Roddey
Explorans limites defectum
Posts: 40,483
Threads: 491
Joined: Aug 2002
Did you make any progress?
Dean Roddey
Explorans limites defectum
Posts: 33
Threads: 8
Joined: Mar 2008
(11-28-2016, 10:20 PM)Dean Roddey Wrote: Did you make any progress?
Hi Dean,
   Got busy and didn't get a chance to come back to this, but after a few more hours, I still don't have it. 
   I restarted the server, removed, and re-included the sensor, updated the VRCOP, and successfully did the auto-config (confirmed in logs, I did do a wake up on battery power to get the auto-config to take), and I am still getting ??? for all values. The one odd thing I noticed is when I highlight any of the fields for the sensor, say the Temp, and click "edit trigger, then save", I get an error that says "could not update the trigger info to the driver, so it may be out of sync with the configuration". When I click on details, it says " Driver V23 does not have a field named 'Unit_38_Lum'" Unit_38 was the previous name I had given to the sensor. If I change the name of the sensor, this error always gives the previous name it had. Any other ideas?
Posts: 40,483
Threads: 491
Joined: Aug 2002
First be sure to hit Save if there are any changes. If the Save button is not greyed out, then there are changes to save. Hit save and wait for the rescan indicator at the bottom of the tab to go away.
Also, those values are going to be ??? until the unit does a wakeup. That will be some number of minutes, depending o the configuration.
Also, up until 5.0.919 there was an issue with the auto-config where the commands wouldn't actually be sent. So, if you are on any version prior to that, it's not really working as it should, which could cause issues.
Dean Roddey
Explorans limites defectum
Posts: 33
Threads: 8
Joined: Mar 2008
(05-24-2017, 12:28 PM)Dean Roddey Wrote: First be sure to hit Save if there are any changes. If the Save button is not greyed out, then there are changes to save. Hit save and wait for the rescan indicator at the bottom of the tab to go away.
Also, those values are going to be ??? until the unit does a wakeup. That will be some number of minutes, depending o the configuration.
Also, up until 5.0.919 there was an issue with the auto-config where the commands wouldn't actually be sent. So, if you are on any version prior to that, it's not really working as it should, which could cause issues.
I went to upgrade to the latest version, but it says I need a new license, I purchased this in Dec of 15, then paid a maintenance fee in Nov of 16 to upgrade to 5.0. I just re-registered making sure to use the last key you sent, then rebooted the machine. Still the same. Am I missing something? 
Corey Smith
Posts: 40,483
Threads: 491
Joined: Aug 2002
You always have to get a new license after any major or minor upgrade. Just send me the install key.
Dean Roddey
Explorans limites defectum
Posts: 40,483
Threads: 491
Joined: Aug 2002
The install key should be displayed in the nag screen you are getting after the upgrade. You are already covered so there's no charge for the new license of course. You just need to get a new license for each new major/minor version. Otherwise, we'd never be able to enforce the coverage rules if we didn't do it this way.
Dean Roddey
Explorans limites defectum
Posts: 40,483
Threads: 491
Joined: Aug 2002
Be sure to make it wake up again after you do the auto-config. I think it now logs auto-config stuff, so you should see it queue it up, and then when it finally sends it when the unit wakes up you should see that.
Dean Roddey
Explorans limites defectum
Posts: 33
Threads: 8
Joined: Mar 2008
(05-24-2017, 01:55 PM)Dean Roddey Wrote: Be sure to make it wake up again after you do the auto-config. I think it now logs auto-config stuff, so you should see it queue it up, and then when it finally sends it when the unit wakes up you should see that.
OK, Dean, now that I upgraded, when I autoconfig the sensor, I get the following in the logs:
starting auto config for unit xxxx
auto config msgs qued for later transmission, unit xxxx
I tried waking the sensor up with the button (seems to be working as the led comes on), and tried waiting, but now instead of ??? in the fields, I get zeros.
I am assuming the above message means the sensor was not ready to receive the config settings.
I am also still getting the odd error when trying to edit a trigger on any of the fields "Driver V23 does not have a field named 'Unit_38_Lum'" again Unit_38 was an old name for the sensor...
|
