Michel Kohanim

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

@vbphil, Apologies. There are 5 important services that have to run: polyglot (and pg3), udx (does sys admin stuff), isy (IoP), and mongod (will be gone when pg3 is official). So, pkg update and upgrade upgrades all packages. The services restart the aforementioned. You should include isy. With kind regards, Michel

Hello all, At this juncture, it's best to use ssh for the last time. The console and pushing the button are the best methods for upgrading. But, since the last update was missing files, none of those will work. I do apologize. In short: sudo pkg upgrade udx sudo pkg upgrade isy sudo service udx restart sudo service isy restart We also found another bug relating to portal subscription which will be installed. With regard to UEFI, if the right most light is not blinking, then you have the right version. Also, when the time comes for this to be mandatory, udx will automatically install it (and we'll let you know). TPM boot depends on UEFI. But, TPM for application (in the Admin Console) does not require UEFI. With kind regards, Michel

All, Sincere apologies. Found two bugs due to two missing files that were not included in the package. Please do: sudo pkg upgrade udx sudo service udx restart Shortly, this will be included in an isy package so that you can upgrade from the Admin Console. With kind regards, Michel

All, Sincere apologies. Found two bugs do to two missing files that were not included in the package. Please do: sudo pkg upgrade udx sudo service udx restart Shortly, this will be included in an isy package so that you can upgrade from the Admin Console. With kind regards, Michel

@macjeff, As I mentioned, Alexa has throttle procedures. After the upgrade, ISY publishes 1000s of events. Alexa sees them and decides that this is too much and thus throttles everything. So, by the time the variables are reported, Alexa ignores them. If you wait 15-30 minutes, they start working again. With kind regards, Michel

Hi Guys, UEFI vs. BIOS. In short, you can ignore it for now. But, you'll eventually have to flash with UEFI. This way, we can make sure that TPM boot is working (i.e. will only boot UD signed OS). With kind regards, Michel

Re, blinking light is because: - UEFI image. Currently, Polisy uses BIOS which does not support TPM boot. If the 3rd light is blinking, it means that you still have BIOS and not UEFI. You can click the button on the front 6 times consecutively and UEFI will be installed. This said, at this juncture, this is NOT mandatory Re, variables not triggering Alexa: If the variables are updated in the Admin Console AND in the Alexa App, I cannot see how this would have anything to do with the upgrade. It's Alexa throttling things. With kind regards, Michel

OUTDATED - This version has been updated and is obsolete. Please see the current release found in the Current Release area of the forums. Hello all, We are very happy to introduce IoP v5.4 which includes many new enhancements and bug fixes. 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 (best option) - 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: - A10/X10 menu missing - UUID tied to the wrong port - Added WebSocket Protocol header back but it's not checked - Fixed User Web Directory access failure - Added customized notifications to node servers - Fixed ISY Portal module not persisting after backup/restore - Error log formatting - Network resources malformed when using URL encoding. Follow these instructions ${sys.node.#.name:url} - URL encodes the resulting string ${sys.node.#.name:std} - Does standard formatting (as done currently) ${sys.node.#.name} – Does default formatting (currently same as using “:std”) Enhancements : - Added Gallon per hour - You can now use the extra network ports as a network switch. To enable/disable, please go to Admin Console | Configuration tab | | Network Settings | Network Switch Mode (ON) - Added support for TPM basic TPM operations (such as enable/disable). To enable/disable, please go to Admin Console | Configuration tab | Security - UEFI image. Currently, Polisy uses BIOS which does not support TPM boot. If the 3rd light is blinking, it means that you still have BIOS and not UEFI. You can click the button on the front 6 times consecutively and UEFI will be installed. This said, at this juncture, this is NOT mandatory Important Note: This version of IoP requires a few packages that come with udx 2.6. If for any reasons IoP is not working properly, it's mostly because udx was not automatically upgraded in the process. If that happens, please do let us know. With kind regards, Michel

This probably means that IoP starts much later than PG2 and PG3, and by that time, PG has given up till the next poll. We'll definitely take a look. With kind regards, Michel

@bpwwer, I totally agree with you. We do not have any resource constraints on Polisy. And, once we get rid of that monster, mongodb, we'll gain back another 800MB. This said, and based on your explanation, I am not so sure. Perhaps we can ask @Chris Jahn. With kind regards, Michel

@bpwwer, is that any different than adding a ST property for a Heartbeat node? With kind regards, Michel

I think this should be a hard requirement: all node servers must report heartbeat. With kind regards, Michel

@vbphil, to which port are you connecting the serial? With kind regards, Michel