larryllix

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?

What type of powerline bridging between the two phases do you have? It may be possible you blew out your phase bridging and now powerline only devices don't work on the far phase. This still sounds like a PLM problem where the dual band devices are carrying the rest of the powerline devices but only in certain locations electrically closer to the dual band devices. How old is your PLM? Is it time to have a spare one that you can test with?

The All On phenomenon is theorised as a clash in Insteon signals that appears as the All On signal to any Insteon device that cleans it up, repeats it, and causes Insteon devices to respond to it. It is thought to be created by RF devices clashing with powerline signals and confusing the protocol somehow. This can suaully be prevented by not echoing commands immediately in programs. eg: When an MS sends an On signal to a device, and a program resends the same command immediately after. One of the big gottchas is the KPLs which contain many devices in one Insteon address and physical box. Receiving a button On signal and turning on any LED in the same KPL is a likely problem. Inserting a Wait 1-2 second(s) is thought to help with Insteon protocol congestion. Using scenes and not programs where possible may help because no second signal is issued. This also may be exasperated by powerline noise as it can confuse signals and cause bits to be falsely enabled in the packets. See the wiki for more clues how to resolve this problem.

The all on bug is a Insteon Scene type signal and does not send a status update. That is the big problem with the all on bug. ISY has not been able to detect the unwanted actions. Polling may help. Sent using Tapatalk

Possibly your PLM powerline output is dead. The co-incidence is too strange. The other powerline devices could be receiving signal via another Insteon dual-band device converting the RF, while the near units cannot see any powerline signal. Try moving a suspect i/oLinc to the same receptacle as a working powerline only device?

Easiest and most likely powerline interference test, is to unplug all garage door openers, and reinstall the KPL i/oLinc again. It's a very common problem with Chamberlain GDOs.

That sounds like some firewall problem that wakes up late to the party. ISY Launcher is a cloud based service app.

I did that with a few X10 Appliance plug-ins to run a big old 50A 240Vac mercury wetted solenoid I had hanging around. Worked great until I tried to turn it off. I am not sure which X10 Appliance model exploded on the first and which exploded on the second trial. A 20Kj MOV lolipop across the coil and another X10 Appliance module has been working for years now. You may want to consider using a MOV across any inductive coil fed by a contact. I am not sure how serious Insteon's hp rating is for their OnOff module / Appliance module. It can;t hurt either way for about $2.

Are you sure about the2413u PLM model number. I thought that model was the USB version and ISY994 doesn't have a USB port. Have you tried the ISY Launcher? It will automatically match your UI version with your firmware. Have you checked if your UI version matches ISY's firmware version? Sounds like a job for super UDI support!

Ithought about that a few years back but it didn't work out for me. One of the most basic things was that WoL can only wake devices on the higher subnet. hmmmm.. ISY may be able to handle WoL with two subnets. Have to examine the WoL admin console page. You would need a second DHCP server to handle the second subnet. Most routers don't handle that well.

For some controllers/bulbs I had to turn the bulb on first before sending colour levels. Others the order didn't matter. Some types cannot have a white command and an RGB colour sent at the same time. Some require a mask to specify which you are sending RGB or White. The wrong sequence, nothing will happen. I found an old copy of the hacked API from the linked thread. Extend your timeout while experimenting to say... 1200 mSec. If you got some response you are the right track. MagicHome API.txt

Cree became so unreliable that Home Depot took them off their shelves. I had about 5 bulbs out of twelve go bad. When I attempted to replace a chandelier full of bulbs the new ones dimmed with different curves and looked like hell. Some Cree bulbs are still in usage but they earned a bad name and many others came to the market with better pricing. I didn't know Cree still existed as a bulb producer.

See post above also. In the examples in the thread you linked to I will a attempt to demo this from memory. Red: 49;255;0;0;0;0;15;63;129;138;139;150 <----checksum should remain the same with a deleted 0 = fourth channel Green: 49;0;255;0;0;0;15;63;129;138;139;150 <----checksum should remain the same with a deleted 0

I don't believe the codes are exactly the same. In the packets you have to send as many channels as your controller has. In my controllers they are 5 channel to support R,G,B,WW, & CW. I do not use the CW, and it was probably discovered it was useless after users owned them for a while. An extra strip of W was not needed as you could mix in some RGB colours and make your own for no extra hardware cost. In the four channel controllers one byte was eliminated in the channel list packet. I assume anther byte would be eliminated in a 3 channel controller. These bulb types annd brands are determined by a common protocol request for status send the the bulbs. Of course NRs would not have that luxury as ISY cannot read any intelligent responses and/or parse the response using NRs. Do you have a RPI or polisy to try the MagicHome NS? It wasn't fancy but IIRC it sorted out the bulb styles and uses the correct packetting. If you are familiar with python3 I have my NRbridge code if you can make some sense out of to create your NR packets. I used variable substitution to create custom colours from one NR. I used three in the end. ON, OFF, & SETLEVELS, for each IP address/bulb. I have since dumped that method and use 3 NRs to send the same but my NRbridge handles the fine details including synchronising bulb groups and animations, and native bulb effects. The flashing is very handy for notifications.

Which method are you attempting to use? NRs or the NS? The NRs do not report ant data back and I am not sure you will get any back unless certain modes are turned on. Have you fixed your IP address for the controller in your router DHCP reservation table and power cycled the controller?