larryllix

They have both listed under different questions. Probably a typo.

This sounds like you either have an inverter close to your PLM or ISY/PLM plugged into an inverter. It also sounds like you may a WiFi antenna very close to your PLM antenna. You don't need to wire your basement, (yet) just take the ISY and PLM upstairs away from that location to try it.

Did you ever figure out why the Test button wouldn't work? All my tests work with my Hue NRs. I wouldn't think programs would work if the test didn't????

I would just rip out the fluorescent ballast and mount a UL approved 12vdc power supply in it's place. Now can you do whatever you want with low voltage wiring and the high voltage wiring changes you made are all inside the metal fixture no different than wiring inside any other fixture.

True but whomever is doing it isn't really comparing anything, other than user's choices of HA system. Looks like a popularity contest. The reason I posted it here is, in that forum, things are very biased with so many participants selling and promoting their own products. The participants always get a biased view of the real world and ISY loses before the book cover can be opened.

Intermittent Insteon things are usually the comm signals have interference, not hardware.Try your ISY in a different location. Make sure you have your two phases of your electrical box bridged with a passive coupler or, Plug in a dual band Insteon device into each pahse of your distribution box. Try a dual band device between your PLM and the device giving problems.

I think one of the tricks with LED strips, and so many other gadgets, is you plug in a UL approved power supply and what you do with the 12vdc side is nobody else's business.

Glad I am not the only one!

At this point in time ISY seems to be second in popularity.

With the ISY994 you can interface almost any type of light into your HA system. I would install silicone sleeved IP68? RGBWW LED strips, with a 12v powers upply and controller and control it from Network resources or NodeLink, depending on controller and RPi availability and controller you use. Now you can light it up with white, bright, dim, Red, Green, Blue or any combination (some controllers can't mix white and RGB). LED strip 5m = $18 Controller = $16, Milight requires a Bridge/Hub = $12 Power supply $10 Connectors $1-3 Network Module = $49? YMMV

Yup. I used a dozen Network resources for 9 bulbs/strips and 2 hubs, for many months. Now io_guy has written a Nodelink Node for them that remebers what you last set them at. Either system you need a 12v 3-6A power supply, and a controller for each strip, but the MiLights also need a WiFi to priority 2.4GHz bridge/hub. The MiLight controllers are one way comms, only, so you can't interrogate them for status. They just obey what you send and with NodeLink, remembers what you set them at. There is a recent thread concerning a newer controller for the strips (around the $15-18 each) that should perform better, and you can mix white and RGB to make pastels or white temperatures. No hub is required being WiFi listening controllers. The technique to NR control these is still being discovered. Look for the recent posts in the thread. The major issues are working. Many of us have these newer controller on order to experiement with so expect more progress.

I believe the "push-in" connectors have disappeared and been replaced by the insert and tighten type connections. I had a house full of "push-ins" with aluminum wire that almost caused a few fires done by some "electrician" the builder hired. back in the 70s. My wfe burned the back of her hand on a receptacle, before we realised how the house was wired. I don't remember grounds ever having the push-in connections.

Link seems to come and disappear but here is the results so far: https://docs.google.com/forms/d/e/1FAIpQLSdiu2EhOi4hb6gN4RQa-U6VA-SZ711Es1wseEkvcBqUI1r7eQ/viewanalytics?usp=form_confirm

My 2441ZTH displays every 0.5º C also but it doesn't send updates to ISY until about a 1.5º C change. I assume that equates to about the same as your 2.x degrees F.

If the results show many are using ISY, many more may follow. People often look for safety in numbers, when making purchases.

Ewwww. I would try to isolate your ISY from those noise makers on a different circuit, as a trial. You don't have the unit plugged into a UPS do you? They can produce the worst waveforms and burn out lots of devices. Just had another thought. Perhaps your ISY power supply is going bad and all your PLMs just look bad but really it has been the ISY PS. You should probably talk to UDI about this and let them help you get to the bottom of this. You have enough history for them to diagnose this and provide further trials to zero in on this.

If this is happenning to several folders and started after a version ugrade, I would install the latest stable version that is showing on your Admin Console after a backup, of course. If that still doesn't solve it I would make another good backup and try to factory reset your ISY, then restore the backup file. You may have to reset your geo location, DHCP, and other basic setup parameters again. It took me about 10 minutes for the whole process.

I assume that you know when the program is freshly triggered by the results and not the program icon colours? Have you tried to change your folder logic to positive? If . . $AlarmArmType is 1 Then . .

As per paul's report post #9 this sounds like the weak capacitors used in PLMs are being bombarded with powerline noise that the PLM filtering caps have to absorb. You envorinment may be making the PLMs die prematurely. Perhaps a change in filter capacitors to top qulity units, and/or finding the noise source may help.

Do the programs in the folder "continue to execute" or continue to be triggered?

May be good for ISY users to represent themselves at cocoontech.com forum. No forum membership involvement. https://docs.google.com/forms/d/e/1FAIpQLSdiu2EhOi4hb6gN4RQa-U6VA-SZ711Es1wseEkvcBqUI1r7eQ/viewform#responses

No Noob there when it comes to posting screenshots etc. When State variables change value they cause the ISY real-time engine to run through your programs and evaluate any logic that contains that variable, usually in the If section. Using too many (hundreds to thousands) may bog down the real-time engine processing, so IMHO you want to limit your State variable usage to only key variables that are needed for this function. This doesn't happen with Integer variables. Integer variables do not trigger any evaluation and just sit there doing nothing. Consider them lazy. I use hundreds of them to define values as in constants that never change. eg $TRUE, $FALSE Both types of variables can be used as logic filters eg: If 20 <= $sVar <= 30, just as well. The gotcha' comes in when you use trigger causing items (State variables, time periods etc.), as conditional logic filters in programs. They can cause sneaky triggers of Then and/or Else programs sections unless the program is disabled. Then the only way you can get the program to run is to call it from another program. EG: If . . $sVar >= 20 Then . . do something . . Wait 10 seconds . . do something else Else . . -- If $sVar changes to 19 while Then is running it will stop during the Wait and run the Else. Got it? ... ....Send money!

I may have missed a big point here. To trigger program and IIRC to get the attention of a folder condition, from the ISY engine, the variable used must be a STATE variable. Integer variables do NOT cause evaluations to trigger programs or folder evaluations upon value changes. Also....most of us use a prefix signifier to signify State variable usage. It helps everybody, including yourself to know what type of variable you have used. I use $sVariable_name, and some use $s.Variable_name. Note: I do not prefix my Integer variables, others may. You are very welcome. I just hope it helps the way others help/ed me.

Your program trigger to detect you are hone is the same one that enables the folder and allows the program to "see' the trigger. You have a race and apparently the folder gets handled last so your program is blind to the change. I would remove the condition from the folder and test. Another thing I prefer, is to set the stat into vacation/home mode. That way, any changes made on the stats become effective without running Admin Console and other clumsy (for every day usage) programs. I use multiple MSes to control my Occupied mode. Based on that and a 16 hour delay, I then flag $sVacation as true. $sVacation sets my stat temperatures back when it changes. Any movement gets a four hour timer to indicate house occupied. After midnight to 8:00 AM, no timer will change that. If the usually mudroom exit place MS gets triggered, the timer is only 20 minutes. If I set my KPL password into the security system programs, Occupied is False immediately after a 1 minute beeper warning. My house will correct about one degree per hour so, if I correct my stat when I enter the house, I will be tossing and turning in the heat and humidity all night. My setbacks are much more conservative. In view of that, I try to remember to set my stat back to Home mode the morning I am travelling home again. Edit:Typos

I use the MiLight controllers but 4100K is not available via them. With the MiLight/LimitlessLED controllers it's RGB or White, no mixing but the SuperNight RGBWW strips have the nicest white I have seen. Very smooth white good for work surfaces without being 6500K but good for softer lighting too. My guess is about 3000-3500K.