All,
About three weeks ago, I switched from an RCSTX16B X10 thermostat, controlled by HomeSeer, to a RCS TR16 (RS485) thermostat controlled by my Elk M1G. The X10 stat was basically fine - maybe two problems in two years, but I wanted to move HVAC over to the most reliable thing in my system, my Elk. So... you can understand my concern when I find that the Elk doesn't appear to be fully reliable at sending commands to the new stat via Rules. In fact, it looks like it's missed about 6 or more cycles in the past three weeks, including a cold house this morning.
I would have thought it was the stat itself, BUT when I change things via the M1 plugin and HomeSeer, the commands go through fine (I'm not using HomeSeer to control the stat regularly, but can change the temp when I like via the UltraM1G plugin). And, my system of using Elk Rules has worked well MOST of the time, but not EVERY time. The biggest concern, though, is that when I check the Elk log after one of these incidents, there's just nothing there in terms of the stat. No communication with the stat appears to have been attempted, which is troubling as it implies a problem with the Elk or its handling of Rules rather than line interference, etc.
Have I stumbled upon some known flaw? Is there some test for diagnosis? I switched to this setup to obtain the most reliable system I could find that was still part of my automation system, and yet it's proving to be much less reliable than my old X10 stat system controlled by HomeSeer.
Anyone have any ideas on this one?
Thanks,
Joe
About three weeks ago, I switched from an RCSTX16B X10 thermostat, controlled by HomeSeer, to a RCS TR16 (RS485) thermostat controlled by my Elk M1G. The X10 stat was basically fine - maybe two problems in two years, but I wanted to move HVAC over to the most reliable thing in my system, my Elk. So... you can understand my concern when I find that the Elk doesn't appear to be fully reliable at sending commands to the new stat via Rules. In fact, it looks like it's missed about 6 or more cycles in the past three weeks, including a cold house this morning.
I would have thought it was the stat itself, BUT when I change things via the M1 plugin and HomeSeer, the commands go through fine (I'm not using HomeSeer to control the stat regularly, but can change the temp when I like via the UltraM1G plugin). And, my system of using Elk Rules has worked well MOST of the time, but not EVERY time. The biggest concern, though, is that when I check the Elk log after one of these incidents, there's just nothing there in terms of the stat. No communication with the stat appears to have been attempted, which is troubling as it implies a problem with the Elk or its handling of Rules rather than line interference, etc.
Have I stumbled upon some known flaw? Is there some test for diagnosis? I switched to this setup to obtain the most reliable system I could find that was still part of my automation system, and yet it's proving to be much less reliable than my old X10 stat system controlled by HomeSeer.
Anyone have any ideas on this one?
Thanks,
Joe