CMortimer

Success! UDI came through when I took out a ticket. Many thanks to Michel Kohanim. The solution asked me to upgrade to PG3x. After the upgrade everything returned to normal operations. Here is the link to the PG3x upgrade ... https://wiki.universal-devices.com/Polisy:User_Guide#Upgrading_to_PG3x

Yes, I was aware of this clickable button. However, even if it did all the start.jnip to run, it sis not create any licensing information. I am now working a ticket on the bigger issue of recovering my Polisy capability.

Thank you Hoosier Daddy, I am running macOS Sonoma 14.4.1 and can replicate the screen images you have shown me. However, at the end of the start.jnip process i still cannot see any license information. It also seems to make a difference as to where I run the start.jnip app. After downloading i can get the process images shown if i run it directly from the download folder. However, if I move it to a folder or to the desktop it does not open and results in another not allowed to run dialog box. On the other matters, I will be requesting a ticket to resolve my access to the Polisy with Z-Matter.

Thanks Techman. Hoosier Daddy - no certificate shows up for the Universal Devices IoX launch app. How do I make it happen so that the start.jnip app has a certificate?

Techman, I tried all you described but not improvement. I'll ponder on the matter and see if I get any inspiration.

I have read the thread with interest. However, this was written two years ago and now my macOS is Sonoma version 14.4.1. Many of the security provisions have changed since 2022. I can down load thé applet start.jnip . But when I run it I have to give permission to macOS to bypass security provisions to allow it to run. It appears that every time I try to run start.jnip it results in the message "Unable to launch application." Clearing cache does not seem to make any difference. It's puzzling because I am still getting some notification messages from the Polisy but with zero values for items like temperature and humidity. So it is sort of alive but not to useful. Am I faced with a total reset where the programs will be lost and the Polisy with Z-matter would have to be reinstalled once again? Help.

Hello Techman, I cleared cache and performed the power off on cycle. But no improvement to normal operations! I recall the last time I saw the AC info the Firmware and UI were both showing version 5.8.3. Also, when I resolved the macOS security issue with opening a app from an unidentified developer, the opening dialog became "Unable to launch application" with a detailed dialog I could not copy. Hello bgrubb1, The configuration page for the network shows all zeros or blank fields with DHCP checked. When I did get the AC to open, the iP address was all zeros and not the normal IP associated with the Polisy. But iCloud access was still possible to get a AC display with no device functionality (Z-wave or Insteon) Any other ideas?

My two year old Polisy with added Z-matter fuctionality has become totally non-functional for devices and programs. I have been uusing my Polisy for a year or two with a mix of Insteon and Z-wave devices. About two weeks ago I noticed my Insteon devices and programs were not working. At the time I was using an older version of the Firmware and UI about 6 months old. I forgot to note the version before this problem cropped up. After checking the Insteon devices carefully and replacing the PLM, there were no improvements. Here is a sequence of what I did to try to get things working again ... 1. PLM status shows as not connected when running PLM status from Admin Console (AC) diagnostics. 2. Any Insteon device action from AC to turn on or off results in a PLM failure message. 3. Changed the old USB PLM (2413U) to a new PLM from the new Insteon vendor and used the specific power off / on PLM and Polisy sequence. Result - no change to Insteon functionality. 4. Decided to do an Upgrade Package action from AC. Result - version 5.8.3 was operational. Also all insteon devices were also operational along with Z-wave devices. Good news was short lived! 5. After makeing a few program updates, Ithe system became unresponsive to all Z-wave devices and there was a message under the Z-Wave portion of the AC stating "Z-matter unresponsive. " Prior this time I could log into the AC using the LAN. 6. Decided to do a reboot from the AC. Upon completion of Reboot, the IoX launcher could not find the Polisy and the URL shown was all zeroes. 7. Tried a Power off / on cycle - No improvement. 8. Access to Polisy is available by Cloud AC. But not functionality for any devices. Tried another Upgrade package by Cloud AC - no improvement. So the Poisy system and all programs is essentially totally non-functional. How can I recover the Poisy and its programs to its correct operating state? The policy has lost its ability to establish a DHCP address and only has access from Cloud AC. Any help will be much appreciated.

Thank you for this useful tip. I will try your suggestions on my other Zooz devices. It is interesting to note that when I removed the device, all program lines referencing the device were deleted forcing me to completely recreate the logic for each blank lines. It would be very nice if Universal Devices would simply flag the code lines as needing device update,

Thank you for letting me know how to do this linking mode or Z-wave sync. I tried this and it did not work. So I decided to reinstall the device and adjust the associated programming. All is now well with all variables showing, along with battery level. I now have to do this procedure with the other Zooz battery powered devices, i.e., ZSE18 motion sensor, and ZSE44 temp/humidity sensor Thank you

The admin page shows a device linking feature but it seems to be for Insteon devices and not Z-Wave. Please clarify what you mean by “putting one of the devices into linking mode.”

After i migrated to ZMatter on my Polisy system, I noticed that none of the battery sensors/devices were displaying battery level on the device main screen, or reporting battery level in a program. At present, all battery devices are reporting a blank field on the Main device page, or a zero value when reported by a program. All other features like motion, temperature and humidity are being correctly displayed and reported. How can I get the battery level to display correctly again. I have looked through many posts but none have addressed my particular situation.

Geddy, Thank yo so much for your help. I also found this same information but when I tried it, it did not work. However ... I found out the solution to this matter of acquiring the actual sensor internal parameters. This approach involves the Action feature in a program. In Actions, select Variable in the left hand box. Then select the variable you have created to hold the sensor value and define the conditional relationship for that variable. I found out you cannot directly use internal sensor values in a program but must equate a variable you create to a sensor internal parameter, i.e. temperature. Then click several times on the small right arrow at the end of this line. This will sequence various features: number, another variable, time, and then another line showing sensor internal options. In this last line you can identify the specific sensor parameter you want to equate to the previously created variable name. See attached picture. This feature does not appear to be described in an easily found reference. It works!!! problem solved! Screen Shot 2022-12-02 at 12.14.55 PM.pdf

I have been using the ISY Polisy for several months with several short programs. However, one aspect of the programming eludes me in spite of searching the forum. That aspect has to do with establishing the names of variables for sensor parameters, like temperature or battery level for use in a notification report, or use in a program. For example, the Zoom ZSE 40 sensor with motion, temperature, battery level and luminance allows a conditional test to be made against a specific numeric value. However, defining that same parameter in a notification is not obvious. This parameter value must be available internally as a variable so that the conditional test can be made, but where is it for the user? What is the convention to acquire the value of a sensor parameter so I can equate it as a value in a variable of my own making? How can I embed sensor variable names in a notification report, so that in the email posted, when the test condition is true, it also provides sensor state about its local conditions. In a conditional test, I have used the ZSE40 temperature tested against a temperature less than 60 degrees. How can I define the internal variable describing the actual temperature, so that it is available for use in a notification report Any help would be much appreciated. Charles

Thanks for REST information. I find it strange that an ISY program can test for a condition (>,=,<, etc) against a sensor parameter value, but this same capability to include, as an action, that parameter value in a report or log defined by a user program does not seem to be available. Weird! Perhaps a ticket to Customer Support may shake the answer from the tree?