MrBill

my launcher entry is https://<ip.addr.of.polisy>:8443/desc

I'm actually on 13.0, but I'm not certain the prerequisite to load ISY on Polisy. Hopefully @Michel Kohanim will clarify soon.

mines not far off.. a few minutes... but I love the concept of it being calculated for the exact location.. after all, if we are here to begin with we're geeks... Another reason is because I have to use the hue bridge timer to start an animation every morning, after that point the ISY takes over management, the ISY994 and the hue bridge currently are only about 2 seconds apart in the calculated times. The author of app running on the hue bridge has told me point blank that not using the hue bridge and his app as the center of automation is the wrong approach... guess what, I don't agree.. hue is a very small part of my total automation package.

Either will work. for the 2413s you need the original cable that came in the box. 2413u is showing in stock on SH, I just rechecked. (a number of people have ordered this week tho, including me).

Small releases are awesome! (much better than waiting months between) Sunrise/Sunset are much closer... I hope that adding Custom Location back is on the list!

If your OS isn't yet updated that's likely the problem, include the results of uname -a in order for @Michel Kohanim to give the best answer. Also Michel, you should probably edit a prerequisite into your posts showing how to load ISY on Polisy.

1) not yet... it's still alpha, manual shell commands are being used today, when it's ready for prime time the menu commands will likely work. 2) ISY on Polisy is capable of either the 2413s or the 2413u. to use the 2413s with ISY on Polisy you need the serial cable that arrived in the 2413s box originally (hopefully you kept it). 3) z-wave will be available soon, they haven't finalized the choice yet tho. We can only assume it will be USB.

That makes sense for time, but where in the world are the sunrise and sunset times from? they are a weird hour and a half or so wrong, yet they should be very close for the ??detected?? city. I'm not sure how it got City, because this is what's set in Polisy, which is a different City and state than the one I blanked out, and sunrise/sunset isn't correct for chicago either.

Just re-add the info for it, copy write it down from 'finder' on your computer that it works, then press the add button in finder on the computer it's not working on.

None of your nodes show because ISY on Polisy is a different ISY. BTW: There is no Z-wave adapter available yet for ISY on Polisy

@Michel Kohanim How is location/time zone being determined? Time is correct. Sunset is not. Sunrise is not. they should be: (this screenshot from ISY-994 and is correct.) There is no change location button. Also the City blanked out is a nearby larger metro area. My hope is that we will soon be able to use exact longitude/latitude as we can in the current production models. Is the Change Location button coming back?

Worked for me! Excellent. I ordered a 2413u for testing.... but it will be the end of the week at least.

@asbril See Michels linked post below. You need to manually add it to finder after you start ISY launcher:

Run ISY launcher and see if you have a new entry in finder..... (mines is the 4th line...) then open the admin console on that one if you do.

I agree google is better at searching this forum.

to paste code, right click the program name in the program tree, and select Copy to Clipboard. Then click into a post and either just hit Ctrl-V (paste) or click the "<>" symbol in the toolbar first, and then Paste into the 'code' window that pops up. I believe your problem is as I alluded to here: and apostolakisl also mentioned If the status of the door changes during the wait, then the program will stop and not finish. The method to get around it is to use two programs (and there is two choices there as well) Program checkfrontdoor If frontdoor is violated then run program frontdoorviolated (then) else (nothing) Program frontdoorviolated (disabled) If (nothing) then turn on entry light turn on garage light $GarageEntry=2 wait 10 minutes $GarageEntry = 3 turn off garage light turn off entry light $GarageEntry=0 else (no else) In this program, the end will be reached if the door becomes no longer violated while the waits are running. However if the door is re-violated during the wait the program will start again from the top. One more version: Program checkfrontdoor If frontdoor is violated then run program frontdoorviolated (then) else (nothing) Program frontdoorviolated (disabled) If (nothing) then Disable checkfrontdoor turn on entry light turn on garage light $GarageEntry=2 wait 10 minutes $GarageEntry = 3 turn off garage light turn off entry light $GarageEntry=0 Enable checkfrontdoor else (no else) In this version we added the disable and enable to the then body, this will cause the first program to ignore more violations until the second program finishes. The second program should be always disabled, disabled programs still run when told to by another program, but not because the condition in the IF statement became true.

This forum allows sections of the Front Page to be collapsed... the problem is only the everyday users/power users would understand that, the casual user or consumer of information would never figure out where to look. If I was the admin, the only set of boards on the front page that would be collapsed by default would be the archived/read only section at the bottom.

see Michel's post in the thread below where I asked that question. You should open a ticket with UDI concerning that, I suspect there might be a timeout that you're hitting based on the size of your z-wave network. (very similar to what happened with Home Assistant after you upgraded to 2021.6 --Since @Javi had a thought in that thread that lead to the solution he may here also.)

I've yet to ever see a forum with that many sub-topics displayed on the front page. The casual user would be lost. The front page would also portray a stagnate community to the casual user. One (10 year long chapter) of my life was professional community (forum) administration at a SV startup for enterprise level forums. At one point clients included all 4 major cell phone providers, several anti-virus software manufacturers, 2 major hard drive manufactures, several computer makers (choosing words to dance around an expired NDA that I usually honor anyway). A best practice that we preached was to eliminate sub-forums that didn't receive 3-5 new posts a day on the average. I don't know all the abilities of the forum software package but it appears to be fairly complex with untapped potential. I'd bet that indeed tags could be enforced in a node server support section, and select members could be deputized to assist keeping the posts tagged correctly.

112 today.... 224 in X amount of time... someday 500... the method is not scalable.

No one searches or looks for past posts due to the level of disorganization in this forum. After all who would go to a thread titled "Serial PLM discontinued according to smarthome" to find this post. I even suggested the same day: But typical for the disorganization found here, we've continued to the drag the original intent of this thread off-topic. Unfortunately properly managing an online forum takes a dedicated person and a fair amount of time. Pouncing on posts that drag a thread off topic and moving them to their own thread in the correct sub-forum. Conversely, pouncing on posts that have currently open topics and moving them into the thread they belong. Another "best practice" in support forums is to automatically lock threads without a new post in 30 days. This forum is all over the place, no one knows where to find anything. It also suffers from "too many choices", that is people can't guess the correct place to post because there are way too many sub-forums for the size of the community. Worse yet, some nodeservers have dedicated sub-forums and some don't, yet it would be a real mess if all 112 nodeseverves had their own sub-forum. I happen to agree with @whywork (although they actually didn't say rename anything) that reclassifying the Polisy section would be good... "Geek Batch" is outdated... It the equivalent of including the word "new" in a name.. time itself expires the title. However since that's really more about Hardware, I think Geek Batch should get renamed Polisy Hardware and OS, then immediately beneath that add the subforum ISY on Polisy. The problem with a new sub-forum named "Polisy Nodeserver" is that there is already an entire section named "Polisy Nodeserver".

Have you tried restarting the ISY? Next suggestion would be to check the error log (Tools > Error Log) and see if there are any clues there. Another question is what does the program do? Post examples... If any of the conditions change during the wait state, it will end the wait state. This is by design and not a bug.

To elaborate on versions people are spitting out.... 5.0.16C is the last ISY firmware version that works with a series 300 z-wave board. If your admin console has a z-wave menu, and Z-Wave > Z-Wave version = 4.55.00 then this is the version you need. You might also think about a z-wave upgrade board from UDI, with possible discounts base on the age of your ISY. If there is no z-wave menu at the top of the admin console, or the answer to Z-Wave > Z-Wave version = 6.81.00 then go to version 5.3.3 Be sure to read all the instructions. Generally upgrades go quick and easily these days, the exception is if your ISY Programs use "Adjust Scene", all of those programs will require a manual fix.

I helped someone else work this out, and I can't find the thread to link. the short answer is you need multiple daisy chained programs: Program: Door_is_unlocked If Status door is unlocked then Run program User_1 (if) Program User_1 (disabled) If access code is 1 then notification user 1 else Run Program User_2 (if) Program User_2 (disabled) If access code is 2 then notification user 2 else Run Program User_3 (if) .....and so on A disabled program runs if run by another program, but not if the IF condition is met. The problem with using 'ZW 003 Schlage Door Lock' User Number is 1' alone is that the user number doesn't always change, and to activate an If statement it needs to change.

log into https://alexa.amazon.com (from a computer browser) and delete every device and scene, then tell Alexa to Discover devices.