jaydrosy

Is your EISY updated to the latest firmware? I was having similar issues 6+ months ago that was fixed with one of the subsequent updates. I haven't seen any similar problems since then with two different brands of z-wave thermostats.

I'm using 2GIG STZ-1 thermostats and they're working really well. They connected easily via Zwave and work well. Good connection and responsiveness communicating both to and from the EISY. The UDMobile thermostat dashboard view does not work well, but the standard view is fine. I've been happy so far running three of them in different zones in our house. Thinking of installing them in a second location.

Me too!

I did not have the disabled program problem, but I do have the problem where sunrise and sunset times are not correct. I din't realize I was having trouble until the past hour or so as things got really dark!

Hi all. I'm not sure if this is the right forum, but I figured I'll try here. I'm working to get rid of all my Insteon stuff in my house, and am upgrading everything to Z-Wave. I'm running EISY with ZMatter, by the way, and generally things run just fine with all my existing devices (mostly light switches and door locks). I picked up three of what I thought were GoControl thermostats but are branded as 2GIG, model STZ-1. Two are now installed. I've had no trouble adding the thermostats to my network. The thermostats also are mostly able to be controlled by my EISY using the Admin Console, and all local changes at the thermostats are immediately reflected in Admin Console. So, I can turn the thermostat off using Admin Console (and UD Mobile for that matter), change to heat or cool, change the fan mode from auto to on or back, no problem; and any local changes made are reflected immediately. The single exception is temperature control. If I adjust the temperature on the thermostats, those changes are immediately picked up by my EISY/Zmatter and are reflected in Admin Console. If, however, I try to adjust the temperature from the Admin Console, I get an error saying "Cannot Communicate with [DEVICE]. Please check connections." (see image below). This happens with both Thermostats. Any ideas what I'm doing wrong or might fix this? I've rebooted EISY just in case. I've done "Update with Interview" on each device, just in case. I'm at a loss. Any help would be much appreciated. Thanks!

Great collaboration here. Thank you @sjenkins for posting this. I followed your recipe and after two reboots have not had any further disabling of programs. Hopefully this is the end of it! @Chris Jahn thank you also for your support on my ticket on this.

You are not alone. I continue to experience this, with 100% of programs being disabled on 100% of reboots. I am actively working through it with support and am hoping a resolution will be found.

Seems fixed indeed with this release. Thanks to the team for addressing this!

I have always had my thermostats update the clock at some point overnight using the Set Time command, primarily to capture daylight savings changes. I’ve never needed Write Changes, but did try it just in case and to no avail. I’ll report back here if I get word of a fix being implemented.

Ticket submitted and the issue has been acknowledged. My understanding is that it will be addressed in a future release. Stay tuned!

Never have before -- no impact now

Hi @DennisC I'm slowly working to eliminate Insteon from my life, but in the meantime these thermostats have been 100% reliable for years. I've had several of them in two properties running (previously) on ISY 994 and no problems at all. Great units as far as I can tell. Problem with the clock cropped up only recently (not exactly when) with some update to IoX and/or the introduction of EISY as a replacement for the old ISY 994. It's not terribly relevant to you but the time is set natively through a command issued in IoX. See image below. No change in behavior after a device restore, unfortunately.

Thanks @Geddy will do.

Hi somebody else was posting about this several months ago in a couple of the IoX release specific threads, but through a few updates this is still a problem. I have three Insteon thermostats (model 2441TH) and IoX sets the time to GMT rather than local time. The time reported by IoX (running EISY and firmware v 5.5.7) is correct in local terms and programs run properly. There was talk of some firmware updates addressing these sorts of things. Any ideas about this one? Thanks!

Your tutorial was exceptionally helpful to me in figuring out how to configure my existing virtual 3- and 4-way switches, some of which have the load controlled by the Z-Wave and with older Insteon switches as remotes, and some of which are the other way around. It took some tinkering but I finally figured it out. The "Scene Button 1" zwave sub reads the top paddle push, "Scene Button 2" the bottom. Setting those as controllers for the insteon switches did the trick. Just fyi Scene Button 1 can be set to default. Scene Button 2 needs to send an "off" command to the insteon. Set the zwave switch to ignore both Scene Button 1 and Scene Button 2 so it can do it's own thing locally. (Recognizing this might not be 100% clear. I can add to it later with images if it would be helpful to people. I'd also be interested in hearing if others have better ways of doing this as it is a bit clunky. I kind of liked the "old" way where ISY would handle everything at the controller to virtualize a scene)