Michel Kohanim

@webminster, do you have any green/gray 1011 icons in your device tree? With kind regards, Michel

All, the issue is that, previously, network resources were queued. In Polisy, they're inline. So, if you have any sort of network issues and network resources, that's the first thing you should take a look at. With kind regards, Michel

@ccclapp, After 2 years, many things might have changed including your router and network settings. In addition to the great feedback above: https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Not_Found With kind regards, Michel

Also, 1000 is very low for timeout. Please use 10000. With kind regards, Michel

Wish her speedy recovery. O lord. As I suspected, it's a lose lose proposition. Here are some answers to prove my point (hopefully I am wrong): 1. Here's the database structure: uuid, active, installed, date installed, date purchased, expiry date (hint, no link to user) 2. We do not keep any statistics on anything 3. When you open the Admin Console: - Check for firmware update so that you'll see the red banner on the top right corner. Polling https://www.universal-devices.com/auto_update/prod-updates.xml - Check whether or not anything needs to be installed/removed (the same thing as Help | Manage Modules) which polls the database in #1 If it cannot connect to the Internet: you will not know there are updates and you will not know whether or not something has to be installed. Nothing else. On ISY: 1. Unless you use a local NTP server, obviously ntp server 2. If you use mail/notifications, obviously email server 3. If you have ISY Portal, obviously my.isy.io Polisy is identical to ISY with one exception: On udx start, if there's missing package, it's installed from pkg.isy.io. With kind regards, Michel

To ask what? Admin console polls the database to see what needs to be installed or uninstalled. How else would it know? ESP? And, if it had ESP, then you would call it magical. So, it's a lose-lose proposition. I urge you stop the fallacy of "suddenly the portal module appears". The portal appears IF AND ONLY IF you click on the Help | Manage Modules menu, AND you are prompted to INSTALL the ISY Portal AND you click Ok. It does not automatically appear. I know you don't believe me (it's quite obvious), so, why don't you try it yourself. Nothing in that post discredits what both @bpwwer and I have outlined above. With kind regards, Michel

Yet more assumptions and absolutely untrue! For 994, there are three ways: 1. Buy the module for $23 (2 years) or $15 (1 year) -> put a record in the database for expiry date in 1 or 2 years 2. Trial license (what we ask customers do with Polisy) -> put a record in the same database for expiry date in 30 days 3. Send a request to sales Admin Console (NOT ISY nor Polisy), Help | Manage Module checks what's installed on Polisy or ISY994 and compares it with what's in the database in the cloud based on UUID. It then presents Install/Uninstall. This process is 10000000000000000000000000000000000000000% identical on both. The only difference is that we do not allow modules to be purchased for Polisy because everything is moving to node servers. Please post the thread that "disclosed" the "must" for PG3 remaining connected to the internet. PG3 itself is not persistently connected to the internet. There might be node servers (all cloud based node servers) that rely on the internet. PG3 itself only checks the license for node servers that are not free/perpetual and only after start of a node server. With kind regards, Michel

A lot of conjecture that could have been answered without the conjecturing, assuming, and presuming things. Completely and utterly 21st century. Just like 994, Polisy does not require internet connectivity for things that are not internet dependent: Z-Wave, INSTEON, Matter etc. Portal tab uses the same exact (100%) procedure as you trial license for ISY994. It's not magical. It's IDENTICAL. Extremely disappointing. With kind regards, Michel

@Gerald l. Agliata, We do not have any tickets from you. Please either send an email to support@universal-devices.com or submit a ticket online. With kind regards, Michel

@bpwwer, Yes, of course and through our slack channel. With kind regards, Michel

@brians, Both were updated: package dependencies as well as udx itself. With kind regards, Michel

I've known Ken since we started 16 years ago. He definitely deserves a chance. With kind regards, Michel

All, Sincere apologies. I should be fired! For security reasons, we are changing the way udx, isy, pg3, and node servers are configured and communicate. In the process, we added another library (libwebsockets) for mqtt. But, udx had a conflict and thus a failure. The upgrade upgrades udx to 2.6.4 and removes the conflict. With kind regards, Michel

Subscription request does not do a query. With kind regards, Michel

Just sent @Panda88 an email. With kind regards, Michel

We could do the same. But, there are multiple issues: The http socket is not persistent. This means that we either have to basically do away with change of state (i.e. Control) or we have to have another thread that keeps polling the buffer (change of state goes into the buffer). Buffer has to be cleared otherwise we will lose data. So, it becomes an exercise in trial and error in timing especially for larger installations. When exactly do you query/clear? Do you query every second? Wait for some event? So, it's just way too much development for something that we have absolutely no control over. With kind regards, Michel

@larryllix, Will look into it. With kind regards, Michel

Here are some things that are not under NDA: 1. We cannot get parts to build our own version of PLM 2. Thanks to a couple of very bright engineers at SmartHome, we can make Nokia Hubs into PLMs. So, if we can buy Nokia Hubs from the person who buys SmartHome, then we should be set 3. If anyone can figure out how to make Hub II (smaller boxes) into PLMs, that would be a good solution too 4. We are still pursuing PLM Pro With kind regards, Michel

Hello all, Some more updates: 1. 100% confident you can restore from Zooz backup 2. 90% confident you can restore from 500 series backup (994) 3. 70% confident you can restore from 300 series backup With regard to change of direction: Our codebase was old with much legacy stuff around 300 series and 994. So, while we managed to migrate it to Polisy + support Zooz, S2, OTA, backup/restore made us rethink our direction as it would have taken us many moons to be able to do all that and also get certified. So, we decided to enter into a licensing agreement with Z-Wave.me and take advantage of the expertise/library for a custom-tailored solution specifically for UD/Polisy. So far, the library itself, their professionalism, and expertise have all met and exceeded all our expectations. This is why I feel confident divulging this information. With kind regards, Michel

I agree with you. There is. But, currently, low priority We abandoned our existing code. All this will start working + S2 + OTA with the new Z-Wave/Matter dongle. With kind regards, Michel

@kowaj, Please send your logs to support@universal-devices.com. With kind regards, Michel

Hi Dennis, with regret, we cannot track bugs based on customer names. Also, it's very difficult to go through all your tickets to figure out which ones were related to bugs especially the older ones. The one from 2 weeks ago was deemed low priority. With kind regards, Michel

It's never grayed out. So, you are welcome to click it as many times as you would like! With kind regards, Michel

@asbril, TPM = Trusted Platform Module At the highest level, it's a cryptographic chip that does not depend on anything else. In our case, it serves two purposes: 1. We can have it check the OS being run and make sure the OS (our version of FreeBSD) is signed/verified by UD 2. A root key is stored on the chip itself. The root key creates and manages a master application key that is used to create as many application keys as necessary for encrypting things (including the whole file system if need be). The only way the root key can be decrypted is via the chip. The only way the application keys can be decrypted are via the root key. So, all keys are themselves stored encrypted so the likelihood that someone can get access to the root key and application keys are exponentially reduced So, when you enable TPM, the following takes place in the RAM (so no residue on the disk): 1. A root key is created and stored in the TPM 2. A master application key is encrypted by the root key and stored in the TPM 3. Both of the above are zipped up in a package and encrypted by your password and a very secure encryption algorithm. This file is stored in the conf directory of your IoP. So, BACK IT UP NOW If you ever have to restore your IoP to another device, you WILL NEEED YOUR PASSWORD to decrypt #3 and recreate the keys in the new chipset. If you lose your password, you will have to start from scratch. With kind regards, Michel

@bpwwer, Currently, 1024 but on polisy, the sky is the limit. So, I wouldn't worry about number of nodes on polisy. I prefer nodes. With kind regards, Michel