paulbates

CopyRon The only reason I can think of for keeping all Control (old) and Status (old) statements is if you think you would ever revert to a 4.x firmware version. The 4.x firmwares would only recognize the (old) versions and programs with any of the "new" 5.x features would need to be touched up as those "new" statements don't exist in 4.x. The only difference I've found between (old) and "new" is that for Keypadlincs and Smartenit's EZFlora; only the first device is available in the "new" Control and Status program statements. For instance, I only see the first key of a keypadlinc in the new Status and Control, and the first sprinkler zone of 8 zones of the Ezflora. The fix for this bug hasn't come in yet in 5.x, it remains in 5.04. FWIW, I've kept my Keypadlinc and Ezflora programs on Control (old) and Status(old), and moved everything else to the "new" versions. I'll move the rest when its addressed in a future version. Paul

I would suggest factory resetting the KPL, and then right-click on the keypad in admin console and select restore device. Then retest.

Someguy To get the admin java application on a system remotely, find the release you are using on the forums Select the release you are using and look at the first post from Michel for the release. Follow the directions under 4. a for either downloading or remotely loading the admin console. The launch the downloaded jnlp. Follow the directions from my first post from there Paul

This should work. I have keypad keys on several keypads that control an attic fan and dampers. The keys always reflect the on/off state whether a key or the ISY turns it on/off. The scene controls the buttons and devices. Can you post and image of your scene configuration from the admin console?

Hi someguy This one is tricky and this happened to me too. Here are the steps. Select and copy the long admin console access link (/desc) from the portal Startup the Admin Console on your remote system When the ISY Finder comes up, click "Add" and a box will pop up Paste in the long admin console link with /desc on the end into the box. Click save Double click on the link you just created in the finder As you already figured out, enter your portal credentials in the Admin Console "Authenticate ISY" login box It typically takes longer than usual for the admin console to fully start up. Sometimes a minute or 2 for me depending what remote network I'm on and also the upload speed you have with your ISP Paul

As Jon pointed out, IFTTT channels, including gmail, have a published 15 minute polling time. I typically don't see that long of a delay checking gmail by labels, usually its a couple of seconds to a few minutes. I get consistent 5 second response from gmail to pushover on the same account and messages, I know its not gmail or the service sending the email. I get the first echo message too, as I don't have an echo, but I did link my ISY to my amazon account. I ignore the message. I don't get the state variable message. If you are unable to do that, I would open a tick with UDI and see if they can assist setup. There are newer channel types called 'quick triggers', and that includes the email channel. I'm experimenting with it as a replacement for gmail, but it doesn't not appear to be as rich as gmail and has some limitations. Still looking for that. Paul

Marcin- Looks great. Quite jealous over here I'm thinking if took the money I sunk in custome KPL keys, I would have a good start on buying one of these things.... Paul

Yes, possibly. The "wander" on mine was quite a bit. It doesn't affect use of the door, however it was always a head scratcher why it would false trigger sometimes. I did an number of tests from inside and made marks on the header, and it was apparent that this was the problem. It was an easy fix and its not happened again. At its worse, the sensor was pretty far from the magnet. Paul

Hi I had a similar approach on the sensor and had similar results with the false triggering, but very infrequently. After looking at it, I found that the garage door "wandered" right to left during use. At certain points, the wandering to one side was enough to put the sensor at the edge of its reach from the magnet. I put a shim board on the side that let the garage door wander too far away from the sensor. I put it at an angle so as the door came down, it gently touch the board at the outside, and over a couple of feet nudged the door to the right spot. Here is a pic Hopefully this will work for you. If you go inside the garage and run a few cycles, you will see it happening and can make some marks for placement Paul (if you right click on the picture and open in new window, it will orient correctly)

mv I'm not sure total number of devices should matter. The writes go to a set of devices at a time. Can you provide a short narrative of one set of devices and related scenes.... here is an example I just did: 2 inline lincs, a light bulb and an iolinc 1 test scene 1 minute 30 seconds What kind of results are your getting?

Michaelv I moved from another system and rebuilt my links one functional group of devices at a time. Its relatively fast and I have a backup of everything. Scenes don't take that long for me to create.. Its <ctrl> click on devices and drag them into the scene, indicate which are controllers. Can you provide details on what part of that process is slow, eg the clicking and dragging, or the time it takes the ISY to write the updates? Paul

Hi Martin, welcome to the forums! The ISY uses an RJ45 style connector for both LAN and Serial, the PLM does too. A standard RJ45 LAN cable will work. The Port A is where the PLM is plugged in, the other port is for the network. No DB9 is used with the ISY. What I would suggest is look at this link which is the wiki. Right at the top is the quickstart guide, that will walk you through initial set up, step by step. Then, a few links down is the complete & comprehensive guide for all the details. We're here on the forum for more detailed questions. What are you planning to filter with the filterlincs? Your power has 2 legs, that need to be bridged so the signal is available on both. Probably one of your appliance lincs will be on the opposite leg, but it will be best to first plug both appliancelincs in their intended home, and run the test page 10 of the appliancelinc manual Paul

More information is available in this parallel thread http://forum.universal-devices.com/topic/18605-3-26-16-portal-issue/

Paul, no. Are you on central time? It was 4:01am for me on ET. Paul

That lines up with mine Michael, my 4:01am et would be your 3:01am ct Paul

I'm guessing since 4am.. i got an expected email notification after midnight and wasn't looking for any since then Here are some other investigative tidbits: Last error log entry, portal: 2016/03/16 00:34:36 System -140005 ISY Last few error log entries, ISY Fri 2016/03/25 06:54:00 PM System -5012 390 Fri 2016/03/25 06:55:06 PM System -5012 391 Rebooted here ~9:51am 3/26 Sat 2016/03/26 09:52:18 AM System -170001 [uDSockets] RSub:24 error:6 Sat 2016/03/26 09:52:30 AM System -5 Start Sat 2016/03/26 09:52:33 AM System -110022 /CONF/SEP/PRICE.LBL Sat 2016/03/26 09:52:41 AM System -110022 /DEF/F3/I1/NLS/EN_US.TXT Sat 2016/03/26 09:52:49 AM System -170001 [Network] Established Sat 2016/03/26 09:52:49 AM System -60006 n/a Sat 2016/03/26 09:56:25 AM System -140005 Net Module Rule: 18 ​​​ISY Programs, network module and email alerts have been working as expected including the time the portal was down Eventlog looks normal throughout the night Looks like some things going on portal wise. Paul

Same. The message says "Offline since Saturday March 26th, at 4:01 am" Reboot fixed it. The AC showed registered and online, pressing refresh changes nothing.

Tim That's more a function of how the MS is configured. If you click on it, and then options. Here are mine in the image below. If you set sensing to 'as motion is sensed', and 'on commands only', your program will get continuous "ons" and start over until motion stops. That keeps lights on while any motion is happening and then 1 minute more of time from the program. The program dims the light back down. Night only mode means it won't waste the battery sensing during the day You do have to take the sensor down, open it and press the set button inside of it until the LED blinks to make these changes. There is more in the Insteon motiosensor manual PDF Paul

Hi Tim Welcome to the UDI Forums! Give this a try Patio Light On - [ID 0014][Parent 0001] If From Sunset To Sunrise (next day) Then Set 'Outside / Patio Light' 40% Else Set 'Outside / Patio Light' Off Patio Light (Motion) - [ID 0015][Parent 0001] If From Sunset To Sunrise (next day) And Control 'Outside / Patio Motion Sensor-Sensor' is switched on Then Set 'Outside / Patio Light' 99% Wait 1 minute Set 'Outside / Patio Light' 40% Paul

ISY programs stop executing when the if clause is no longer true. As soon as the light gets turned on to 15%, the program exits. You can make a separate program (2) with no If clause and put the Then statements in it. Replace the statements in your existing program (1) with a Program Run Then statement to run program (2). That program will run until complete NiteLite 1 If Status 'MBR-Corner Lamp' is Off And Control 'ZW 002 MBR Motion Sensor' is switched On Then Run Program 'NightLite 2' Then clause Else - No Actions - (To add one, press 'Action') NiteLite 2 If Then Set 'MBR-Corner Lamp' 15% Wait 20 seconds Set 'MBR-Corner Lamp' Off Else - No Actions - (To add one, press 'Action') Paul

Kevin Its a new feature, and AFAIK you can't get rid of it short of solving comm related issues with the responses to the links that the switch sends. I have keypad key that turns off 2 sets of low voltage light transformers. One of them is very far away on the power line and I always get a red blink when turning it off. If its functioning properly outside of the red blink, suppose you could disassemble the switchlinc and cut the leads to the LED. Paul

Give this a look. Sounds like the memory card Paul

Great point, I forgot about that. When zwave was introduced to HS2, there was a long (2 years?) period of it crashing, memory leaks, etc. I lost a lot of WAF from that one, and think I finally have it back. As you say, it seems better now from reviewing board posts. However, having tried both, it turned out to be easier to migrate from HS2->ISY than HS2->HS3 Paul

Hi and weclome to the forums I used Homeseer for 10 years, V1 - V2, and a short stint on V3. I did have a hub 1 using Homeseer and was able to use both HS functionality, through Mark Sandler's Insteon plugin as well as the insteon mobile apps. You'd have to read HS board to see if that's true for the new alljoyn and Homekit compatible hubs. I came to UDI a year and a half ago because I didn't want to maintain a windows server for the sake of homeseer, and HS3 did not really offer me a clean upgrade path. However, I do believe HS can be run on Raspberry Pi. Overall, I'm happier with the ISY for my HA network, which is all Insteon from a powerline perspective. I think the ISY is better for your basic requirement of:"So here is my goal, I simply want to create scenes(?) that take advantage of the if then logic. Time of day, day of week, what else is going on with other devices and so on. " ISY Insteon integration is pretty tight. Homeseer is .net based which has some coding and integration advantages. The ISY is simpler, to me, to organize devices and logic, and the new portal capability makes it safe and relatively easy to access your ISY remotely while integrating with newer capabilities like the Echo and IFTTT. Kind of rambly, but I hope this helps PAul

GIve this a try On the ISY finder, click "Add" enter http://#.#.#.#/desc (Replace #.#.#.# with your isy's local NAT'd ip address) If it adds in the window, Double click on the ip address If it does not add or run, what behavior are you seeing? As a longer term solution, I would download the admin.jnlp on to your system and run it directly Paul