larryllix

Isn't that little arrow supposed to point at the sensor? I would think that would be the side of the open magnetic field (horseshoe magnet format) and you have it across the steel hinge.

This has come up before where two variables are compared. What you see is a rounded off value based on the NS programmer's algorithm which may not be the same value the ISY rounds off to. 2.99999999 is not 3.00000000 The < should have worked though.

As per @garybixlerabove but take the time condition out of the If section, and then you can either wait for the value to change, or run the If section manually to your hearts content, until you have it figured out. Then replace the time restraint condition.

Ahhhh....My guess is you have the magnet and sensor enclosed in an almost complete ferrous loop that bypasses the magnetic field and weakens the magnet's strength.. You could try mounting it a wooden board or aluminum plate to isolate it from all the steel and iron surrounding it.

The program can only ever run true when the ISY clock runs the program at exactly 1:37 PM. I am not sure how you are testing it. The 2.8 volts will alarm with the batteries about 50% left, in cold environments, and almost dead in warm environments.

Speed usually doesn't matter but filed strength of the magnet does. However if the magnetic field is barely string enough, the speed may cause a mechanical vibration inside the device, or if you create some mechanical shock the contact inside may be jarred loose enough to make it transfer. I have seen many contacts that will not close with a weak field but work when some mechanical shock is added in relay work over the years. Are you sure your magnetic gap is wide enough to make the device sense "Open/off"? @Brian H may be able to tell us what type of contact is inside these devices. I assume they are sealed reed type contacts. May be a manufacturing defect where something sticky (oil?) was inside the sealed glass envelope or on the contact making it sticky.

I would think we can conclude it is happening inside the modules and not ISY. Also freezing and/or ice inside is not an issue. Possibly some rain got inside? But both is a snag in that logic. Can you test with another external magnet? Possibly the magnetic strength is too weak or too large of a gap? Have you tried wiggling the device (physical shock) after the first close, and it fails to update, to see if the contacts have some stickiness to them? Some devices have 3v AA lithium batteries. If you replaced them with a 1.5V AA battery, it could do strange things.

Did this happen in the warmer months also?

How many devices do you have connected to your router? Not just WiFi but your whole LAN count of devices? My ASUS AC68u (about 5 years old) would not handle more than about 52 devices. No errors, no complaints from the router. When I was running WRT-?? OEM firmware on that router the count allowance was even less. It threw NVRAM shortage errors for a long time once I crossed about the 45 device mark, but I didn't understand why and their suggestions were not helpful. It turned out they upgraded that model's NVRAM from 64MB to 128MB and I got an old model on sale. Three years of anguish was not worth a few bucks. Don't be confused by the range of the IP address table. It is not related. My problematic router could distribute 510 IP addresses easily, but couldn't actually remember that many. When you reboot all the devices compete for an IP address via the DHCP server. When mine finally disallowed my ISY994 and polyisy fro getting IP addresses while in the Caribbean, I wasn't too happy with it, and bought another $600 in routers in order to sleuth the problem and look for a fix. ISY was attempting to send out commands using a 0.0.0.0 address in the logs.

Did you know the admin console has a search engine to find anything by Variable name, program name etc?.... Right click on any program name and select "Search and Replace" option on the pulldown menu.

The Stop at the end of a section is useless anyway. Without Stop at the end of each section the program was going to end anyway.

A scene with 0% will not do it, as you are turning the switch Off which will turn any scene off also. A scene with Closet Light On as an output will not work as it would also turn on the closet light with the main room light turn on. You will have to use a program and no scene(s). What is the problem with a 1 second delay to turn the closet light off? An On delay can definitely be annoying but what is the problem with a slight Off delay due to Insteon comm delays?

I wondered about that combo colour also. I agree it sounds like a hardware problem now. Likely software colours are mixed up with hardware colours as well as two traces shorted together where the cut was made, or a connector doesn't line up with the traces on the LED strip. RGBW strips have at least 5 traces to connect to while RGB only has four traces to connect to. They cannot be interchanged. Things are not always solderless, just plug and play, in this world.

ISY is a self-triggering event driven language. When you manipulate an element's status within a program you usually suffer a repetitive oscillation in the program when the same program's "If" section detects the change. "Stop" only stops the current execution but the If section retriggers it and it starts again. You may have trouble getting control of your ISY if you run this program.

Welcome to the UDI forums!! I have a few dozen of these strips and many of them have different wiring. First when cut the opposite end has the wiring reversed. The ends of the LED strip may be marked RGBWC for Red, Green,Blue,White, and Common. First you need to find the common conductor on the strip and wire it to the C on the controller. Then turn on one colour only and touch the wires from each LED contact to it until the colour matches the selected colour. Repeat until all proper colours are wired.

Unless the door closes before

To combine both taps styles you can OR them into the same program trigger. If SwitcLinc is switched On OR SwitchLinc is switched Fast On Then whatever

If ELK Garage door sensor is violated Then Wait 2 minutes You're a pushover Else ------- If the status changes the timer ether starts over or runs else and cancels the timer process in Then.

Did you know the admin console has a search and replace function? You can right click on any program title in the program tree and select "Find and Replace" (or something similar) and then find any occurrence of that program name by various parameters. You may be able to find a forgotten program calling your suspect program.

Correct. The ISY Portal provides a tunnel type access that is initiated by ISY from inside your LAN. Then your external access uses a fixed address via UDI's server that can send controlled access packets into your ISY. When your ISP IP address changes you don't have to track it or know it. To me the security is less than port forwarding as you now have an account and password to access your ISY as well as UDI having access to it. It does work well, it's easy, and you can get international access that is static and considered safer by most.

Yes. The java admin console was launched about a decade ago and improved every few months. The HTML5 conversion is not known when. It has been worked on but many other more important projects sidelined it over the past few years.

ISY Admin Console runs on java. Java has been running under almost every operating system for decades. Once the admin console is ported over the HTML5/CSS/js it will run on any browser than runs under any O/S.

Some observations. Netflux is the brandname used in the past. The app being shown does not appear to be the MagicHome app, despite their many claims of using the MagicHome app. It appears to be another protocol that nobody has cracked yet. OTOH they do show the actual MagicHome logo. I would try the MagicHome NS. It isn't fancy but may get you going and prove it one way or another. I am not sure if the NS will self-adapt to 3 channel controllers though. Most people want white also.

I think the LED shows it connected to the PLM. It still looks like could be a PLM problem to me.

Yes but some report most Insteon devices won;t function plugged into the same receptacle. It may over drive the receiver circuit. If the PLM powerline transmitter isn't working it wouldn't work either. Did you try plugging a bad i/oLinc into the same receptacle with a working dual band Insteon device? Have you tried the four tap test to determine if the Insteon signals are transversing your phases to the i/oLinc? Have you tried another Insteon transmitting device with the i/oLincs or just the PLM?