I’m in UI7, latest. I have humidity sensors now for all 4 of my CT100s. They were created back in mid April. Maybe after a firmware upgrade. The thing is, only 2 of the 4 are pulling in values. They are listed as embedded devices with the thermostat as the parentID. Anyone else see these now? Are they working?
I have 3 Lowe’s iris versions of these. The humidity sensor showed up for each of them. None of them read. Contacted support and they asked me to repair the devices. Did that after new firmware upgrade yesterday, neither thing helped.
Sent another email this morning, waiting for reply.
BUMP
I tried to reconfigure node; still not pulling humidity for two devices. I guess I will try a support ticket and post results here.
Same here. I have one CT100 from Amazon which is pulling the value, and one CT101 from Lowes that is not.
When I first bought the one from Lowes several years back it worked fine (although it was a hidden device). At some point during UI 5 development that stopped working and hasn’t started again even through updates of UI7.
The value does show up on the unit itself so it obviously is able to read it.
Dafunk?
??? must have been a google search result.
I did hear back from support. They said:
Hi Paul, I managed to connect to your unit and I checked the humidity sensors from your thermostats. As far as I can see in the logs the humidity level is not reported by your thermostats and that?s why the humidity level is not updated on the humidity sensors. Could you try to exclude the thermostats and then check if they will report the humidity level ? Please let me know how it goes. Thank you!
When/if i have time; I may do this… but i have so many higher life priorities than humidity values. I just want it to work without troubleshooting.
If it helps I’ve tried excluding and re-adding the thermostat several times and it never sends the value.
Obviously it might be nice for someone else to try it as well just to get another person’s experience. But at this point this idea of excluding and reincluding is not promising.
Hi All,
I think I inadvertently found the solution to this problem. I had two of these thermostats that did not have humidity numbers coming (and one that did) into the Vera and now they do. This is an issue i worked for hours over the course of the last year or so trying to fix, so I am happy it works now.
First, how I found it. I inherited one of these thermostats and decided to use it to control my guest room’s thermostat. I hooked it up and got it showing up perfectly in Vera showing all of the humidity values correctly. However, after a day or so I noticed that due to the placement of the unit, it was sometimes not keeping connection perfectly, so I decided to re-include in to vera. So first I excluded it successfully, and re-included. During the re-inclusion it went to “purging associations” and would fail. The thermostat portion still worked perfectly fine, but the humidity did not. And if I tried to poll the device it would fail. On the unit I had that does work fine, polling works successfully as expected.
So here I had a unit that did work perfectly fine when I first included it, and now doesn’t. So I know it’s not a defective unit. And as I thought about it, I remembered that the other unit that didn’t work also did at one point send humidity values, but later did not. So, I had the idea that it might be an association issue. Perhaps the unit wasn’t getting cleaned up properly by the Vera during the exclusion process and therefore would partially fail the re-inclusion.
On a hunch I started messing around with the “Automatically Configure” functionality, as well as the associations fields and eventually got it working again.
Here’s how I did it. I followed similar steps on my two thermostats and both started working. Now, I don’t know which of these steps (or combination thereof) actually did the trick. So some of the steps may be superfluous.
- Go to the Settings tab of the thermostat and set “Automatically Configure” to “No”.
- Go to Advanced tab, click Commands, and click “Configure Node”.
- Once things are done reloading, go to the thermostat’s “Device Options” tab, and add any number (added 0 in one case, and 1 in another case) into the “Group ID” field. Then press “Apply changes”.
- Remove the number you entered, and click “Apply changes”.
- Go back to the “Settings” tab, and set “Automatically Configure” to “Yes” (“Use default behavior” also likely works)
- Go back to the advanced tab, click the “Commands” and click “Configure Node”.
Once the device reconfigures, the humidity values started showing up again.
Again, steps like this worked for me on two of my offending thermostats (one was a CT100, the other a CT101 from Lowes). Some of the steps I did may be superfluous but they shouldn’t hurt to do them all anyway.
I’d love to hear if any of you also have success with this!
Thanks for the details; I had not found a solution. Are your steps for UI5? I do not see auto config in UI7, settings.
**EDIT - See it now… trying will update
**Edit2 - Worked just as described; Just FYI, I used 0 in groupID on both, worked 1st time
THANK YOU!
PC
Happy it worked for you too!
This was truly driving me nuts for a long time. Glad we seemed to have found a solution.
It’s definitely a vera problem, not a thermostat one. My guess is that if you exclude the thermostat it’s not being cleaned up properly by Vera, so that when it’s included again it errors out at the point where it works on the humidity levels.
[quote=“andrewgarfield”]Hi All,
I think I inadvertently found the solution to this problem. I had two of these thermostats that did not have humidity numbers coming (and one that did) into the Vera and now they do. This is an issue i worked for hours over the course of the last year or so trying to fix, so I am happy it works now.
First, how I found it. I inherited one of these thermostats and decided to use it to control my guest room’s thermostat. I hooked it up and got it showing up perfectly in Vera showing all of the humidity values correctly. However, after a day or so I noticed that due to the placement of the unit, it was sometimes not keeping connection perfectly, so I decided to re-include in to vera. So first I excluded it successfully, and re-included. During the re-inclusion it went to “purging associations” and would fail. The thermostat portion still worked perfectly fine, but the humidity did not. And if I tried to poll the device it would fail. On the unit I had that does work fine, polling works successfully as expected.
So here I had a unit that did work perfectly fine when I first included it, and now doesn’t. So I know it’s not a defective unit. And as I thought about it, I remembered that the other unit that didn’t work also did at one point send humidity values, but later did not. So, I had the idea that it might be an association issue. Perhaps the unit wasn’t getting cleaned up properly by the Vera during the exclusion process and therefore would partially fail the re-inclusion.
On a hunch I started messing around with the “Automatically Configure” functionality, as well as the associations fields and eventually got it working again.
Here’s how I did it. I followed similar steps on my two thermostats and both started working. Now, I don’t know which of these steps (or combination thereof) actually did the trick. So some of the steps may be superfluous.
- Go to the Settings tab of the thermostat and set “Automatically Configure” to “No”.
- Go to Advanced tab, click Commands, and click “Configure Node”.
- Once things are done reloading, go to the thermostat’s “Device Options” tab, and add any number (added 0 in one case, and 1 in another case) into the “Group ID” field. Then press “Apply changes”.
- Remove the number you entered, and click “Apply changes”.
- Go back to the “Settings” tab, and set “Automatically Configure” to “Yes” (“Use default behavior” also likely works)
- Go back to the advanced tab, click the “Commands” and click “Configure Node”.
Once the device reconfigures, the humidity values started showing up again.
Again, steps like this worked for me on two of my offending thermostats (one was a CT100, the other a CT101 from Lowes). Some of the steps I did may be superfluous but they shouldn’t hurt to do them all anyway.
I’d love to hear if any of you also have success with this![/quote]
Not sure how you found this but thanks. Worked for me with three Lowe’s ct101 thermostats.
Just needed to make sure I let it sit for a while after doing the manual config, kept rushing it and it didn’t work at first.
Not sure if it is the same for you guys too, but I have been watching my humidity numbers and it appears that they are never changing in the two affected thermostats I have.
Are you guys values changing?
Seems we may have found only a partial fix.
I just came back to the forum to ask the very same question.
Mine don’t seem to update either. Just got the value once. Temps update ok. Need to reach out to Vera again.
I sent a ticket to vera describing your workaround. Maybe they will do something in the next year or two.
At least they have been pretty good with monthly updates, just need to get this on the top of their list
Thanks for sending in a ticket!
It’s definitely something to do with the vera unit. In my experience any particular unit seems to pair fine and work as intended initially, but if it’s ever excluded and reincluded it starts to have this strange issue.
I have never had them functioning. The humidity showed up after a ui7 monthly update but was always blank. I had a ticket then, they just asked to repair the devices. That didn’t work, then they logged into my system and told me they don’t send humidity data.
That’s obviously not true.
Mine have not changed. The other two that were automatically set up have changed.
*Edit - Just checked values on devices and they are the same as reported.
As the two in question are only heat (not A/C), I have had them in OFF since April. I just turned one of them to A/C to see if that changes the reporting of humidity values on either differently.
After monitoring for two days, it is clear that the two that were not reporting humidity values prior to work-around above are not updating their values. The two that were working without work-around are updating. In looking at the device variables, you can see the ones not updating have additional variables. One of them is “Last Updated” which shows 0 (see attached)
So the workaround only worked for 1 update. Thoughts?
I wanted to monitor for several days before updating, but i was able to get one of my thermostats completely working a few days ago. I checked over several days to see if the values were updating, and it seems that they are.
What I did was a combination between the steps I had written earlier and actually excluding the device and reincluding. I don’t recall exactly what I did so soon i’m going to try it on my on my other thermostat that doesn’t update humidity. If I can get that one working too i’ll post my steps for everyone.
It may be a while before I can do this. The thermostat I had been working with was not heavily used in my scenes, however, this next one is very integrated. It will need to wait until I have the time to properly go through these motions, reinclude and then also put back into all my scenes. So i’ll need a time when I can set aside a decent amount of time. Not sure when i’ll have that.
In the meant time, maybe others want to try this? Try going through some of these steps I listed (to various degrees) and reincluding and see if they can reproduce a working unit.
Thanks. A few observations.
Both that are working have ManufacturerInfo value of 152,25601,263 and VersionInfo value of 3,3,28,9,1
The two that don’t work have ManufacuterInfo value of 152,25601,262 and VersionInfo value of 3,3,28,9,0
Maybe the exclue/include would change this based upon firmware info. Vera support suggested that include/exclude, which was too much work for a humidity value… but then again, so is posting this 