CompKing

Glad I could help! I'm just learning too, and ran into some of the same frustrations. Glad I could get you on the right course.

They key is to make sure they show up as "Accessories" in HomeBridge before trying to pull them into the phone. It make take trial and error to get this to work, as if there is certain unsupported devices on your ISY it may crash the Homebridge interface, and no Accessories show up. Start with one device at a time (i.e start with default being exclude all devices, and then bring in individual devices).

Update: The problem was the wired unit, which was replaced.. Aartech went beyond expectations for a Canadian Insteon customer. After purchasing a 2441TH Insteon thermostat, it turned out it was incompatible with a future purchase of a wirless add-on thermostat (2441ZTH) I acquired. The manufacturer support was not helpful, and Aartech team quickly got involved when I contacted them, and worked with senior management at the manufacturer to isolate the issue. After learning the issue could not be resolved without replacing my 2441TH, Aartech allowed me to do a return of my defective unit, even though they didn't have to as it was out of their scope. They took a frustrating situation and turned it into a satisfied customer who will be happy to continue being a long term customer. It is service like this that makes a big difference when working with bleeding edge technology which can sometimes have downfalls. Thank you Aartech

In my case, I am linking the 2441TH wired and the 2441ZTH wireless. I want the 2441ZTH to be master so it controls the call for heat at the thermostat. I don't want to involve the ISY in any of this logic, as it shouldn't need a controller for it to work. I'm not sure how a program like that would work. I would have to manipulate the set point at the wired controller to try to achieve a proper balance based on the temperature at the wireless. As far as I know you can't use the values from the thermostat queries very easily as criteria in programs, and also can't easily get them into variables for comparison purposes.. I am not sure why there aren't more reports of this issue. I think you are right that it could be a my version of 2441TH and 2441ZTH. Have quite a few been sold in Canada?

I would go from Metric to Fahrenheit too, but I have dozens of programs related to humidity and temperature, and climate to humidity and underground watering. I will probably mess things up as it is a couple years ago when I set it up..

After investing in a wired 2441TH Insteon Thermostat, I wanted to get a new zone for my upstairs which is always significantly different than where the wired thermostat is located on the main floor. I ordered the 2441ZTH (V1.5) recently and learned of a horrid bug which SH has not tasked to fix yet, and has been a known issue for over a year. The problem is that when both the Wired and Wireless are set to Celsius display, the wireless device thinks the current temperature is Farenheit and compares it the celsius set point comparing apples and oranges. The net result is that it is ALWAYS calling for cool (i.e. 24c setpoint is < than 77f measured temp / 24 < 77), or never calls heat because of the same logic. Bottom line is that the device is useless in Canada and AARTECH (Canada Resellet of SH) should remove it from their inventory until SH fixes the issue. If you have the wireless device (or the wired device and could buy a wireless device) and live in canada, e-mail custsvc@smarthome.com and ask them when they are going to fix this. --------------------------------------------------- Here is the ticket details I sent in, and only so far have had a verbal (use Farenheit or return the device for refund) answer: Symptom: 1) When in cool mode, and MASTER is set to wireless, A/C is always being demanded, regardless of setting 2) When in heat mode, and MASTER is set to wireless/ Heat is NEVER Demanded, regardless of setting Issue: 1) Although all aspects of displays Sync properly, and both display Celsius, the Remote Wireless device logic is treating the set point value as Fahrenheit when the value is actually in Celsius. i.e. Room Temp = 25c, cool set point 27c - Call for cool because 27c is smaller than 25c translated to Fahrenheit (i.e. 77f) - 77 > 27 therefore cool needs to called. Max setting in C is 38c, so will always call for cool as long as the room is warmer than 38F Room Temp = 25c, heat set point 27c - No Call for heat because 27c is smaller than 25c translated to Fahrenheit (i.e. 77f) - 77 > 27 therefore no heat needed to be called. Max setting in C is 38c, so will never call for heat as long as the room is warmer than 38F It is confirmed this is the issue, as changing the setting back to "F" as the unit of measure, the unit functions properly and only calls for heat/cool when the main unit used to (according to the actual temp at the remote unit) The system also properly functions in "C" when the MASTER unit is the wired unit I have tried factory reset on the 2441ZTH and changing from "F" to C" prior to linking the devices, and the problem still exists. 2441TH = Rev 1.15 - 1222 2441ZTH = V1.5 - 4414 - 14J4

I agree with this point. I understand this is available in the API Query.

I am now facing a similar issue on my 2441TH. It was working fine for the first part of cooling season, but clearly some kind of spike has changed my thermostat permanently [damage?] Symptom: I don't get "Energy Mode", but I get a mode/temperature change no matter what prior mode I am [Cool Only, Auto, Program Cool] when my AC unit finishes its cycle [causing noise]; my thermostat resets to Auto Mode and sets Heat Setpoint to 3c and Cool Setpoing to 31c. This happens every time AC unit finishes its cycle. I can write a program to detect this, but I don't always have a proper value of the previous mode to reset it back to. Diagnosis: To isolate the issue, I unplugged my ISY-994i and Factory Reset the 2441TH to see if the issue still happens. Without the ISY and the 2441TH in factory defaults, the symptom still happens. Attempted Solution: I put in line on each lead on the thermostat a TVS Diode to try to isolate the voltage spikes. This has not improved the senario, and the thermostat continues to go back to these values. I believe this is not a program or a bad link on my system, but purely due to electrical noise. I am going to try more isolation steps by doing separate 24VAC to my HVAC system from a separate transformer. I have not yet been in contact with SmartHome. My 2441TH unit shows "Rev 1.15" on a sticker on the wiring surface. Based on this forum, I am hesitatnt to call SmartHome due to their lack of good support on this issue, though I would like to know if anyone has a unit with a more current "Rev" number which I could ask Smarthome to update. Likely a replacement unit could work for me, since this problem only surfaced part way through cooling season, and was working fine prevously. Thoughts? http://ca.mouser.com/Search/ProductDetail.aspx?R=P6KE30A-E3/54virtualkey61370000virtualkey625-P6KE30A-E3

Can anyone else report success in doing a "Device Restore" on 2420M since 2.6.14??

I have to assume that the relative "quiteness" in forums since this latest beta means everyone else is having the same great experiences that I am. Hats of to UDI folks. This beta seems to be one of the most stable versions thus far. Thanks for being so responsive to everyone's concerns. I think your support model will pay dividends in the long term. Regards

I have been playing around with a handful of 2420M's now that they seem to be mostly bug free. At one time I was going to try to get all the LowBatt Controllers into a Scene which I can monitor, but quickly learned this would involve a lot of simultaneous putting of the 2420M into program mode. It appears when your go to put a 2nd 2420M into program mode that the 1st one sees it as a "link request" and stop flashing, likely ending up making a link between the modules that ISY wouldn't know about (or want). I quickly gave up on that, but then noted an issue (new??) with this version. In all of my attempts to use "Restore Device" I get a device failed. I was hoping to use this function to clean out any bad links I created above. Even after factory reset, this function wouldn't work. (yes, I am putting the device in program mode [both the slow and fast flash]) I ended up having to remove the device, and re-add it instead. (which works fine, but is a long drawn out process). Can you reproduce the "Restore Device" failure? Regards

So far, so good. Been almost 24 hours, and no zero's noted. Fingers crossed

By moving the AP from 40ft to 4ft away from the thermostat module, I have not detected a zero value for the returned value since. It is unfortunate that noise would be interpreted as a zero instead of an invalid result (and thus ignored). I am assuming that noise caused the issue since it did resolve itself, but even 40 ft away shouldn't be a problem (same floor, neighboring room, mostly open space between) I haven't been ignoring your response, I have been on vacation. I do note that in the 4ft location that I still do occasionally get 0 thermostat values in my programs, though not as often (once ever 40 hours or so). I can try moving it back to the original location (when I have a sec), and see if the problem worsens. Regardless, even at 4 ft I still get the invalid/zero values. Regards

I have been noting on occasion when I reboot the ISY (using telnet) that sometimes the program's which were flagged to be run at startup no longer have this flag. I am unsure if I have done anything different lately to cause this. My programs don't adjust program "run status" within themselves. Knowing that a "non-beta" release is pending, I am hoping to squash some of more visible bugs if they exist. Cheers

Is in intentional that the ISY GUI doesn't show these buttons when you select a scene on the "Main" tab. They don't show a status in either the "whole scene" or the device as part of the scene, yet you can show a status when you look under "My Lighting". Is this to avoid confusion, or is these a technical limitation to this? Regards