Michel Kohanim

Hello all, We are very happy to introduce IoP v5.4.2 which is a minor bug fix release and security enhancements. If you are new to Polisy, please do make sure to review Polisy User Guide. To upgrade, you have a few choices: - Click the button on the front of the unit only once and wait for the beep - In the Admin Console, click on Help | Automatically Upgrade Polisy menu - If you are a geek, ssh and: sudo pkg update && sudo pkg upgrade && sudo service isy restart Bug fixes: - Fixed sunrise sunset UI mismatch - Removed TPM dependence on flash - Unnecessary flash usage - Flash is no longer automatically upgraded to UEFI - Z-Wave: Added support back for 3 byte config params Enhancements: - System editor support for _sys_notify_short allowing node servers to receive notification text in command parameters https://wiki.universal-devices.com/index.php?title=Polisy_Developers:ISY:API:System_Editors - Z-Wave: Added support for showing all Z-Wave native links available (in Node Level popup menu and Top level Z-Wave menu) - Security: Independent security keys are now sealed with the TPM. This allows all clients to use as many different keys as they need ... for instance, each node server can have its own keys that are sealed by the TPM Important Note: UEFI upgrade is no longer forced because of variability of the outcome. If the 2nd or 3rd (or both) are constantly blinking, it's best to force upgrade the BIOS on your own by clicking the button on the front 6 times in quick succession Support Thread: With kind regards, Michel

@peterathans, Working on an updated UI that is less restrictive than what Z-Wave certification requires. Should have something fairly soon. With kind regards, Michel

We cannot fix Echo issues. It's 100% related to throttling. It was also reported by someone with 4.7 firmware. WOL is low priority. We have no devices to test this feature. Variables having incorrect time is a UI bug and will be fixed. Random events being ascribed to Polisy being online is obviously a node server not a ghost. With kind regards, Michel

@Techman, I have reported this to @Chris Jahn. With kind regards, Michel

@kowaj, Apologies ... please try again. @brians, With the coupon code, it's even less expensive. Around $16.00. With kind regards, Michel

Sunrise/sunset times in IoP are UI only issues and already fixed. With kind regards, Michel

@JimboAutomates, the earliest versions might have an issue depending on what's been flashed. I would say the first 30 units in the early batch might have this issue. In addition, the flash update might take up to 5 minutes and, in at least one instance, the customer rebooted during the flash update (the 2 and 3 light blink while updating the flash). The good news is that, even if the flash is destroyed, there's a flash chip that you can plugin. The bad news is that it'll take time. @larryllix, I am sorry. When I did a remote session to your unit (spare), rc.conf had been modified by the original owner not to include polyglot_enable="YES" (it was changed to NO) and mongod_enable="YES" ... udx (the thing that talks to hardware) requires both of these to be running. If they don't run, udx doesn't have the cert to communicate with anything else including ISY. That's why you would get 0000 as the UUID. Once I left the session, everything was working. What changed thereafter was changing the IP address and most probably a reboot. Perhaps the original owner has a script that disables those and which runs after reboot? With kind regards, Michel

Thank you both. I have asked @Chris Jahn to read the reports and provide much needed details and clarity. With kind regards, Michel

@matthewjocko, Of course and without a question. With kind regards, Michel

@larryllix, Whatever you do, do NOT reboot. Submit a ticket and we'll do a remote session tomorrow. With kind regards, Michel

@mmb, Currently, the only way to verify UEFI: sudo vi /var/udx/logs/log ... scroll down to a few lines before the bottom and you should see somthing like: Tue Mar 8 15:28:22 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices Tue Mar 8 15:28:22 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Tue Mar 8 15:28:22 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.1.3 Tue Mar 8 15:28:22 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios has the correct version With kind regards, Michel

@DennisC, Please submit a ticket. Please do NOT reboot polisy. With kind regards, Michel

All, here's the support thread for IoP v5.4.1 With kind regards, Michel

All, this is the support thread for 5.4.1: With kind regards, Michel

Hello all, We are very happy to introduce IoP v5.4.1 which a major bug fix + updates the BIOS to UEFI. If you are new to Polisy, please do make sure to review Polisy User Guide. To upgrade, you have a few choices: - Click the button on the front of the unit only once and wait for the beep - In the Admin Console, click on Help | Automatically Upgrade Polisy menu - If you are a geek, ssh and: sudo pkg update && sudo pkg upgrade && sudo service isy restart Bug fixes: - Fixed crash - Removed extra \n in the log Enhancements: - Force updating BIOS to UEFI Important Note: In order to make sure everyone has the capability to upgrade to our future OS versions, in this release we are force updating the BIOS to UEFI (if not already done so). Since this is a very sensitive process, please make sure you do NOT unplug your polisy for at least 10 minutes. The process is as follows: If you already have UEFI, you will hear two beeps within 10 seconds of each other If not, you will hear a beep, the two right most LEDs start blinking for about 1 minute. Then, you hear a beep as polisy reboots After reboot, the initial boot up sequence might feel a little slower but that's only for the first time With kind regards, Michel

@mbking, thank you. Thanks to @macjeff, we found the bug and crushed it: 1. Polisy is much much faster than 994 and thus the queues/elements were not optimized to handle the performance improvement 2. There was a bug that caused infinite loop for those with massive number of nodes Should have 5.4.1 out shortly which also includes forced migration of BIOS to UEFI. With kind regards, Michel

@kzboray, thank you for the details. All, those who think a device should support scene/associations, please save the contents of the Z-Wave Information in Event Viewer and paste here. With kind regards, Michel

@johnnyt, sudo pkg delete isy sudo pkg install isy With kind regards, Michel

@kzboray, you are very wise. Not one week goes by without new owners calling us and expecting a crash course, support, training, and almost all are so demanding. It's just a nightmare dealing with new owners. So, lately, we just send them a canned response: The most important thing is to make sure you have the username/password to login to ISY Once you have that, start from here https://www.universal-devices.com/start so that you can access ISY. Once you have accessed ISY: The best source for information, tutorials, and examples is our Wiki and the best reading material is our Cookbook If you have specific questions, we’d be delighted to answer them (the same method as you used to create this ticket) We have a huge and very friendly user community at our forum And, if you would like training and remote session support, we offer scheduled remote sessions (training, walkthrough, programming, etc.) at $125/hour @roadking2003, in addition to what kzboray suggested, please leave them your credentials, a backup, and a link to https://www.universal-devices.com/start . Also, you can transfer your ISY Portal account:https://wiki.universal-devices.com/index.php?title=ISY_Portal_Transfer_Instructions. With kind regards, Michel

@DennisC, It depends on the change. As long as they support client keys, it should work. With kind regards, Michel

@kzboray, Association can only be found if devices are inside a scene. One is called Z-Wave Association and the other Z-Wave Scene. Once inside the scene, click on the controller and see whether or not you see Association or Scene (in addition to Default and Command). With kind regards, Michel

We'll take a look. With kind regards, Michel

@johnnyt, Please follow the instructions here. With kind regards, Michel

All, there are three bugs we are trying to crush: 1. IoP crashes on bootup if you open the event viewer + system busy. Found the root cause, should be fixed shortly 2. PG3 crashes and creates multiple duplicate node servers. Thanks to @dbwarner5, we are very close to finding root cause 3. Variable updated times are not accurate. Trying to reproduce With kind regards, Michel

@asbril, That's a bug with PG3. It's already fixed. We are working on ensuring that ssh etc. are no longer necessary. With kind regards, Michel