Michel Kohanim

If you are experiencing "connection refused" for ssh, please click on the Upgrade Packages in the Admin Console. With kind regards, Michel

The only reason I am responding to this topic is to make sure this topic is stopped because it does nothing but create confusion. Beeps are there in lieu of a progress bar which we are working on. There's absolutely no way to describe all the different permutation of beeps that you may experience. For instance, if the upgrade process installs udx or isy, then those have their own set of beeps. So, for now, the best thing to do is to not upgrade unless you are sent an email to upgrade. Once we have the progress bar working, then you can upgrade as many times as @macjeff does (once every second). In any case, the issue of crash and corrupted user database has been fixed. If and only if you are experiencing this issue, please click on the upgrade button. With kind regards, Michel

@JBanaszak, this is very very strange. Have you tried clicking on the Upgrade Packages button in the Admin Console? With kind regards, Michel

@JTsao, What do you mean by "sometimes the button presses get backed up"? With kind regards, Michel

That would be a great idea! A better idea would be to let us transform Nokia hubs to PLMs With kind regards, Michel

@hart2hart, thank you so very much for asking. Unfortunately not at the moment. With kind regards, Michel

Hello all, The issue is that we migrated all ssh pkg commands to the Admin Console to ensure the correct sequence of things are done. For instance, migrating from 12 to 13 required all those scripts (10% failed). Upgrade from 13 to 13.1 has a bug that corrupts the password file. By using the button in the Admin Console, the system will figure out which scripts should be run to avoid all these problems. The biggest issue was that, except a mention in release notes, I didn't advertise this fact. Given the millions of times we asked everyone to use pkg update/upgrade, OS version 13 was moved to 13.1 and thus corrupted the password file. The fix is rather simple using what was described by @mwester. Sincere apologies for the inconvenience. With kind regards, Michel

@Techman, Still waiting to hear back. No news ... With kind regards, Michel

Past tense for us. I am not sure about INSTEON tech. It was part of the sale in such a way that the buyer is responsible to pay all the past dues/storage fees/etc. to the storage company and/or somehow come to an agreement. With kind regards, Michel

In storage. But it would be impossible to sell them without another contract with Nokia (we did have a call with them). With kind regards, Michel

@dcard, yes, we have been thinking about the same and currently working on two fronts: 1. Internal Z-Wave/Zigbee board for Polisy 2. For new customers, considering Polisy-mini which has a smaller form factor + mounting brackets. Z-Wave/Zigbee will be external dongles, this way, we can address not only the size but also improve the range With kind regards, Michel

Sincere apologies to all. We tried very hard to get Ring to officially provide us with the APIs. But, they want a business plan etc. to approve us. We are working on it. With kind regards, Michel

@jec6613, yes, we should have the first samples in 10 days. We shall keep you all posted. With kind regards, Michel

@4wireE&M, I responded to your ticket. Are you still having this issue? With kind regards, Michel

@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