rrehart

I think this is broken again. This started happening to me yesterday. I have deleted all devices/scenes from alexa, then disabled the skill. Re-enabled, and re-discovered. Same issue. Getting this error periodically on the ISY via the Admin Console: "Socket Open Failed javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake"

Examples

No, you don't have to delete and start over. On the specific button ("fan High", for instance) of the KPL just click the button "Copy Scene attributes from [name of scene]". That will copy down the "off" state for the other buttons and set the fanlinc to the proper setting (in this example "High"). Do that for each button and everything will work fine.

No, I didn't. I just replaced the capacitors to get it back in action. Nothing programatically was done.

Jon - The system was down when the PLM was down. That being said, I just removed all of the dimmers from all scenes, folders, and deleted them (in that order), then re-discovered each dimmer and re-added to folder/scenes as appropriate. That fixed the issue. Now the event viewer sees when a device is controlled locally. Weird that would happen only to the dimmers and nothing else. I'll chock it up to ghosts in the machine! Thanks for the help! -Ross

Interesting. I did not replace it, but had to rebuild it. I have done a restore on the dimmers themselves (to no avail), and, subsequent to that even tried a factory reset on one of them. Again, no joy. Should I try a restore on the PLM itself?

Thanks Michel. One more: When exporting the log to Excel it tells me if a Program, Web Request, or the System triggered an event. It doesn't say WHICH program triggered it. Is there a way to add that to the output?

@ Jon - UI/Firmware confirmed to match: 4.4.3 on both. Device Links compare = [identical]. When I operate the switch via the admin console, I see: Fri 04/01/2016 11:22:24 : [std-Direct Ack] 22.3A.60-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 When I operate the switch locally, nothing comes up in the event viewer (no log whatsoever). @Techman - Yes, both.

I have a weird problem. I have pretty extensive Insteon installation in my home (70+ devices), including SwitchLincs (Dimmer and Switch type), OutletLinc, FanLincs, etc... In the admin console whenever a state changes for any of them, the interface updates with current state, as it should, with one exception: If I change the state of a Dimmer (2477D) programatically (that is, via the admin console, portal, mobilinc, or program run), the interface updates appropriately. However, if I change the state at the switch, the ISY does not update unless I do a manual query of the switch. Example: I set the FamilyRoom Dimmer to 40% via program. In the admin console, I can see that following the program run, the "Current State" is "40%". Then, when I turn the switch off at the wall (physically), the "Current State" remains at "40%" until I right click on the switch and select "Query"; at which time it changes to "Off". This is only happening with the dimmers (all of them), not the switches or any other device type. The problem this creates is that I have other programs that depend on knowing the current state of a given dimmer to run or not to run. If that state is not accurate, it causes those programs to act inappropriately. Any ideas on how to fix this? Thanks.

What I am after is to ask Alexa, "What is the current temperature in the house?" and for her to return "72 degrees" or something like that. I tried IFTTT with the "Alexa" "If" and the "Maker" then but nothing returned.

Not sure if Q&A is the right place to put this, but: When creating a new program I frequently run into the problem of the device/scene/program/etc.. selection menu being too small (50 characters) to read the entire string. This leads to some frustrating guessing as to which (for instance) KPL button I am selecting when trying to create a new program. My ISY is hyper organized, so a typical KPL scene would read like: "Inside / Family Room / Fan / FRKP-Main / FRKP - Low". When I try to select it, since an icon is shown before the name I get cut off at "... / FRKP -"; meaning I have to guess which one is Low, High, etc... Therefore, Feature request: Please make the selection menu in the programming tab a variable length or fixed at 100 character length field. Please! Thank you!

I have a Venstar Thermostat connected to WiFi and a Venlink server setup on my Raspberry Pi. The ISY can read the Venlink just fine and update settings based on various programs. Great. However, I would like to be able to query/present the "iVenstar_IndoorTemp" integer variable when I ask my echo, "Alexa, what is the current temp?". Since I can only use programs, scenes, and devices in the "Amazon Echo" tool in the ISY portal, I can't poll the variable directly. I tried to setup a simple program with a "then" statement to just get the variable, but "query" is not an option for variables in the then statement. I also tried to setup an IFTTT with Alexa/Maker (I can query via HTTP GET https://my.isy.io/isy/[key]/rest/vars/get/2/21),but that failed as well. So, any ideas on how I can get the value of that variable to pop when I ask Alexa for the temp? As always, thanks in advance.

Well... duh! Thank you. Can't believe I missed that one.

I have a bit of a unique problem. I recently had to rebuild my PLM (thank you Danu1964 for the instructions). After I rebuilt and restored it, all of my scenes ceased work. Not a big deal, I just rebuilt the 30 or so I have. All of the individual device commands worked just fine, and all devices reported. So far, so good. But... Even after restoring the PLM and rebuilding the scenes, I have found that the physical KeypadLinc buttons all cause my fan motor to go to "High" on the three ceiling fans in my network. For instance, if I press the (6-key) KeypadLinc "B" button - associated to Scene "Office Fan Low", with the "B" button being the controller and A, C, D, and the fan motor being responders, the motor goes to "High". The scene (in the admin console) reflects that the "B" button is on, and the fan motor is on High. The scene itself is working, as I can execute it either directly from the admin console or the MobiLinc app on my phone (configured for my.isy.io) and it properly turns the motor to "Low" and the "B" button to "On" This is happening on every KeypadLinc/FanLinc combo I have, so I seriously doubt its the hardware. As to the KeypadLinc programming, I am using Scenes, not groupings, and have all of the buttons programmed to "Non-toggle [on]". This is exactly how it was programmed prior to the PLM going out; which was working for 3 1/2 years. I have tried deleting and re-adding the: 1. Associated Scenes 2. The FanLinc 3. The KeypadLinc I have also tried via buttons grouping with no luck. I have attached screenshots here. Any help would be greatly appreciated. Thanks.

Is it possible to use IFTTT to change a variable on the ISY via REST?