So now I see that it’s not just reading +27F but its actually setting the temp +27F! I am sweltering! Caffreyboy, which firmware version are you running?
Looks like this is a Vera UI issue. I can set the correct temperature via the findvera/mobile smartphone app but when I use the vera UI it goes immediately to +27F. So I have to deduct 27F from my intended set point while using the UI but I can enter the corect temp on my phone. Not very friendly… :-\
I had mine running fine, reading within a degree or two with 1.0.616. So I know the 'stats are OK. (2 of them acting the same way) Vera adds 27F to the set point. Renders them unusable. This happened all of a sudden when I upgraded to .979, and both are behaving the same. I excluded them and re-included under .979 to same results…
It’s a Vera problem for sure. Looking for some help here…
I have not submitted a ticket yet. I still have this problem. I haven’t had a chance to call WD but the way these are behaving it seems like a Vera issue to me. Thanks,
–SteveO123
I called Wayne Dalton and they said that the 'stats seem to be working fine.
They referred me to their home controls group-- They only take email inquiries but as soon as I get any info I will post it here.
the latest 1.0.9xx and 1.1.xxx apparently have ‘the same’ backend. So relatively “concurrent”. But the different versions have slightly different versions of that backend and MCV isn’t exactly clear (to me at least) which version of the backend is in each UI version.
if both UI2 and UI3 have the same issue I’d vote the backend might be faulty for that device. if 1.0.988-1 fixes it than you would need to find what 1.1.xxx has at least that fresh of a backend (so probably wait for the next released 1.1.xxx)