Veralite & Trane thermometer

Chuck xtension4osx at mac.com
Wed Nov 25 20:39:27 EST 2015


I noticed the same issue in the recent update. The Trane setpoint, cool setpoint, heat setpoint are all the same. If I set the cool setpoint for 85 it changes the hot setpoint and the setpoint. Yet it all seems to work, the numbers just aren't right.

And you are correct, it was all from the last update that this all changed.

Chuck

Sent from my iPad and butchered by Siri

> On Nov 25, 2015, at 10:07 AM, Brian Williams <brwill at me.com> wrote:
> 
> I return again to the question posed by Dave about the relationship between the Trane thermostat, Vera, and XTension.
> 
> I approached the recent Vera firmware update cautiously because a previous update really messed up my system, especially the thermostat. All seemed to go well with this recent update, but it really is easy to miss changes if one had changed the name(s) of the peripheral thermostat units. Here I am talking about the three 'points' that are created in addition to the central thermostat. 
> 
> The message that Vera sends to XTension contains a lot of data. Here is an example from my installation:
> 
> 2015-11-25 07:26:50 Vera Lite 3SBC: work json: {"altid":"15","id":"26","subcategory":"1","room":"7","parent":"1","fanmode":"Auto","hvacstate":"Idle","mode":"HeatOn","temperature":"25.5","setpoint":"29.0","heat":"29.0","cool":"29.0","commFailure":"0","humidity":"43","state":"
> 
> Note that setpoint, heat, and cool all report 29. These are not true values - no setpoint in my system is set at 29. The 'setpoint' in this line should be the current setpoint, regardless of heating or cooling. The 'heat' should represent the setpoint that would govern if the system was in the heating mode, and 'cool' should represent the setpoint that would govern if the system was in the cooling mode.  Interestingly, Vera does know the current setpoint. When one looks at the Vera web page to see the thermostat, most everything is there. Vera knows the correct setpoint, but doesn't report it correctly. I don't know if Vera knows the separately reported 'heat' and 'cool' setpoints, but the are recorded in the actual thermostat. Much of this is a change from a prior version of the Vera software. The reporting was accurate then, and I could change the setpoint through the XTension unit. I don't seem to be able to do that now.
> 
> I mentioned three peripheral units, each of which is given its own ID. One is marked temperature, one is marked humidity, and one is currently an unknown (although I have a suspicion that it is for the currently-uninstalled outdoor thermometer. I am working on that – punched the hole in the wall yesterday and am dealing with conduit, etc.).
> 
> Here are messages associated with those:
> 
> 2015-11-25 07:31:08 Vera Lite 3SBC: work json: {"name":"GET_LANG(generic_sensor,sensor)","altid":"m2","id":41,"category":4,"subcategory":0,"room":7,"parent":26}
> 2015-11-25 07:31:08 Vera Lite 3SBC: work json: {"name":"Humidity Sensor","altid":"m5","id":42,"category":16,"subcategory":0,"room":7,"parent":26,"humidity":"43"}
> 2015-11-25 07:31:09 Vera Lite 3SBC: work json: {"name":"Temperature Sensor","altid":"m1","id":40,"category":17,"subcategory":0,"room":7,"parent":26,"temperature":"25.5"}
> 
> After the recent update of the firmware, I noticed inconsistencies with my graphs and values in my XT Web Remote pages. I discovered that Vera had re-assigned these last three point (different IDs=different addresses), and I had used those in my XTRemote displays rather than the base units. I fixed that easily, but was alerted to the possibility of address changes with new firmware and automatic reconfiguration of the thermostat units (in Vera).
> 
> Vera doesn't have a defined profile for this thermostat. Instead it seems to use some generic profile. Until Vera gets smart about this device, we have to live with certain inaccuracies.
> 
> I have sent a note off to the Vera folk, in which I included JSON messages and a screen shot from the Vera page. That combo clearly shows that Vera is sending inaccurate data. We shall see what the furure has in store for this thermostat.
> 
> Regards,  Brian
> 
> 
> _______________________________________________
> XTensionList mailing list
> XTensionList at machomeautomation.com
> http://mail.machomeautomation.com/mailman/listinfo/xtensionlist


More information about the XTensionList mailing list