larryllix

Have a read about strip LEDs here and many threads around that era.

Thanks. I corrected the post just after. "RF" means Insteon, not wireless model.

Only four left. https://www.amazon.ca/Insteon-2441TH-Thermostat-RF-Only/dp/B007X5TY16/ref=sr_1_1?ie=UTF8&qid=1541642641&sr=8-1&keywords=2441TH EDIT: My mistake. The title states "RF only" meaning Insteon protocol. It the 2441TH (no Z)

It's been a while for me with LDs but linking cannot be done without going into linking mode first. This applies to all battery Insteon devices as a battery saving feature. They do not repeat Insteon commands or respond to queries either.

I have had this problem with other devices when some of the new options are enabled. My ISY slowed right to a standstill almost. Put the LDs into linking mode, one at a time, and let ISY play out what it is trying to do. Fix the options. IMHO some options don't work properly with many devices.

" Lights going on and off, programs going on and off, etc... I could barely use the AC with all those programs running. I finally had to unplug the ISY and go to bed." OK. maybe I misunderstood that comment or it has changed. Maybe you could get @Michel to interpret your log about 4 posts up?

Do you have any programs set to "Run at Power up"? If I create two programs with tight loops my ISY will grind to a halt and it will appear as if no program are running. The way I have found some of these are the icon flashing red and green erratically. When the ISY engine bogs down it's hard to get proper indications to find these. Flashing LEDs on the front may be a clue indicating ISY is running as fast as it can go.

"it still took forever to boot up and be able to login and once I could login I found that all the programs that were supposed to be disabled were enabled causing all sorts of issues. Lights going on and off, programs going on and off, etc... I could barely use the AC with all those programs running" This appears to be one or more programs oscillating in an endless tight loop and the finally bogged your Ethernet cache down.

I am.

@kclenden Nice!! Thanks for that. I didn't know you could see PLM links.

Network Resource module does that in 15 different shades of Ethernet.

Agreed! You have to be very careful with Else and multiple conditions / triggers. Somebody had requested UDI abolish the Else as few years ago. But what he really meant was to replace them with a "case" construct.

I think we are confusing links with scenes for counting. Not real sure on the bit twiddling involved Insteon anymore (never was ) but IIRC It takes one link for every node (I incorrectly posted "device") connected to the PLM. Most devices have a few nodes and can require a link for each node both ways. Insteon Scenes use one link in a broadcast fashion. One transmission activates all device nodes that contain that Scene link. I have 140 Insteon nodes listed in ISY, and 215 links used in my PLM. This affords a link each way to most devices, as well as a link to the PLM, and a link for each Scene installed in the device. When you add more than one device(s) to an Insteon scene, no new PLM links should be required.

The NodeServers present some advantages over Network Resources and vice versa. With the NRs I require a line to set each lamp parameters before calling the unified NR but I see you are doing that with PolyGlot, anyway. NRs do not allow you to read the current lighting settings and Polyglot does. NRs are all self-contained in ISY and do not depend on a third party box/hub. I use state variables for my major lighting setups. In my main gathering room I have variables $sGathRm.mode and $sGathRm.colour. I have defined a bank of Integer variable constants for white light scenes, as well as colour scenes suchs as $cSTRIP.RED, $cHUE.AQUA, $cML.BLUE $c.MODE.FULLON, $c.MODE.DIM, $c.MODE.TV, $cMODE.READING etc.. Each constant variable has predefined number assigned to it permanently. I have a bank of programs for each control variable with each mode and colour, as appropriate, tha does the diry work. These are combinations of scene calls, node server device calls, Network Resorce calls etc... to do whatever it takes to get the lighting I want. Ramp speed is adjusted to make the various time delays look similar and smooth. On the upper layer I have a bank of programs for each input from Alexa, GH, and a few SwitchLincs. These programs do very simple things like If SwitchLinc is switched Fast On Then set $sGathRm.mode = $cMODE.FULLON set $sGathRm.colour = $cMOOD.BRIGHT Else ---- Any program can now one-line stuff a single integer into these control variables and change a bank of 22 lights of 10 different brands, and match the colour responses. In addition, when you want to borrow a lamp to flash or change colour (garage door is open) , you can save the control variable into a temp location, use the lamp or parameter for an indicator, and then write the saved setup back in one line of code, when the alarm is done.

I have deleted my single program above. Use of the Else section in this manner may case oscillation of the variable and program after the program modifies one of it's own trigger elements. The single variable looper program should not function properly. My apologies for introducing this concept without proofing it again. As per @oberkc the parenthesese are still required.

How many scenes have you created? My understanding is that a scene containing every device would take only one linking position in the PLM as well as one link position in each device. When the PLM calls out "Now serving roast beef!", all the devices waiting with a roast beef ticket get served from that one call.

I was just going to add about the same words as Apostolakisl. You don't want two grounds and his analogy was excellent. Further than the zip-tie, you may consider a wired in module to avoid the exposed 3-prong receptacle without a ground and the second connectable feed to the outbuilding, that violate the safety codes.

Z-Mudroom Motion - [ID 001D][Parent 0001] If Status 'Z-Motion SII-Sensor' is On Or Control 'Z-Motion SII-Sensor' is switched On Or Status 'Z-Motion SII-Sensor' is Off Or Control 'Z-Motion SII-Sensor' is switched Off Then Send Notification to 'NGC' content 'ProgramName' Else - No Actions - (To add one, press 'Action')

Maybe try the program copy 'n paste again.

Post your program here so people can help you. R.Click on the program title in the program tree, select "copy to clipboard", then paste it here. Have you watched the devices webpage in admin console, to see if the signal is being recorded by ISY? You probably have links messed up between ISY/PLM and the MS.

In addition to beninsteon above, those programs can use just one of the six codes available from most Insteon devices. What this means is that you can use your Paddle up for the normal On, your paddle down for your normal off, and say the fade up (paddle up, long tap) for these sequences. I use one SwitchLinc to control about 20 different scenes, with 22 different lamps. <EDIT: Single looping program may become unstable with oscillation of the state variable retriggerring the program. Removed to avoid future confusion.> Another trick I used in my ensuite for an RGBWW rope around the room on the floor, was to add a "Wait 5 seconds, Turn lights off" to the Then section. This way the colours rotate with each Fast Off paddle input but after 5 seconds of Waiting it turns them Off. So you get 5 seconds between each tap for colour change but when you come back later and do the same button tap the lights turn off. So many programs to write....so little time!

I use a pre-defined value for each room to populate one variable for 11 MSes. I use easy names to remember for these values like $cROOM.MBR, and $cROOM.MUDRM, etc.. One common program watches this variable for changes off 0 value and sends reports, memorises the value in a variable log, and then resets the variable, ready for the next room. When I get around to replacing batteries I have a list of rooms needing service. BTW: The room constants defined also get used for other monitoring schemes, like Leak detection, motion during alarm sensing, etc.. I send a room chart with each notification of urgent involved texts. In my Integer variables I predefine about 100 variable values that never change = constants. I make them like this $cXXXXXXXXX

Two points must be reset. The lowBatt signal inside the MS as well as the ISY program / variable. Rebooting ISY may take care of the variable OK, but the MS will be locked on lowBatt and will never send it again. If you change the battery, power cycling the MS, the lowBatt signal should be reset at that point. I was hoping SH would have fixed/improved these MSes with the new version release. Already having 11-12 of the old ones it is not likely I will find out.

If you do not reset the device node first the program can continuously set your variable to the triggered state or never trigger again, depending on how you detect the change or node value.

My MS units are over 4 years old and they work fine yet. Seriously though...we lost the post numbering in this new forum software but the linking button on the top right of each post can indicate the exact post if you copy'n paste it.