Goose66

I don't know that a third-party Echo app is going to be better than the HUE emulator, in that third-party apps have to be addressed by spoken name before speaking any related commands, e.g.: Alexa, launch Home Controller and turn on kitchen lights, Alexa, ask Home Controller to set basement thermostat to 55 degrees, or Alexa, tell Home Controller to turn off all lights That said, the programming looks pretty easy. I should have something in a week or two. As far as configuration for the masses, until Amazon adds configuration of app parameters to the Alexa SDK, I think you will need a third-party website to configure. I am using Amazon's DynamoDB to persist user settings (address and user ID/password for my ISY, scene names to URI mappings, etc.). It would be fairly straight forward to create a website to allow users to add a user ID, put in the configuration parameters, run a script to download scene and/or device names from the UDI, etc. and store all of that in DynamoDB. Also, what this effort (and others, I suppose) could use is a place in the ISY data model to add a "spoken name" attribute for scenes and devices. I guess I could be put these in the notes field (are the notes accessible through REST?) for now until there is a better place to put them. Custom attributes, Michel?

A program with: IF from 12am to 11:59:59pm, same day will run precisely two time a day - at 12:00:00 am where it will execute the "Then" branch and at 11:59:59 pm where it will execute the "Else" branch. I think what you want is to add a Wait and a Repeat at the end of your Then branch to have it repeat every five minutes or so or change the condition so that it runs when the value of the $stat den indoor temp or $stat den cool setpoint variables change.

I have a domain name/port routed through my router to my ISY 994i Pro port 443. When I access the ISY 994i remotely using https://<domain name>:port#, the Chrome Web Browser scratches out the https:. If I start the Admin Console, I get a warning saying the ISY is setup with the default SSL certificate and that is a security risk. I select the button to configure SSL Certificates and get the guide mentioned above. I have downloaded the Dashboard mentioned in the guide for version 4.2.16 and tried to create a self-signed Server certificate according to the instructions. The fields of the server certificate dialog are not described in the guide: 1) Issuer is blank and I can't set it to anything 2) Fingerprint is blank and I leave it blank 3) Email Address is blank and I have tried with and without When I fill out the fields and click "Self Signed" I get a pop-up box that asks whether I have filled out the fields properly, I click yes, and I get 5 errors saying "Subject class type invalid." Any help here would be appreciated. Thanks.

Not to mention that, unlike MOST OF the other consumer electronic devices that I own, this one is constantly being improved and enhanced. I saw the upgrade fee as just my contribution to that effort. From my experience, I bet they may work with you on extending the upgrade offer.

I looked at them, and the info said they have local on/off just like the ApplianceLincs. I just assumed they would have the same current leakage problems. Plus $50 a shot to replace my $40 ApplianceLinc modules -- again may be throwing good money after bad. Maybe if I could get $25 a piece back for the ApplianceLincs.

I have an ISY994i/IR Pro connected to a 2412S PLM v.92 (I think). I created a program that sends an X10 signal to an X10 module. I can't get this program to work no matter where I plug in the X10 module. Am I missing something from this setup that I need to get X10 to work? I ask because I am thinking about replacing ApplianceLincs with X10 Appliance Modules in my holiday lighting scenes to avoid leakage of current which causes the LED lights to glow even when the devices are off.

One of the best things that happened to X10 was the patents expiring, allowing lots of vendors to get into the fray. Of course, by that point the technology was suffering from age. Will this happen to Insteon? Well, frankly no. First, the earliest patents will not expire until the mid 2020s. Plus, there are plenty of alternatives such as Zigbee (IEEE802.15) and UPB (PLC). So we won't see a drop in prices and a flood of new devices in the market with Insteon like we did with X10. For example, there are no Insteon debugging/troubleshooting devices which are sorely needed,and would be cost effective to build if not for the Insteon licensing fees, I imagine.

Thus my original post -- without tools there is no way to troubleshoot.

I have a number of line filters in the house. They are on the UPS that attached to computers, and one for the surge suppressor for my stereo rack. But I have a house full of electronics. Am I supposed to buy and install a line filter on every power supply and electronic device in my home? At $35+ a shot, that would cost a lot of dough. Also, I have several fluorescent lights, like in my closets, garage, shop, under-counter lights, etc. that are hardwired in the house. No filter for those. I have often suggested that a filter built into a SwitchLinc would be awesome, but have only ever heard excuses for why such can't be done.

I notice the 2413S on Smarthome.com says its now compatible with HouseLinc software. I would like to use this software to troubleshoot my Insteon network. The 2413S on Amazon is $6 cheaper and Prime eligible but doesn't necessarily say its HouseLinc compatible. Does anyone know if all 2413Ses are the same?

I assume you are talking about the 2993. That's no better than moving your PLM around on an extension cord and sending repeated messages from your ISY. What's need is a plugin device that can show line noise in the Insteon band, SNR of received signals, packet counts and quality or validity of received signals, and send signals. i had such a device for X10 and it was an excellent diagnostic tool. Today i would think it would be an iPhone app with a portable plm with USB port. It would be nice if the ISY would show and/or log this information as well, and even produce network data such as hops and (one can dream) routing plans.

There is just no way to diagnose it, because no behavior is predictable enough to draw any conclusion. I can trip a breaker to my washing machine, and something may start working. Try the same thing the next night, and no good. There are too many variables to deal with. If there was some way to measure PLM or device signal strength at individual outlets, or measure noise while operating different devices, that would be different. But the only way I have seen to do this is to buy (and learn to operate) an occilliscope, which is a ridiculous level of sophistication to go to diagnose what is supposed to be a consumer product. For the most part, the basic Insteon functionality works pretty good. Motion detectors turn on lights, keypads control other deices, etc. My primary problem is the ISY/PLM doesn't seem to want to talk to half my devices. For example, if I try and add the new 2477Ds, I get "Cannot determine Insteon Engine" from the ISY. I was told above this is because the ISY/PLM cannot communicate with them. Yet if I operate the newly installed and manually linked 2477Ds, their activity shows up in the ISY's logs and event viewer. Even plugging the PLM into an outlet on the circuit didn't resolve it. There's just too much complexity and not enough transparency into what is actually supposed to be happening in all this. Makes me long for X10, while just as unreliable, was much easier to understand the communication and diagnose problems.

Well that explains my multiple progress bars. I have A LOT of communication problems.

That worked...kind of. I ran an extension cord to a garage plug, and that allowed the ISY to access and write updates to both keypads, even though the keypads are on different circuits. I then plugged the extension cord into a downstairs hall outlet that is on the same circuit as two new 2477Ds I am trying to add to my system (see my other post). This did not allow the ISY to talk to the 2477Ds that are on that same circuit. There just seems to be neither rhyme nor reason to how Insteon communications function and in what scenarios they are reliable or not. This could have been something as subtle as my dishwasher running, or the satellite STB in standby instead of on, or one of the kids turning on the florescent lights in their closet. There is no way to know and no way to debug the system. I have a 4800 square foot house with 50-60 breakers in two panels supplying power to hundreds of devices connected to wall warts, surge suppressors, UPSes, and power strips. Should I be spending any more time or money on Insteon, or is it just not capable of performing in an environment such as mine?

Guys, honestly, does the progress bar in the ISY admin interface mean anything real, or is it just something to display to make us think the ISY is working. I have never thought the progress bar means anything. Query System is an excellent example: the progress bar counts from 1% to 100% with an occasional display of event data beneath, usually an RR, CLIHUM, or a wind speed or light rate reading. If the progress bar reaches 100%, it goes away and then comes back and starts counting from 1% again. Depending on the function, there may be three, four, or more progress bars. Once the system is finished with the Query System or other task, the progress bar goes away, even if it was at 41%! Seriously, why not just display an hour glass or wait icon with a mouse cursor? Why display a progress bar that evidently means nothing?

This would be easier than unscrewing light bulbs. How far can the PLM be from the ISY 994i on a cat 5e cable (and not supplying power).

Shouldn't the 2477Ds, being dual band, be reachable wirelessly? My wired Insteon sucks, and the lack of any diagnostic tools for Insteon ensure that is will continue to suck for a long time. But I thought the dual-band devices would also be reachable wirelessly, through at least one of the 4 access points in my house. There is one access point not 15 feet from each of two 2477Ds on a 3-way circuit, yet the ISY can talk to one but not the other (now - originally couldn't talk to any of them). These two 2477Ds are wired directly together for the 3-way circuit. How is it possible that the communications could be so bad in this scenario?

I am attempting to add 5 SwitchLinc 2477Ds to my setup in order to improve system reliability. These will be installed across two circuits (a 3-way and a 4-way) that are on different phases and hopefully will improve phase coupling and stability in my system. However, I cannot add any of the SwitchLinc 2477Ds to the ISY 994i. I get "Cannot determine Insteon Engine." This happens regardless of whether I select AutoDiscover or 2477D in the device type list. Very bad for WAF, as now she can't control any of our downstairs or upstairs hall lights. I will either have to pull out the switches or manually link them using the Insteon method. Does anyone have SwitchLinc 2477Ds working with an ISY? Here are my events from trying to add: Sun 03/24/2013 07:30:31 PM : [1D DB EC ] Added to list of devices to link to ISY Sun 03/24/2013 07:30:31 PM : [iNST-TX-I1 ] 02 62 1D DB EC 0F 0D 00 Sun 03/24/2013 07:30:31 PM : [iNST-ACK ] 02 62 1D.DB.EC 0F 0D 00 06 (00) Sun 03/24/2013 07:30:33 PM : [iNST-SRX ] 02 50 1D.DB.EC 11.CE.0A A3 0D FF (FF) Sun 03/24/2013 07:30:33 PM : [std-Direct Nack] 1D.DB.EC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sun 03/24/2013 07:30:33 PM : [iNST-TX-I2CS] 02 62 1D DB EC 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 Sun 03/24/2013 07:30:33 PM : [iNST-ACK ] 02 62 1D.DB.EC 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01) Sun 03/24/2013 07:30:34 PM : [iNST-SRX ] 02 50 1D.DB.EC 11.CE.0A 23 09 01 LNK-ON (01) Sun 03/24/2013 07:30:34 PM : [std-Direct Ack] 1D.DB.EC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sun 03/24/2013 07:30:34 PM : [LNK-BGN ] 02 64 01 00 06 Sun 03/24/2013 07:30:38 PM : [1D DB EC 0 ] Failed to add device Sun 03/24/2013 07:30:38 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65)

I have two 8-key keypads (2486D v.36) that use to work just fine, but now the ISY 99/994i cannot update them. This happened a couple of years ago -- as I added more Insteon devices in the network, the performance and stability of my Insteon communications went majorly downhill. This hasn't really been a problem, though, because they function just fine. The ISY can hear the keypresses and the keypads respond just fine to all scenes -- it's just that the ISY cannot talk to them well enough to update them so it always thinks they are "out-of-communication." I recently replaced my motion detectors outside with updated models. Now, I need to reprogram both these keypads to put the newer motion detectors in the scenes. Any ideas on how to temporarilly restore communication to these keypads (short of taking them out of the j-boxes and hard-wiring them to the PLM) so that I can get them reprogrammed with the new motion detectors?

What is the date window on the upgrade program?

I see that. What does the 994 offer over the 99i - more processing power? If just FLASH memory is the problem, why can't I just replace the SD card in my current 99i?

Sort of melancholy that the I can no longer look forward to ISY99i updates. So much promise and so much future functionality that never came to pass. I guess it's time to move on to the next HA solution.

Sometimes the quirkiness of the ISY programming architecture has some perhaps surprising advantages. For example, consider the following program: If From Sunset To Sunrise (next day) And Control 'Outdoor / Driveway Motion-Sensor' is switched On Then Set Scene 'Outdoor / Driveway Floods on Motion' On Wait 8 minutes Set Scene 'Outdoor / Driveway Floods on Motion' Off Else Set Scene 'Outdoor / Driveway Floods on Motion' Off The first advantage is that as long as there is motion on the driveway, the program will continuously be restarted, and the flood light will stay on 8 minutes past the last detected motion. The second advantage is that if sunrise occurs while the floodlight is on, it will be turned immediately off, even if the 8 minutes hasn't expired. The disadvantage is that it will send OFF commands to the driveway flood throughout the day as driveway motion occurs -- needless Insteon traffic. The OFF in the else is necessary, however, because if you happen to be leaving the house just minutes before sunrise (something that occurs for several days for me two times a year), then your floodlight gets left on all day (the sunrise trigger preempts the WAIT before the OFF and goes to the Else branch). But alas, the quirkiness is often just too complex to think through the various states. So you may just want to stick with the two level programming described above and avoid the use of Else branches, just to keep it simple until a more robust programming environment becomes available.

Because the IF statements in an ISY program embody both a decision as to which branch of the program to execute AND which events can trigger your program, you often must write programs in two levels. For example, consider your situation below: Program 1 'On Dining Motion' (enabled): If Elk Zone 'Dining Motion' is Violated Then Run Program 'Handle Dining Motion' Program 2 'Handle Dining Motion' (disabled): If $Dining_Motion <= 1 Then $Dining_Motion = 2 Wait 4 seconds $Dining_Motion -= 1

Also, don't forget to disable your second program, so that it will never be executed by the ISY outside of the call from the first program. This is not technically necessary for an integer variable, but is good practice when using other nested programs with IF statements that you don't want to also be program triggers.