Troubleshooting Z-Wave thermostat

[michmill]

I have a 2Gig CT30e z-wave thermostat (it's in the Pepper DB) that I've been using for a few years with HomeSeer.  I recently converted to HomeGenie on Ubuntu, and I'm having trouble polling the thermostat and setting SetPoints now. It worked fine with HomeSeer. I deleted and re-added the thermostat to the primary controller. The thermostat command "Off" seems to be the most reliable, but it responds only about 60% of the time.  SetPoints have never worked since moving to HG.

Is there a z-wave log file to help me troubleshoot the communication issues?  Is anyone using HomeGenie with the CT30e thermostat?

Cheers,
Mike

[bradvoy]

I ran into a similar problem with my Radio Thermostat CT101 thermostats.  HomeGenie used to control them just fine, but a few months ago HomeGenie stopped being able to change the setpoints.  See the thread I started at http://www.homegenie.it/forum/index.php?topic=951.0.  A couple of people tried to help me with this problem, but we didn't make any progress. 

[michmill]

I think I may have found the problem.  The thermostat is reporting it's temp back to HomeGenie in Celsius, but HomeGenie is sending the setpoint to the thermostat is Fahrenheit.  I'd like to try sending the setpoint in Celsius.

Does anyone know which module I should look at to find where it's sending the setpoint so I can do the conversion to C before it's sent?

Thanks in advance for the help!

Cheers,
Mike

[michmill]

The widget sending Fahrenheit instead of Celsius to the thermostat is definitely the issue.  I changed the widget to display Celsius.  I changed the setpoint using the widget, and it sent Celsius to the thermostat, which it happily accepted.

So, is there an central place in the HG code I can modify that will always do the F->C conversion?

Cheers,
Mike

[Maximo]

I'll be following this thread with interest as I have two thermostats.

[michmill]

I've modified the generic thermostat widget and the Timetable program to handle the CT30 thermostat.  Both programs need a little more testing.

I'm now modifying the Z-Wave thermostat polling program to retrieve the current setpoint.

Let me know if you want me to post work in progress.

Cheers,
Mike

[bradvoy]

I would be happy to test what you have so far with my CT-101 thermostats.

[Maximo]

Let me know if you want me to post work in progress.

Yes please.

Thanks, Garry

[michmill]

I've uploaded my changes to the Z-Wave thermostat poll program, Timetable program, and the generic thermostat widget to a different thread here.

It works great on my setup.  I hope this helps other people, too.

Cheers,
Mike

[Maximo]

I've tried your altered code but it's not worked for my setup. I'm using Secure SRT321 thermostats, any further suggestions?

[michmill]

Can you provide more information on what's not working?  Also, can you attach a screenshot of the HG log communicating with your thermostat?

Cheers,
Mike

[bradvoy]

I tried your updated components with my CT-101 thermostats, and they're mostly working!  It's great to be able to control my thermostats again with HomeGenie.  The only problem I'm seeing is that the thermostat widget is sometimes displaying the setpoints incorrectly.  It always shows the correct temperature.  But the setpoints are sometimes showing "169.0" or "172.0".  Other times they are displayed correctly.

[michmill]

I've noticed the setpoints will display incorrectly as soon as another process sends a new setpoint to the thermostat.  This corrects itself after the next poll.  What's happening is HomeGenie is sending the new setpoint to the termostat in Fahrenheit, but the thermostat widget is also getting the notification.  Since my updated widget is expecting the setpoint to come back in Celsius, it converts the setpoint, which is already in Fahrenheit, to Fahrenheit again.

The formula to convert C to F is ( t * 1.8 ) + 32.  If you have the time when you see the incorrect setpoint again, try taking the bad reading through this formula ( t - 32 ) / 1.8 and let me know if the result is what the setpoint should be.

Cheers,
Mike

[Maximo]

Hi Mike,

Apologies for not getting back to you sooner, been a little busy at work so haven't had time to play with interesting stuff.

I'll take a look later on and update you. Appreciate your help and efforts.

Cheers,

Garry

[michmill]

No worries.

I'm working on an update that should minimize the incorrect setpoint display.  Basically, if the result after converting to Fahrenheit is greater than 120 degrees, it's probably shouldn't have been converted.  I'm hoping to have an update in a few days for you.

Cheers,
Mike