larryllix

If you answer oberkc's question it may change the method of condition in the program. The one given will not detect if the light us turned on from other sources. Sent using Tapatalk

Are fanlinks not just another triac based dimmer used with a motor, and why they cause humming and burn out frequently? OTOH, fanlincs may have some built in noise suppression in an attempt to make them more suitable for motor applications. Sent using Tapatalk

We need to see the exact syntax for the program. There are various methods of detecting events. Right click on the program title in the program tree and select copy to clipboard. Then past it here. What MS device are you using?

Welcome to the UDI forums!!! A simple re-kicker If section in case of stalling (reboot or user interference) and a looping repeat in Then should do your job. If time is 8:00 AM OR time is 8:00 PM <------- more times could be added if critical that it runs. Then Repeat every 19 minutes <-----this really means "Repeat after waiting 19 minutes". set Scene On Wait 1 minute set Scene Off Else ----

@keribi ...and the program icons should be displayed with a warning...in yellow. Look for other programs with yellow avatars.

Somebody could unscrew the bulb and then there would be nothing ISY could do. If somebody turned the switch off, they may want it left off. If we don't ever want it off, ISY can deal with the notification when it was switched. The options are there for whatever you can imagine to do with it and not just lightbulbs.

Gives a bracketed timeframe from x time FOR y time. Sent using Tapatalk

ISY cannot cycle itself. Once off what would turn it back on? Heartbeats for LDs do not reset themselves. They just transmit a signal each 24 hours. If you detect anything that is not 99999 you should trigger your program each day. LDs need to be manually reset with the button on them after triggering or they will not trigger again. Sent using Tapatalk

Yes. I have had this same problem. Insteon likes to retry a few times when no response is received. The PLM should be able to accept this trouble and work around it but it doesn't seem to in my case. This seems like it may be a problem between the PLM and ISY missing some handshaking and overflowing a cache. You can insert a Wait 5 seconds line after the bad unit command line, or move that program line to the bottom of the program and retest.

I have found each MagicHome bulb clone uses the same protocol except that some will not mix RGB with White and some will not accept dimming commands until turned on while others can be set before and then turned on. I have done a lot of work with python on various LED strip controllers as well as bulbs. They all have some different quirk. @Scottmichaelj was upset about the popcorning effect for the bulbs and strips, as they take time to set each one via Ethernet. I have found ways to make the sequencing delays almost imperceptible to the human eye, but with 23 bulbs the delay is really long after turning them on/off from ISY. So it is wait for a while and group turn them on/of or activate one at a time in a sequence. If you use variable substitution with 3 or 4 NRs only you will run into the 1 seconds delay factor. If you set a bulb to blue and then set another one to red immediately, the singe;/shared NR will set both to the last colour as the program will change the variable substituted before ISY sends out the first NR. I only use four NR for all bulbs. ON, Off, Set, and effect. I send them to a RPI python program which handle groups of bulbs and speeds things up. Now I have discovered RPi 3 has a slow task switching time that interferes with fast send sequences too.

V5.0.15 The latest. In this case beta does not mean unstable.

V5 since it started (2015?). Always been stable. Only some ZWave quirks are being worked out. The new features have always worked from v5.0.1

Are we talking disable the local control of a lightswitch, for example? Sent using Tapatalk

I don't have any zwave but with Insteon you could possibly trigger a program using the switched event ANDed with the On status. I am not sure how ISY works with zwave triggers but it would worth a try. Another technique would be to have another program enable a trap program when the status goes on. In the newly enabled trap program you could capture the same event and notify from it, then wait 1-2 seconds and disable itself again. Sent using Tapatalk

I have almost all LEDs bulbs with Insteon SwitchLinc Dimmers. I have no problems down to about 6 to 12% depending on the quality of the bulb. None of them flicker at the low end except a few of the old Cree bulb models that HD dumped years ago. If you are using 4" pot lights, are they not low voltage (12vdc?) with an electronic transformer inside? I am using all 120v LED bulbs directly with my switches.

In conjunction with Techman (above), you can add a small resistor or incandescent lamp to the strips to create some "normal" loading. Updating your ApplianceLinc to an OnOff module also gets you a dual band network improvement.

I find the batteries last the same length of time in the cold or warm. What does change is the battery voltage and it ma appear to be a low voltage. The tag battery percentage left compensates for the low voltage when they are exposed to cold temperatures. If you have one with a lower voltage you may notice the voltage will come back up when the battery is warmed up again. "arming" is the term they apply to the Tag for motion sensitivity. Temperature, humidity and lux can be set to a range limit and can update automatically if it falls outside of your set limits. All notifications can be disabled and still trigger the kumoapp updates. I haven't found any good explanations from CAO on this, but have done some experimenting to discover these tags don't have to be set to fast updating, using up the battery life and "hammering" ISY with constant data.

LOL! You must have gone through dozens of batteries per year with those 1 minute updates. I leave mine all at 15 minute updates but you can set specific characteristics of each Tag to update when triggered by that action. eg: The tag on my garage door updates every 15 minutes but notifies me via KumoApps ----> REST ----> ISY in seconds when the door moves open or closed. The same with leaving my fridge door open too long. You may need to re-examine your approach there by using the monitoring options in Kumoapps, to avoid killing batteries and swamping your ISY. The KumoApps line tag.updated = function() { only runs the code to update ISY when something changes so you should only have had updates in ISY when something changed. I have since installed a heartbeat in that code so I can tell the Tags are even still alive after many minutes of nothing updating. I use five variables for each of my 8 tags without making my ISY busy. Glad you got your ISY problem isolated now

How did you resolve the kumoapps hyperactivity? What does your kumapps code look like?

I let ISY control everything and use no other skill inside Alexa or Google Home apps. That way I can order things to look the best. Longer ramping for the first devices and turning on the ones most prevalent to your eye all helps. I find the Insteon controls overhead pot lights are best coming on first. Then the cabinet lights and other fluff can come on later once I can see. They don't get noticed because most of them are behind your back as you enter the room. Turning things off is usually done the opposite sequence for best effect. For off sequences I usually install a Repeat 2 times loop in the program. I have few stubborn WiFi bulbs that miss every so often.

In conjunction with io_guy above, a few minutes of off every cycle can allow some wicks/filters to soften the scale somewhat, as it re-wets itself more completely. The hardened scales can stop the water from wicking completely and wear out your wick/drum faster.

I don't dim or brighten a scene. If I did modify the scene, and then turn it on, it would take many seconds to get a lighting response and I would reprogrmming the eproms in the switchLinc dimmers every time.. In my Gathering Room I use individual commands like... Alexa Turn On TV lights Alexa. Turn On Reading lights OK Google. Turn on movie lights OK Google. Turn on Easter lights Alexa. Turn on bright lights Alexa. Turn on dim lights OK google. Turn off gathering room lights These are all programs that operate banks of lights. The Insteon lights are in scenes and the non-Insteon are NRs. Some were Hues (just removed them) and others to a RPi that can operate them (RGBWW) almost simultaneously However, I do use relative commands for A/V volume as the receiver supports it. Alexa. Turn On louder Alexa. Turn on softer

The US spelling was the answer!!! So I had two problems. Alexa routine process was somehow locked up and vocals are translated into US spelling and then compared with your text. Thanks so much. In the back of my mind, I did see somebody discussing US spelling differences but I wasn't into that subject matter at the time, and walked away mentally. The UDI forum has so much diversification now, it is hard to even read/absorb it all, now.

Wow! Looks like UV exposure but on the back against a receptacle, it's not likely. I don't see any signs of overheating from a loose connection and/or high loads. You need to put some vaseline on the next plug inserted there and plug it in and out a few times to wipe it in. Silicone grease is even better if you have access to some. This can happen with aluminum against some other metals. They can bond after a time.

Ahhhh! Never thought of that. Since Alexa doesn't seem to use phonetic spelling analysis it may not recognise the word or spelling. I'll have to try the US spelling as a test. Some of my neighbours are bors so.......I knew I should have bought my Echoes at amazon.Ceh?