larryllix

I have found different code techniques are required for so many different versions of the MagicHome/LEDenet bulb versions. Some of the newer bulb versions have simulated candlelight flickering built into the bulbs. White temperature adjustable LED lamps and some bulbs require a different technique where the white blends use a brilliance parameter and white temperature balance parameter instead of discreet CW/WW values. The PG3 NS may not support some of these versions. I have had to make many adjustments to my code many times when purchasing a new batch of bulbs. Mine vary from v1 to v10. Have you added new bulbs recently?

I use STATE variables to trigger almost all lighting scenes, also. When I want to "borrow" a lighting setup (eg: flash lights) I only need to save the existing value, replace with another value, and then after a delay replace the original value back into the control variable. Also, with mostly WiFi lighting, with no available feedback, I always know what the last lighting scene I left things at is. Using STATE variables for lighting controls makes things so easy to program, from multiple sources, once the bank of drivers is created and tucked away in a folder.

You can comment lines between lines and also comment the whole program. These are found in different portions of the edit boxes.

Confused me also. Is there a new skill being released or not?

Ditto here. Paddle switches cannot set colour schemes and 5 different lighting levels using combinations of lamps and levels for various usages. When I go to bed at nights, I would have to pull chains on 15 different lamps to turn them off, or use one vocal... ....Alexa, turn off inside lights.

Also IoX has a nice provided feature to copy'n paste your programs to this website. It makes it much easier for posters to read and understand. Right click on the program name in the tree, and select copy to clipboard in the falldown menu, then paste it into the code option box in your post.

Have you tried a factory reset on the MS first before attempting linking?

I only have two bulbs controlled by Insteon left now, after moving. However, I have about 20 WiFi operated RGBCW/WW bulbs throughout my apartment now. These run on LEDenet/MagicHome protocol, for which I wrote my own drivers that self-adapt to many different bulb revisions, including some White (CW+WW) only floor stand LED lamps. WiFi bulbs present no flicker right down to 1% brightness and are great to be able to adjust the colour temperature from about 2100K to 6500K. I use ISY programs to automatically dim them down from more daylight colours down to a orangey warm white, as the evening gets later and we do notice a difference in bed times lately.

Most LED bulbs do not offer enough leakage to maintain the dimmer circuit inside the control device. The dimmer has no waveform to lock onto for timing and when it shuts off the LED bulb circuit leakage then accumulates somewhat and the dimmer attempt to turn on again. A small incandescent bulb mixed in or wiring one of the small capacitor devices across one lamp socket usually fixes the problem. I bought a few packages of the Warm-Glow bulbs but they were the worst I have ever tried with an Insteon SwitchLinc dimmer. They would only turn on reliably at about 45% brightness. Home Depot refunded my money. HD has since discontinued all Philips bulbs in my area, Ontario, Canada.

I do not have an eISY, but two polISYs and they get warm also. I found routers that would crash on warmer summer days despite A/C in the house but, standing them vertically worked very well for increased cooling. I have several USB run muffin fans that I plug into other boxes to keep them cool. One was created out of surplus 12Vdc desktop box fans, however two are attached by permanent wiring, and one was purchased with USB attached from amazon. If there is cooling holes in the bottom, devices can lay flat on top of the 5 inch muffin fans with some standoff spacer legs.. The attached double units have a speed switch that was inside the media PC's case. I just run the fan on the low speed. It's enough to move the air.

I have a Govee Tower Fan, a Remote BT only Thermostat, an LED Array Curtain, and a LED String. Only one Govee devices could ever be found. I believe it found the LED Curtain initially until I installed the LED String. Then it switched over to that. I concluded the Govee NS could only handle one device at a time.

IIRC there was an instruction by clicking on the NS info in PG3x. There was a parameter to install into the NS setup in PG3 and it tells you about it in that info.

One more. I found ASUS routers didn't completely get a fresh start by rebooting them (I have owned four model now). When things got tough I always had to power cycle them. Reserved in the DHCP table makes the IP address static by the router enforcement.. Also defining it in a device makes it static.

AWAY is not VACATION. VACATION is a separate function with many more settings. AFAIK Vacations can be set fully on the thermostat or app where it includes dates and times for on and off, and also setpoint temperatures for heat and A/C.

This appears to be the same problem I had with my ISY994s, my polisys and possibly with eISY. From what I can gather: The power goes out and ISY products beat the router in powering up. ISY asks the router for an IP address from the router's DHCP server. Router is not prepared to be asked, and ghosts ISY, with no response. ISY tries again (x times?) and then gives up. Router boots up and sends out broadcast "Hello, everybody, I'm home" ISY doesn't hear it, or does not respond to it, due to being busy, or low level drivers still have some deficiencies with retries. ISY never tries again, and ISY never gets connected to router due to not obtaining an IP address. Years ago I had another WiFi based receptacle that could power cycle my ISY, as well as some detection software written inside my ISY that could automatically power cycle the router again with successive increasing time delays on retries. That seemed to rid my system of that problem. MY ISY counters did show some counts a few times over the years. Since polISY came to me, this happens occasionally but very seldom. It would seem possible that the O/Ses of both may be using the same C++ drivers.