Michel Kohanim

@fmk2, You need to remove them from ISY: Admin Console | Node Servers | Configure| Hubitat ... Delete. With kind regards, Michel

Hello everyone, First of all, I am so very honored and, frankly, this is the greatest career achievement I could have ever imagined for anyone let alone for myself. So, THANK YOU. From my perspective, things that are worth it: 1. Hub customers ... but I think 100K is exaggerated 2. PLM 3. INSTEON IP if and only if it's relatively inexpensive. The reason is that, for the technology to be viable, a) it has to be secure and b) it has to be extensible (not just for switches/sensors and simple thing for which the market is way too saturated). So, the tech will need to be extended since the current 24 bytes are not sufficient for any type of security or extensibility. If the tech can support longer packet sizes (even if fragmented), then the sky is the limit since we can have node servers on devices, and thus the same protocol can be used for pretty much anything in the world. Therefore, an opportunity to license it to everyone and for anything We are still going through all the numbers and their documentation. I will keep you all posted. Thanks again so much for your vote of confidence. With kind regards, Michel

Working on it. With kind regards, Michel

Thank you @lilyoyo1. We have also contacted the original PLM manufacturer and trying to see whether or not he has some stock. If interested, please create an account or login to an existing one, uncheck everything except for Product News & Announcements, and once we have confirmation, we'll notify you. With kind regards, Michel

@Techman, yes ... With kind regards, Michel

@mmb, Hub does not have bidirectional communications through TCP. So, it will require major development to get it to work. In the meantime, one of our very good friends provided us with the contact info for INSTEON manufacturing in China. They might still have some PLMs so we'll try to get as many as we can (and pray that they won't die). We shall keep you posted. With kind regards, Michel

@lilyoyo1, thank you. So, you still have the delays even with 2413S? With kind regards, Michel

Thank you all for your feedback. We are trying to reproduce ... @arshishk, did the event viewer show DON or did you get DON after 20 seconds? @vbphil, are these variables incremented based on INSTEON events Do all of you have 2413U? With kind regards, Michel

@arshishk, What exactly is Family Flood.1? @lilyoyo1, Please post programs that are intermittently slow. For those with these issues, there has been a major change but only for network resources: now, network resources and node servers are not queued. This means that if you have programs sending network commands, and with default connect time out of 10 seconds, there might be delays. Thus my question about Flood.1. With kind regards, Michel

@rskirch, Please try: https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_is_very_slow_or_hangs With kind regards, Michel

What I know is that they were going to sell but it didn't go through, so they just decided to shut down. With regard to PLM and devices, the outlook is grim. If they would offer me their PLM code/chip in return for $ per unit, I might consider (all we need is the chip since we already designed it once before they shut us down). I will not entertain up front $. The only goal would be to support existing customers. With kind regards, Michel

No more speculations ... they are gone! It's 100% official and it has been for a couple of weeks now. With kind regards, Michel

@DaveStLou, Thank you. Please ask them whether or not you can have 3rd party HAN devices connect to the meter. With kind regards, Michel

Hi @DaveStLou, OpenADR and Smart Meters are two different things. Smart Meter allows you to have real time access to the whole house energy usage/production (in case of solar). Smart Meters use Zigbee for communications. OpenADR, on the other hand, is an Internet based communication protocol that allow utilities to communicate with behind-the-meter devices and give them signals such as real time prices, load on the grid, etc. usually used for Demand Response. So, what exactly are they offering? With kind regards, Michel

Hello All, This is the support topic for IoP 5.4.3: With kind regards, Michel

Hello all, We are very happy to introduce IoP v5.4.3 which is mostly a bug fix release. 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: Missing names for uom 145 & 146 (for system editors) Fixed seconds/minutes from start of day (for assigning system values in program variables) Fixed last updated time for variables when they are updated using a program Fixed current date/time as shown in the Admin Console Cannot set or query using Z-Wave configuration parameters popup Enhancements: Added rename node as a REST API for node servers Increase max node servers from 25 to 100 Important Note: UEFI upgrade is no longer forced because of variability of the outcome. If the 2nd or 3rd (or both) LED 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

@mbking, Yes! With kind regards, Michel

The goal is to shut down PG2. It's using too much resources on Polisy: storage: mongo: 870M polyglot: 330M 1.1GB is more than 1/4 of the total memory available on polisy. CPU: With no load: mongo, always the most CPU consuming process using an average of 1% (doing nothing) and Polyglot is always second at 0.2% (doing nothing). On the other hand, pg3 is not even in the top 20 processes or memory users. So, PG2 and mongo must go ... at this juncture, we have contact all PG2 developers and almost 3/4s have been ported. If we cannot contact the respective developers, we'll probably port PG2 node servers ourselves. With kind regards, Michel

@tlightne, Here you go: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Migrating_from_994_to_Polisy With kind regards, Michel

@teuhl, We had call with Ring last week: They have streamlined access to Ring APIs and, at the moment, they don't want to approve access. We need to provide them with detailed prospects etc. and make a business case. At the moment, just a little too much for us to handle. With kind regards, Michel

@xgfreon, Unfortunately, you cannot till such time that IoP is integrated with PG3. The reason is that we have so many different ports (PG2, PG3, MQTT for PG2, MQTT for PG3, etc.). And, we had too many support calls due to port conflicts. With kind regards, Michel

@oskrypuch, yes, of course. All you need to do is to point to your ISY. This said, why not migrate to IoP? With kind regards, Michel

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

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