gviliunas

******** My experience detailed below has been fixed with version 0.32 of UD Mobile. After installing and entering ISY Portal credentials, the sync operation now completes successfully without needing to configure the Local Connection ********* ************************ Got an invitation to install and give UD Mobile a try. (I thought that this was an updated geofencing client but was in for a good surprise) I'm using a Google Pixel 3a phone with Android 11 1. Downloaded UD Mobile from the Google store. 2. Entered ISY Portal credentials - Save 3. See Remote Connection Settings - Save 4. Sync ISY with UD Mobile - Yes Observe lots of transfer activity 1st try, the sync stalls with java.net.SocketTimeoutException: timeout (no Screenshot) 2nd try, try again. This time stalls at Inserting: Network Resources (See Screenshot attached) 5. 3rd try: Notice that on the Remote Connection Settings page there is an "Advanced Settings" area. 6. In Advanced Settings, entered IP and credentials for Local Port Settings 7. Clicked to Add New Local Network - Populated with current WIFI info (Thanks for that button!) - Save 8. Select to Add New Local Network and click on the WIFI SSID previously added - Save 9. Sync - Notice this is much faster than the previous sync via the ISY Portal. 10. Received "Finished with Error" message (See Screenshot attached) 11. 4th try: Back into Settings, try sync again. This time the sync finished with no errors. Although I had not had a need for mobile ISY access, I like the look and feel of this app. I can see myself making use of this to check light and thermostat status when I'm away

@WFPI believe that when you do a device replace, it is normal, at the end of the replacement, for the Admin Console to close. This isn't a "crash." I think you are warned of this in the replace dialog.

@Michel Kohanim Command was successful but nothing was upgraded: [admin@polisy /usr/local/etc/pkg/repos]$ sudo pkg upgrade Password: Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (0 candidates): 100% Processing candidates (0 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. [admin@polisy /usr/local/etc/pkg/repos]$ uname -a FreeBSD polisy 12.1-RELEASE-p10 FreeBSD 12.1-RELEASE-p10 r365882 POLISY amd64 [admin@polisy /usr/local/etc/pkg/repos]$ IS it possible that the FreeBSD url in update121.sh is incorrect? If I go to "https://pkg.isy.io/FreeBSD-base/\${ABI}/latest" I get a 404. I am guessing that the url needs to have ".../FreeBSD:12:amd64/" in the path

@Michel Kohanim [admin@polisy ~]$ uname -a FreeBSD polisy 12.1-RELEASE-p10 FreeBSD 12.1-RELEASE-p10 r365882 POLISY amd64 [admin@polisy ~]$ Hmmm Did this upgrade to 12.2? Here is the full upgrade output: [admin@polisy ~]$ curl -s https://pkg.isy.io/script/update121.sh | sudo bash Installing FreeBSD-base updates Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.txz: 100% 97 KiB 99.5kB/s 00:01 Processing entries: 0% Processing entries: 100% udi repository update completed. 356 packages processed. All repositories are up to date. Checking for upgrades (5 candidates): 100% Processing candidates (5 candidates): 100% The following 5 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: boost-libs: 1.72.0_2 -> 1.72.0_3 [udi] git: 2.28.0 -> 2.29.2 [udi] icu: 67.1,1 -> 68.1,1 [udi] node: 15.0.1 -> 15.0.1_1 [udi] sqlite3: 3.33.0,1 -> 3.33.0_1,1 [udi] Number of packages to be upgraded: 5 The operation will free 11 MiB. 36 MiB to be downloaded. [1/5] Fetching sqlite3-3.33.0_1,1.txz: 100% 1 MiB 1.5MB/s 00:01 [2/5] Fetching node-15.0.1_1.txz: 100% 7 MiB 7.4MB/s 00:01 [3/5] Fetching icu-68.1,1.txz: 100% 10 MiB 10.8MB/s 00:01 [4/5] Fetching git-2.29.2.txz: 100% 5 MiB 5.2MB/s 00:01 [5/5] Fetching boost-libs-1.72.0_3.txz: 100% 12 MiB 13.1MB/s 00:01 Checking integrity... done (0 conflicting) [1/5] Upgrading sqlite3 from 3.33.0,1 to 3.33.0_1,1... [1/5] Extracting sqlite3-3.33.0_1,1: 100% [2/5] Upgrading icu from 67.1,1 to 68.1,1... [2/5] Extracting icu-68.1,1: 100% [3/5] Upgrading node from 15.0.1 to 15.0.1_1... [3/5] Extracting node-15.0.1_1: 100% [4/5] Upgrading git from 2.28.0 to 2.29.2... ===> Creating groups. Using existing group 'git_daemon'. ===> Creating users Using existing user 'git_daemon'. [4/5] Extracting git-2.29.2: 100% [5/5] Upgrading boost-libs from 1.72.0_2 to 1.72.0_3... [5/5] Extracting boost-libs-1.72.0_3: 100% Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. All repositories are up to date. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. pkg: No packages available to install matching 'FreeBSD-*' have been found in the repositories lookig for .pkgnew files... Preserving files that are unique to Polisy lookig for any left over .pkgnew files... Upgrade complete, please reboot using: sudo shutdown -r now [admin@polisy ~]$ sudo shutdown -r now

Thanks for your help @Michel KohanimThe upgrade was successful. 5 packages were upgraded successfully. Installed packages to be UPGRADED: boost-libs: 1.72.0_2 -> 1.72.0_3 [udi] git: 2.28.0 -> 2.29.2 [udi] icu: 67.1,1 -> 68.1,1 [udi] node: 15.0.1 -> 15.0.1_1 [udi] sqlite3: 3.33.0,1 -> 3.33.0_1,1 [udi] Number of packages to be upgraded: 5 After a reboot, Polisy is running version 2.2.9-5 normally. Checking for updates does result in the "No updates available green banner..."

Sorry @Michel KohanimI think the url here: https://pkg.isy.io/script/update121 is bad, I get a 404 error when trying this [admin@polisy ~]$ curl -s https://pkg.isy.io/script/update121 | sudo bash Password: bash: line 1: html: No such file or directory bash: line 2: syntax error near unexpected token `<' 'ash: line 2: `<head><title>404 Not Found</title></head>

Maybe I declared victory too early.... I am actually seeing the same behavior as @macjeff. After a Polyglot restart, you get the green "No updates available..." bar BUT, one day later, the bar no longer appears. Past history has been for updates to be released at least every week. I plan to wait a few weeks and see if any updates are received and successfully installed. @Michel Kohanim, You mentioned optionally upgrading to freebsd 12.2. I started down that path using freebsd-update but received a warning that I would be overwriting the "polisy" kernel with a generic version. I stopped when I saw the warning. Do you have a procedure to safely perform FreeBSD upgrades?

ISY 5.3.0 Most people might be aware of this problem/solution. I wasn't until last weekend so thought I'd document this in case some are still having problems with Z-Wave and Control program triggers. I'm using a Homeseer WD200+ switch (v5.14 firmware) in an entry hallway. I rely on being able to detect "Control" conditions in order to properly trigger entry and exit programs. Sometime in the recent ISY update past, "Control" stopped triggering my programs. While looking through this, I discovered a new feature UDI added to the device Z-Wave menu: "Add/Refresh Button Press Node." I clicked to add this new "Detect Button Press" node to my WD200+ Hallways switch and then used this new node as the Control test condition in my programs. WORKS PERFECTLY. Just to be clear, my issue is with triggering udi programs. I have not tried using a button press node to trigger scenes and am not sure this will work for those needing a z-wave scene controller.

@Michel Kohanim Ah ha...I rebooted Polisy and now get the proper "No updates available ...: message. Everything working great! Thanks for your help

@Michel Kohanim The UI upgrade check does not complain but suspiciously, after I click to check for upgrade, I never get the green-banner message that "No upgrades were available. I only get the green banner "Sent upgrade check to Polisy..." After a few seconds, this message clears.

Hi @Michel KohanimThanks for looking into this. I tried sudo pkg upgrade. It did not appear to upgrade anything but I do not get the version mis-match error. Should the freebsd version be: 12.1-RELEASE-p10 ? [admin@polisy ~]$ sudo pkg upgrade Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (0 candidates): 100% Processing candidates (0 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. [admin@polisy ~]$ [admin@polisy ~]$ [admin@polisy ~]$ freebsd-version 12.1-RELEASE-p10

I opened a ticket on this and received a response that the UDI guys are on it.

@TomL With Z-Wave, there is still a bit of "wild west." Not so much plug-and-play but more of plug-and-play-with-it.... I don't have these anymore but was able to get my hinge pin sensors to work by changing the notification mode of the sensor. I remember that the default setting did not work. The GE instructions have you press the button. There is an entry on the Z-wave Alliance showing this being controlled by Parameter 20. Try the button method or setting parameter 20 to 2 or 3 after waking-up the sensor. One of these should work. The node I used once connected to ISY is the "Barrier Sensor"

@ExDvtchWhat version of firmware did you upgrade from? Are you using the 500-series Z-Wave dongle (No blue LED in the rear of ISY)? Ver. 5.3 does not support the older 300-series dongle.

@Mecheng70, I tested this code and it seems to work properly but there are two caveats and one question: 1. The variable s.casita_guest_code must be a State variable. If not, the program will never be triggered. Programs cannot be triggered by changes in Integer variables. Because you are setting s.previous_guest_code = s.casita_guest_code in your program, it seems that something changing s.casita_guest_code will cause the program to do what you want. 2. The variable s.previous_guest_code may be a State or Integer variable. In your program, changing this variable will not change s.casita_guest_code so you probably don't want the program to run if s.previous_guest_code changes so this can be (and you probably want this to be) an Integer. Question: Why do you have this line: "Stop program 'Door - Casita Code?" Once triggered, all of the "Then" lines are atomic and the program will stop anyway.

@esloyerIt is usually better to use your own ISP's email server or gmail rather than UDI's default server.

Yes, it looks like UDI took the Boot Loader line out with v5.2.0 RC3. That is okay. 6.81.00 is the latest version so you have no problem here. The 500 series doesn't need a Boot Loader

This is normal. I believe that the 500 series chip does not need a boot loader.

@TexMike @hart2hart Here are the instructions we followed when beta testing the 500 dongle (I suspect any FW 5.0.13+ will work): Note backup of the 300 board is very slow (40 min- 1 hr) and may fail and need to be repeated. You must be running 5.0.13 You must backup your Z-Wave dongle (Z-Wave | Tools | Backup) … this is going to take a LONG time so, if you decide to go for this beta, it's best to backup now Disable query at restart Replace the dongle Restore your Z-Wave dongle by doing Z-Wave | Tools | Restore … this is going to be pretty fast Test communications, Heal the network, backup, and range (should be a little better)

@Bspect I set a variable equal to the MS6 temperature node each time the node updates. Here is the pseudocode: If status of Kitchen Temp is not 1000 Then set sTempVariable = MS6 Temperature node degrees F Your other program can check if the Temp is too high and send the e-mail In the E-mail customization, you can reference the variable

Successfully upgraded from v5.1.0 to v5.2.0. No issues encountered and everything, including Z-wave devices, is working well. Thanks for the great development effort!

@mitch236 You query the top level node in your Devices section. For me, this node is called "ISY" but your may be different. See attached screen shots.

@bobchap There were 2 versions of the Z-Wave dongle released by UDI. The first version was based on the 300-series Z-Wave chip. This version had FW version 4.55 and sported the ability to connect an external antenna and had a blue LED on the dongle which protruded through the rear of the ISY case. The newer version of Z-Wave dongle release ~ July, 2018 was based on the 500-series chip. This version had FW version 6.81.00. This version does not support an external antenna and there is no blue LED on the dongle.

For Homeseer WD200+ Users, ISY v5.1.0 creates a new "Basic" node if you synchronize this device. The Basic node and the Dimmer nodes appear to operate similarly but status back on the Basic node does not update properly: 1. If you switch-On or Switch-Off this device from the local switch, The Admin Console status will not change. (1st problem) 2. If you switch-On or Switch-Off from the Admin Console, the Status will rise or fall but will not end-up at the correct value. i.e. Turn-On and expect to see 35% but instead see random values from 16-22% (Incorrect) If you query this node, the status value jumps to 35% (Correct). Turn-off and expect to see 0% but instead see 16-9% (Incorrect) Again, if you manually query the node, the status will be correct 0% (2nd problem) I tried changing the "Automatically sends status update" setting but this did not fix status reporting for the Basic node of the WD200+ The Dimmer node seems to report status properly both when controlled locally and via the AC - I recommend that you use this node in your programs and scenes Event viewer L3 data attached. Basic Node Turn ZW072 On and Off from AC.txt

If we "old guys" stick together, we only need to remember how part of this system works ?