jmed999 Posted June 7, 2013 Author Posted June 7, 2013 But your is a different version, correct? My stat was in both heat and cool when I added it.
LeeG Posted June 7, 2013 Posted June 7, 2013 That is correct, it is running v.0B firmware. The comment about getting set point changes was more related to it being run by battery than what firmware is running. Regarding being in Off mode when adding a tstat, I have not had any problems adding a tstat when not in Off mode but all the instructions posted by UDI state the tstat should be in Off mode when adding to the ISY. Put the tstat in either Heat or Cool mode and see if set point change messages are sent. There are some things that cannot be changed from the ISY to the tstat when in Auto mode. Not sure about restrictions the other way.
jmed999 Posted June 7, 2013 Author Posted June 7, 2013 Put the tstat in either Heat or Cool mode and see if set point change messages are sent. There are some things that cannot be changed from the ISY to the tstat when in Auto mode. Not sure about restrictions the other way. I did this and the setpoint changes were not sent from the stat to the ISY. The ISY shows blanks for current state, hum, and setpoint temp. What now?
jmed999 Posted June 7, 2013 Author Posted June 7, 2013 I have no next. lol!!! Thanks for your time today Lee! Maybe the UD guys can offer some input??
LeeG Posted June 7, 2013 Posted June 7, 2013 Could be. Do other RF devices report state changes correctly from the same physical location as the tstats.
Michel Kohanim Posted June 7, 2013 Posted June 7, 2013 Hi jmed999, The best thing to do would be to submit a ticket so that we can see what's going on. With kind regards, Michel
jmed999 Posted June 7, 2013 Author Posted June 7, 2013 Could be. Do other RF devices report state changes correctly from the same physical location as the tstats. Yes these are sitting here in the center of my house with lots of dual band devices close. Other battery operation devices (remotelinc2) work great in this location. I could always sit these 1 foot away from the PLM and see what happens.
jmed999 Posted June 7, 2013 Author Posted June 7, 2013 Hi jmed999, The best thing to do would be to submit a ticket so that we can see what's going on. With kind regards, Michel Just submitted the ticket. Thanks!
LeeG Posted June 10, 2013 Posted June 10, 2013 jmed999 Take a look at the last few posts of this topic. This user had a v.0D thermostat not reporting. It was resolved by installing a new Dual Band device. Now the v.0D firmware is reporting. viewtopic.php?f=27&t=10822&start=15
jmed999 Posted June 10, 2013 Author Posted June 10, 2013 Thanks Lee! I saw that. I relinked my stats in the off mode and tried to put in master mode but they wouldn't go into master mode. The owners manual says it won't go into master mode unless part of a scene. My hardware is version v1.3. The UD guys have been working with me and they have contacted smarthome to help. We'll see what they say. I have 8 dual band devices that work great within 10 feet in open air. Sent using my Galaxy S4 and Tapatalk!
jmed999 Posted June 10, 2013 Author Posted June 10, 2013 Check this out... http://youtu.be/ii2rcpTapHA Sent using my Galaxy S4 and Tapatalk!
unispeed Posted November 30, 2013 Posted November 30, 2013 not sure if this got resolved, I had the experienced no heat/cool state statuses once I upgraded to 994i I just went to the stat and manually raised the set point to call for heat and now it is there just thought I would share ..
Michel Kohanim Posted December 1, 2013 Posted December 1, 2013 Hi unispeed, Unfortunately that state is not queryable. So, as soon as you upgrade ISY, the state is lost and cannot be queried till the next time you change the state on the thermostat itself. With kind regards, Michel
Recommended Posts