MrBill

@Jay M One at a time, right click each device in the scene then pick "Restore Device" from the context menu.

I've been deep into the differences and the Schlage documentation today and ended up swapping up from Encode to Encode Plus. I feel that the API will work the same with both models. and two, I doubt Schlage will change too much of the API because they have shared it with Amazon and Google.

I believe encode plus is the HomeKit version.

I found this thread: And don't see newer information in the forum. @hart2hart 's quote Things may have changed. I was researching this Schlage Encode recently because it's an option that's only a small increase in the options on a custom front entry I was ordering. It appears Home Assistant has a custom integration installable from HACS, it also appears there is a separate python library available. Given that a Node Server should be doable now. those that participated in the original thread are: @RandyT @hart2hart @lilyoyo1 I placed my order with the Encode Wifi lock... I'll update after it's installed. It's unclear to me if Lock/Unlock is supported, but Status (locked/unlocked/jammed is reported, and last code used to unlock Id# and Name#. Edit to add: I just looked at the documentation for the python library, apparently it's reverse engineered but includes all or most abilities, including code changes, lock/unlock... etc

Why should Doc's be repetitive? If anything perhaps a migration Troubleshooting section could be added, "if you're seeing this then see step __ of the migration instructions."

You need to set the off scene up to turn off the devices... just like you did the other button. BUT there's a better way! Instead, create one scene, with one values programed the way you would like them to be. Then change Button H to "Non-toggle ON" and Change Button G to "Non-toggle Off" When Button H is pressed it will send the scene an ON command, when button G is pressed it will send the scene an OFF command. The only real change to the functionality as you've described is that Button G doesn't stay lit when the scene is OFF, Button G will light breifly as it's pressed but then go back off. Button H can be configured to turn on/off with the scene. Use the button to change G and H to non-toggle mode.

Nothing is Broken, what works is what RR has chosen to include.

No actually it was because @n8ur9irl said she wanted it to stop at 12:00 The important thing to understand is that the two programs are designed to interact with each other. The reason they are designed to interact with each other is so that a Motion event at the end of the window will end with the light off. For that reason it's a Must that the SUNSET Program also include the off time, and that not be two separate programs. But are these programs even for the same light? Looking back it looks like we are dealing with 'Outdoor lights' and "parking pad'. So I'm going to use a GENERIC device "Light" in this example to illustrate how it works: Program Light If From Sunset To Sunrise (next day) Then Set 'Light' on 35% Else Set 'Light' Off this program will make 'light' be 35% from Sunset to Sunrise. Now we add a second related program: Program Motion If Motion_Detected is switched on AND From Sunset to Sunrise (next day) then Set 'light' on 100% Wait 15 min Run Program Light (if) This program, on motion during the same time period will turn the light up to 100%, wait 15 minutes, then run the Original program to turn the light back down. Why do we run the original program, instead of just going back to 35%? Because if the motion occurred 5 minutes before Sunrise, the light would first get bright for motion, the light would first turn off at Sunrise, then when the end of the Wait 15 minutes occurred it would turn back on to 35%. Since we have interrelated these two programs what will happen now is that the light will go bright 5 minutes before sunrise and turn off at sunrise then when the Wait expires it will turn off again.

Yes. Scene's in a V5 are a tad more complicated to set up tho. Here's a few tips to help: First, Find this button on the admin console ribbon. Turning it off allows you to make multiple changes to scenes without the ISY communicating with the devices. Make all your changes with the button off and it will queue up the scene changes and send them to the devices all at once when you turn the button back on. Second, in V5 there's no copy button anymore. This means that the scene must be configured for EACH Controller in the scene. Consider this Scene: It has 3 controllers, The root of the scene, in this case "Christmas-All", is always a controller. The Red nodes are also Controllers. So when we configure this scene we need to do it 3 times: Christmas-All, Holiday Lights, and {hide}Lower Deck - G-H Holida. Those 3 configurations could all be the same, or they might be different. For Example in this case the 3rd controller (Lower Deck) only turns on one module of the scene, that's only used differently in the summer. Another example might be say the Kitchen with 2 switches (both controllers) that turn the lights on to differnt levels... enter from the garage using that switch and one thing happens, enter from the living room and use that switch then another thing happens. And finally directly relating to your scene, you'll need to add Buttons G and H both to the scene and Both as controllers. The admin console asks a weird question when you try to add the second, it will say "button X is already a controller would you like to make this a responder?" (or similar wording), the answer is no, because you do want Both buttons to be controllers. When configuring G, make sure to turn H off, and when configuring H make sure to turn G off... For this sentence that is only talking about the button, not the scene.

You need the else in the Sunset program to turn the light off. I assumed that you meant you wanted the light to turn off at midnight, or a little before.

@kzboray Use Javi's program to manage the button with a scene and coordinate UD mobile, but add a second line Run Program SetWhatever (then) or Run Program Setwhatever (else)

and those two programs should work fine together, this one and the motion... Also when posting programs it's really better to Right click the program name then Copy to Clipboard and paste into the message, like i did above. If you do that over screen shots people helping can cut and paste to re-arrange a program, screenshots take more typing to re-create.

Change that to like this: If From Sunset To 11:59:59PM (same day) Then Set 'Christmas Tree#' On 35% Else Set 'Christmas Tree#' Off I choose 11:59:59 because I'm not certain whether the ISY considers 12:00:00 exactly to be "Same Day" or "Next day".. I'm certain 12:00:01 would be Next Day, it should include 12:00:00 AM as Next Day, but since I didn't test the best advice it to just avoid it and use 11:59:59 because I know that is "Same Day".

Looks correct now. Show what your Sunset program has in it.

I believe under ZMatter all the nodes should be renamed to ZY, if you have ZW nodes hanging around I've seen where it was advised to open a ticket because they didn't migrate correctly.

the Statement to turn it up should be Use On 100% not "On Level"... On Level is something else.

On Level isn't the value to change. (what "On level" set is the level that is set when the switch is turned on manually.) This will change the current dim level.

In addition to the upgrade instructions, I suggest that users make a text copy of programs. Single Click then Right Click "My Programs" (or whatever the root folder of the program tree is named if it's not "My Programs"), Choose "Copy Folder to Clipboard" at the bottom of the popup menu. Next open any simple text editor (that doesn't add any formatting) Windows Notepad is a perfect choice. Click into that window and then type Ctrl-V to paste all your programs into the Notepad window. then File > Save As give it a name.txt and save it... now if you need to see what a program looked like before the upgrade you can. After the upgrade is complete, you'll log into the admin console using admin/admin for credentials, you'll need to change that back to whatever you were using. First stop in the admin console when you get back in after the upgrade is Help > About to check the Firmware and UI version numbers match. If they don't match then stop and fix it, because if they don't match the next step will give false information. Next go to the Programs Tab > Summary sub-tab and look for YELLOW, if you see any yellow the associated program is broken and needs to be manually fixed. Most likely it used "Adjust Scene" which has more settings and ways it can be linked in V5 that values can't be assumed or defaulted, so programs with "Adjust Scene" will need to be manually repaired.... (Remember the .txt copy of your programs we made above? this is where it will come in handy.)

i finally get the distinction.. I have none of the i3 products yet. I'd still open a ticket to ensure it's a known issue.

Except most users are reporting that it works as expected in 5.6.0 see the @Bumbershoot post i liked above. in this case that would be particularly important since others report that it works as expected. Have you read any of the other posts above? or that i linked? You're in the minority, UD thinks it "works as expected" because that's what has been reported.

I don't believer that information is correct: from the release announcement: Bug Fixes Insteon I3 Dial status not updated after turning dial There is also discussion higher up in this thread. cc: @vbPhil EDIT: See also

It seems it would be pretty simple for a node server to achieve this, as there is a python library for holiday calculations.https://python-holidays.readthedocs.io/en/latest/ perhaps the developer of time and date node server could add holidays. US Easter might be missing (seems to only have UK Easter on a Monday), but Good Friday is correct so Easter can be known that way. Hopefully that information is out of date and US Easter is included.

Just to double check... are you using JAVA 8 downloaded from https://www.java.com ? that's the target version of Java for the Launcher

@shane4581 Windows or MacOS? If Mac, half the users report never being able to use the Launcher, others have no problem. I have no idea what the common denominator is. IF MAC: download a copy of the admin console from the ISY itself... http://IP.ADDR.GOES.HERE/admin.jnlp save it on the desktop for easy use. Anytime you change the ISY firmware to a different version you must Rinse and Repeat. Launcher works fine with any Win10/11.

@shane4581 try deleting your .state files.