larryllix

If you are still concerned, check the Program Summary tab for the Last Run column times indicated.

UDI may be aware of a method to save his bacon. Other than that, you can factory reset your ISY. load an ISY image, restore a good backup, and be back in business with new security credentials in about an hour.

They should be red, indicating they last ran False / Else until the next trigger leaving them green, indicating they last ran True / Then. BTW: You have modified your Christmastree programs and haven't saved the changes.

One step missing is to reload the ISY firmware image. IIRC it will be one of the only options available on the admin console the first access. Then you can load your backup file. Sent from my SM-G781W using Tapatalk

yeah. I have been thinking about an HTML chart to show the options of all the devices to show what andcwhen with just checkmark but have never gotten a 'round tuit. Sent from my SM-G781W using Tapatalk

Changing state from 10% to 11% is also an event. It's mostly about semantics anyway.

Note: A "control switched on/off" is always false when tested by another initiation/trigger. It can only be True when it calls the attention of the program to evaluate it. eg. If control X is switched On AND If control Y is switched On. will never be true. One statement can be true but, the other will always be False at the same time.

Did you do a power cycle? I find many warm reboots on devices don't seem to do it properly for me anymore.

Just use the old ISY technique using a long off delay timer, and set the MS II timer to something short...say 15 or 30 seconds, to avoid too much battery and Insteon protocol action. You may want to disable the Off commands from the MS II, if you are not going to use them, to save battery life. This should work if motion is not continuously seen by the MS II during your time out period. If motion is seen before the MS II internal timeout then your light may time off occasionally. You may be able to use a one and only one set of programs to ensure a long timer, ignoring retriggers, while a shorter timer using retriggers runs, and ORed together to get the best of both timing logics.

Telnet is not the Internet and no Internet access is needed. Port forwarding is not needed and should not be enabled much, if at all. The IP addresses you are posting would not even work outside your LAN. I forget the syntax for Telnetting (look it up on duckduckgo.com) but it is done from an open command window on your PC or laptop. https://www.lifewire.com/what-is-telnet-2626026

Nope. I never have worked out a decent way. I let the MSII do the timing and turn the lights on and off now. However ISY can dim the light in the scene dependent on time of day. Only the length of time cannot be adjusted. My MS IIs have all been retired to occupancy detectors now, except one in my laundry room. The internal timer is retriggerable too so it works OK in that application.

Yup, my google calendar connection disappeared two weeks ago, and when I got it back it was inside my other gmail account somehow???. Suddenly last week, the original account connection appeared again and I had duplicate events all through my calendar, until I removed the google calendar found inside my other google account. Google plays with their security process frequently and annoys the heck out of clients with repeated logins every time some code writer thinks s/he has a better idea. Then, they try to make the client think they forgot their password, so they can get another piece of personal information each new login, from him/her.

Use the "restore" command on each device in the admin console and then test again. You may be missing a link in some fan controllers.

I use a few state variables that trigger banks of programs, scenes, and NRs to control my coloured lighting and my white lighting. When I want Chistmas lighting I use this. Set $sRGBW.mode = $cMODE.XMAS Set $sWhite.mode = $cMODE.XMAS <---- some predefined permanent value in the constant variable (Integer type) ..and the banks of programs do it all. When you "borrow" a lamp for temporary usage/flashing alarms, etc, the status quo can be returned by replacing the variable with the saved/same value, and your ISY will restore everything again.

Welcome to Google security advances beta! I get this on some google or gmail service about once per month for the last five years. Another new summer student working on his latest security idea.

I use a combination of techniques. For alarming methods I use scenes containing every Insteon light and noise maker in one scene, so I can flash it on and off. For controlling levels of Insteon bulb circuits in my Gathering room I use programs and continuously vary the levels via programs to simulate sunset and late night lighting fade down. Of course a lot of that is combined with 15 or so WiFi RGBW bulbs and lighting strips too. If you operate a lot of Insteon devices from a program you need to insert Wait 1-2 seconds between more than 2-3 operations or you can overrun ISY's Insteon protocol cache. That gives a random bulb change look that isn't desirable. Ramping can help that somewhat. I do use scenes for my same Gathering room bulbs but they are grouped into scenes like "FullOn", "Bright", "Dim", "TV Watching", "Reading". Those are then combined with WiFi RGBW lighting to create the same brightness levels as well as festive coloured lighting. My decks and porch do the same. The MagicHome bulbs are under $10 each and I run a piece of software on a RPi that groups them into scene operations. That is controlled by three ISY NR's and variables inside ISY all based on percent levels.

Use programs to scale through useful brightness levels. I won't use scenes much. I find the really only useful levels to be about 100%, 40%, 20% , and 10-12%, depending on LED bulbs low end capabilities without flickering and extinguishing. It should oly take a few minutes to drag and drop 75 devices into each scene. You aren't going to do it more than once. ISY V5 has made setting levels to a variable and I use it do gradually dim many bulbs to simulate a sunset style lihting drop by multiplying the level of each bulb by a fixed percentage each iteration. I wouldn't try this with scenes as you may wear a few Insteon device EPROMs out, constantly rewriting them.

Can we use it for a musical instrument until fixed?

Because with that size of a business somebody has to answer email and sweep the floors. Rhetorical answer.

I hope it wasn't three short, three long, and then three short again.

I would think an air movement detector would be a better option. Trouble is the size of the circuitry/mechanism in that location. Possibly a vane flap with a CAO Tag sensor on it, could work. You would have to change the CR2032 battery every 8-12 months. The dust and grease may be a problem for any mechanism, though.

Are you using the Chrome browser locally? If so you may need to use HTTP://.... (no 's', & no port:443). You may not be able to use the Basic security technique on a Chrome URL line (browsers will not allow it now) so it may never work. Also, I am not sure a browser will actually do anything for you as it take admin console with java to access it properly. ISY may not substitute a full URL with https:/xxx.xxx.xxx.xxx:433 and you may have to type the whole URL, not just an IP address and port number. Is your browser external to your router to access the port forwarding side?

I wouldn't add too much wait time as the user will activate the switch and walk away, not realising the lights came back on. The user needs to know they came back on. I would presonally use about 1-2 seconds so the user can see what happened.

We still haven't seen any program attempt to help with. That is usually the basic starting point with people wanting help, using a starting model. Anybody else?

When you have a list of Insteon devices to operate, and one hiccoughs, the Insteon protocol will retry three times, each time waiting for a confirmation. Then ISY's cache wil overflow and it will have to drop something = missing operations. Like the rest said....insert some Wait 1-2 seconds every couple of lines and post your program. Right click on the admin tree name of program and "copy to clipboard". Paste into your post using the code feature = '<>'