drw Posted August 23, 2017 Share Posted August 23, 2017 I have a 2441TH thermostat which is reporting temperature 0...after a power failure. The thermostat seems to be working normally otherwise..as reported by the ISY. This thermostat has been working correctly for several years...and it has a slave 2441ZTH which is also not reporting temperature. I am running v4.5.4 of the ISY software...this software has been running correctly for some time. Is there any way to remotely reset the thermostat to get the proper temperature reading? I am not able to do a reset/power-off of the thermostat in person. Link to comment
stusviews Posted August 23, 2017 Share Posted August 23, 2017 Virtually every factory reset requires manual pressing. That's a security feature that, IMO, should not be bypassed however nice that would be. Security should never be nice and easy. The nicer and easier, the less secure! It may help if you delete, re-add and restore the thermostat using the Insteon ID. Link to comment
smokegrub Posted August 23, 2017 Share Posted August 23, 2017 I suggest removing the power, waiting a couple of minutes and restoring power. If successful, it will take a few minutes for the temp to display correctly. Link to comment
drw Posted August 23, 2017 Author Share Posted August 23, 2017 Good news is that the temperature reading returned overnight. Now reading 68 deg. I do have a routine that sets the time on the thermostat (using 'synchronize clock' command). This might have restarted the temperature readings. The remote thermostat is not reporting temperature but that is not a problem since it is a slave unit. Smokegrub, agreed that cycling power would fix the problem...this would require cycling the power to the furnace which provides the 24v power to the thermostat. But I am not able to do that remotely. Link to comment
larryllix Posted August 23, 2017 Share Posted August 23, 2017 ISY doesn't show what it doesn't know. Insteon devices have a very dumb application layer in the protocol. They only report when something changes, rather than adding in a cyclic all-else-fails report in addition to the exception style reporting. Querying a device seems to be an Insteon protocol feature, attempting to alleviate this problem after power off/on, but many devices do not handle that properly, either. Perhaps you could build an ISY program to query certain things upon ISY powering up. There is no hope for Insteon battery operated devices, except to wait for a change in status. Link to comment
smokegrub Posted August 23, 2017 Share Posted August 23, 2017 Good news is that the temperature reading returned overnight. Now reading 68 deg. I do have a routine that sets the time on the thermostat (using 'synchronize clock' command). This might have restarted the temperature readings. The remote thermostat is not reporting temperature but that is not a problem since it is a slave unit. Smokegrub, agreed that cycling power would fix the problem...this would require cycling the power to the furnace which provides the 24v power to the thermostat. But I am not able to do that remotely. I have similar problems with that stat and mine is located remotely (325 miles), as well. My stat is critical since I use it to alert me if a propane stove heating system has failed. I addressed this problem by placing an ApplianceLinc in the outlet and plugged the stat into the ApplianceLinc. That allows me to reboot the stat as needed. Rube Goldberg but it works. Link to comment
stusviews Posted August 24, 2017 Share Posted August 24, 2017 That'll only work with a line voltage thermostat. But one could power cycle a standard thermostat using an I/O Linc. Link to comment
smokegrub Posted August 24, 2017 Share Posted August 24, 2017 That'll only work with a line voltage thermostat. But one could power cycle a standard thermostat using an I/O Linc. Mine is the zth and is powered by the dongle. Hs worked successfully many, many times, including yesterday. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.