mango

^ Interesting. How does the ISY see the second press? I get nothing. Just to confirm, this is not a double tap, that can be tracked. This is a second press made some time after the switch has reached its ON level.

Good morning folks and thanks again to you for assigning your time to this. Some context: I have the ISY run in 2 main modes: Owner and Guest mode. In guest mode I am only trying to apply this to 2 switches. One is a weird chandelier with 6 A19 sockets that have 60w equivalent bulbs in them. 100% is not nice. 'Fit smaller bulbs' you say. Lockdown has prevented me obtaining such bulbs (dimmable 20w or less that work properly). lilyoyo1 I watched the vid, and was educated somewhat more into the use of variables, but I still don't think it will help as the second press is completely transparent to the ISY. It is unable to be tracked, so the variable cannot change. xlurkr your suggestion seems to work very well along with the program at the top of this thread, I have another that senses the first press on then brightens by 1%. This results in every time the button is second pressed, the switch just returns to it's on level, then the program kicks in again raising by 1%. It's a super clean simple work around, that is perfect for the application I want to use it for.

Ahh, nice thinking, so have the switch tweaked 1% away when manually turned on (first press). That would be undetectable. I think I understand, I will give it a shot tomorrow hopefully as well as check the variable video, I've had to work later than planned...

No, not yet, working today but I will this evening thank you.

The $64k question would be, how can variables help if the status change to 100% is completely transparent to the ISY?

My goodness, I never even considered looking at the switches status on the second tap. You are quite correct the switch does not send its new status out. The ISY is none-the-wiser. Thank you!

ahh it could be the wait, I tried if status is 100%, I will view the vid and try the wait time, thanks!

It is not a guest only location, but there will be times when guests are using it. It's a cottage address. The scene on levels are certainly high enough in the way of light levels. Most locations have 60w equivalent bulbs that I prefer to use but when they are full brightness it is much too bright, if that makes sense. 100% in these locations is too high. Do you know which function will catch this: Status or control? I've tried both and the program does not trigger. To put it another way, what 'if' line do I need to add to catch the second press which causes the switch to go to 100%? I appreciate your help thank you.

This is for any switch, KPL or SWL. a single tap ON turns on the switch to it's preset on level. A second tap ON turns the switch to 100%. It is this second tap I am unable to track via the ISY using either status or ON level through if. Am I missing something simple? Should it just be: Or 'Living Rm / SL Dimmer - CHANDELIER' is status is 100% because it's not catching it. The location is going to be used by guests that I am unable to 'train' to use the switches properly.

Excuse my constant editing of posts. I have a few problems with communication including grammar and I see the errors once posted that appeared fine before posting.

So, then perhaps a dinosaur approach with a timer that is a activated when the scene is turned on, to periodically check (every 5 seconds or so) for the load to be 100%. What a waste of resources this way, there must be a more economical method?

Thanks Lilyoyo1, Strange that I can catch a double tap, or a manual hold down to ramp up, but not a second press? This is a local load device. The switch powers the load. I use programs sparingly, and try to keep most of the day-2-day workings of the environment to be outside of the ISY with controller/responder scenes.

Hi all, This must be easy, but I seem to be unable to find it: I have a couple of areas running KPL's and SL's that I require to remain at a constant brightness level via a scene I refer to as 'main'. Should a user 'accidentally' double press ON or manually hold down ON to ramp up, a program detects this and fires back the main scene to ON as a response. What I am unable to detect is if a switch is already ON, then the ON button is pressed once more, the lights ramp up to 100% and the program does not detect it. I have tried both STATUS and CONTROL states. Any pointers? I have tried all sorts of things such as or if status =100% or if control =100% Here's a basic program I have running. In this instance the scene keeps CHANDELIER at 10%. Return to Preset - [ID 007A][Parent 002D] If 'Living Rm / SL Dimmer - CHANDELIER' Status > 11% Or 'Living Rm / SL Dimmer - CHANDELIER' is switched Fast On Then Set 'Living Rm / Lounge Main' On Else - No Actions - (To add one, press 'Action')

With my limited skills I made a crude program to override the unwanted behavior and return the KPL to the desired level, including the next time it is controlled via button. This is for a guest environment so at present there is no need to set different dimming levels for the hallway. Hallway scene is this KPL and a SL set to 38% 2 second ramp. Comments and laughter welcome. Hallway KPL fix - [ID 0020][Parent 0001] If 'Hallway / KPL6 FrntDr' Status > 39% Or 'Hallway / KPL6 FrntDr' Status < 37% And 'Hallway / KPL6 FrntDr' Status is not Off Then Set 'Hallway / Hallway' On Else - No Actions - (To add one, press 'Action')

Hi all, ISY 5.3.0 Trying to make sense of this, possibly not an ISY issue: I have 2x new KeypadLinc Dimmers 6 button 2334-2 v.45. Same delivery batch. Double tapping the load switch to ON causes them to go to 100% as expected, but pressing ON again a single time does not return them to their programmed on level. They stay at 100% BUT they are reporting to the ISY that they have returned to programmed ON level. An ISY query results in the correct reporting of 100% once more. Has anyone experienced this? Bad batch? I have factory reset both, yet they retain the issue, clean state and after a restore.

Okay understood. I shall do that. Edit: This has been done for status 'unknown'. Which segways to another question: The lock has some alarm nodes. I attach a pic, They are currently blank, I am unsure how each reports if they trigger, so ideally I would like to be notified by a push notification also, especially as they are 'alarms'. This example shows node ZW002_174 Hardware Failure Alarm. Is there a way to find out how this node reports when triggered or is it simply an 'ON' or a '1' ? Is there a trick to interrogate the lock to find out how it communicates?

Hmm, interesting comment. These particular locks have a user 0 which matches for anything like locking or unlocking the lever manually from the inside or locking from the outside by pressing the Schlage button (locks without having to enter a code). I think that takes care of 'unknown'? I have user 0 setup.

I adjusted my programming and naturally everything works perfectly ? 12 users setup, and Pushover is issuing notifications correctly. Now an easy copy/paste and tweak of the folder for the back door.

Amazing, I understand more now and have a lot of info to work with, thank you.

HI Bill, I just added a pic. Here is the example code too: [FrontDoor U10] Locked Guest - [ID 0006][Parent 0005] If 'Front Door / ZW 002 Front Door Lock' Status is Locked And 'Front Door / ZW 002 Front Door Lock' User Number is 10 Then Resource '[FrontDoor U10] Locked Guest' Else - No Actions - (To add one, press 'Action')

I'm back! It's been a hectic few weeks, I am only just able to spend some time on this again. So, Mr.Bill I have a crude setup working with your strategy of 1 program per NR. but with a weird bug: Example - randomly when a user unlocks, both a lock and unlock status occurs. Do I need to insert a pause, or perhaps a stop command to else to prevent more than one trigger occurring? This happens randomly, not every time the lock is used.

Maybe something that checks layer 3 for connectivity every hour, whilst holding the failed send until it can retry with success. For my cottage (regular power outages - covered with line UPS and generator / occasional DSL internet outages - no cell signal - no 3G/LTE fail over), I was considering something running locally on a Pi or mini PC that the ISY would send to, and give the job of re-try's to a different device.

I could not work on this last night due to news of a further impending lock down here in Ontario Canada. I should be able to pick this up in the next few days, thanks again.

BOOM! Light bulb. That is gold mine information, thank you.

hmm, so I was doing it right, even with a new line, there doesn't seem to be any black magic stuff. As you say above then it may be the wrong values for Schalge locks? I'll dig deeper tonight, thanks again.