CoolToys

The long run for insteon doesn't look promising, My bet is it goes the way of X-10, even though my entire home is Insteon run by an UD994 Pro. I had my fingers crossed for ReQuest. I love that thing too. The real problem is that none of these technologies crossed the chasm. Amazon and Google money insured their products did it first. I think the sad truth is you can be completely closed system minded like Crestron or it needs to be open source. Its just another version of the Mac V PC fight. Yes my insteon leaves a light on from time to time but the whole system cost less than my entry keypad from Crestron. My first "smart home" was HAI in 1999. For a few years my company was a Crestron Dealer, but all of that went away in 2009. I got lucky and made it out with my shirt. Since I have an ELK M1 Gold, I may just keep expanding that and write my own interface for automation since theirs is pretty unimpressive. Someday that may not work either. At least Home Controls is still alive. My bigger worry for the short term is that UDI web pages are starting to vanish or not be updated. The phone number no longer works and the last post I can find is June 2021 from UDI? The interesting thing is there are some 2022 copyright dates and other odd information are being updated on my icy portal page. I have two open tickets, hoping for a response.

There is a variable with options of "True" or "False" in the admin console when setting up thermostats. Both thermostats defaulted to false. I have no idea what this does and entering it verbatim into the Wiki only shows me the thermostat modes which I understand. Is there a new feature? Is this part of the electricity module for flex alert? The admin console says to manage the electricity module in the "dashboard" which I do not like as it is over simplified and not easy to use on a mac. Thank you.

Well it was nothing, at least so far. IN 5.0.14(beta) the siren was found but has four functions that appear to be tied to the alarm only. Ironically I still can't get the elk to communicate with the ISY. With 4.6.1 and older, I had it set up so when the relay closed the siren sounded a chime. I have found the chime feature, but I can't trigger it with a scene or a program that I have figured out. If I do, I'll post it.

I upgraded to 4.7.3 and the siren is not supported. A little afraid to update to a beta but since the siren is my only door bell, here goes nothing....

Anyone know why these aren't supported? I upgraded to 4.7.3 while troubleshooting a link to my ELK and suddenly my door bell stopped working. I use a relay from a button on the keypad at the gate to close the remote relay and trigger the buzzer. Other than being a bit loud it worked fine for over a year, and with the new update it shows as "unsupported device" Why would UDI drop a device that had been working?

I got bored, did a factory reset, it took about 30 minutes and it appeared in the IP scanner. I had to reboot my mac to get the ISY launcher to find it (cached data?), but the ISY came back up. I reloaded my latest back up only losing one new program, which is my fault for not backing up after I added it.

At 2 am a closet light came on that is controlled by a motion sensor. No one was in there, so I figured the battery must be low and simply closed the door. This morning I tried to connect my ISY to my ELK M1 for the first time (second house doing this), and the ISY only has the Power light on. I rebooted it and the PLM, and it appears to check in normally and after the boot sequence back to power light only, IP scanner doesn't see it, network switch indicates a 10/100 device is connected, no activity and no address assigned or being requested. I did power off and re-insert the SD card, no idea why, I just did. No change. I have put in a support ticket and if anyone has Ideas in the interim, thank you for your help.

I too added a Siren to my network, and used a horrible workaround to get it to work. The contractor didn't move my doorbell when we added on to the house. Ring, and Skybell are great but don't work with gate intercom. Since I could not hear the doorbell in the new section of the house, I bought a 2868-222 Siren and 2450 I/O link (which came up "refurbished" on my 994 Console?). The horrible workaround is that I added the Insteon Hub back to the network with the sole job of activating the chime when the I/O link "sensed" the closure of the doorbell circuit on the gate intercom. Whoever wrote the marketing lit for the Siren saying it also has a "more pleasing chime" must like the door sensor sound at 7-11. It is horrible sounding and way too loud, but I don't miss visitors at the gate. Looking forward to 5.x beta so I can take the hub back out before my wife adds alexa to it. I know, but I am too cheap to add alexa to the 994i

Might have figureed it out. 1. link to a switch. 2. "Add links" from switch 3. add device and "remove links" It didn't accept the name, it added it as an address.

Re-wrote to the "Garage" 2845-222 and it appears to be working again. Still can't re-write "front door" but I linked a switch to it and it works fine as a controller, just can't connect it to ISY.

There are dual mode controllers on both phases. The system was working just fine before a recent power outage. Now I can manually turn on a program and it works fine. i.e. "night" whch used to come on at sunset +- 21 minutes random after sunset. It did not come on automatically last night or tonight. From the admin console I can control any scene or switch and yet none of the programs are working as they did. Very confusing. I have powered down, re-booted. Hub works fine when I plug it in and use iPhone app to control it. PLM status is "connected".

Thu 03/17/2016 08:57:52 PM : [2B 0 50 ] Added to list of devices to link to ISY Thu 03/17/2016 08:57:52 PM : [iNST-TX-I1 ] 02 62 2B 00 50 0F 0D 00 Thu 03/17/2016 08:57:52 PM : [iNST-ACK ] 02 62 2B.00.50 0F 0D 00 06 (00) Thu 03/17/2016 08:58:01 PM : [iNST-TX-I1 ] 02 62 2B 00 50 0F 0D 00 Thu 03/17/2016 08:58:01 PM : [iNST-ACK ] 02 62 2B.00.50 0F 0D 00 06 (00) Thu 03/17/2016 08:58:10 PM : [iNST-TX-I1 ] 02 62 2B 00 50 0F 0D 00 Thu 03/17/2016 08:58:10 PM : [iNST-ACK ] 02 62 2B.00.50 0F 0D 00 06 (00) Thu 03/17/2016 08:58:14 PM : [2B 0 50 0 ] Failed to add device, reason 3 Thu 03/17/2016 08:58:14 PM : [All ] Writing 0 bytes to devices Thu 03/17/2016 08:58:44 PM : [ Time] 20:58:54 0(0)

Yes, I got the device to go into linking mode. I can link it to other devices, or to the hub. Not the ISY 994i Both of the sensors that were working, are now not working. I have deleted them and tried to re-add them, and get "Cannot determine Insteon Engine". With Old software, auto detect didn't work and I recall that I had to select a different device to get it to work. Can't find the email I have tried auto detect, and 2845-222 and both give "Cannot determine Insteon Engine" Pretty large system, 24 devices,10 long programs. Don't want to start over.

Found a thread on linking mode. Got it to beep, Still get "Cannot Determine Insteon Engine"

Ok so. 1. How to put the hidden door sensor in "linking mode" it isn't in user guide. It shows how to add it as a controller and remove devices it controls. That works fine. 2. Now that I upgraded to 4.4.5 the Garage Sensor quit completely from the 994i. Both still work on Insteon Hub fine.

994i Running 4.3.26 UI and Firmware. I have two 2845-222 Hidden Door Sensors. They were working and then after the batteries died one went stupid. I have replaced the batteries, and they both add fine to insteon hub, but not the ISY. The first one "garage door" reloaded and works fine. The second one, "Front Door" doesn't work. The docs for the Insteon Hub are easy, click "Add" and then press button until it adds. For the ISY, I see all kinds of notes about making sure you have the right firmware and it is close to a dual band switch. It is 3' from a dual band switch, and the "garage" is 12'. When I attempt to "auto discover" I get the "Unable to add device" "Unable to determine Insteon Engine" I know I had this issue when I first bought these, and thought I kept notes, but I can't find anything. I recall it being something about adding them as a specific device that isn't a "hidden sensor" and not to use "Automatic discovery", but I have tried all other sensors, same results.