Michel Kohanim

Hello all, We found the issue with Z-Wave. The chip is going to bridge mode and thus all the issues. It's already fixed and we are testing. We should have another release by no later than tomorrow. With kind regards, Michel

Hello all, Sincere apologies for all the issues. We have identified the root cause of Z-Wave not working properly and working on it. It seems to be a configuration issue with some of the dongles. Please stay tuned. With kind regards, Michel

@larryllix, please submit a ticket. With kind regards, Michel

@rob.bushkaufer, Thank you very much. Just found that issue working on @mbking 's unit. The way the upgrade process works is to first check for an upgrade to udx. If none is available, then it continues upgrading packages including the kernel. If udx does have an update, then it will install udx first and then exits. Once udx restarts, it starts the upgrade again. For some reason pkg is not being upgraded automatically. We are trying to find the root cause. Should have a fix shortly. @larryllix, precisions for variables are way down on our list of things to do. With kind regards, Michel

@mbking, As mentioned, it might take a long time depending on how old your os level is. Please be patient. With kind regards, Michel

Hello all, This is the support thread for IoX v5.5.0. In future releases, IoX will have its own forum and support not tied to any hardware: https://forum.universal-devices.com/topic/39380-iox-release-v550-is-now-available/ What to expect: 1. We could not get migration to work without losing all routing information. We will continue to work on it 2. OTA definitely has issues but now it's very highly likely that the issue is on the device side With kind regards, Michel

* IoX = ISY on Anything. Welcome to ZMatter Z-Wave+ Beta ! This is probably one of the bigger endeavors we have taken on as a company. It's basically a combination of hardware + rewriting all the Z-Wave code we had, as well as testing and regression testing over and over again. Although very proud of our accomplishment, we still missed two crucial features that we had promised but could not deliver: 1. Migration - there's a bug in SiLab's firmware which corrupts memory by reading/writing from the NV area of the dongle. Silabs has been notified but the likelihood of a quick resolution is very low. As such, on parallel, we have been working on an alternative that uses ISY information to rebuild the network. The main issue with this approach is that we lose the routing tables (you will have to go around, wake devices up, and update neighbors for each). We are trying to find a solution. 2. OTA - in some cases, the end device gets corrupted. At this juncture, it's highly likely that the issue is with the end devices. This said, we decided not to include this feature yet lest it bricks your device(s). Once we have a definitive answer as to which devices exhibit this behavior and whether or not our firmware contributes (highly unlikely), we'll include it We are working on Migration as we speak, and in addition to bug fixes, that's our #1 priority. Getting Started Make a backup of Polisy (Admin Console | File | Backup IoX ) Launch the Admin Console, go to the Configuration tab, click on Update Packages. Warning, this might take a while depending on how current your OS is Once completed (4 beeps + 1), unplug Polisy Remove the Zooz stick (or other 700 series Z-Wave dongle) If not already, install the ZMatter board inside your Polisy. Here are the instructions: ZMatter-Assembly- Instructions.pdf (universal-devices.com). Ensure that the antennas are connected in the proper location (Z-Wave = yellow band, on the left. Zigbee = red band, on the right) If you are using INSTEON, make sure the PLM is connected Power up your Polisy note that initial boot might take a much longer time than normal because udx might want to install missing packages to assist with migration (in the future) Once boot up is complete, Launch Admin Console and go to the Configuration tab Press the Move to ZMatter Z-Wave button A popup will appear, select Ok to start using ZMatter Z-Wave+ When IoX restarts, all existing Z-Wave nodes from the old installation are removed Note: The only way to go back is to restore a backup that was made prior to moving to ZMatter Z-Wave+ Lift Off! At this point you are now using ZMatter Z-Wave+ ... Congratulations!!! If there is an existing network on the ZMatter Z-Wave+ board, it will be used but devices using S0/S2 security will not operate (they will have to be removed and added again). To use the existing network Z-Wave | Synchronize | New & Deleted with Interview from the top-level menu To start over and build a new network select Z-Wave | Advanced | Factory Reset Z-Wave Dongle Build your Z-Wave Network using the top-level Z-Wave menu to Add and Remove devices Features S2 security Improved network communications Fast backup/restore of the Z-Wave network Scenes using native links (associations) Smart Start Next Migration! Support Thread With kind regards, Michel

@ACastiglione, no but we should by very early 2023. With kind regards, Michel

Hello everyone, Uploading the 5.5.0 firmware as we speak. Working on instructions and documentations. Please note: 1. We could not get migration to work without losing all routing information. We will continue to work on it 2. OTA definitely has issues but now it's very highly likely that the issue is on the device side With kind regards, Michel

@MWareman, yes, 13.1p5 has already fixed it (released last week). To upgrade please use the Admin Console. With kind regards, Michel

@FerventGeek, Thank you. I spoke to Wes. He might consider adding the security requirements that we need for portal integration. He will consider as time permits. With kind regards, Michel

@robgarrett, The prices will surely go up after January simply because Intel decided to raise its CPU prices by 20% in October!!! With kind regards, Michel

All, about 2:00PM PST. With kind regards, Michel

@snesgenesis, As far as I know, ELK only supports one TCP connection at a time (or at least, that's how it was a few years ago). So, I very much doubt they will work together. With kind regards, Michel

First of all, I would like to apologize for the poor choice of words I used in describing those who are eligible for refunds. Extremely bad choice ... It's true with only one comment: eisy does not have PG2 and mongodb installed. It's only pg3, and to be exact pg3x to which everyone will be migrated (without any impact). With pg3x, each node server has its own OS user + own certificate + authenticated against broker using those certificates. As such, there is a little heavier load on each node server. But I do not see any performance degradations if you don't have 15-20 node servers bombarding pg3->iox every few seconds. With kind regards, Michel

Hello everyone, As mentioned before, Polisy is not obsolete. We plan to maintain and enhance it till 01/01/2026. With kind regards, Michel

Hello everyone, Apologies, doing final testing. Should be there tomorrow. With kind regards, Michel

High level comments: 1. Yes, everything should run without having to fiddle with it 2. Yes, the website should be more user friend 3. Yes, we should provide more news Unfortunately, 1. Some things are beyond our control such as $6K/year minimum for Weather services 2. People not reading their emails 3. Us being too geeky and less sociable and thus focus more on the product than the website and news With kind regards, Michel

Polyglot will remain on Polisy till such time that it's no longer supported by the available libraries. Polyglot is NOT available on eisy. Only PG3x is available on eisy. PG3x is a more secure version of pg3 and supports ALL pg3 node servers. The only differences are: 1. Authenticates users against iox while being authenticated itself by udx (it does not have its own user/password anymore) 2. Each node server has its own user, home directory, certificate and channel. Therefore, node servers cannot read from/write to the filesystem of other node servers nor can they listen in on other node servers' mqtt channels 3. Does not depend on node.js implementation of mqtt (aedes) that is included in polyglot and pg3 4. Designed so that we can support remote access 5. Best of all, saves 800M of RAM So, I guess we need to find developer who can migrate pg2 to pg3. With kind regards, Michel

@FerventGeek, apologies, with all that's going on, TL;DR ... I'll talk to Wes. With kind regards, Michel

@johnnyt, PLM is dying or will die. It's just a sign of deterioration in performance when the PLM responds with junk and thus -10. With kind regards, Michel

@FerventGeek, It's probably not connected to IoX. Please follow these instructions: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#ISYs With kind regards, Michel

@EJones01, If you are on OS 13.1, you can install anything you want but it's definitely not something we support. To search for packages to install: pkg search adb or pkg search nvidia to install: sudo pkg install <name> to remove sudo pkg remove (or delete) <name> With kind regards, Michel

@MWareman, If you are still having this issue, please do submit a ticket and we'll get to the root cause. With kind regards, Michel

Hello all, 1. Yes, you need to wait for 12/1 isy package. The only thing holding us back right now is migration of S0 devices to S2. But I think we finally have it fixed 2. For those in Canada, AARTech is carrying ZMatter now: https://www.aartech.ca/universal-devices-zmatter.html With kind regards, Michel