larryllix

Your last line in the first program cancels the scene ramping and sets the lights to 35%. ISY programming is not concurrent but threaded style. You call the scene control program it it spawns off to do it while the next line sets the lamps to 35% nullifying any scene action that has already taken place. Switch the lines order and insert a Wait 1 second between them. or Just write a delay loop with dimming in each loop, as Stu suggested above. If you have v5.xx you can examine the level, and subtract x% from it each time.

My apologies. I missed the "nor" there. Follow Stu. I had to factory reset my 2441ZTH units sometimes a dozen times and link them before one acted properly and one newer version never did. Both report OK but control will not work for the newer firmware,

If you have a group/ungroup menu it is for a reason. That means ISY sees more than one Node at that address.

I hear ya. Each bulb type seems to have a different curve and I usually want the bottom reliable brightness level. That does make it hard to find one percentage level that would fit all. I have some that use about 10%, some 12% and some that don't work reliably below about 17%. With voice operating three or four scenes that level would have to be programmed for each application/bulb and then the spoken phrases could be standardised. So when we use the "brighten" command the step could just be in 3-4 discreet clicks and operate those on user presets matched to that bulb/device.

What Teken said above. ...also scenes do not have the security of transmission signal that straight programmed signals do. Regular Insteon signals have confirmations and retries upon failures that, as I understand it, scene signals do not. I only use scenes for large groups or to tie two devices (think MS and lamps) together, making them independent and faster than ISY can do.

Yeah but the LED bulbs don't appear to follow a consistent curve either. I had to replace one CREE bulb in a dining room fixture of 5 bulbs. Despite being the same power rating CREE, they changed their style and it dims differently than the other four. Looks awful about 15-25% . I guess back to your point I don't think people need all these 0-100% either. Ramping is one thing, for looks, but people don't need many "clicks", just maybe full, medium, low, very dim. We don't need to have 48, 49, & 50% for fan speeds either.

Sure it is. log2( 6.25 / 3.125) = 1 log2( 12.5 / 3.125) = 2 log2( 25 / 3.125) = 3 log2( 50 / 3.125) = 4 log2( 100 / 3.12 5) = 5

I have a Venmar HRV that I cycle every 40 minutes for the last 8 years but I switch it from the input sensing and the timer input sensing.

I have to agree with Alex (above). When I use Alexa, turn off all lights it turns off the lights in only that room (24 lights) That is the way I set it up, but I don't feel I have any use for Alexa in other rooms as far as HA goes. I am not going back to the clapper level for bedroom lights in the middle of the night, yelling Alexa, turn off the bedroom light. I want HA light control, not waking my spouse up by yelling or clapping. She may want some action and I am not bothering with that nonsense, when I am dreaming of a better class of people. Geeeesh!

That sounds a little counterproductive for the Echo though. In my situation I have a wall switch that can do almost all of it when coming in/out of the room or walking by in/out of kitchen. Of course the switch walk is avoided when home with just us, and for the shopping list we are finding invaluable to eliminate that notepad stuck to the fridge, with the lost pencil and not with us when we happen to be in the shopping zone, 20 highway minutes from home.

Logarithmic levels would be excellent! Light intensity response to the human is is logarithmic and also LEDs tend to hang on to every last bit of voltage they can get so they don't appear linear. This would make 100%, 50%, 25%, 12.5%, 6% for example.

Don't use scenes for it then. Use the devices. I don't use any scenes with the Echo, only programs that activate scenes for Insteon and dozens of other devices that co-oribate by programs only. "Alexa. Turn on xxx lights to 50%"

WE are using Echo more and more with ISY994 and alone, just web support. But we have found Alexa is almost completely useless in a crowded room with background noise and talking. You have to stand right in front of Alexa and speak loudly to get it to respond even about 50% of the time. The wall switches are just as easy then and always reliable.

LOL. OK. I thought we were discussing the KPL. I never use toggle mode on my KPL or mini-remotes and they function exactly the same except for the linking mode in the KPL, that never gets used with ISY.

In response to the OP post #6 "Push on/Push off control. Without having to press twice if the device is controlled by something else, such as schedule, other control, etc." You replied in post #7 "But if the remote truned it on it will remember it is on so if something else turns it off, the remote will think it is still on and issue an off command on the first push." The problem is the KPL toggle mode being used, and using only scenes does not allow a solution to that problem..

You and the OP already agreed in posts 6,7,8 & 9 that this doesn't work. Secondary buttons take no commands and do not understand other devices status. The LEDs do, but not the buttons.

KPL buttons do not know what state the device is in. The LED can if you control it from a scene showing the device is on or off but the button toggle sends On-Off-On-Off-On no matter what state the device is in. The only way to insure it only results (not sends) in a single push toggle is to turn the KPL toggle off, turn on the non-toggle On mode, and use a program to operate the device. The toggle function must be done inside ISY with the program dependent on the status of the device. Scenes cannot do this or help the button to know what state the device is in. The LED yes, but not the button command signal issued.

Without any experience doing this myself, IIRC you can't switch masters from ISY programs.

Did you power cycle your ISY after the purchase? Some things don't show up until reboot when they enable that feature/module. The Network Resource Module is existing in most versions of ISY firmware and just gets cloud enabled. I assume you have browsed your tabs to find it? It was an option to include it with the Portal Purchase. I didn't as I had the NR before.

What do you have updating the DDNS service?

The name shown in your device tree is for your Insteon network, not Ethernet network. Unrelated.

hmmmmm... My ISYfinder comes up with two IP addresses ( that I installed) and I have to double click one, to connect to ISY with the path I choose, every time. The local IP address and the remote IP address are easy to identify by their numbers and could identify two different ISYs also. There is no ISY friendly name used, or seen, there. Using MobiLinc Pro (android) the switching is done automatically dependent on whether your WiFi is enabled or not. Two different ISYs could be made to respond to LAN and WAN access methods. I guess I don't understand where you ever see a friendly name for your local ISY.

So you are manually switching the ISY IP addresses in your apps, to access each ISY and it's a PITA?

In the end you will probably end up writing an occupancy program using a variable to keep track if anybody is home or not. I have any Insteon action to trigger a "Home" varible and it times off with different stimuli. Like 20 minutes after I leave by my usual door. Immediately if I set the alarm system 4 hours if I trigger any other MS in the house. Never after bedtime until 7:00 AM again then 4 hours After creating this variable programs can use the variable to test for people home. If the variable is a state variable it can also trigger programs to run by itself or with other logic combined. Now you stop you furnace fan from cycling, ventilation off, temperature down or up, lock the doors after X minutes.etc..etc..

I am sure of one finger you are holding up.