Michel Kohanim

Hi All, Apologies. The email also had a link back to the news on our website. So, if you hover over the link, you can see our website. In short, yes, we were hacked and the hacker wanted $1500 in bitcoin! With kind regards, Michel

@hart2hart, If new, you don't need to format. With kind regards, Michel

@MrBill, The NLS files are put in place by the upgrade and not the format. With kind regards, Michel

@MrBill, The LIB Error 403 is because the NLS files have not been installed. It has nothing to do with the format. With regard to the logs, ISY does not log continuously. It stores as much as possible into the memory before flushing it. The size of the log matters (as @Teken suggested, you can change this value through the shell). Furthermore, ISY rotates the logs based on the size you choose. So, you will have error.A, B, and C files before they are rewritten. If you have too much traffic/logging, it's best to use larger log sizes. With kind regards, Michel

@Teken, 1. As mentioned, existing INSTEON is either native or node server with preference for the latter. Migration might not be included 2. Network resources should work with the exception of binary payload (at least initially). Preference is to get rid of these modules and make everything a node server. Perhaps a generic node server for sending packets 3. ELK is already a node server 4. Climate is already there as node server with many more options 5. Z-Wave will be a dongle Again, please do not hold us responsible for new INSTEON devices. At the moment, and without further information from SmartHome/INSTEON, we have no plans of supporting them natively. If we go the node server route, perhaps the developer him/herself might. But, then again, the rumors and indications point to the world where third party integration is not something being offered by SmartHome/INSTEON. Am I missing anything? With kind regards, Michel

@Teken Exaggerate a little? 1. Support is different than migration 2. Please read everything above again (twice more) With kind regards, Michel

@Whitehambone, Precisely! And, the ever increasing rumors (form multiple sources) of no longer supporting third party integration + complete lack of APIs/Specs, are just making it very difficult for us to embark on any new INSTEON endeavors. With kind regards, Michel

@bpwwer, Absolutely! With kind regards, Michel

Hello everyone, We'll be updating the certificates on ISY Portal at 5AM PST on 03/14/2021. You may experience a couple of minutes of disruption. Thank you. With kind regards, Michel

@hart2hart, As I mentioned before, we'll do our utmost to support our existing customers with existing devices (as we always have). This said, there are things that are out of our hands. I cannot guarantee that we can pull a miracle when you need to replace your dead switch (or PLM) with a new switch (or something) for which we have absolutely no specs, no APIs, no contacts, etc. We are not going to back to those painful days of hacking, reverse engineering, and putting all our efforts in getting things to work for INSTEON/SmartHome. It's just not a sustainable business model. With kind regards, Michel

@MrBill, At the end of the day, it would be difficult to continue supporting something for which there's no demand outside of our existing customers (<5% of our sales) and no APIs/specs. So, of course we will do our utmost to make sure our existing customers are taken care of with existing specs/devices. The rest is pretty much up to SmartHome/INSTEON. If 13 years of history is any indication, I wouldn't put much hope on things changing. With kind regards, Michel

@Jimbo, Why would it matter if the functionality is the same? With kind regards, Michel

@MrBill, Has nothing to do with the PLM or hardware interface. It has to do with specs, APIs, and support of which we have none. As mentioned before, at the moment, this is not a choice for us since there's no information available to use to be able to size the effort of supporting new INSTEON devices. With regard to existing devices, we are debating native support (port from ISY) or a node server. Most probably the latter. @garybixler, Supporting network resources is not a problem and can be added depending on the number of users who request it. At the moment, everything works with network resources except for binary. Migrating binary resources to Polisy is non-trivial. With kind regards, Michel

@lilyoyo1, thank you very much! @carealtor, it's really not a choice as we have not been given one. There are no APIs, no specs, no information. The extent of our knowledge of anything INSTEON starts and ends with what we read on this forum. With kind regards, Michel

@lilyoyo1, Thank you very much for the feedback. At the moment - and since we are still 100000% in the dark - the thought of having to relive even 0.00001% of all the reverse engineering, all the blames, and all the support calls we had to endure gives me the hibby jibbies. Let's all hope that INSTEON will shine a light at the end of this very dark tunnel. With kind regards, Michel

@Blackbird, It's really not a can. ISY is currently running on Polisy extremely well and very fast! As a matter of fact, as of right now, you can do pretty much whatever you did with ISY (to speed development, unfortunately, it's still through the Admin Console) such as programs, node servers, and even portal connectivity. What's not there: 1. Z-Wave: figuring out which dongle to use (ours or off the shelf) + need certification 2. INSTEON: we are debating whether or not we want to support it at all 3. Modules: -- ELK is migrated to a node server @Jimbo -- Network module is no longer supported -- All climate modules are already supported as node servers What we are working now: 1. Stress testing 2. UDX service to advertise as polisy.local (so that you don't have to look for IP) 3. Secure and encrypted storage of certificates and sensitive info using TPM 4. Tighter integration with Polyglot We should have the alpha package in a month or so. If you are interested to test, please do make sure you are subscribed to our Product News and Announcements. With kind regards, Michel

@LFMc, Thanks so very much. Looking into it. With kind regards, Michel

Hi Steve, You should not do any port forwarding as it causes interference with everything else. What you need to look at is your error log to see why ISY cannot connect to ISY Portal. With kind regards, Michel

@n4bos, https://wiki.universal-devices.com/index.php?title=Main_Page#Changed_ISP.2FRouter_-_Can_no_longer_access_ISY With kind regards, Michel

@LFMc, Thanks so much for the update. I am very interested. With kind regards, Michel

@kclenden, 100% correct. Thank you. ISY is looking for: 0x00 0x1C :: 2342-242 Insteon Mini Remote - Switch (915 MHz) With kind regards, Michel

@docrix, Not really sure what you are seeking. What you need to do is to use the Launcher. The instructions for clearing everything else is also included in the link. With kind regards, Michel

Hi @asbril, Sure, please send me your error log. I don't think the fix had anything to do with reinstallation. I think you are reaching the limits of how many events ISY can handle at the same time (255 per queue at any given point in time and about 10 per second). So, if you have a lot of queries or if you have node servers with a very low short polling interval and if you have many programs that depend on these events, then for certain your queues are going to get full. With kind regards, Michel

@vbphil, You can safely ignore this ... most probably you have firewall software blocking UDP packets to the UPnP port. Since ISY no longer depends on UPnP for finding ISY, you can safely ignore this error. With kind regards, Michel

@thruster999, Cannot really debug with generic information such as above. If you have this issue, please send your UUID + the approximate time of the event so that we can take a look at the logs. With kind regards, Michel