Wayne Dalton thermostat set point reading is way off

Correction:

UI1 was a long time ago (more than a year) in early firmware versions…

1.0.1xx through 1.0.3xx - UI1, early golden days of Vera :slight_smile:
1.0.4xx through 1.0.6xx - UI2, no Luup. Considered “stable” for Vera1 hardware (although, latest Luup versions are quite stable)
1.0.7xx through 1.0.9xx - UI2, with Luup.
1.1.xxx - UI3, Flash-based, comes default on Vera2 hardware, can be installed on Vera1 also

I just upgraded to 1.0.988-1 to no avail. :cry:

Still reading +27F from the setpoint. I am getting pretty good at subtracting in my head.

Not a huge problem but yet another example of Vera being “not ready for prime time” in my opinion. I didn’t realize that I was being a Beta tester when I bought this product…

Did anyone else submit a support ticket for this? I just did as I have the same issue, as well as the fan auto/on toggle not working. I did not see this in the current bug lists being worked on.

I have the latest greatest firmware version 1.1.228

Dude, if someone submitted a trouble ticket for this, then MCV fixed it within, like, three hours of receiving the trouble ticket. Come on.

Guess again…

Did you check the calibration of the Tstat to another thermometer? The Tstat can be calibrated:

Your thermostat comes from the factory calibrated to +/- 1 degree of actual temperature. It is an accurate instrument.

If you want your thermostat to display the same temperature as another thermometer in your home, you can adjust its calibration.

To change the calibration:

  1. Remove the top cover.

  2. Locate the Calibration switch and slide it to the ON position. The current calibration factor (+/-) of the WDTC-20 will appear in the LCD display.

  3. Push the UP or DOWN arrows until the desired calibration factor is reached.

  4. Slide the Calibration switch to the OFF position. The new calibrated temperature will be displayed
    on the LCD.

Thanks, but it isn’t the calibration that is wrong, it’s feeding the stat a set point, which has to be 27 degrees less than what you want.

I checked the temp. calibration, and it is within a degree of others in my home.

It appears to be Vera’s software.

Im getting the same readings (+27 degrees) and I will try to submit a ticket…what are the ramifications for having the in correct setpoints???

If you set -27F you will get correct temps. The UI software takes a number from you, adds 27F then sends the increased number to to the tstat. If you can look a the tstat face when you issue the command you will see the panel flash “67” when you send “40”. Once the tstat is set it appears to be OK. You just have to get used to adding and subtracting 27 degrees…

Isn’t this fun? ::slight_smile:

Not just venting this time…

We need to take a step back here. MCV, Vera is broken, and you need to fix it! Workarounds for thermostats off by 27 degrees is not a great idea in my book.

Although I love to play around with stuff, and Vera can be considered one of my very few hobbies, I also have a serious need for this product to keep my second home “alive” when I’m not there. I put two Wayne Dalton T-stats in and they have been working perfectly with 1.0.979 for over a year, but I read this topic, and worry like crazy. Will I have mushrooms growing in the house when Vera decides the temperature should be 105 degrees? Being in South Carolina, not that far from the truth! Good thing I have a few webcams in the place so I can see if the portabellos are actually growing.

I would love to play around with my Vera and try different things, but reading the forums has me treating it like an unexploded bomb, stay far away as possible, be very gentle, and let only the experts touch it… Well, maybe I was venting a bit.

Anthony

This is definately a Vera problem. I just installed my WD thermostat and the UI3 and mobile version both will show the correct reading that you set on the theromostat manually, but when you try to change the temp via either Vera interface, it sends exactly 27 degrees more than you indicated. I can then go to the thermostat and manually correct the temperature and Vera will show the right settings. The problem only arises when you try to change the temp via the Vera UI or Mobile UI. Also, the UI3 interface shows Blue for heat and Red for cool.

Hi all,

We have a couple of trouble tickets received with logs and we will identify the problem today and fix it!

We identified the problem, fixed it and we will release a firmware right away (probably tomorrow).

First, thank you MCV for fixing the problem and putting this to bed. Here’s my question. I’ve been running 1.0.979 and have NOT seen this problem. Is the nature of the bug you found such that I MIGHT have this occur? i.e. should I upgrade to the new firmware. If you read my post above you will detect that I prefer not to touch Vera right now, but I do need to weigh the possibility of my T-stats going nuts on me when I’m not there.

Please advise, and I will do as you say. Thanks,
Anthony

Hi,

Anthony420, not for now. It didn’t happen to all the customers. If your thermostat and the rest of the devices are working properly, no need to update the firmware. We fixed this just in case and that users have a quick fix for the problem with a firmware upgrade.

Now that you have fixed this, how do I go about updating the firmware? ???

We haven’t released the firmware yet. We must test all the changes we did. We tested the thermostat, the problem is solved, but we don’t want to release it without intensely tests.

Did you also fix the problem with “Normal” and “Energy Save” modes not being displayed properly. When I manually set the thermostat to “Energy Save”, Vera shows the Hot and Cool setting for “Normal” mode, even though the thermostat is showing it is in “Energy Save” mode. I am away from the house and the Heat is set for 55. Vera shows the current temp as 55, but the Heat setting as 70. Obviously that is not right.

Is the new firmware coming out soon?

I heard back from MCV the other day that the latest 989 release should have fixed the issue. Has anyone tried it yet? I won’t be able to upgrade firmware for another week til I get back to the vaca home…

Any feedback? Are we OK now on this one?