larryllix

If these devices are Insteon, right click on each device, and select Restore in the admin console, device tree. Give it about 30 seconds to write the link table in the device. You may have lost links to each device.

My last router (ASUS RT-AC68u, AC1900) started crashing out connections about 52 devices. On power up they just couldn't get an IP address assignment. Sometimes it was my ISY994. Sometimes it was my polisy that didn't get an IP address. ISY using 0.0.0.0 for an IP address doesn't work too well.

ecobee all the way. I have tried many and ecobee is the best for stability, accuracy, and stability, and looks. WiFi to cloud as they all are. Awesome drop in NS that handles it well. Nodelink also supports it. Sent using Tapatalk

Check all your spam folders in every email you have ever had. There may be a permission email you missed to authorise a new connection, or a connection they want more information from you before it will allow it. Access the google mail webpage access and check there.

I don't totally avoid Insteon scenes. I use them with MSes for speed of ON response. I use them for multiple lights in my gathering room to allow them to be fairly synchronised, along with my WiFi lighting bulbs and strips. I use scenes for all lights functions like flashing the whole house for alarm purposes. Most of these are non-critical applications and if they fail it isn;t such a big problem. In my 3:00 AM routine to turn off everything I use programs with individual lines of code, so that the status is reported back, and Insteon will retry up to three times if no ACK is received from each device. If your 3-way scene is not working you may need to improve your comms or reduce your interference somehow. If it always fails use the admin console to examine and compare links. The direct linked scene is the way I would do it also, in that case. From programs you could operate the light directly. ISY doesn't know anything about secens anyway as they have no status. My ISY bulbs and strips are all RGBWW units. I have 31 units now. To control them I use NRs to send command like URLs, receive them in my own NRbridge software, running inside polisy, that determines what brand of bulb they are and sends the appropriate URL lines out to each bulb. By prepping every bul that will be operated first and then sending out the final levels in rapid sequence I can make them appear almost simultaneous (no popcorn effect). In that case the effective "scenes" are hard coded into the NRbridge software. ISY and polyglot NSs haven't been able to do things fast enough yet.

I have never controlled a scene directly from Alexa ----> ISY Portal. I use very few scenes and mostly control programs and/or Insteon devices. The majority of my lights are WiFi protocol so it takes an ISY program to co-ordinate them with Insteon devices/scenes. In ISY Portal I define most of my devices as Switches so they only get On/Off commands. Scenes have no checkback confirmation from the device, so no Insteon retries. If I want dimmer lights I use "Alexa...turn on dim decks lights" and a program does the rest. The delay is insignificant from a vocal command anyway.

@skierdude Use an Alexa device control instead of an announcement

Click on the cyclic arrow,almost top right.

V5.2.0 installed over v5.1.0. Went like clockwork without a hitch. I have only Insteon and LAN based bulbs/devices, no Zwave., + polisy with ecobee NS.

Yeah, programming is critical. Without that 1 minute delay that program could hang your ISY so it may never catch up.

Here is the program I posted: If KPL.A is switched On AND $sLED1.timer <= 90 Then $sLED1.timer += 30 Else $sLED1.timer = 0 Here is what you posted: 'LANE1-30' is switched On And $sS.L1.TIMER >= 90 Then $sS.L1.TIMER += 30 Else $sS.L1.TIMER = 0 Do you see any difference other than the element names? Your other programs have been even worse. You need to proofread more closely.

Turning off the power to these types of devices does not usually work. The control unit will come back on with full On, the last known setting, or not at all. Then it will take 20-60 seconds to reconnect to your router and reset it's circuitry. Likely you will have to get a packet sniffer and hack the bits coming out of the app, unless somebody has already done it for you or they publish a local API for the interface. With an Ardiuno i/f you may have a pretty good chance of access methods. Those lights are pretty cool but any automated lights on staircases is a bad idea. If an off animation like that happened while somebody is walking down the stairs they would likely fall down the stairs. Even just plain old fashioned lights out can cause falls. People's brains react badly to simultaneous physical co-ordination and visual stimulation. Ask anybody that has experienced VR headset simulations.

Yup! UDI is awesome! That is one big reason so many of us are here!!!

You need to pay closer attention to all the lines in the programs. I am totally confused by what you have done. I suggest you copy verbatim until you get it running and then experiment for education purposes.

Just to complicate things here If status of SwitchLinc is On Then turn On light Else turn Off light Functions almost the same as If SwitchLinc is switched On AND SwitchLinc is NOT switched Off <------ when switched off becomes NOT True Then turn on light Else turn off light Except for one small point ..SwitchLinc is Switched ON/Off tells you when a finger is on the switch first depressing it. ..SwitchLinc status tells you level of the dimmer electronics no matter what changes the level. State variables present both a status level and a changes trigger. A SwitchLinc line in a program is only True when being called by the ISY event and always False any other time (the button is not likely pressed, anyway). Status can be true or false anytime. Hopefully my ramblings help somewhat.

That's when lighting power conservation was paramount and there wasn't much more we wanted to control.

@poetaaronFirst get rid of the Else code for each program. When the variable changes to any number less than 30, all program Elses sections will attempt to run simultaneously. Your Insteon system won't like that much traffic. Rather than finding it I will create the countdown timer from mental confusion. If $sLED1.timer > 0 Then Wait 1 minute $sLED1.timer -= 1 Else set lamp Off That's it. Self triggering and self- retriggerring, and simple. ISY is amazing! Oh! BTW! You can right click on your program name in the program tree and select copy to clipboard. Paste into your post.

When using the MS II, the retriggerable possibilities in ISY programs is not possible. When you disable the Off command from the MS II, you lose the retriggerable timer possibilities, from the MS II, also. Now that I am aware the Off cycle in the MS II is NOT doing what I thought it was, I can see some possibilities for a very short timer duration inside the MS II and make it run like the original MSes. More experimentation needed here but sounds more promising now.

Take one for the team. Contact UDI support. They will want to know about this and will help you quickly.

Interesting. I have not seen any other poster reporting this about any MS II. Can you post a screenshot of your option settings?

There are many threads about fixing PLM power supplies in the forums. My guess is the same power supply capacitors are used. @Brian H here is a top notch hardware guy that has driven most of the fixin's on that note and may have ideas or info on the insides of the Hub.

If he is in Canada, the shipping costs will cost him almost half the price of an ISY994i and it will come without bad power supply capacitors. It sounds like Insteon is starting to admit that bad PSU components were used.

It is all about having lights on bright and for extended retriggerable times during the day light hours, and very dim and for very short retriggerable times during the night time hours. This doesn't seem to be possible using the MS II with a direct Insteon Scene, whereas using the old MS it was, using a combination of Insteon scene and ISY programs. For occupancy I mostly use MSes that set a programmable timer. Each room sets the timer at different times. In the TV watching room I use 180 minutes due to little motion at times, while the typically exit room, I use only 20 minutes, assuming the person may exit. Is the house security is turn on the timer is set to 1 minute and times out quickly. From 11:00 PM to 8 AM the timer is stopped from counting down. BTW: To use the '@' notification system you must choose the name from the dropdown menu or it just becomes normal text. @greazer vs. @greazer

Always, always, always, factory reset every device before linking to ISY 994. Build your Scenes between Insteon devices in the ISY admin console. ISY is a fabulous Insteon scene manager and will make it easy to edit or create them. Then programs can turn scenes on and off inside ISY also. Insteon devices that are not factory reset can give you a lot of grief down the road when they magically do things they shouldn't and cannot explain. Welcome to the world of ISY! It will take some time to get the triggered events concept down but you will not regret it later. Make sure you upgrade to ISY V5.++ if you do not have it installed. Upgrading from v4 to v5 can cause some stress at times, with existing programs and scenes.

ewwww. I hope there are plans for that one. The owing Battery Writes cause a lot of delay in my ISY.