Michel Kohanim

@larryllix, Just so that we can stave off confusion (I hope), although Polisy is based on PC Engines APU2, but it's not identical as we have our own BIOS chipset with TPM + additional interfaces. In short, ISY specific code will NOT run on PC Engines. @jfailenschmid, 12V @ max 2A (when you have peripherals). But, normally 12V @1A = 12W. Temperature range is commercial. @giesen, That's what we are leaning towards as well. With kind regards, Michel

@lilyoyo1, Thank you for the accurate reading of my responses. @Blackbird, The current Polisy models will, at the minimum, be as functional as your existing ISY. The only possible hardware you might need is a Z-Wave thing. At the moment, we are researching whether or not we should use something off the shelf (USB) or painfully make our own again. With kind regards, Michel

@Blackbird, 1. In all likelihood ELK will become a Poly with nodes. Your ELK module will of course have the same features as you already have with your ISY's ELK module 2. Nothing is future proof. This said, the AMD CPU is Quad Core 1GHz and I doubt there will be anything more powerful for our purposes especially given our OS and 4GB of RAM + 32 GB of SSD 3. If we decide to use an off the shelf Z-Wave dongle (we are investigating two), a) it will be 700 series and b) it will have discount prices for upgrade for existing Z-Wave owners With kind regards, Michel

@apostolakisl, No, it will not. But, obviously, we'll be spending more time supporting Polisy. With kind regards, Michel

In order to be fair to everyone (and due to over abundance of queries for the developer discount), we had to create a plan in order to vet developers. Also, this will allow us to link Poly reviews and pay out royalties in case the Polys are not free. With kind regards, Michel

All, Polisy will replace ISY994 but ISY994 will remain an active and supported product for a variety of business reasons. I cannot give you accurate ETAs. Suffice it to say that we have been working on the port for over a year now and it's continuing in a good pace. INSTEON, there's a DB9 jack on the back which will be used to communicate with INSTEON. Given our horrid history with Z-Wave boards (manufacturing, certification, FCC, obsolescence, etc.), we are considering vetting one (max of two) USB dongles that work reliably (700 series). We are researching. For those on the fence, my algorithm for the decision would have been: Do I use or plan to use Polyglot? If no, wait … again, ISY994 is NOT going away. If yes, then: do I mind losing the discount? If no, wait. If yes, buy now. For developers and geeks, with the 50% discount on top of the sale price, I really do not see any reason why you want to wait regardless. Polisy is what you have been waiting for. With kind regards, Michel

@stealle, Ring is supported in PGC but there are some bugs + we are adding flood lights and some other things. With kind regards, Michel

@fasttimes, Thanks so very much for the kind words. We had to think about this long and hard. If we become a software company that runs on any hardware then: 1. Our already complex system is going to be even more complex by forcing people to do installation 2. We will not be in charge of ensuring that the product - as a whole - is stable, secure, and reliable. And, thus won't be able to provide the same level of support 3. We will lose most (if not all) of our utility contracts 4. We will be another Indigo, HomeSeer, Home Assistant, Node Red, etc. So, we took the middle ground, an off-the-shelf hardware that is modified with our own BIOS and security chip for TPM. And, our own modified version of BSD with all the bloat taken out. And, our own package management system that houses only packages that we have tested and compiled ourselves and that we can support. We also thought about adding jails but decided against it. So, developers and geeks at heart are free to do whatever they want with the system. With kind regards, Michel

@Blackbird, Yes, for sure. With kind regards, Michel

@TexMike, No, you don't. At least not for now. With kind regards, Michel

@smokegrub, Most probably the remote ISY was rebooted and, since you cannot query battery operated devices, their states are blank. With kind regards, Michel

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

@FarmerGeek, It seems that you have DNS problems: https://wiki.universal-devices.com/index.php?title=Main_Page#DNS_Error With kind regards, Michel

@fasttimes, I do not know what ISY Component is. You asked whether or not you can expose ISY Portal to Home Assistant and the answer is an absolute and unqualified yes. i.e. if HASS already talks to ISY directly, it should be able to talk to ISY through the portal with minor modifications of the base url and credentials. With kind regards, Michel

@ctviggen1, You need to provide the missing records from 16291 to 16314. With kind regards, Michel

@ctviggen1, If you don't see Program in the column before last, then this device is being turned on/off AT THE DEVICE. i.e. System = response from the device, Program = ISY Program, Web = web client. I see neither program nor web. So, it's not ISY turning it on/off. Perhaps a ghost? With kind regards, Michel

@FarmerGeek, Admin Console | Tools | Error Log. With kind regards, Michel

@FarmerGeek, The best place to start is the error log. If you are still having trouble, please do not hesitate to submit a ticket. With kind regards, Michel

@lmhinman, Definitely related to the router not giving ISY an IP address. Are you certain that ISY is connected to the router either directly or indirectly? With kind regards, Michel

@fasttimes, Everything that is available from ISY directly is available through the portal (i.e. portal acts as a proxy to ISY). The only change is the base URL and the credentials. So, what you need is to go to Select Tools menu | ISY Information and then use that given URL as the base and use your ISY Portal credentials. With kind regards, Michel

@Goose66, Thank you! I think the best approach would be to have a scripting language extension for those who want to program. Perhaps in our next lives :). With kind regards, Michel

@Goose66, Thanks so very much for the detailed explanation. I think what you are looking for is a full featured programming/scripting language (such as JavaScript/Lua/pawn) and I am almost certain that, even though you might love it, we'll have to have all non-programmers having to take programming courses. Cases in point … take a look at our competitors. Also, it's pretty much an impossibility for Wait and Repeat not to finish. They both have a limit and, if the condition changes, then they will stop. Anyway, I just didn't want to let "shortcomings in ISY's programming model" to be left unanswered. Yes, perhaps shortcomings for a programmer. The same way that Java fixes the shortcomings of C++ (e.g. garbage collection) and C++ fixes the shortcomings of Java (e.g. no interpreter required) and on and on …. With kind regards, Michel

@Goose66, Thanks so very much for the details. With sincere apologies, I still don't get it. ISY supports the first 3 (as events) which are published in pub/sub fashion to clients. Now, within ISY, you have a choice: to do something with those events (condition on the event) or not. Apart from subscriptions, are you saying that there are other purposes for "events" without any conditions? If so, what? What do you want to do with those events? With kind regards, Michel

@Goose66, I still don't get it. What's an event and what's a condition? With kind regards, Michel

@TomNow2, By event driven I mean that programs are evaluated based on events. i.e. if there are NO events (changes in the properties of devices, smart meter, electricity pricing, climate conditions, etc.), then the programs will NOT be evaluated at all UNLESS they are schedule based. Some high level information: 1. Based on whether or not the incoming event makes the If true or false, Then or Else sections are executed respectively 2. You can use Repeat or Wait in Then/Else. But, note that both are interruptible. This means that if the condition changes to false based on another incoming event, then Wait/Repeat will terminate in the Then. And, if true, Wait/Repeat terminate in Else 3. If the status/property of a device does not change, an event is not generated so the programs depending on Status will only work based on change of state 4. Programs based on physical activity are handled by Control. This means that if a device is already on, and you go and physically turn it on again, then the program will be evaluated IF AND ONLY IF it's checking for Control In short, everything happening in ISY is based on generated and processed events. Of course, you can force programs to run/stop etc. but that's just the means for giving you more control over what should happen and/or reuse of certain constructs. With kind regards, Michel