MrBill

BTW... since you're using Locative and the Portal nodeserver, you might want to revisit the wikipage and add the HOME folder node (step 4). @Javiand I recently corrected Step 4 so that it makes better sense. Essentially by adding Location, you get a third condition that is True if EITHER of you are Home, and false if NEITHER of you are home. This greatly simplifies what you're trying to do above.

Yes. If EITHER change then ALL are evaluated. Most of the time if you have AND (or even sometimes OR) in an IF statement you won't want to use the ELSE. (it will run too often since it runs anytime any portion of the IF statement is false. Instead write a second program with inverted IF logic for what your wanting to put in Else.

No. You want to upgrade to 5.0.16C since you have a 300 series z-wave board. Because you shouldn't be using it. If you remove the Z-wave board from your ISY then you should install 5.3.4 Do you HAVE wireless tags? If not, you need neither. That's do-able... for what it's worth... I thought i was going to augment sunrise/sunset time with a light sensor.... Truth is I just don't need it. Where I live there might be one storm a year where it gets dark enough during the day that we might want outside lighting, but even during that storm there is really no need. --- at this point in the game my specific advice to you... would be upgrade to 5.0.16C. Do not upgrade your z-wave at this time. In the future buy a Polisy, the standard version is fine, you don't need pro. Today Polisy will run local nodeservers that work with your current ISY, in the not too distant future Polisy will also be your next ISY... running both the nodeserver software and the ISY software in one box. Whats a nodeserver? Curently your ISY can pretty much just have Insteon and Z-wave nodes in the device tree. The nodeserver allows you to add more type of nodes for other devices. Once you upgrade to 5.0.16C you will immediatly be able to use the nodesever that are available in the UDI cloud (assuming that you have a UDI portal account). You can view the node servers available in the cloud store here: https://polyglot.isy.io/store To view the nodeservers available in the Polisy (local) store check here: https://polyglot.universal-devices.com/ (why 2 lists? some nodeservers can only run in the cloud--on UDI's servers, and some can only run on your local network--on Polisy). It should also be noted that the local nodeservers can currently be run by installing Polyglot2 on a raspberry pi, so you can get started that way too... At the same time tho it should also be noted Polyglot3 is almost here and that only runs on Polisy-- no Pi option anymore. --- Upgrading is not as bad as it once was. The single biggest problem is programs the use the "Adjust Scene" feature, they will have to be manually fixed. (Disclaimer: Follow the real instructions in the release post as well.... I don't have z-Wave, if there is a z-wave step it won't be in my overview below.) 1) Backup your ISY 2) click the Programs tab in the admin console and click the top folder (Usually "My Programs" but you could have changed it), then right click it and pick "Copy Folder to Clipboard") 3) now open any simple text editor that won't add formatting (Windows Notepad is perfect) and paste the clipboard (ctrl-v) into the editor. Save that file. Now you also have a text backup of all your programs to refer to. 3A) Make sure you've read the Z-wave sections of the release page instructions (disclaimer again: I don't have Z-wave, my instructions don't include z-wave.) 4) Download the correct zip file (if you have insteon you want the first file, the second file is when you don't have an Insteon PLM) and do NOT unzip it, leave it as a compressed folder 5) Use Admin Console Help > Manually Upgrade ISY and upload the .zip file/compressed folder. 6) before logging back in after the upgrade you need to clear your Java cache and install the ISY Launcher. Basically clear your cache including "Installed Applications and Applets" (that box won't be checked by default) then once java is cleared click this link: https://isy.universal-devices.com/start.jnlp 7) the first time the ISY Launcher runs it will install an icon on your desktop called ISY Launcher in the future, use this Icon to start the admin console. 7a) You should also do Java runtime memory section of the release instructions adding -Xmx512m to the appropriate place in the java control panel. (the 5.x admin console takes more memory than the 4.9 version you're using... personally my system is large and I use -Xmx1024m). (Keep in mind you need to redo this anytime you clear the Java cache or after most Java updates.) NOTE: It's in the detailed release instructions but a lot of people seem to miss it, your admin console credentials after the upgrade will be reset to admin/admin. 8 ) First thing to do when you get logged back into the admin console after the upgrade is check Help > About and make sure both the firmware AND the UI version are the same.. 5.0.16C in your case. If you're sill on a version 4 admin console, do not proceed to the next step until you've fixed that. 9) Second thing to do is go to the "Programs" tab, "Summary" sub-tab then look for the Color YELLOW, any program with a Yellow trouble icon/message will need to be manually fixed. 10) you should be done pretty much.

This Program Runs when either geofence changes state. Assuming that iNeighborhood is an Interger variable it will not run when the variable changes state. (however, if it was a State variable it would also run when the variable changes state.) When it runs it will evaluate all 3 conditions to either true or false. When all 3 are true the THEN block will run, OTHERWISE the ELSE Block will run. So in a nutshell, if EITHER geofence changes state, then EITHER "Then" or "Else" will be executed. Grouping with ( ) causes what's inside the () to be evaluated first. (just like algebra) so if you put the 2nd and 3rd elements in your above IF statement in ( ) then the iNeighboorhood condistion would only apply to APiPhone.

@larryllix I think @AAdsit doesn't realize you're speaking of ISY on Polisy w/ USB PLM, and I think @AAdsit is referring to ISY-994 with Serial PLM.

this is what we are looking at:

@ellisr63 I think @jfai has identifed your problem... but to be more specific 3:00PM = 15:00 4:00PM = 16:00 Your ISY is showing on the top line that is after 4PM

If you go over to the main tab and click on the device like this: do the On and Off buttons at the bottom of the screen work? If not, you need to solve that problem first. If so, then your program should look like this: aaa Test - [ID 00E6][Parent 0001] If From 10:00:00PM To 9:00:00AM (next day) Then Set 'Aquarium / Air Bubbler' On Else Set 'Aquarium / Air Bubbler' Off

with 4.9 I doubt the cache size is the issue, but it could be. that's good to hear!

To clarify, did you put start.jnlp on the desktop? or admin.jnlp? start.jnlp is the ISY launcher, admin.jnlp is the admin console being started separately without the help of the ISY launcher. I'd try to get admin.jnlp from the ISY with https://<IP.of.the.ISY>/admin.jnlp (replace <IP.of.the.ISY> with the actual IP address, so the end result will look more like https://192.168.1.22/admin.jnlp but with your ISY IP address. MacOS will warn you, tell you the file is not trusted and shouldn't be used blah blah... but the file is coming from your ISY not the internet, so ignore the warnings. I think you must use https (not http) on a mac but I'm really not positive on that point since I don't have a Mac. I assume both ISY's are on 4.9? if not you need a separate admin.jnlp file for each ISY.

no kidding... Wifi APs shouldn't have anything to do with... Insteon is at 915MHz so it's not even polluting the 2.4GHz airspace. Wish there was a method to figure out cause and effect...

I'll be looking forward to reading what @bmercier says.....

A better method nowadays is to use the Wireless tag node server and not a Kumo App, although Kumo app method will still work. (when I had 10 tags reporting temps and battery voltages via Kumo apps there were A LOT of errors and issues ongoing, since switching the the Wireless Tags Nodeserver I've had many fewer issues.)

@kzboray-- not so fast. Warning: Install 5.0.16C if you have a 300 series Z-wave Board. If your ISY has no z-wave board, or has a 500 Series Z-wave board then it's okay to go up to 5.3.4 How to tell. Open the admin console and look for a Z-wave menu across the top. If there is no z-wave menu, the ISY doesn't have Z-wave, proceed to 5.3.4 If there is a Z-wave menu check the z-wave version (last item on the Z-wave menu) 4.55.00 = 300 series Z-wave... Install 5.0.16C and do not go further. Also note that a user coming from v4.x at this point is the game most likely has this version if they have z-wave. 6.81.00 = 500 series Z-wave... Install 5.3.4 and keep up to date going forward. @Stan Wetmore A few additional notes: 1) In addition to making an ISY backup (and z-wave backup if appropriate) before you start also make a TEXT backup of your programs. Open the programs tab and click the top folder (usually My Programs) then right click it and choose "Copy Folder to Clipboard"... now open any simple editor that won't add formatting (notepad on windows is perfect) and paste. Now save the file. 2) It's in the instructions but everyone misses it, after the upgrade the admin console login credentials will be reset to admin/admin 3) Immediately upon logging back after upgrade in go to Help > About and verify that your Firmware and UI versions are the same... If they are NOT... Do not pass Go... you MUST fix the UI version so that it matches the firmware. I'd recommend using the ISY Launcher as discussed here. 4) Next, open the "Programs" tab, then "Summary" sub-tab. If you see the color YELLOW anywhere, that program needs to be manually fixed. It probably has the "Adjust Scene" function. NOTE: if you ignored step 3 above, you won't get past this step. Manually fixing programs that didn't convert is why you did step 1 above.

Or maybe your looking for the prefered UUID in the box above the dropdown:

Can you elaborate?... i thought I knew what you were asking about, but if that's not what you're seeking then I have no idea what you're talking about.

Log into Portal. Top left corner of screen, "My Profile".. change the dropdown to "use all ISY's in account" Does that solve the issue you have? Also Polisy comes with a Portal License... I think 2 years... to activate that 2 years tho you have to tell support which UUID to attach it to.

You're correct, XS was the last model with 3D touch. Se this article: https://support.apple.com/guide/iphone/touch-accommodations-iph77bcdd132/ios Note the section titled "Adjust settings for touch-and-hold gestures"

Nope. My serials PLMs both came with DB9 to RJ45, and it works with Polisy (I've tested).

Initially we had the opposite problem... Exit was broken, Enter worked perfectly, reinstall resolved that... not sure I'm looking forward to the next update.

Normally I'd say @kewashi could probably identify the issue the fastest even if it's something to communicate to UDI rather than adapt housepanel, but he seems to have vanished https://github.com/kewashi Jan 26th 2021 is the last time he touched any code.

There's always this device: https://www.amazon.com/StarTech-com-Serial-adapter-DB-9-RJ-45/dp/B00006IRQA/ which could be used with a plain ethernet cable. I would think someday UDI would identify a cable on Amazon with known compatibility. There have been multiple forum posts on the topic, but no word from @Michel Kohanim

There are apparently Geofencing issues in iOS 15 https://discussions.apple.com/thread/253247480 Until this morning I thought this was a Locative issue, but it looks like Apple broke it. that said... that doesn't explain why long press to reach the manual triggers isn't working for you. Obviously since it works for you on one, you know what to do and should be able to do it on the other. I would expect the XR to be the odd man out tho...

Is your wife's App up to date? That was added to the app in version 5.2.0 of locative about 6 months ago. (it was added as a direct result of an email I sent to the developer.)

Apparently there is a known issue with geofences and iOS 15. FWIW, I solved the problem for my wife and I by reinstalling Locative app, it's worked perfectly for us since... (reinstall was early in iOS 15, life, probably during 15.01's cycle) https://discussions.apple.com/thread/253247480 (skip the marked "answer" and read the rest of the thread)