MrBill

looking thru a scene I see that the node selected calls itself default. Click the root of the scene or the scene name, do all three table entries say insteon? Click each node of the scene, the node itself seems to say default but the other two should show Insteon.

All three are insteon right? are all 3 set to insteon?

That will work too, but the switch, the button, and the motion sensor, must all be in the same scene.

The only way to control the ON/OFF status of backlight behind a button is to put the button in a scene (controller or responder either one doesn't matter) and then control the scene. My guess is that's already they case, and the button is a controller. Therefor the program for the motion detector must be controlling the light directly and not the scene. If that's not the case. please right click the program name and select Copy to Clipboard, then in a forum reply hit the "<>" button on the editor toolbar and paste the clipboard (Ctrl-V) into the window that pops up.

Don't forget Polisy also comes with 2 years of Portal Access.

Are these insteon or z-wave switches? And these are insteon? ----- Assuming Insteon, these 5 programs should get you started... Program GarageLightOn If GarageSensor1 status is on OR GarageSensor2 status is on then Stop Program GarageLightOff Set GarageLightScene on ----- Program GarageLightOff If GarageSensor1 status is off AND GarageSensor1 status is off then Enable Program ManualOverrideStayOn Wait 5 Minutes Set GarageLightScene off Disable Program ManualOverrideStayOn -------- Program ManualOverrideStayOn (disabled) If Switch1 is switched on (Control menu, not status) or Switch2 is switched on or Switch3 is switched on or Switch4 is switched on then Disable Program GarageLightOn Disable Program GarageLightOff Enable Program CancelOverride ---- Program CancelOverride (disabled) If Switch1 is switched off (Control menu, not status) or Switch2 is switched off or Switch3 is switched off or Switch4 is switched off then enable program GarageLightOn enable program GarageLightOff disable Program ManualOverrideStayOn disable Program CancelOverride (this MUST BE LAST, because its disabling itself) ---- Program InitializeGarageLightPrograms (Disabled) (Run at Startup) if (nothing) then enable Program GarageLightOn enable Program GarageLightOff disable Program ManualOverrideStayOn disable Program CancelOverride

No the opposite. Leave it be, if it rebooted the values for battery devices will remain blank until the device checks in again. The ISY can't query battery devices, so when status is lost it takes time to recover. (Edit to add: the information should repopulate within 24 hours) Some people have luck running a query as a response to a transmission from the device. YMMV and it likely depends on which device, which version and which device firmware. Nonetheless it would take a specific program running when a motion alert is received. Note that I specifically asked about an error line that looks like this: Thu 2021/04/01 09:41:51 AM System -5 Start That entry specifically means the ISY booted, or restarted. Restarts of course happen when power was lost and restored, or when you manually press the reboot button in the admin console or portal. There are also certain conditions where the errors or race conditions cause the ISY to say "holy crap I don't know what to do" and it automatically reboots (I can't tell you specifically, but I've had it happen). If you have many lines of errors everyday, you might want to clear the error log, reboot the ISY and then wait about two days, then send your error log into UDI so that they can make suggestions for what might need help. My ISY is fairly loaded and healthy I get half dozen "error" lines a day typically, if yours is getting 100's or 1000's lines of errors per day its definitely something that should be addressed.

My issue turned out to need Michel's Magic Wand, my issue is fixed now (it developed I think because I was one of the first people that added portal back on 7/1 and the process changed a little thereafter.) I think @whywork was simply pointing out that it's not a one size fits all answer, and that there are some open issues.

The "trial" lisc is for the portal... If you bought a Polisy or Polisy Pro you get ISY on Polisy software running as a service at no additional cost. UDI hasn't said yet what happens when the 30 trial portal lisc expires, I'd imagine we'll be finding out in the next few days. (my trial portal lisc expires 7/31 and I think I was one of the first to add it for ISY on Polisy). Theoretically Polisy hardware was sold with a 2 year portal lisc included, I doubt we should be using that up in this alpha stage but there is definitely a grey area... not to mention portal is inexpensive at less that $1/month.

I wonder if your ISY resarted for some reason? did you have a power failure? can you look in Tools > Error log and see if you see a recent entry "Start" with a "-5" error code, that entry appears whenever your ISY restarts or reboots.

@CPrince The explanation by @gzahar is correct. Let us know if you have questions. another way to write this might be using TO rather than "for" If From Sunrise - 30 minutes to 10:30 AM And From 5:30:00AM to 10:30 AM Then Turn Light on In which case the later of the two times gets the light turned on If we instead use OR it will mean the Earlier of the two times If From Sunrise - 30 minutes to 10:30 AM OR From 5:30:00AM to 10:30 AM Then Turn Light on In this simple case we could probably even get away with an ELSE to turn the light off. But keep in mind the ISY is event based, whatever events are programed in the IF clause that cause the program to "run" are going to make the IF statement be evaluated. When it is evaluated it's either going to be TRUE or FALSE, and anytime the evaluation occurs either THEN (True) or ELSE (False) is going to run. Else is usually happening more than people realize. For Example, lets say you manually turned the light on in the wee hours of the morning because something special was going to happen, it's winter time so Sunrise is late, say 8am, (or sunrise -30 is 7:30). Your expecting your friend to arrive from the airport so you walk over and put the light on at the switch at 5:15am... normally that's perfectly legal maneuver and has no effect, the light would already be ON when it was supposed to turn on. BUT if this program had and Else to turn the light off at 10:30am, it would also turn the light off at 5:30am because 5:30AM AND 7:30AM evaluates to False and False makes the Else get executed. So turn it on manually, at 5:30 the program runs and turns the light back off. So when using a compound IF statement, its best to only use the THEN block and leave the ELSE block blank. Then you would have a second program If Time is 10:30 AM then Turn light off.

worked correctly for me.... found my USB PLM too.

The most interesting button modification I've done, there is a 8-button KPL on both sides of our bed, there's 3 buttons that have the possibility of being on overnight. I took the clear plastic square under the button out and painted it fully black with black fingernail polish. Now those 3 buttons have a nice soft outline rather than glowing. Most of my six button switches have an OFF button modification, a dab of gorilla tape over the 2 LED under the off button.

ISY seems unavailable after upgrade... sent ticket.

iOS edition, minor, but the keyboard opened for changing a variable value doesn't have a - (negative) symbol. .numbersAndPunctuation is a better choice, unfortunately I don't see a number pad type keyboard that has a minus.

I didn't tell you anything about the LED Brightness button. I told you how to use the backlight drown, and that it's usage isn't intuitive, and that it has a bug around its retention of settings. Actually I just tested the LED brightness button for the first time in probably years... it seems to work better and less buggy than the dropdown that is named differently but seems to adjust the same parameter in the switch. No ideas why we have two functions with different naming that seem to adjust the parameter.

All backlight buttons are set as one. There is no method to have different levels per button. That’s an Insteon hardware limitation, not an ISY issue (you can’t set it differently manually either). To set the backlight make a selection in the drop down, then click the word Backlight, to the left of the drop down—this is not intuitive but it is how it works. This will send the value currently set in the drop down to the device. The setting will be retained by the device until it’s changed again. There is how ever a bug surrounding the drop down. As you move to another device you’ll find the drop down is set to whatever you set on the last device. Further when the admin console is restarted, it will be back to zeros. The device however has correctly retained its setting. This bug has existed in every v5.x branch, it worked correctly in v4.x.

You quoted the wrong message in your initial reply then. The message that you quoted of mine was answering the OP's follow up question, which has nothing to do with what you are "chiming in with". But again, your "clarifying comments" are not really pertinent to the "device writes" bug that existed nearly 2 years and was finally fixed in v5.3.2 which is the initial question by the OP.

To be clear, again, there is no queries, or wireless devices, or heartbeats being discussed in my reply to the poster that asked the question. You are bringing up confusing points that have no bearing on the question that was asked.

To be clear, no wireless devices are being discussed here. Point 1 is that is NOT intuitive to set the dropdown then press a button to the left of the dropdown to SET the value. Point 2 is that "backlight" does not correctly "default" the dropdown to the value stored in the device. If the admin console was started before arriving on this node it will say 0 "zero" regardless of what is stored in the device, it will NOT fix the the value displayed in the admin console if the device is queried. If we CHANGE the value in the dropdown to an odd value say 24%, then move to a DIFFERENT Device, the dropdown box will be populated not with 0 but with 24%. This is an admin console bug. The dropdown does however work correctly for SENDING a value to the DEVICE, which will be retained by the device once it is sent, regardless of what the admin console subsequently says. All switches with a BACKLIGHT are wired, this has nothing to do with not being able to query a wireless device.

For the First issue: Schedule 10:30Pm or whatever then insert a random Wait before the action. A random 30 minute wait till wait between 1 and 30 minutes. aaa Test - [ID 00E6][Parent 0001] If Time is 10:30:00PM Then Wait 30 minutes (Random) Set 'Pool Lights' Off Else - No Actions - (To add one, press 'Action') -------------------- For the second issue use AND EDIT: Actually I'm not sure that simple method will work, but this will: Of course 6 hours is much longer than needed but I just used that value randomly. You will not want to use an ELSE clause with this type of program. This IF is evaluated 4 times, only once is it true, the other three times it will be false which would cause ELSE to run each time. Also note that this type of logic can also be used with OR which would cause the THEN to run at the earliest of Sunrise-30min or 5:30AM

As i mentioned yesterday in a different thread, my vote is ISY on Polisy should move to v6.x

subscription in the context of the admin console starting is not the same thing as (paid) subscription to the portal. When the admin console starts it "subscribes" to updates from the ISY. The type of subscription the dialog is about will usually fix itself if you log out and stay logged out for awhile (so that subscriptions expire). A sure way to fix tho, is reboot the ISY, that will clear all subscriptions. Edit to add: you can view this type of subscription status by using http://IP.ADDR.OF.ISY/rest/subscriptions. There are 10 slots, slots are used by things like the Admin console, Portal, UD mobile, mobilinc/agave/ekeypad, a home assistant instance, etc.

The answer is not intuitive. set the dropdown, then push the button to the left of the dropdown. On, Beep, On Level, Ramp Rate, and Backlight are buttons. there is an unfixed bug around backlight. You can set the backlight by setting the dropdown and hitting the backlight button, the change will be sent to the device. but you can't trust what the dropdown says without setting. after admin console is restarted it will say 0 again... it's not. After you set one device that setting will appear to be be carried forward to the next device... that's a lie. the dropdown and button work reliably, but there is no way to tell what the setting in the actual device is.

the bug you are encountering was fixed in 5.3.2... don't stop there tho, upgrade to 5.3.3 After you upgrade you will need to wake up all your wireless sensors (press the set button until the LED starts blinking) and get the cached desire to write taken care of (right click the device in the tree and select "write updates to device"). when complete the green 1011 icon will disappear on those wireless nodes.