MrBill

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.

Yes....

Install 5.3.3, although it's labeled Test Build it has been out since March 8th at this point and is stable with no known issues. admin/admin for the default user name and password. If you're on Windows, Install The Launcher for the admin console, then you'll always have the correct version. Do any of your programs use "Adjust scene", those will require manual intervention. One more thing... Open Notepad, Click the top of your program tree My Programs, then right click it, then select Copy Folder to Clipboard. Click in the empty notepad window and Ctrl-V (paste) then Save As and give it what ever name you like. Now you have a text based copy of your programs for reference. After updating if any of your programs need updating they will be marked in YELLOW on the Programs > Summary tab, and they most likely will include "Adjust Scene" entries that couldn't migrate.

I'm unlcear how to add the ISY Portal module as the Purchase Modules menu item doesn't seem to exist in v5.0.2 --- Unrelated Suggestion: duplicating the V5.x numbering system seems like it's going to create ongoing confusion and make using search engines difficult. Should perhaps ISY on Polisy have a distinct version number? perhaps v6.x ???

Without all the programs it's hard to trace, (you said you have 9 but I see 6). The first thing to do tho, is not use status with your KPL buttons, instead use the "control" dropdown, and use OR in the same program for all equivalent keys on different keypads. For example: if 'Mudroom_Entry / DB.Dog Bath / DB.Dog Bath.E' is switched On Or 'otherkeypad.E' is switched On Or 'anotherkeypad.E is switched On then --- that will probably clear up your race condition that occurs because Control means someone actually pushed the button, rather than the status that can also be triggered by scenes. If you still have issues after that change, please repost with all programs included. The easy way to post programs to the forum is to click on the program name, then right click and pick Copy to Clipboard, then in a forum post click the "<>" in the toolbar which will bring up a popup window, then click in that window and type Ctrl-V. Also if all the programs are conveniently grouped in a folder you can right click the folder and pick Copy Folder to Clipboard and post all with just one paste.

More details needed. What kind of sensor? What are we actually controlling with the relay?

As pointed out update your firmware to v4.9.0 (there is also a 5.x branch, however don't dive in until you've done some reading, there are several caveats) I'm confused about your expired certificate, because it's not a self signed certificate, so I can't help there. I can tell you that in 2021 there is a better way to access your ISY remotely. Close your ports, remove the port forwarding entirely and use the ISY portal. Secure access via a cloud portal. Yes it's an additional charge but less the $1.00/month. In addition to secure remote access, you get Alexa / Google home integration and free access to cloud nodeservers.

If 1st floor off button is switched off (use the 'control' dropdown not status) then disable program Evening Lights On wait 30 Minutes enable program Evening Lights On else (nothing) that should do it, adjust the wait to fit, i picked 30 minutes because you said 30 minutes.

I suspect you need to update the ISY firmware. Click Help > About when logged into the admin console locallly and tell use the firmware and UI version numbers.

Polisy hardware is production (i.e. not alpha or beta), and currently runs polyglot 2, which is soon to upgrade to polyglot 3. Many of us have the Alpha version of "ISY on Polisy" also running, that software is alpha test.

Your existing serial PLM can be used with ISY on Polisy, all you need is the serial cable that was originally shipped in the box. ISY on Polisy is also supporting the USB PLM that is currently in stock at Smarthome. ISY on Polisy will also support Z-wave, but UDI has yet to announce which Z-wave board is needed... likely it will be USB. Keep in mind the ISY on Polisy project is currently in ALPHA testing, it's not ready to run your mature system quite yet.

The quickest way to do what you're talking about an "all off scene", is to make a standard scene including all the devices as responders.... sending the scene an ON would turn it on, sending the scene and OFF turns it off. Once that's done, add your KPL button that you want to use as All Off as a controller. then change the Buttons Toggle Mode for that button to "Non-toggle [off]". The button will always send OFF and never send ON, so the scene works as "All Off". There is no need to set each device to the off position in the scene.

I hadn't tried http and 8080 yet, but I just did and it worked for me.

the steps outlined in the linked post state: you typed [admin@polisy ~]$ sudo pkg upgrade isy

Portal for ISY on Polisy is also currently disabled. (I can't post a link to the post that says that because I learned that in a ticket reply from Michel.)

Use "find/repalce" on the program tree to find each usage of a device in a program. Click "My programs" (or whatever your top level folder is if you renamed it) then right click the same and choose "Find/Replace"